You can reduce DSO without hiring more AR staff by fixing the four things that cost the most days: late cash posting, invoice errors, an unranked collections list, and slow disputes. Automate the matching and chasing, and let your existing team approve the exceptions.
Most teams already know their days sales outstanding is too high. What they lack is the time to find out why. Accounts receivable automation takes the data entry and follow-ups off the team, while a person still approves anything that posts money.
This post is for controllers and CFOs who can’t add headcount this quarter. We rank six fixes by effort, starting with the ones that need no new people.
Quick Answer To reduce DSO without adding staff, first split your days into terms-driven and lateness-driven. Then post cash the same day, fix invoice errors before sending, rank collections by risk, and resolve disputes on a clock. Automate the routine work and keep a person approving every posting.
High days sales outstanding has three usual causes: long payment terms, invoices that go out wrong, and receivables that sit unworked. The first step to reduce DSO is knowing which one you have, because each needs a different fix.
The standard DSO formula is accounts receivable divided by credit sales, multiplied by the days in the period. Use the same period for both numbers. A quarter and 90 days works, and so does a year and 365 days. Mixing them is the most common arithmetic mistake we see.
The QServices Framework Reduce DSO = Diagnose → Apply cash → Bill clean → Rank → Resolve → Measure
The order matters because each stage removes noise from the next. You can’t rank a collections list while unapplied cash makes good customers look late.
How to calculate DSO by customer segment is simple: run the same formula on each group’s receivables and credit sales. Split by customer size, payment method or region.
A blended number hides the problem. One segment often drags the whole figure up, and that is where your first week of effort should go.
Calculate best possible DSO (BPDSO) as current, not past-due, receivables divided by credit sales, times days. It is the DSO you’d have if every customer paid on time. Subtract it from your DSO and you get average days delinquent (ADD).
If the gap is small, your days sit in terms and billing timing, so fix the invoice and the terms. If it’s large, fix collections.
A good DSO is one close to your own best possible DSO and trending down. The Credit Research Foundation reports Q2 2026 median DSO of 37.5 days with best possible DSO at 34.0 and average days delinquent at 3.7. That’s the independent median across its domestic trade receivables survey.
That 3.7-day gap suggests many US days come from terms rather than lateness, which is our inference, not CRF’s claim. For the full set of formulas and levers, see our guide to the days sales outstanding formula.
Post every payment to the right invoice on the day it arrives. Cash sitting in suspense leaves invoices open, so receivables look older than they are and DSO rises for no real reason.
Same-day or next-day posting is the usual target. Vendors claim big DSO drops from it, but no independent study measures the effect, so we won’t quote one. Run your own before-and-after instead.
Unapplied cash is subtracted from nothing. It just stays in a suspense account while the invoice it paid shows as open. Our cash application services page covers how agents match remittances to invoices.
Real-World Scenario A typical case we see: a controller at a company with $12M in quarterly credit sales reports $6.4M in receivables, so DSO is 48 days. Of that, $0.4M is cash already received but unapplied. Removing it gives $6.0M and a true DSO of 45. Three of the 48 days were a posting delay, caught at the Apply cash stage before anyone chased a customer who had already paid.
If auto-matching improves but unapplied cash doesn’t fall, the exceptions process is the bottleneck. Short pays, missing remittance detail and one payment covering many invoices are the usual culprits. Our walkthrough of the cash application process shows where each step breaks, and the unapplied cash backlog guide covers clearing what has already built up.
An invoice that fails a customer’s approval check pays late, whatever your collectors do. Preventing that error is cheaper than chasing it.
Key Insight In a Vertex survey of 300 B2B AR professionals, 39% said more than a quarter of their late payments stem from invoice disputes. It’s self-reported, but it points at the cheapest fix on this list.
An agent can run these checks on every invoice draft inside your ERP. A person approves any invoice it flags.
The oldest-and-biggest list is easy to build and often wrong. A smaller overdue invoice from a customer with worsening payment history can matter more than a large one from a reliable payer.
How to prioritize a collections list comes down to three inputs: amount, days past due and payment history. Score each account, work the top of the list daily, and send automated reminders to the rest. A workable cadence is before the due date, on it, then at 7, 14 and 21 days past due.
| Oldest-first list | Risk-ranked list | |
|---|---|---|
| Setup effort | None | Needs payment-history data and scoring rules |
| Collector time | Spread evenly | Concentrated on likely problems |
| Customer tone | Same for everyone | Gentle for reliable payers, firm for risky ones |
| Downside | Wastes calls on good payers | Costs more to set up and needs upkeep as behavior shifts |
This is where our collections and dispute management work sits. The agent drafts the reminder and the ranking. Your collector sends it.
A disputed invoice usually blocks the whole payment, even when only a line is in question. Separate the two and the undisputed part can still be collected.
How to resolve invoice disputes faster starts with a simple log. We haven’t found an authoritative benchmark for resolution time, so set your own targets and track them.
The top categories tell you which upstream fix to make next. Most trace back to the invoice checks above.
DSO is volatile and less reliable over short windows, so judge it on a rolling period. Weekly tracking of the drivers underneath it is our own recommendation, not something a published source prescribes.
Review DSO monthly and the drivers weekly. A CFO should see the trend over three to six months, not a single month’s swing.
The five weekly numbers:
Standards & References
- Credit Research Foundation: publishes national median DSO, BPDSO, CEI and delinquency figures
We start with Diagnose, because the fix depends on whether your days sit in terms or in lateness. Agents run inside your own ERP and CRM, and your team approves every action before anything posts.
The fixed-scope AR Cash Assessment is where we do step 1.
Implementation Checklist
- DSO, BPDSO and average days delinquent calculated on one consistent period
- DSO split by at least two customer segments
- Unapplied cash balance known and reviewed weekly
- Cash posted within one business day of receipt
- PO number validated before each invoice is sent
- Collections list ranked by risk, not only age
- Disputed amounts logged separately from undisputed balances
- A named owner approves every posting an agent proposes
To reduce DSO with the team you already have, pilot same-day cash application on one entity for 30 days and measure unapplied cash, hours to post and DSO. Then add invoice checks and a ranked collections list once the first fix holds. When you’re ready, Book the AR Cash Assessment.
Written by Rohit Dabra
Co-Founder and CTO, QServices IT Solutions Pvt Ltd
Rohit Dabra is the Co-Founder and Chief Technology Officer at QServices, a software development company focused on building practical digital solutions for businesses. At QServices, Rohit works closely with startups and growing businesses to design and develop web platforms, mobile applications, and scalable cloud systems. He is particularly interested in automation and artificial intelligence, building systems that automate routine tasks for teams and organizations.
The fastest wins are posting cash the same day and checking invoices for PO and pricing errors before they’re sent. Both remove days without a single customer call. Then rank your collections list by risk so the team’s limited time goes to the accounts most likely to pay late.
A good DSO is one close to your own best possible DSO and falling over time. The Credit Research Foundation reported a Q2 2026 median DSO of 37.5 days, with best possible DSO at 34.0. Your target depends on your payment terms, so compare against terms first.
The usual causes are long payment terms, invoice errors that trigger disputes, unapplied cash that leaves paid invoices open, and collections work that isn’t prioritized. Compare DSO with best possible DSO to see whether lateness or terms is the larger share.
Yes. Automate the routine work, which is cash matching, invoice checks and reminder drafting, and keep your existing team approving exceptions and anything that posts money. To start, calculate DSO by customer segment and pilot same-day cash application on one entity.
Review DSO monthly on a rolling basis and the underlying drivers weekly. Watch unapplied cash, percent current, collection effectiveness, dispute age and average days delinquent. Judge the trend over three to six months, because single-month DSO swings are common.
Reduce DSO without adding headcount. Six fixes ranked by effort, from same-day cash application to cleaner invoices and faster dispute resolution.
Learn to read an EDI 820 segment by segment, match it to the invoices it pays, and post it cleanly in SYSPRO, Epicor or Business Central.
Copilot Studio agents can read remittances, take orders from email and triage tickets. See what each needs from your ERP and where a person approves.
Get a free remittance advice template, learn what a good one includes, and see how 200 customer formats hit your AR team. Download the template today.
When PDF text extraction drops the spaces between words, AI agents can’t find facts that are right there. How we found it in Azure AI Foundry and fixed it.
Pint AE explained for UAE finance teams with one sample invoice: see which fields come from your ERP, which go missing, and how to test before go-live.
Reduce DSO without adding headcount. Six fixes ranked by effort, from same-day cash application to cleaner invoices and faster dispute resolution.
Learn to read an EDI 820 segment by segment, match it to the invoices it pays, and post it cleanly in SYSPRO, Epicor or Business Central.
Copilot Studio agents can read remittances, take orders from email and triage tickets. See what each needs from your ERP and where a person approves.
Get a free remittance advice template, learn what a good one includes, and see how 200 customer formats hit your AR team. Download the template today.
When PDF text extraction drops the spaces between words, AI agents can’t find facts that are right there. How we found it in Azure AI Foundry and fixed it.
Pint AE explained for UAE finance teams with one sample invoice: see which fields come from your ERP, which go missing, and how to test before go-live.
Earning Global Recognition: A Testament to Quality Work and Client Satisfaction. Our Business Thrives on Customer Partnership
Founder and CEO
Chief Sales Officer
Join our live webinar on Sept 24 and see five
ways to automate meetings, approvals, and
document search with tools already in your
tenant.
