MSP client collections: the complete guide to recovering unpaid invoices without suspending service

The MSP collections problem is a structural mismatch. You deliver value continuously (managed infrastructure, 24/7 monitoring, emergency response at 2am), but the leverage you have when a client stops paying is binary and explosive: suspend service. Pull the kill switch and the client either pays fast or you’ve just publicly broken the relationship and probably the client’s business too. There’s no middle ground built into the typical MSP toolset.

This guide is the middle ground. It’s a working playbook for MSPs collecting on late retainers and one-off invoices without using suspension as the lever. It assumes you’re a 1-50 employee MSP or MSSP. You bill monthly recurring (MRR) plus project work. You have at least one client who’s gone past 60 days on their retainer in the past 12 months. You don’t want to fire them, but you can’t carry them indefinitely. If you want the general, non-MSP version of this playbook, the small business AR recovery guide covers the same ground for owner-operators outside the channel.

We built ti3 (disclosure: ti3.co) for exactly this problem. The patterns below come from working with MSPs across both Captira’s two decades of customer software work and the recent product-specific learnings since ti3 launched. None of it requires you to pay us anything to use; the guide is the system.

Why the suspension trap matters

When a retainer goes 30, 45, 60 days past due, the instinct for most MSP owners is to threaten suspension. “If payment isn’t received by Friday, all managed services will be paused.” Sometimes this works. Frequently it doesn’t, and when it doesn’t it’s catastrophic.

Three reasons:

First, suspension makes the MSP look unreliable to other clients. Industry whispers travel fast, and in a regional MSP market the buyer pool is small enough that they arrive. Other buyers hear “X cut off Y over $4,000” and start hedging their own renewal decisions. We have no survey to put a number on this and we are not going to invent one, but the mechanism is not controversial: referral is the dominant acquisition channel in managed services, and a cautionary story travels the same network a referral does.

Second, suspension creates a real legal problem if you have an SLA. Most managed-services contracts include uptime or response-time commitments. The instant you suspend, you may be in breach of the SLA you signed even if they’re in breach of payment. Now you’re trading a collections fight for a counter-claim, and the counter-claim is documented (the SLA terms) while the payment problem may not be (especially if your contract is loose).

Third, suspension permanently breaks the relationship. You will not be doing renewal work with a client you’ve suspended. The math works out terribly.

Those are not benchmarks and we are not presenting them as research. They are arithmetic on this guide’s own stated assumptions, shown so you can substitute your real average retainer and your real average tenure. Do that before the next time you are tempted. The point survives almost any inputs you plug in: one month’s invoice is a small fraction of a managed-services relationship, and suspension puts the whole relationship on the table to collect the fraction.

The right move isn’t suspension. It’s a structured recovery sequence that escalates pressure without ever triggering the suspension nuclear option.

The MSP collections sequence

Here’s what works, by day count, for a typical $3,000-$8,000 monthly retainer that’s gone past due.

Day 1 past due: the soft nudge

Standard friendly reminder, sent automatically by your billing tool (ConnectBooster, FlexPoint, BluLogix, manual via QuickBooks, doesn’t matter). Reference the invoice number, the due date, the payment link. No pressure. Most retainers paid late are simply a missed automatic-pay or a card update on the client’s end.

If you have automated retry on file (ConnectBooster, Stripe Billing, etc.), let it run for 3-5 days before any human touch. A meaningful share of late retainers clear here without anyone doing anything, because the underlying cause is an expired card or a failed ACH rather than a decision. We don’t publish a percentage for this because we haven’t measured one across enough MSP books to stand behind it, and the figures circulating for “dunning recovery rate” are vendor marketing about consumer subscriptions, not MSP retainers.

Day 7 past due: forced-choice email from the owner

If the soft nudge didn’t resolve it, send a personal email from the MSP owner (not the bookkeeper, not a billing alias) to the client’s primary contact. Forced choice:

“Hi [name], our April retainer invoice is now 7 days past due. By Friday I need to confirm one of three things: (1) the payment is processing on your end, (2) there’s a specific issue with the invoice I can fix, or (3) we should set up a different payment arrangement this month. Let me know which.”

The forced choice works because it makes silence cost more than responding. Three named options are harder to ignore than an open-ended “please advise,” and one of the three is an admission you can actually act on.

What it explicitly does NOT do:

• Threaten suspension
• Use guilt or shame language (“We’ve been so patient…”)
• Send to a generic billing email; goes to a named human

Day 14: the settlement option

Still nothing. The client has now actively decided to deprioritize. Time to introduce structure.

“Hi [name], following up on the April retainer. If cash flow is the issue this month, I can offer two options: (a) split the April invoice into two payments, one this week and one mid-May, or (b) take 10% off the April invoice for payment received by Friday. Either works on my side. Let me know which you’d prefer.”

Settlement discounts (5-15% off for immediate payment) feel like leaving money on the table. They aren’t.

Day 21-30: Final Demand Notice

If the settlement offer didn’t move it, the client has crossed into “decision not to pay” territory. Time for a formal Final Demand Notice. This is different from another reminder email.

Three things make a Final Demand Notice work for MSPs:

1. It’s framed as a formal business document, not an email. Letterhead. Business address. Certified language. Either send via certified mail (USPS) or via a service like DocuSign that captures delivery proof. The certified-mail step matters because it preserves the option to escalate to court later.

2. It states what happens after the deadline. Not “we’ll suspend service” (don’t do that), but “After 10 business days, this account will be escalated to a structured first-party recovery process administered on our behalf.” The phrasing is intentional: you’re not suspending, you’re escalating the collection process. The client understands the difference.

3. It documents the prior good-faith attempts. “We’ve sent reminders on [dates] and received no response.” This matters if you ever go to small claims court; the judge wants to see the paper trail.

We don’t publish a hit rate for this stage, because we haven’t measured one across enough accounts to stand behind, and the demand-letter response rates you’ll find quoted around the collections industry trace back to nobody. What the Final Demand reliably does is force a decision. The client either pays, or surfaces the real issue, which for MSPs is very often a service grievance nobody escalated. If it’s the second, you’ve learned something the reminder emails were never going to tell you.

Day 35: structured recovery sequence in your MSP’s name

If the Final Demand didn’t shake it loose, you’re now at the decision point. The wrong move here is to either (a) suspend, or (b) hand to a collection agency. Both nuke the relationship.

The right move is a structured 5-week recovery sequence that runs in your name. Same letterhead, same sender, same business address. The escalation language gets progressively firmer (week 2 is a settlement-options reminder, week 3 is a payment-plan offer, week 4 is a notice of intent to escalate, week 5 is the actual escalation decision). At every stage, the client only sees your MSP’s name on the communications.

This is what ti3 does for MSPs. We’re not a collection agency, we don’t take a percentage, and we never touch the money: payment moves directly from your client to your merchant account, so you keep all of what comes back. The client never sees a third party unless you choose to escalate to one after the sequence completes. Learn how it works, or read what first-party collections actually means if the distinction is new to you.

What the sequence buys you is not a guaranteed hit rate, it’s that the escalation keeps happening on a schedule after you’ve stopped having the energy to drive it, and it happens without the suspension switch ever entering the conversation.

Day 60+: the real escalation decision

If even structured recovery didn’t work after 5 weeks, the client has made a hard “won’t pay” decision. Now you have three options:

Option A: small claims court. For amounts under your state’s small claims cap ($5,000-$15,000 depending on state), you can sue without a lawyer. Filing fees $30-$150. Worth it for amounts above $2,000 where you have a clean paper trail and the client has assets. The Final Demand Notice from day 21 becomes critical evidence here.

Option B: third-party collection agency. Hand the account to a commercially specialised agency. Most are consumer-debt shops, so confirm they actually do B2B. Contingency typically runs 25% to 50% of what they recover. Be careful with the recovery rates agencies publish: the credible ones are aggregates across a whole book of placements, and an agency inherits the same aging curve you do. An account placed at nine months is worth well under half what it was worth at three, before anyone’s fee comes off. Run the contingency against realistic recovery at the age you’re actually placing, not against face value. Bad trade for the relationship, sometimes a necessary trade for the cash. What collection agencies charge has the ranges by balance and age.

Option C: write off. Sometimes the right call. If you’re on accrual accounting and you already booked the retainer as income, a bad-debt deduction is available under IRS Topic 453. Cash-basis MSPs generally can’t deduct it, because the income was never recognised in the first place, so there’s nothing to reverse. Ask your accountant which you are; we build software and this isn’t tax advice. How to write off bad debt covers the bookkeeping side. Better to take the loss and stop spending attention on it than to grind for six more months on a 28-cent account.

What you should NOT do at this point: suspend service to leverage payment. By the time you’re at 60+ days post-Final Demand, suspension won’t work. The client has either gone out of business, found another MSP, or simply decided they don’t care if you cut them off. Suspension at this stage just makes you look bad to anyone watching.

The contract clauses that make collections easier

The collections problem starts at contract signing, not at day 30 past due. Two clauses MSPs should always have:

A defined late-payment trigger and consequence. “Invoices unpaid after 30 days are subject to a 1.5% per month late fee. Invoices unpaid after 60 days will be referred to a structured first-party recovery process.” Spell it out in the master service agreement. When you escalate, you’re enforcing the contract, not improvising. On the fee itself: no US state caps a late fee on a B2B trade invoice the way usury statutes cap loan interest. The real limit is the liquidated-damages test, meaning the fee has to be a defensible estimate of what late payment costs you rather than a punishment, which is why 1% to 1.5% a month is the working range and 5% a month is the kind of number a judge strikes. Arkansas is the one genuine statutory ceiling. How to charge a late fee legally by state has the detail, and the MSP late-payment policy template has clause language you can lift.

An automatic-pay requirement on retainers. Card or ACH on file, auto-charged on the same day each month. This removes an entire category of lateness, the kind that was never a decision at all: the expired card, the changed bank, the AP clerk who left. Those are the cheapest collections problems to solve because they solve themselves, and the only reason they become 45-day problems is that nobody set up the rail. Yes, some clients will push back; the ones that push back hardest are usually the ones who would have been the late-payment problem anyway. Filter them at signing.

If your existing contracts don’t have these, add them at the next renewal cycle. Don’t try to amend mid-contract; it creates friction. New clients sign the new template, existing clients get migrated at renewal.

The “we’re already past 60 days” emergency playbook

If you’re reading this because you have a $5,000+ retainer that’s already 60-90 days past due and you’re considering suspension, stop. Do these four things in order:

1. Today: send the Final Demand Notice. Write your own, or use ours at 99¢ a notice. Send via certified mail. 10-business-day deadline.
2. Day 11: if no response, start the structured recovery sequence. If you’re not using software, the past-due invoice email templates cover the language for each week. If you’re using ti3, run the analysis to confirm the account is recoverable and start the sequence.
3. Day 45 from Final Demand: assess. If they’ve paid, great. If they’ve engaged but are slow, settlement options. If they’ve gone fully silent, the relationship is over; pick small claims or write-off based on amount.
4. Never suspend, never use suspension as the threat. If they’ve decided not to pay, suspension won’t change that. If they’re slow but engaged, suspension destroys what’s left of the relationship for nothing.

Frequently asked questions

Can I include collection costs in the amount I demand?

In B2B contracts where the contract specifies the client is responsible for collection costs (a “fees-shifting” clause), yes. Without that clause, no; the client owes the invoice amount plus any contracted late fees, but not your collection expenses. Add the fees-shifting clause to your MSA.

What if the late-paying client is also our biggest client?

Tighter playbook, same structure. Run the sequence faster (skip the 5-day soft retry, go straight to forced-choice on day 5). The owner-to-owner email matters more here. Don’t avoid the conversation; the longer you carry the receivable, the more leverage they have and the worse the eventual write-off.

Can we sell our unpaid B2B invoices to a factor?

Yes, but only at a steep discount, and the discount is driven by your client’s creditworthiness rather than yours. The important thing to understand is what factoring is for. It advances cash against invoices that are expected to be paid. Once an invoice is genuinely past due and contested, most factors either won’t touch it or will price it as distressed paper, and some facilities are recourse, meaning the invoice comes back to you unpaid and you repay the advance. Factoring is a cash-flow tool, not a recovery strategy. Use it before invoices go bad, not after. Get a written quote on your actual book rather than planning around a published rate.

Do collection agencies work for MSPs specifically?

Most collection agencies are consumer-debt specialists. For B2B MSP collections, you want an agency that explicitly does commercial / B2B work. ACA International’s directory lists agencies by specialty. Expect 25-50% contingency, expect them to focus on amounts over $5,000, expect their tactics to be aggressive in ways that may not match your brand. This is why structured first-party recovery (software-based) usually beats agency for MSPs.

What about insurance?

Trade credit insurance (Atradius, Coface, Allianz Trade, formerly Euler Hermes) covers B2B receivables against client insolvency and protracted default. Premiums are quoted as a fraction of a percent of insured turnover, but the quote depends on your client mix, your concentration and your own credit-control process, so the only number worth planning around is the one on a quote for your book. Worth exploring if you have concentration risk, meaning one client above roughly 20% of revenue, or you sell into sectors with elevated insolvency rates. It is not a substitute for a collection sequence. It covers the catastrophic-loss scenario, not the slow-pay one, and most policies require you to have followed a documented credit-control procedure before they’ll pay a claim.

The client says the invoice is wrong. Do we pause the sequence?

No, and this is the single most common way MSP recovery stalls. Answer the dispute in parallel, in writing, with whatever evidence settles it: the ticket log, the signed change order, the SLA clause, the timestamps from your RMM. The reminder schedule keeps running while you do. The only thing that should pause it is you looking at the dispute and concluding the client is right, in which case you credit the line and reissue. Pausing on the assertion alone teaches every client that “I have a question about this invoice” is an unlimited extension, and in managed services a vague grievance about response times is the easiest possible thing to assert. Log the dispute, answer it, keep the clock running.

They’re 60 days behind and we’re still paying Microsoft for their seats every month. What do we do about the pass-through?

This is the MSP-specific version of the problem and it’s worse than a plain unpaid invoice, because the hole gets deeper on a schedule you don’t control. Separate the two decisions. The recovery sequence on the outstanding balance runs as described above, unchanged. The licence exposure is a forward-looking commercial decision: you can decline to add seats, decline to renew annual commitments coming up for term, or move the client to a model where they hold their own CSP tenancy and pay the vendor directly. All of those are contract decisions you make with notice, in writing, at a natural boundary. None of them is suspending the service you’ve already agreed to deliver this month. Notice the difference: not renewing on terms that are losing you money is ordinary business, and cutting off a live client to force payment is the trap this whole guide is about.

Should we report a non-paying client to a commercial credit bureau?

Probably not as a lever on one account, because it doesn’t work that way. D&B, Experian Business and Equifax Business take trade payment data through furnisher programs, which means you enrol and report your whole ledger on a schedule. It is infrastructure you set up in advance, not a button you press on a client who annoyed you. Note also that commercial credit files sit largely outside the Fair Credit Reporting Act, which governs consumer reports (15 U.S.C. § 1681a(d)), so the accuracy and dispute-investigation duties you might assume apply generally don’t. What binds you is your furnisher agreement plus ordinary defamation and unfair-practices exposure. Reporting something inaccurate is your problem, not the bureau’s.

Our MSA auto-renews and they’re behind. Can we just decline to renew?

Usually yes, and it is a cleaner instrument than suspension because it operates at a contract boundary rather than in breach of one. Check your own notice period, which is commonly 30, 60 or 90 days before the term date, and send the non-renewal notice in writing inside that window. Two things to be careful of. First, non-renewal does not collect the outstanding balance; keep the recovery sequence running on what’s already owed, because your leverage drops the day you’re no longer their MSP. Second, plan the offboarding as if you’ll be doing it, including credential handover and data export, because a disorderly exit is how a collections dispute turns into a negligence claim. What to do when an MSP client ghosts you covers the silent-client version of this.

Where to start today

If you have any MSP retainer over 30 days past due right now: send the forced-choice email today. Don’t wait for the next billing cycle. Across the CCAA benchmark’s first year past due, collectability declines by roughly five points a month. That is a smaller number than the collections industry likes to quote, and it is more dangerous for exactly that reason. No single month looks bad enough to interrupt your week over, which is how a $4,000 retainer quietly becomes a 28-cent account without anyone deciding to let it.

If you have one over 60 days: skip ahead and send a Final Demand Notice today. Write your own or use ours. Certified mail.

If you have multiple over 60 days: that’s a system problem, not a per-account problem. Run them all through ti3’s free recovery analysis to see which are recoverable and which are write-off candidates. The analysis is free and tells you, per account, the likely recovery position and the recommended next step. Running the actual sequence is a paid plan; the analysis is not.

The hardest part of MSP collections isn’t the law, the tactics, or the wording. It’s resisting the suspension instinct when an invoice gets old. Every MSP we work with has the same realization eventually: structured recovery without suspension recovers more money AND preserves more relationships AND ends fewer client tenures. The suspension lever feels powerful but it costs more than it pays back. Lock the lever in the off position and run the sequence.

Sources

• Commercial Collection Agency Association of the Commercial Law League of America, collectability by age of account
• IRS Topic 453 (bad debt deduction, creditor side)
• IRS Topic 431 (canceled debt, debtor side, the 1099-C question)
• 15 U.S.C. § 1681a(d) (FCRA: definition of a consumer report)
• Ark. Const. amend. 89, § 3 (17% per year maximum lawful rate)
• ACA International (trade body for the collections industry; agency contingency ranges)

Where we stand: ti3 is our product, so read the structured-recovery section with that in mind. We build first-party recovery software. We are not a collection agency, we don’t practice law or accounting, and nothing here is legal or tax advice. Where an account genuinely needs a lawyer, an accountant or an agency, we’ve said so above.