Key takeaways
- Report average days delinquent and collection effectiveness index alongside DSO. Together they separate collection performance from sales timing and agreed payment terms.
- Age receivables by due date, not invoice date, and strip out disputed invoices and unapplied cash before anyone makes a collection call.
- Classify every material overdue as administrative, dispute, process or capacity. Most overdue value sits in the first three categories, where chasing does not help.
- Segment the dunning cadence by value at risk and payment behaviour, vary the channel and sender, and pre-announce escalation so it is never a surprise.
- The cheapest days are recovered upstream: bill on the day of delivery, bill correctly first time, and apply cash daily so the ageing report is accurate.
Every finance team asked to reduce days sales outstanding reaches for the same lever: chase harder. It works for a quarter. Collections rise, the ageing improves, and then the sales director arrives with a list of customers who have been called four times about an invoice that was wrong in the first place, and the programme is quietly wound back.
The teams that hold a lower DSO permanently do something different. They treat collections as the last stage of an order-to-cash process rather than the whole of it, they segment their approach instead of applying one cadence to everyone, and they measure with three numbers rather than one. The customer experience improves at the same time as the cash position, because most of what was irritating customers was administrative error, not politeness.
Start with a diagnosis, not a target
DSO is a symptom. Before setting a target, the ageing has to be read properly, and most ageing reports are built in a way that hides the answer.
- Age by due date, not invoice date. A ninety-day-terms customer and a thirty-day-terms customer both appear as “60 days” on an invoice-date ageing, though one is current and the other is a month late.
- Separate overdue from disputed. A disputed invoice is a service or billing failure sitting in the receivables ledger. Chasing it is wasted effort and it damages the relationship.
- Show concentration. In most mid-market ledgers a small number of accounts explain the majority of overdue value. The response to those accounts should not be the same as the response to the tail.
- Track unapplied cash and credits. Receipts sitting unallocated inflate the ageing and generate collection calls on invoices the customer has already paid — the single fastest way to lose credibility with a customer.
Measuring properly
Standard DSO is closing trade receivables divided by credit sales for the period, multiplied by the number of days in the period. It is adequate for trend, poor for seasonal businesses, because a quarter with a heavy final month inflates the number without any change in customer behaviour. Where seasonality is material, the countback or exhaustion method — working backwards through prior months’ sales until the receivable balance is consumed — gives a truer picture.
DSO alone cannot tell you whether performance changed or the sales pattern did. Two companion metrics fix that.
| Metric | Calculation | What it tells you |
|---|---|---|
| DSO | Closing receivables divided by credit sales for the period, times days in period | Headline conversion speed; sensitive to sales timing |
| Best possible DSO | Current (not yet due) receivables divided by credit sales, times days in period | The DSO you would achieve if every customer paid exactly on terms |
| Average days delinquent | DSO minus best possible DSO | Pure lateness, stripped of terms and sales-mix effects. The cleanest measure of collection performance |
| Collection effectiveness index | Opening receivables plus credit sales, less closing total receivables; divided by opening receivables plus credit sales, less closing current receivables; expressed as a percentage | Proportion of what was collectable in the period that was actually collected. Approaching 100 per cent indicates a well-run function |
| Percentage current | Not-yet-due receivables as a share of total receivables | Portfolio health; deteriorates before DSO does |
| Dispute rate and cycle time | Disputed value as a share of billed value; average days from dispute raised to resolved | Where the upstream process is failing and how fast it recovers |
| Right first time billing | Invoices requiring no correction or credit note, as a percentage | The leading indicator for most of the above |
Reporting average days delinquent alongside DSO changes the internal conversation immediately, because it separates what the collections team controls from what the sales calendar and the agreed terms determine.
Four root causes, four different responses
Classify every overdue invoice above a value threshold into one of four causes. Response design follows from the classification.
- Administrative. Missing purchase order number, invoice sent to the wrong contact or portal, incorrect GSTIN or billing address, missing supporting documentation, tax or e-invoicing details that block the customer’s own booking. Fix at source; no amount of chasing helps.
- Dispute. Quantity, quality, pricing, service level or contractual deduction. Route to the commercial owner with a resolution service level, not to collections.
- Process. The customer’s own payment run happens twice a month and the invoice missed the cut-off; approvals sit with someone on leave. Solvable by aligning submission timing to the customer’s cycle.
- Capacity or intent. The customer cannot pay, or has decided to stretch suppliers. This is the only category that genuinely needs escalation, credit action or a payment plan.
In most ledgers the first three categories account for the large majority of overdue value. Treating them all as category four is what makes collections feel adversarial to customers who were never trying to delay.
Fix the invoice before you chase it
The cheapest days of DSO are recovered upstream, before any call is made.
- Bill promptly. The interval between delivery or milestone and invoice issue is pure, self-inflicted DSO. A target of same or next business day is achievable in most businesses.
- Bill correctly the first time. Capture the customer’s purchase order requirements, reference formats, portal submission rules and required attachments at onboarding, and validate them before the invoice is released.
- Make terms unambiguous at order acceptance. Terms agreed verbally by sales and different terms printed on the invoice is a recurring source of both delay and dispute.
- Offer payment methods the customer actually uses. Bank details on the invoice, e-mandate options, and a clear remittance advice route so cash can be applied on receipt.
- Apply cash daily. Unapplied receipts create false overdues and false chasing.
Designing a dunning cadence that does not annoy
One cadence for the whole ledger is either too aggressive for good customers or too soft for the accounts that matter. Segment on two axes — value at risk and payment behaviour — and vary channel, timing and sender.
| Segment | Cadence | Channel and sender |
|---|---|---|
| High value, good history | Statement seven days before due; courtesy check on due date; personal contact at day seven overdue | Named account contact from finance; phone first, email confirming |
| High value, deteriorating | Pre-due confirmation of scheduled payment; contact at day three, seven and fourteen; commercial escalation at day thirty | Finance lead plus relationship owner; documented and dated |
| Mid value, routine | Automated reminder at due date, day seven, day twenty-one; call at day thirty | Automated email from a monitored mailbox with statement attached |
| Long tail, low value | Automated statement and reminder series only; consolidated call cycle monthly | Fully automated; exception-based human contact |
| Disputed, any value | Suspended from dunning; tracked on dispute service level instead | Commercial owner with a resolution date committed to the customer |
Three design rules matter more than the schedule itself. Every communication should carry the full invoice detail and a copy of the document, so the customer can act without asking. Every communication should be accurate, which means suppressing anything disputed, credited or already paid. And escalation should be pre-announced: telling a customer at day seven what will happen at day thirty removes the surprise that damages relationships, and frequently produces payment before day thirty arrives.
Credit policy is the upstream control
Collections cannot repair a bad credit decision. A workable policy has five components: a credit application and approval process with defined authority levels; a limit set from financial information, payment history and, where available, external credit data; differentiated terms by segment rather than a single company-wide default; security where exposure warrants it, whether advance payment, bank guarantee, letter of credit or credit insurance; and a defined review trigger — a limit breach, a deterioration in payment behaviour, or a public event affecting the customer.
Early payment discounts should be priced rather than assumed. Two per cent for payment in ten days against thirty-day terms is an annualised cost in the mid-thirties per cent — attractive only if the alternative funding cost is higher or the credit risk is material. Dynamic discounting, where the discount scales with how early the payment lands, is usually a better structure than a fixed offer.
Deductions and disputes
Where deductions are a feature of the sector, they need their own workflow. Code each deduction at the point it is taken — pricing, promotion, shortage, quality, freight, unauthorised — assign an owner by code, set a resolution service level, and report the ageing of open disputes separately from the receivables ageing. Root cause reporting by code, reviewed monthly with sales and operations, is what reduces the volume over time. Without it, the collections team spends its capacity re-litigating the same six issues every month.
Escalating without damage
Escalation should be predictable, proportionate and jointly owned. Predictable means the customer knows the ladder in advance. Proportionate means the step matches the cause: a payment plan for a genuine capacity problem, a credit hold for deliberate stretching, legal action only where the relationship is already over. Jointly owned means the relationship manager is informed before, not after, a hold is applied — the fastest way to break internal alignment is for a salesperson to learn about a stopped shipment from their customer.
It is worth stating the counter-position openly with the sales function: extending terms is a financing decision. Where a customer genuinely needs longer to pay, that can be a valid commercial choice, priced accordingly and approved through the credit process, rather than an undocumented drift that only the ageing report ever discovers.
What good looks like
A mature receivables function reviews a weekly worklist prioritised by value at risk rather than by age; holds a monthly cross-functional review of disputes by root cause; reports DSO, average days delinquent and collection effectiveness index together; keeps a written credit policy that is actually applied; and can show, for any overdue invoice, the full contact history in one place. Improvement is typically measured in a handful of days per quarter, sustained, rather than a step change that reverses.
Artham Fintech provides accounts receivable management as a managed service, covering ageing and root-cause analysis, dunning design, dispute workflow and the reporting cadence that keeps DSO from drifting back. If your receivables position has moved and the cause is not yet clear, an ageing diagnostic is usually the first useful step.