An 8-day DSO reduction on a $40M AR portfolio frees approximately $880K in working capital. This is the sequence of changes that gets you there.
Days Sales Outstanding is the most watched number in AR management — and one of the most frequently misunderstood. The standard formula (AR balance ÷ average daily revenue) is simple enough, but DSO is a composite metric that reflects four distinct dynamics simultaneously: invoice delivery speed, payment terms alignment, dispute frequency, and collections effectiveness. Improving DSO requires knowing which of those four is driving your number, because the interventions are completely different.
This playbook focuses on mid-market B2B companies — roughly $20M to $80M in annual revenue, 400 to 1,500 open invoices at any given time, net-30 to net-60 standard terms — where DSO reduction of 8-12 days is achievable within 90-180 days without renegotiating customer contracts or tightening credit terms in ways that drive away business. The math on that target: on a $40M annual revenue base with a $10M average AR balance, an 8-day DSO reduction frees approximately $880K in working capital. On a $60M revenue base with a $15M AR balance, the same 8-day improvement is $1.3M.
Diagnosing Your DSO Drivers Before You Touch Anything
Before any change to dunning cadence, escalation policy, or collections tooling, you need a clear picture of where your current DSO is being manufactured. Pull the last 12 months of payment data and answer four specific questions:
1. What percentage of your DSO is driven by your top 20% of customers by invoice volume? In many mid-market portfolios, 15-20 accounts represent 60-70% of total AR balance. If three of those accounts have a structural habit of paying at 45 DPD regardless of terms, those three accounts alone may be adding 8-10 days to your portfolio DSO. Fixing them is a relationship and terms conversation, not a collections operations problem.
2. How much of your aging is sitting in uninvoiced or dispute-held status? Uninvoiced revenue and invoices parked in dispute resolution inflate DSO without any connection to collection performance. If 12% of your AR balance is in open dispute at any given time and disputes take an average of 21 days to resolve, that's a meaningful contribution to your reported DSO that no amount of dunning improvement will fix.
3. What is your invoice-to-delivery lag? Invoices that aren't delivered until 3-5 days after goods ship or services are rendered start the payment clock late. On net-30 terms, a consistent 4-day delivery lag effectively makes all your terms net-34, and it shows up in DSO as phantom lateness. Electronic delivery with confirmation tracking eliminates this entirely.
4. What is your first-contact resolution rate on disputes? A dispute that takes two rounds of back-and-forth to resolve adds an average of 7-10 days to collection time versus a dispute resolved on first contact. If your dispute resolution process is slow, it's adding directly to DSO.
Phase 1: Fix the Structural Leaks (Weeks 1-4)
Structural fixes come before collections process changes because they produce DSO improvement without requiring behavior change from customers or from AR teams. They're also often faster to implement.
Move to electronic invoice delivery with read receipts
If you're still mailing invoices or sending them as PDF attachments without delivery confirmation, you're adding noise to your payment timing data and losing 3-5 days of effective payment window on a meaningful share of invoices. Every invoice should have a confirmed delivery timestamp. Disputes about whether an invoice was received — still a surprisingly common collections conversation — disappear when you have delivery confirmation.
Standardize payment terms in the ERP, not just in contracts
A common source of DSO inflation: customer contracts specify net-30, but the ERP has the account coded as net-45 because someone changed it years ago and nobody noticed. The invoice goes out with net-45 terms printed on it, the customer pays at day 42 (technically on time), and the DSO calculation reflects it as a 42-day receivable. Auditing your ERP payment terms coding against actual contracts is tedious but often surfaces a 2-4 day DSO improvement for free.
Implement structured dispute intake
Disputes received by email get resolved more slowly than disputes received through a structured intake channel, because email disputes require someone to read, triage, and route them before resolution work begins. A simple dispute intake form — accessible to customers, capturing invoice number, dispute type, and contact information — reduces average time-to-resolution by eliminating the clarification loop. Faster resolution means less AR balance sitting in dispute hold.
Phase 2: Segment-Specific Collections Improvement (Weeks 4-10)
After structural fixes are in place, collections process improvement targets the segment of your portfolio where improved outreach timing and cadence actually changes payment behavior. This is roughly your 50th to 90th percentile accounts by payment reliability — customers who sometimes pay late, not structural offenders.
Identify the float segment
Most mid-market AR portfolios have a segment of customers who pay at 35-50 DPD consistently — not because they can't pay within terms, but because they haven't been given a reason to prioritize your invoice over others in their AP queue. This "float segment" often represents 20-30% of open AR by count and 15-25% by value. Improving their average payment day by 8-12 days — from day 40 to day 30 — is achievable with targeted, consistent follow-up that your current generic dunning cadence isn't delivering.
Build a segment-specific dunning cadence for the float segment
The float segment responds to personalized, direct communication better than to generic reminder emails. The key elements: a pre-due-date reminder at net-25 (a payment preview, not a demand), a due-date confirmation on the exact due date ("Invoice #4421 due today — let us know if there are any questions"), and a 7-DPD follow-up that asks for a specific payment date. This three-touch sequence, when run consistently, moves a meaningful portion of the float segment into on-time or near-on-time payment. Generic dunning runs the same sequence on every account — this doesn't.
Phase 3: Early Intervention on High-Risk Accounts (Weeks 6-12)
The third lever is the highest-impact and the hardest to implement without a predictive signal: identifying which invoices in your current portfolio are heading toward 60+ DPD while they're still in the net-30 window, and intervening early enough that you're resolving the issue before it becomes a collections problem.
For a $40M revenue company with 1,200 open invoices, there may be 40-80 invoices at any given time that have elevated payment-slip probability — flagged by patterns like the customer's last two invoices being paid progressively later, a recent dispute that went unresolved, or payment behavior that diverges from the customer's historical baseline. Early outreach on these accounts — at day 10-15, not at day 31 — changes the outcome. The AR specialist isn't calling to demand payment; they're calling to check whether the invoice is in the customer's AP queue and whether there are any questions. That call, made early, resolves more issues than the same call made at 40 DPD.
The DSO impact of systematic early intervention is typically 4-7 days across the portfolio within 60-90 days of implementation, because a meaningful share of invoices that would have slipped to 45-60 DPD get resolved at 25-35 DPD instead. This isn't a small improvement in collection execution — it's a structural shift in when your team gets engaged with at-risk accounts.
Measuring Progress Without Being Misled by DSO Fluctuation
DSO fluctuates naturally with revenue seasonality and invoice timing. A 10-day DSO jump at month-end that reverses by mid-month is noise, not signal. Track DSO as a rolling 90-day average to remove the timing noise, and supplement it with two more stable metrics: best possible DSO (what DSO would be if every invoice paid on exact terms — this tells you how much of your actual DSO is structural vs. collections-driven) and the percentage of AR balance in the current bucket vs. 30+ DPD. The latter tracks whether your collections improvements are actually shifting invoices into the current bucket, not just changing when they arrive in the past-due buckets.
An 8-12 day DSO reduction over 90-180 days is a realistic target for most mid-market AR operations that follow this sequence. The improvements don't all arrive simultaneously — structural fixes show up in weeks 2-4, float-segment cadence improvements in weeks 6-10, and early-intervention impact in weeks 8-16. Track each independently, and don't declare success or failure on the overall DSO number until 90 days of data have accumulated.