An MSP client stops responding to your invoices. Emails bounce off. The account manager reaches out. Nothing. The invoice is 45 days past due and the office manager is asking where the money went.
This is the signature MSP collections problem. Ghosting isn’t always refusal. It’s often disorganization, a procurement holdout, or the decision-maker being unreachable. But ghosting kills your cash flow the same way refusal does.
The sequence below is built for ghosted MSP invoices. It works because it treats ghosting as a communication problem, not a character problem, right up until the moment you need to treat it as both.
Days 1-7: the obvious channel
Day 1: Invoice lands in the client’s mailbox (or ticketing system, depending on your billing setup). Standard invoice, clear payment terms, clear due date.
Day 7: First touch is the invoice number only. One-line subject, two-sentence body. Don’t assume they saw the original.
Subject: Invoice #5432 - just checking Hi [contact], Following up on invoice #5432 ($2,800 for December retainer), due [date]. If it's already queued for payment, you can ignore this. If you haven't seen it yet, here's the payment link: [link]. Thanks, [Your name]
Why this works at day 7: most of your ghosting comes from administrative delay, not refusal. Reachable clients reply or pay immediately. Non-responsive clients tell you that communication is the bottleneck.
Days 14-21: escalate the path, not the tone
At day 14, the client has had the invoice for two weeks and hasn’t replied to the day-7 reminder. Something is wrong. The route might be broken or the decision-maker unavailable.
On day 14, email the same contact but cc their manager or another stakeholder you have a relationship with. Don’t change the tone. Just change the audience.
Subject: Invoice #5432 - payment routing check needed Hi [contact], Invoice #5432 ($2,800) is now two weeks overdue. I haven't heard back on my last two reminders, so I'm wondering if payment got held up in your approval process or if the invoice got misfiled. [Cc'd stakeholder], I'm copying you to help [contact] get this unstuck. Can one of you confirm by [day] whether this is a timing thing or something that needs fixing on our side? Payment link: [link] Thanks, [Your name]
Cc’ing works because it:
- Signals you’re patient, not aggressive (you’re still fixing, not threatening).
- Forces a response from someone. If [contact] is ghosting, the cc’d person often jumps in to solve it.
- Documents the sequence. You’ve now asked nicely through two channels.
Days 30-45: the settlement
By day 30, you’ve sent three reminders (day 1, 7, 14) and hit the escalation cc. The invoice is still unpaid. Two things are now true: payment is either genuinely blocked (procurement issue, budget hold, change of decision-maker) or the client has decided not to pay.
Offer a settlement discount tied to a fast response window.
Subject: Invoice #5432 settlement offer - expires Friday Hi [contact] and [cc'd stakeholder], Invoice #5432 ($2,800) is now 30 days past due. I want to get this closed before it becomes a bigger problem. Here's what I'm offering: if you can pay $2,100 (25% off) by Friday EOD, we're done. No more reminders, no escalation, just settled. If full payment is what you want to do instead, here's the link: [standard payment link] If neither of those work, reply and tell me what does work. But I need confirmation by Friday so I can document where this stands. Settlement link (25% off): [discounted payment link] Thanks, [Your name]
The settlement offer is the last gesture that treats this as a relationship worth saving. If it doesn’t land by Friday, the client has decided not to engage. The next step is formal recovery.
Days 45-60: formal recovery
At day 45 with no settlement, the client has been unresponsive for six weeks. Send one final notice, in writing, that names a specific action if payment doesn’t land.
This email should be from you directly (not the account manager), and it should reference everything you’ve tried.
Subject: Invoice #5432 final notice - required by [specific date] Hi [contact], Invoice #5432 ($2,800) is now 45 days past due. Over the past month, I've sent four reminders and offered a settlement discount. I haven't received a response. I need payment by [specific date, 10 business days out]. If payment doesn't arrive by that date, I'll be moving this to our collections process, which may affect: 1. Your account's payment status with us. 2. Future service engagement. I'd still rather work this out directly. If there's a reason the invoice hasn't been paid, reply and tell me. But I need to document that I gave you a reasonable window. Payment link: [link] [Your name] Founder/Manager [Company] [Direct phone]
This email is not aggressive. It’s professional documentation. It names a consequence, but the consequence is operational (payment status) not legal. That matters for the client relationship.
After day 60: you move to escalation
At day 60 with no response, the ghosting client has now demonstrated that they’re either unable to reach a decision-maker or have chosen not to engage. Email alone is no longer the right tool.
At this point you have three realistic options:
1. Accept the loss. If the invoice is under $3,000 and the client relationship is immaterial, write it off. The cost of recovery (time, process, tools) exceeds what you’ll collect. Document the write-off.
2. Move to structured recovery. Use a platform like ti3 to send a formal demand sequence in your name, without hiring a debt collector. A structured sequence (formal letters, demand notices) often succeeds where email reminders failed because the letter format signals seriousness in a way email doesn’t.
3. Refer to a recovery specialist. If the invoice is large ($5,000+) and the client has clear ability to pay (they’re still operating their business, still paying other vendors), refer to a collections specialist. This is a second-party collections option. The specialist works on your behalf, in your name, to chase the payment.
The MSP-specific guardrail
Throughout this sequence, you never suspend service, pause access, or cut off support as a recovery lever. That’s the core MSP-collections principle: you can chase payment and escalate, but you don’t weaponize the service to force it.
Here’s why: suspending service (even as a pressure tactic) risks turning a cash-flow problem into a client-relations disaster. The client’s customers lose access. The client loses revenue. Your relationship goes from “stubborn about paying” to “actively harming my business.” You’ve moved from creditor to threat.
Instead, escalate through communication (cc’ing, formal notice, structured recovery) and let the client decide whether the relationship is worth saving. Some clients, faced with a formal demand from an outside service, pay immediately. Others decide the relationship isn’t worth keeping. Both outcomes are fine. You get paid or you end a bad relationship. Either way, you move on.
FAQ
Q: What if the client says payment is blocked by their finance team?
A: That’s legitimate. The fix is structural. Ask for a specific date their finance team will review it, and confirm it in writing from the client. Then follow up on that date. You’re no longer pushing the client; you’re working with them on their timeline.
Q: Should I charge late fees?
A: Only if your contract allows it and the fee structure is enforceable in the client’s state. Most MSP contracts include late fees (1-1.5% per month), but enforcement varies by state. If you have the right in contract, add it at day 30 when you’re sending the settlement offer.
Q: Can I sue an MSP client for nonpayment?
A: Yes, if the invoice exceeds your court’s jurisdiction (usually $5,000-$10,000 depending on state) and you have a signed contract. But litigation is expensive and takes months. Use it as a backstop, not your first move.
Q: What if the ghosting client comes back as a prospect for new services?
A: Don’t resume work until the old invoice is settled or officially written off. New service on top of unresolved debt poisons both invoices. Get the old one resolved first (pay, settlement, or writeoff).
What happens if settlement and formal notice both fail
If you’ve moved through the full sequence (settlement offer included) and the client still hasn’t engaged, you’ve documented everything. At that point, you have three clean options:
- Write it off (small invoices, operational decision).
- Use a structured recovery service (formal demand letters, final notice, escalation without a lawsuit).
- Refer to a collections specialist (if the invoice is large and the client is still operating).
For MSPs, structured recovery (option 2) is usually the right fit. It sends a letter in your name, hits differently than email, and often surfaces the real problem. A missing decision-maker, a procurement hold, or the discovery that the client is actually unable to pay. Those realities come out fast when a formal letter arrives.
If the client still doesn’t respond after a formal demand, you’ve given yourself the documentation to take the next step, whatever that is.
For MSPs with a book of recurring invoices, the core insight is this: ghosting is almost never personal refusal at the first sign. It’s almost always a communication or decision-making problem. Your first five reminders should be diagnostic, figuring out what the real block is. Only after settlement offer + formal notice are you allowed to assume it’s adversarial.
Follow this sequence and most ghosted invoices resolve. The ones that don’t have given you the documentation and data to make the next move with confidence.