How to Reduce DSO: A 90-Day Collections Plan

Executive summary

Days sales outstanding (DSO) tells you how many days of sales are sitting in receivables. Each day of DSO is worth a fixed amount of cash: your credit sales per day. A company with $48M of annual credit sales has about $131,500 of cash tied up in every day of DSO. Cutting five days releases roughly $657,000 without a single new sale.

Most DSO programs stall because the team treats DSO as one number owned by "collections." In practice it is three problems that have different owners: invoices that go out late or wrong (billing), customers who pay later than terms (credit and collections), and disputes that stop payment entirely (sales, operations, and customer service). The plan below separates the three, sizes each in days, and assigns each an owner and a weekly review.

The first move is not a dunning campaign. It is computing DSO, best possible DSO, and average days delinquent from your own ledger, so you know how many of your days are actually recoverable.

When to use this

Use this guide when:

• Revenue is growing but cash is not.
• The 13-week cash forecast keeps missing on the receipts line.
• A lender, a sponsor, or an acquirer is asking about working capital.
• DSO has drifted up over three or more consecutive months.
• You are preparing for a sale and want the working capital peg to reflect clean receivables.

Do not use this as your first step if you cannot reconcile the AR subledger to the general ledger. Fix that first, because every figure below depends on it.

The formulas

1. Simple DSO

DSO = (Ending accounts receivable ÷ Credit sales in the period) × Days in the period

Use credit sales only (exclude cash and card sales that never enter AR). Use the same period for sales and days: quarterly sales with 90 days, monthly with 30 or 31, annual with 365. State which one you used every time, because DSO calculated on annual sales and DSO calculated on the last quarter can differ by several days in a growing or seasonal business.

2. Count-back DSO

Simple DSO assumes sales were flat across the period. If sales are growing or seasonal, it misstates DSO. The count-back method walks backward through monthly sales until the ending AR is used up:

1. Start with ending AR.
2. Subtract the most recent month's credit sales, and count that month's days.
3. If AR remains, subtract the prior month's sales, counting its days, and so on.
4. For the final month, take the remaining AR as a fraction of that month's sales, multiplied by the month's days.

Count-back DSO is the sum of the days. It answers a sharper question: how old, in sales terms, is the oldest invoice you are still waiting for?

3. Best possible DSO and average days delinquent

Best possible DSO (BPDSO) = (Current, not-yet-due AR ÷ Credit sales) × Days in the period
Average days delinquent (ADD) = DSO − BPDSO

BPDSO is the DSO you would have if every customer paid exactly on the due date. It reflects your terms and your billing speed. ADD is the part customers (and disputes) add on top. ADD is the number a collections team can attack directly. BPDSO can only be moved by changing terms, billing timing, or invoice accuracy.

4. Collection effectiveness index (CEI)

CEI = (Beginning AR + Credit sales − Ending total AR) ÷ (Beginning AR + Credit sales − Ending current AR) × 100

CEI measures the share of collectible receivables actually collected in the period. Close to 100% means collection is working. CEI is useful because it does not move with sales growth the way DSO does.

Worked example (illustrative)

The numbers below are made up to show the method. They are not benchmarks.

A distributor has, for the quarter July to September:

Simple DSO = 5.4 ÷ 12.0 × 90 = 40.5 days.

Count-back DSO: September sales of $4.4M cover 30 days and leave $1.0M of AR. That $1.0M is 1.0 ÷ 4.0 of August's sales, or 0.25 × 31 = 7.75 days. Count-back DSO = 30 + 7.75 = 37.75 days. It is lower than simple DSO because sales were growing, so the simple method overstates how old the receivables are.

Best possible DSO = 4.2 ÷ 12.0 × 90 = 31.5 days.

Average days delinquent = 40.5 − 31.5 = 9.0 days.

CEI = (4.6 + 12.0 − 5.4) ÷ (4.6 + 12.0 − 4.2) × 100 = 11.2 ÷ 12.4 = 90.3%.

Value of a day: $12.0M ÷ 90 = $133,300 per day.

What this tells the operator:

• Nine of the 40.5 days are delinquency. Closing half of that gap (4.5 days) releases about $600,000.
• The remaining 31.5 days are terms plus billing timing. If the contractual terms are net 30, then 1.5 days of this are billing delay or invoice lag, and that is a pure process fix with no customer conversation.
• Whether the $1.2M past due is a few large invoices or many small ones decides the plan. Use the aging view in the next section.

Aging view for the example

The 61+ bucket is small in dollars but is where write-off risk and disputes concentrate. The 1-30 bucket is the cheapest cash to collect: a reminder call before escalation.

Diagnostic questions

Answer these from the ERP and AR subledger. Most take under an hour each.

1. Does the AR subledger reconcile to the general ledger at month-end, with no unexplained difference?
2. What is the lag between shipment or service completion and invoice date? Measure the median and the 90th percentile.
3. What percentage of invoices are disputed or corrected after being sent, and what are the top three reasons?
4. For the top 20 customers by AR balance, what are the contractual terms, and what are the actual days-to-pay over the last 12 months?
5. How much AR is past due, and how much of it sits in the top 10 customers?
6. Is there a written credit policy, and who can approve exceptions or credit holds?
7. Who owns each past-due invoice by name, and when was the last documented contact?
8. How many customers pay by a method that adds delay (check, mailed remittance) versus ACH or portal?
9. Are unapplied cash and short-pays posted within two business days?
10. Do sales commissions depend on collected cash or only on booked revenue?
11. Are there customers with terms longer than the standard terms, and does anyone know why?
12. What is the aged trend for the last six months: is the 61+ bucket growing as a share of AR?

Rule of thumb for reading answers: if question 2 shows a long invoice lag, start with billing. If question 3 shows a high dispute rate, start with root-cause fixes upstream. If question 7 shows invoices with no owner, start with accountability. Collections calls will not fix any of these.

The framework: three components of DSO

Size each component in days using the formulas above: BPDSO splits into contractual terms and billing lag, and ADD splits into undisputed delinquency and disputes. Then spend effort in proportion to days recoverable, not to which team is loudest.

Step-by-step: a 90-day collections operating plan

Weeks 1-2: Baseline and ownership

1. Reconcile AR subledger to GL. Clear unapplied cash and credit memos older than 30 days. Owner: Controller. Output: clean AR file.
2. Compute simple DSO, count-back DSO, BPDSO, ADD, CEI, and value per day. Owner: FP&A. Output: one-page baseline.
3. Split past-due AR into undisputed and disputed. Owner: Collections lead. Output: two lists.
4. Assign every invoice over a materiality threshold (for example, the largest invoices that make up 80% of past-due dollars) to a named person. Output: owner column in the AR file.

Weeks 3-4: Quick cash

5. Call the 1-30 bucket before invoices age further: confirm receipt, confirm the payment date, ask for a committed date. Log it.
6. Fix billing lag: set a rule that invoices are issued within one business day of shipment or service completion, with a daily exception report of uninvoiced shipments.
7. Send statements weekly to customers with open past-due items, not monthly.
8. Post cash daily and apply it, so collectors do not chase invoices already paid.

Weeks 5-8: Fix the structural causes

9. Root-cause the disputes: take the top 25 disputed invoices and tag each with a cause (price, quantity, quality, missing PO, terms mismatch, service not delivered). Fix the two biggest causes at the source with the department that owns them.
10. Review terms for the top 20 customers: where actual days-to-pay exceed terms by a pattern, decide to enforce, renegotiate, or price in the cost of carry. Do this deliberately, not by accident.
11. Write a credit policy (limits, holds, escalation steps, who can release a hold). Even one page works.
12. Offer easier payment: ACH, portal, remittance details on every invoice, named billing contact.

Weeks 9-12: Lock in the cadence

13. Weekly AR review (30 minutes): top past-due items, promised dates versus actual, escalations, disputes aging. Same agenda every week.
14. Escalation ladder: reminder at due date minus a few days (for large accounts), call at due date plus a few days, sales or executive contact at a stated threshold, credit hold at a stated threshold.
15. Align incentives: where possible tie part of sales compensation to collected cash or to the absence of disputes on the accounts they own.
16. Feed the cash forecast: update the receipts line of the 13-week cash flow forecast from promised dates, with a haircut for historical broken promises.

Templates

Collections log (copy into a spreadsheet)

Weekly AR review agenda

1. DSO, BPDSO, ADD, and CEI versus last week and versus plan (5 min).
2. Top 10 past-due invoices: status, promised date, blocker (10 min).
3. Broken promises from last week and the escalation applied (5 min).
4. Disputes: new, resolved, oldest, cause tags (5 min).
5. Decisions needed from sales or operations (5 min).

Dunning message structure

• Before due date (large accounts only): invoice number, amount, due date, how to pay.
• Due date plus a few days: confirm receipt, ask for payment date.
• Later stage: state the amount, the age, the next step (credit hold, referral), and a named person with authority to resolve.

Write the exact wording for your customers and brand. The structure matters more than the script.

Metrics and KPIs

Setting targets without invented benchmarks. Use three anchors in this order: your own BPDSO (the floor if customers pay perfectly), your own best trailing six-month DSO (what you have already achieved), and published DSO for your sector in a named public source such as listed-peer filings. Set the first-year ADD target as a percentage of the current ADD that your dispute and ownership analysis supports. Do not take a number from a blog and apply it to your terms and customer mix.

Common mistakes

1. Managing the blended DSO. A DSO that drops because sales jumped at the end of the period has not improved collections. Track ADD and CEI.
2. Chasing the largest overdue balance first. The largest balance may be a customer that always pays at day 75. The cheapest cash is usually the 1-30 bucket across many accounts.
3. Calling customers about disputed invoices. No collections call resolves a pricing error. Route disputes to the owner of the cause.
4. Pushing terms without sales involvement. Aggressive collection of a key customer that sales did not warn will cost more than the cash is worth. Align on a customer-by-customer plan.
5. Window dressing. Factoring, pulling forward billing, or accepting early-pay discounts without costing them lowers DSO and may destroy margin. Price the cost of capital before using them.
6. Ignoring unapplied cash. Cash that is received but not applied makes AR look older than it is and wastes collector time.
7. No named owner per invoice. Shared inboxes do not collect cash.
8. Treating the forecast as an output. If promised dates do not feed the cash forecast, the weekly review has no consequence.

AI prompt assistance

AI is useful for preparing the analysis and drafting messages. It is not a substitute for checking the numbers. For each prompt, supply the data yourself and verify the output against the ledger before acting.

1. Diagnose DSO from a ledger extract.

I will paste an AR aging report and monthly credit sales for the last 12 months. Compute simple DSO, count-back DSO, best possible DSO, average days delinquent, and CEI for the latest month. Show every calculation step. Then list the ten customers that make up the most past-due dollars, with each one's share of past due.

Check: recompute one figure by hand and confirm that the totals tie to your subledger.

2. Classify dispute reasons.

Here are 40 disputed invoices with the free-text notes from collectors. Tag each with one cause from this list: pricing, quantity, quality, missing PO, terms mismatch, service not delivered, other. Return a table and a count by cause. Flag any note that you could not classify with confidence.

Check: spot-check ten rows. Do not assign root cause without confirming with the operating team.

3. Draft escalation messages.

Draft three versions of a firm, professional payment reminder for an invoice that is 20 days past due for a long-standing customer. Include the invoice number, amount, original due date, and a request for a committed payment date. Do not threaten legal action.

Check: have the account owner approve the tone for strategic accounts.

4. Summarize the weekly review.

Given this week's collections log (pasted), write a half-page summary for the CFO: change in past due versus last week, the five invoices most likely to slip, broken promises, and decisions needed.

Check: confirm every dollar figure against the log.

Implementation guide

Governance: the CFO owns the target, the Controller owns the process, Sales owns terms and customer conversations, Operations owns upstream defects. Report DSO, ADD, CEI, and dispute rate monthly to the CEO or the board alongside cash.

What to expect: the first improvement usually comes from billing lag and the 1-30 bucket within a month. Dispute reduction and terms changes take a quarter or more, and show up as a lower ADD over the following periods. Do not announce a target in the first month.

Downloadable assets

The collections log and weekly agenda above are designed to be copied into a spreadsheet.

Related resources

• Working capital: 3 levers that move your cash cycle: where DSO sits next to inventory and payables.
• 13-week cash flow forecast template: turning promised dates into a receipts forecast.
• Quality of earnings report before you close: how a buyer tests the quality of your receivables.

Frequently asked questions

What is a good DSO?

A good DSO is one close to your best possible DSO, which is set by your own terms and billing speed. Compute best possible DSO (current, not-yet-due AR divided by credit sales, times days) and treat the gap to actual DSO as the part you can recover. Compare against listed peers with similar terms, not a generic number.

How do you calculate DSO?

DSO equals ending accounts receivable divided by credit sales for the period, multiplied by the days in that period. Use credit sales only and match the period: quarterly sales with 90 days, monthly with 30 or 31. If sales are growing or seasonal, use the count-back method, which walks backward through monthly sales instead of assuming they were flat.

What is the difference between DSO and best possible DSO?

DSO measures how long customers actually take to pay. Best possible DSO measures how long they would take if everyone paid exactly on the due date. The difference is average days delinquent, the part of DSO that collections and dispute resolution can directly reduce.

How much cash does one day of DSO release?

One day of DSO equals your credit sales per day. For example, $48M of annual credit sales is about $131,500 per day, so a five-day reduction releases roughly $657,000. Divide period credit sales by the days in the period to find your own figure.

How long does it take to reduce DSO?

Billing lag and the 1-30 day past-due bucket usually respond within the first month. Dispute reduction and terms changes take a quarter or more and show up as a lower average days delinquent in later periods. Avoid announcing a target before the baseline and ownership work is done.

How this works in a System of Performance

The weekly AR review only helps if what was decided and what happened next stay linked. Which collector contacted which customer, what was promised, whether the promise was kept, and what the resulting cash was are scattered across the ERP, email, and spreadsheets in most companies. A Performis routine can take on a recurring job like this, with the scope and fit agreed with you: it works from the records your team supplies, prepares the work for your named reviewer, and keeps each approval on record. If you want to see how much receivable days sit in your own ledger, bring it to us as a launch partner.