Why DSO Matters More to an MSP Than Most Businesses
An MSP pays technicians, vendor licenses and distributor invoices every month whether or not clients have paid. Microsoft, your RMM vendor and your backup provider bill you on their schedule, not your clients' schedule. When DSO rises, you are funding your clients' cash flow out of your own, and a growing MSP feels it first as a tight payroll week rather than as a line on a report.
Track the number on the Days Sales Outstanding KPI page, and read it next to accounts receivable, because DSO is simply your receivables expressed in days of revenue.
How to Calculate It
Take the accounts receivable balance at the end of a period, divide it by the revenue billed in that period, and multiply by the number of days in the period. Use the same window every time, usually a month or a quarter, so the trend is comparable.
| Input | Where It Comes From |
|---|---|
| Ending AR balance | Your accounting system or PSA aging report |
| Revenue billed in the period | Invoices issued, not cash received |
| Days in the period | 30, 90 or 365 to match the revenue window |
Billing in advance distorts the number in a useful way. If recurring agreements are invoiced on the first of the month for that month, a client who pays on day ten still shows a short DSO. Hourly and project work billed after the fact will always pull the average up.
What Moves DSO at an MSP
- Payment method: card or direct debit on file for recurring services removes most of the chasing.
- Billing timing: invoicing managed services in advance rather than in arrears.
- Agreement terms: net terms, late fees and the right to suspend service written into the managed services agreement.
- Project billing: deposits and milestone invoices instead of one bill at completion.
- Invoice accuracy: a disputed line item holds up the whole invoice, so reconcile seats and licenses before you bill.
Read the Aging Report, Not Just the Average
An average hides the problem client. One large account sitting at ninety days can make a healthy book look mediocre, and a handful of small clients paying late can hide behind one fast payer. Sort the aging report by balance and by age, and call the oldest large balances first.
When a client is always late, treat it as a relationship signal as well as a cash one. Chronic late payment often travels with scope arguments and low engagement, and it belongs in the conversation about letting go of a bad client.
Common Questions
Should my PSA or my accounting system own DSO?
Use whichever system holds the final invoice and payment record, usually the accounting system. If the PSA and accounting totals disagree, fix the sync before trusting either DSO figure.
Does billing in advance make DSO misleading?
It makes DSO look better than the underlying payment habits. Track days past due separately so you still see which clients pay late.
Should I include resold hardware in DSO?
Yes, because it is money you have already paid a distributor for. You can also split DSO by revenue type to see whether hardware or projects are the slow payers.
Is a falling DSO always good news?
Usually, but check that it is not falling because billed revenue jumped from a large one-off project. Compare it with the aging buckets before celebrating.