MSP Accounts Receivable: Fix the Process Before You Have a Problem

If you’ve ever looked at your P&L and thought “we’re doing well” but then looked at your bank account and thought “where the heck is all the cash?” you’re not alone. Accounts receivable is one of the most common pain points I hear from MSP owners, and the gap between revenue on paper and cash in the bank can be brutal. It seems like many MSPs don’t manage their cash well. Either they don’t have cash in the bank, they don’t control the cash in the bank, or they have a ton of extra cash because they don’t know what’s going to happen.

Here’s the thing: this is almost always a process problem. If you allow your clients to send you checks, chasing invoices manually, sending one-off emails, or relying on the same person who has a relationship with the client to also be the one demanding payment, you’ve already put yourself at a disadvantage.

Thankfully, your Accounts Receivable (AR) process is fixable. But you have to build the system before you have a problem, not after.

Why MSPs End Up at the Back of the Line

One of the most common things I see is that clients put the MSP’s invoice at the back of the list to get paid. Why?

Your clients have finite cash, and they prioritize vendors who have consequences for non-payment. The cable company gets paid because everyone knows what happens if they don’t. Your MSP gets deprioritized because clients have learned, often through experience, that you’ll wait.

MSPs tend to be too friendly, too flexible, and too reluctant to enforce their own contracts. The relationship feels personal, so enforcement feels personal too. But your MSA is a business document. The moment you start treating it like one, your AR situation starts to improve.

The goal isn’t to become adversarial with your clients. The goal is to build a system where enforcement is just policy, not a confrontation.

The Levers, In Order of Impact

Make Auto-Pay the Default

This is the single biggest lever you have, and it’s not close. ACH or credit card auto-pay should be a requirement in your MSA for all new clients, not a preference or a nice-to-have. When a client signs with you, setting up auto-pay is part of onboarding. Full stop.

For existing clients, run a migration campaign. Frame it as “this is how we do things now” rather than a reaction to a specific problem. Most clients will comply without pushback, especially if you give them a reasonable runway.

The invoicing cadence that works well: invoice on the 10th of the month for the following month (you’re billing ahead), due on the 1st, and for auto-pay clients you pull on the 1st. Predictable for you, predictable for them.

When auto-pay is the norm, AR problems largely disappear. That’s the point. You may run into a prospect that won’t do auto payment during the sales process. You can choose to take on this client that wants to pay via check, but that should be the exception. Not the rule.

Shorten Your Terms

Net 30 is a holdover from a different era. Net 10 or due on receipt is increasingly standard for MSP recurring services, and there’s no reason you can’t move in that direction. At a minimum, lock in shorter terms for every new contract going forward. Don’t wait for an AR crisis to make this change.

Enforce the Late Fees You Already Have

Most MSAs already include a late fee clause, typically around 1.5% per month. If yours does, use it. The first time a client sees that fee on an invoice is usually the last time they pay late. If your MSA doesn’t include a late fee clause, add it at the next renewal.

The clause is worthless if you never enforce it. That’s the pattern I see most often: MSPs have the language, but they waive the fee to keep the peace. Every time you do that, you’re training the client that the terms aren’t real.

Automate the Follow-Up

Don’t rely on a person to chase invoices manually. It’s awkward, it’s inconsistent, and it will fall through the cracks. Tools like Gradient MSP, Wise-Sync, or even QuickBooks’ built-in reminders can send escalating notices automatically at day 5, day 15, day 30, and beyond.

When the reminder comes from a system, it feels like policy. When it comes from Jess, it feels like Jess is bugging them. Automate it and take the personal dynamic out of it entirely.

Build an Escalation Ladder

Automation handles most situations, but not all of them. When you need human intervention, you need a defined path so it doesn’t just fall to whoever feels like dealing with it that day.

A simple ladder: your admin sends a friendly reminder at 15 days, you send a firmer note at 30, and at 45 days services pause per the terms of your MSA. Document the ladder. Stick to it. Clients learn quickly that the cadence is real.

Yes, you will have to get involved personally at some point. That’s fine. Having the process behind you makes your involvement feel like a policy step rather than a personal confrontation. Define when you need to get involved, and make sure that you follow your process.

The Service Suspension Clause

This is the strongest tool in your MSA, and also the most misunderstood.

I hear MSP owners tie themselves in knots over this one, especially when Microsoft 365 or Azure is in the picture. The concern goes something like: “I can’t actually suspend their services, can I?”

Think about your cable company. They will cut your internet circuit for non-payment without much hesitation. Here’s the thing: cable and telecom companies are regulated as common carriers and utilities, which actually creates more restrictions on when they can act, not fewer. MSPs operate under no such regulatory burden. You’re a private business providing contracted services.

Your MSA governs your relationship with your client, not Microsoft’s terms of service. As a CSP partner, Microsoft’s own agreements actually allow for license suspension for non-payment. You’re not in violation of anything by acting on your contract.

A few places to be thoughtful: life-safety systems, healthcare environments, or any regulated vertical. These deserve explicit language in your MSA and a real conversation with a contracts attorney. And as always, verify the specifics with your own lawyer before you act. I’m a practitioner, not a legal expert.

The practical reality is that you rarely have to use the suspension clause. The existence of it, communicated clearly, changes behavior. Clients who know services can pause for non-payment treat your invoices differently. And the ones who do get suspended tend to pay very quickly once services go dark.

The key here is to make sure that you’ve done your communication pieces as mentioned above and that the client knows the clause exists in your contracts and you’re fairly safe here.

All that said. . . I am not a lawyer, and I’m definitely not YOUR lawyer, so it’s best to consult one before you get to this point with any of your clients.

The Mindset Shift

None of this works if you’re not willing to enforce it. That’s the real problem for most MSPs. The tools, the clauses, the automation, it’s all available. The willingness to use it is what separates MSPs with healthy Accounts Receivable process from the ones chasing invoices every month.

The awkwardness of enforcement is almost always worse in your head than in practice. Most clients respect clear, consistent policies. It’s the inconsistent ones that get taken advantage of.

You are not a bank. Stop operating like one.

Where to Start

If you take nothing else from this post, start here:

• Make auto-pay a requirement for every new client starting now.
• Audit your MSA for a late fee clause and a service suspension clause. If they’re not there, get them added at the next renewal.
• Set up automated invoice reminders if you haven’t already.

Build the system before you need it. AR problems are almost always preventable. The MSPs who struggle with cash flow despite solid revenue are almost always the ones who never built the process in the first place.