Best Practice: Credit Control & Getting Paid
Profitable businesses fail for a boring, preventable reason more often than an exciting one: they run out of cash while waiting to be paid for work they've already done. An MSP is particularly exposed to this, because the work is delivered continuously and invoiced in arrears, so the gap between doing the work and holding the money is baked into the model from day one.
Credit control is the discipline that keeps that gap from becoming dangerous. It has an undeserved reputation as awkward or confrontational — chasing a client for money can feel like it threatens the relationship — but the evidence runs the other way: a business that invoices cleanly, sets terms clearly, and follows up consistently reads as more professional, not less, and a predictable collections process is something good clients respect rather than resent.
This guide covers the general discipline, then where MSP Pulse's own mechanics genuinely support it — and, just as importantly, where MSP Pulse deliberately leaves the job to your accounting platform rather than reinventing it.
1. Decide creditworthiness and terms before work starts
Every invoice you issue on payment terms is, functionally, a short-term loan to that client. Treat the decision to extend it with the same seriousness you'd want someone extending credit to you.
Check before you commit, not after the first invoice goes quiet. Winning a new client is exciting, and it's tempting to skip straight to onboarding — but a quick look at how an organisation is known to pay (a credit check, a reference, or simply what you already know about them) costs little and tells you a lot about what terms are appropriate.
If credit genuinely isn't warranted, don't extend it. That's not a punishment — it's an honest reflection of risk. A new or unproven client paying upfront or on shorter terms is a completely normal, professional arrangement, not an insult.
Set terms deliberately, per client, and say so clearly before work begins. Net 30 is the common default for a reason — it balances client goodwill against your own cash-flow needs — but it's a default, not a rule. A client with a track record of slow payment is a reasonable candidate for shorter terms or upfront deposits; don't apply one blanket policy to everyone regardless of history.
Put terms in writing, every time, not just implied by habit. The terms a client agreed to need to be unambiguous and referenceable — on the agreement, in the contract, somewhere neither side has to rely on memory when a dispute eventually comes up.
2. Invoice accurately and promptly — remove every legitimate excuse to delay
A late payment caused by a genuinely bad invoice — wrong amount, missing PO number, sent to the wrong person, arriving weeks after the work — is the collections problem you have full control over, and it's the one worth eliminating entirely before chasing anything else.
MSP Pulse has a single invoicing path: Invoicing → Load pending → Generate draft. Every billable item flows through one consistent route rather than being invoiced ad hoc from wherever someone happens to remember it, so unbilled work is visible in one place and the client isn't surprised months later by a backlog of charges that should have arrived incrementally. It only helps if someone actually works that list on a regular rhythm.
Prices and rates are frozen at the point they're committed, not recalculated later — at logging for time entries, and when a quote is sent or won. That removes one of the most common sources of a disputed invoice: a client querying a number because it doesn't match what they remember agreeing to.
A customer PO is picked up from the most specific place it was recorded: the ticket, then the project, then the agreement. An invoice that combines several jobs for a client leaves the PO blank for you to fill in by hand, and you can edit it on the invoice even after it's sent. Check this before sending to a client whose accounts-payable team rejects invoices without a PO — it is one of the most mundane and avoidable reasons for a payment stalling.
The billing contact is resolved deliberately, not left to guesswork. The invoice takes the contact on the ticket it came from, otherwise the client's nominated billing contact, otherwise the primary contact, and you can change it on a draft before it goes out. You can also add extra recipients on the client (Finance → Settings → "Also send invoices to"), such as a generic accounts inbox, who are copied on every invoice.
3. Know whether the invoice actually arrived before you chase it
A surprisingly large share of what looks like a slow-paying client is actually an invoice that silently never landed — bounced, caught by a spam filter, sent to an inbox nobody checks. Chasing a client over an invoice they genuinely never received doesn't just fail to collect the money; it damages the relationship you were trying to protect by doing credit control properly in the first place.
MSP Pulse helps here in specific ways. An invoice is only marked sent if the email was genuinely sent: if your tenant has no working outbound email, the send fails with a reason and the invoice stays a draft instead of quietly showing as sent. Every customer-facing email is also recorded in Settings → Email → Recent email activity, with the recipient, outcome and reason.
Be clear about how far that goes. If you use MSP Pulse's managed sending (SES with your verified domain), the activity log is updated with delivered, bounced or complained results as they arrive. If you send through your own SMTP server, the best the log can say is that the message was handed off. Know which one you're on before you rely on it.
Practical implication for your collections process: before the first chase on an overdue invoice, check the activity log rather than assuming. If it bounced or never went, fix the address and use Resend on the invoice (available on sent and paid invoices) instead of sending an awkward "following up on this unpaid invoice" message to someone who's never seen it.
4. Match payment terms and deposits to actual risk
Payment terms are resolved from the narrowest place they're set: the agreement, then the client, then your tenant default, then 30 days. You can set them on a billing agreement (a blank field means inherit; 0 means due on receipt), on the client, and as a tenant-wide default in Settings → Accounting. So you're not stuck with one blanket policy: a client whose agreements all share the same terms gets one simple invoice, while a service line you're less confident about can be put on tighter terms without touching anything else.
When a client's work resolves to different terms, Load pending produces one invoice per distinct set of terms rather than blending everything onto one invoice with one due date that doesn't describe what was agreed. Two agreements on the same terms do not split. If you have deliberately put one category of charge on Due on Receipt while the rest sits on standard terms, that distinction survives all the way to what is sent, and each invoice gets its own due date.
As a general practice, a deposit is one of the simplest and least confrontational credit-control tools available — it's agreed upfront as part of the normal sales conversation, not raised awkwardly after trust has already been tested. A common approach is a percentage of the total project value (something in the 20–50% range is typical, scaled to the size and risk of the job) collected before work begins, with the balance due on completion or at agreed milestones. Framed correctly — "our standard terms for a project this size include a deposit" — it reads as professional process, not suspicion of the specific client. The size of the deposit should scale with the exposure: a small, short engagement may not need one at all, while a large project with a new or unproven client is exactly where it earns its place.
In MSP Pulse a deposit is a billing event on the quote. You can set it to invoice automatically when the client accepts the quote, or to wait until you choose to bill it (useful for a delayed start). Either way it is invoiced up front and then credited back automatically on the itemised invoice for the work, so the client pays net and is never billed twice, and a ticket with an outstanding deposit is invoiced on its own so the credit nets against only that work.
5. Use the credit control tools MSP Pulse does have
MSP Pulse can warn about, and optionally block, new work for a client who owes too much or has paid too slowly. It is off by default, so nothing happens until you switch it on.
Set it up in two places. The mode is a tenant setting under Settings → Accounting → Credit Control: Off, Warn or Enforce. The numbers are per client under Finance → Settings: a credit limit (blank uses your tenant default), plus an optional grace amount and grace days.
It watches two things independently.
- Exposure: how much the client owes against their limit. Over the limit is a Credit-Warn; over the limit by more than the grace amount is a Credit-Hold.
- Ageing: the oldest overdue invoice against the client's payment terms. Overdue is a warn; more days overdue than the grace days is a hold.
What a hold actually does. In Warn mode, nothing is blocked; the client's Credit Position card on the Finance tab and the New Ticket form show a banner. In Enforce mode, a held client can't have a new ticket created or a quote approved or won by anyone except an owner/admin, who can proceed and has the override recorded on the ticket. A client can be exempted, or put on a manual hold regardless of the numbers. A hold clears itself as soon as the figures recover.
What it deliberately does not do. It never blocks work already in flight. It does not stop inbound email or alert tickets, tickets raised from the customer portal (so a client can always report an outage), or a client accepting a quote through the public link. Only people creating new commitments inside MSP Pulse are stopped.
It is only as accurate as your payment records. "Owed" means invoiced and not yet paid, so if payments aren't recorded in MSP Pulse a client looks like they owe more than they do, and can be held wrongly. Payments are recorded on the invoice (partial payments are supported) or from the client's Statement tab, where you can also apply a credit note or an overpayment held as credit on account. Automatic payment status from Xero or QuickBooks is built but needs extra setup on your side and has not been proven in live use, so don't count on it. Before switching to Enforce, try Warn for a while and check the figures against your own books.
6. Where MSP Pulse hands off
MSP Pulse follows a deliberate "integrate, don't rebuild" principle elsewhere in the platform, and the same is true here. It gets an invoice out accurately, on time, to the right person, on the right terms, and warns you about exposure. It does not itself chase the payment once that invoice is sent. There are no automated payment reminders or dunning emails for overdue invoices; those live on the accounting-platform side (Xero and QuickBooks both have their own reminder features) or in a manual process you run yourself.
That is a reasonable division of labour, not a missing feature to apologise for: collections workflow is exactly what a dedicated accounting platform already does well, and duplicating it would mean two systems of record for the same debt. But it does mean you should set up reminder automation on whichever platform you've connected, and not assume an unpaid invoice will surface itself.
7. Build the weekly habit — credit control is discipline, not firefighting
Credit control fails most often not from any single bad decision but from inconsistency — reminders sent sometimes, aging reviewed only when cash feels tight, a client's growing balance noticed only once it's already a problem.
Review aged debt on a fixed cadence — weekly is reasonable for most MSPs — not only when cash flow already feels tight. In MSP Pulse each client's Statement tab shows the balance broken into Not due, 1–30, 31–60, 61–90 and 90+ days, with a running transaction list. By the time a shortfall is actually felt, the receivables that caused it have usually been aging quietly for weeks.
Reconcile against your accounting platform. On the same tab, "Reconcile with accounting package" compares MSP Pulse's balances for invoices you've already pushed with the balances in Xero or QuickBooks and lists any differences, plus invoices not yet pushed. A mismatch is often an unrecorded payment, which is exactly the thing that makes credit control inaccurate.
Track days sales outstanding (DSO) as a trend, not a single snapshot. MSP Pulse doesn't calculate DSO for you, so take the figure from your accounting platform or work it out yourself on a regular schedule. One slow-paying client is a conversation; a DSO that's been climbing for three months running is a process problem worth addressing directly — tighter terms for new clients, earlier reminders, or a harder look at who's actually being extended credit.
Treat a consistently slow payer as a terms decision for next time, not just a collections problem this time. If a client is reliably 20 days late every cycle, chasing the same invoice every month isn't solving anything — revisiting their terms (shorter cycle, a deposit requirement, or in the worst case choosing not to continue extending credit) is the actual fix.
Pair this review with the same cadence as your agreement and catalogue reviews (covered in the earlier guides) rather than running it as a separate, easily-skipped task — the renewal conversation is often exactly the right moment to also address a payment pattern that's been building.
Pre-flight checklist for credit control
- [ ] Creditworthiness considered before onboarding, not assumed
- [ ] Payment terms set deliberately per client and agreement — not a single blanket default applied without thought
- [ ] Terms are in writing and referenceable, not left to memory or implication
- [ ] Invoices generated through the single Load pending path, and that list worked on a regular rhythm
- [ ] PO numbers and billing contacts correct before an invoice goes out, not discovered wrong after
- [ ] Email activity log checked (and the address fixed and the invoice resent if needed) before the first chase on any overdue invoice
- [ ] Deposits used deliberately for new or higher-risk project work
- [ ] Credit control mode chosen on purpose, with limits and grace set per client where it matters; Warn tried before Enforce
- [ ] Payments recorded in MSP Pulse promptly, since credit control reads from them
- [ ] Reminder automation configured on the connected accounting platform — not assumed to happen in MSP Pulse
- [ ] Aged debt reviewed weekly, and the reconciliation check run periodically
- [ ] DSO tracked as a trend, reviewed alongside agreement and catalogue reviews
- [ ] A consistently slow payer prompts a terms decision for next time, not just another chase this time