Get a personalized demo of Stuut and see how it can help with AR automation.
Every day of DSO is cash sitting in receivables instead of funding operations. For a $100M revenue company, cutting DSO by just five days frees up roughly $1.37 million in working capital (calculated as ($100M ÷ 365) × 5) that your business can use to reduce credit lines or invest in capacity.
But sustainable DSO reduction doesn't come from working harder or making more calls. It comes from fixing upstream data errors that cause invoices to bounce, policy gaps that let sales promise terms AR never approved, and process bottlenecks that inflate your AR balance even after customers have paid. This checklist gives you the structured, phase-by-phase process to address all of it.
Days sales outstanding (DSO) measures how long it takes, on average, for your company to collect cash after a credit sale. Wall Street Prep defines it as the average accounts receivable outstanding divided by net credit sales, multiplied by the number of days in the period.
The standard DSO formula:
DSO = (Accounts Receivable ÷ Net Credit Sales) × Number of Days in Period
The Corporate Finance Institute defines DSO as the average number of days credit sales take to convert into cash, making it a direct measure of both liquidity and operational efficiency in your order-to-cash cycle.
Why DSO benchmarks matter by industry: CreditPulse's 2025 benchmark data shows manufacturing companies typically carry DSO of 45 to 60 days, while wholesale distribution targets 30 to 50 days. If your DSO sits above these ranges, you're giving customers an interest-free loan on cash your business has already earned. Stuut customers reduce DSO by an average of 37%, according to Stuut's Series A announcement. For a manufacturing company at $200M in revenue with a 55-day DSO, that improvement means converting revenue to usable cash more than 20 days faster.
Most DSO problems don't start in collections. They start weeks earlier, when a customer's AP contact has changed, an invoice went to the wrong address, or no one noticed a $30,000 invoice aging into the 61 to 90 bucket while the team was chasing three large accounts. Phase 1 is about diagnosing exactly where your AR breaks down before you try to fix it.
An invoice that bounces because the AP contact left the company six months ago is an invisible DSO driver. Your team may not discover the bounce for days, and by then the invoice has aged further through no fault of the customer. No collections strategy fixes this if you don't know the invoice never arrived.
Run a report on your last 90 days of email delivery failures. For each bounced invoice, document the customer account, invoice value, how many days elapsed before the bounce was discovered, how the correct contact was eventually located, and the final days-to-payment versus the account average. This analysis gives you a concrete DSO cost that bad contact data is extracting from your portfolio. Intuit's AR guide identifies regular contact data verification as a foundational step before any other collections process improvement can take hold.
Pull your aging report and segment it in two dimensions: by customer size (revenue contribution) and by days outstanding (0 to 30, 31 to 60, 61 to 90, 90 plus). This view answers the question your CFO will ask: is the problem concentrated in a few large strategic accounts, or spread across hundreds of smaller customers your team doesn't have time to contact?
The answer determines your strategy. If the problem is concentrated in the top 20 accounts by value, it's a relationship and dispute management problem. If it's spread across hundreds of accounts in the 31 to 60 bucket, it's a coverage problem. Large AR portfolios structurally exceed what any human team can contact consistently, and coverage problems require automation, not additional headcount.
Pull average days-to-pay for your top 50 accounts and compare it to the contractual payment terms you've extended. If you're offering Net 30 to accounts that consistently pay in 45 to 55 days, you're extending effective credit without pricing it into your terms. CreditPulse's DSO benchmark analysis identifies this misalignment as one of the most common structural drivers of above-benchmark DSO in manufacturing and distribution. Document the gap for each account because you'll need this data in Phase 2 when you renegotiate terms with sales, and the CFO will want to know why extending effective credit without pricing it costs the company working capital.
Phase 2 addresses the upstream decisions that either prevent problems or guarantee they'll repeat next quarter: credit terms, invoice delivery, and sales alignment.
Sales promising Net 60 to close a deal while your credit policy requires a credit check is one of the most expensive AR process failures. It starts a customer relationship with a broken internal process, and AR absorbs the blame when collections friction follows.
Build a governance rule: any payment terms extended beyond your standard policy require written approval from the AR Director before the sales order is confirmed. Implement this as a field in your CRM or ERP order entry screen, not an email thread. The documentation protects AR when disputes arise and gives you an audit trail the Controller can rely on. This alignment reduces the disputes that stall payment and inflate AR simultaneously while damaging customer relationships.
Paper invoices and PDF attachments are the slowest path to cash. For customers using procurement portals like Ariba or Coupa, an invoice not submitted through the portal may sit invisible for weeks before the customer's AP team knows it exists. Run an analysis on your invoice delivery mix:
Each gap in this list adds days to your DSO before collections ever begins.
Extending unlimited credit to a customer with deteriorating payment behavior concentrates risk in accounts most likely to become bad debt. Your aging report from Step 2 will show which accounts trend toward 90-plus day balances consistently. For those accounts, set and enforce credit limits in your ERP. When an account hits its limit, sales should be notified before a new order ships, not after. This isn't about being aggressive with customers. It's about making credit decisions based on payment behavior data rather than relationship history alone, which protects the business and gives AR a defensible position when escalation becomes necessary.
Phases 1 and 2 fix the structural problems and create the conditions for DSO improvement. Phase 3 is where you scale that improvement through autonomous execution. Legacy platforms like HighRadius and Billtrust are designed primarily to remind collectors to take action, while Stuut is designed to execute the work itself, and that difference determines whether DSO improvement scales or stalls. Kolleno's analysis of HighRadius alternatives notes that traditional enterprise AR platforms typically require three to six months to implement and still require collectors to execute tasks the system only flags. The reason most AR teams can't sustain DSO improvement after an initial push is that collector-dependent execution doesn't scale beyond 50 to 100 accounts.
Every reminder email your team hand-writes and sends is time that could go to complex disputes, payment plan negotiations, or relationship management on strategic accounts. Routine dunning, invoice resends, and pre-due date reminders are rule-based and follow predictable patterns. They don't require human judgment. They require consistent execution at scale.
An autonomous AR agent like Stuut handles multi-channel outreach (email, SMS, and voice) based on customer payment history, aging bucket, and invoice value without a collector writing a single email. Razvan Bratu, Head of Quote-to-Cash at Honeywell, describes the outcome directly:
"The platform handles the routine work so our people drive increased real business value." - Razvan Bratu, Head of Quote-to-Cash at Honeywell
Manual collections vs. autonomous collections:
The fundamental difference is capacity. Your team executes high-quality collections on a limited number of accounts. Autonomous agent execute consistent collections across the entire portfolio while your team focuses on the accounts that require judgment, negotiation, or relationship management.
Stuut integrates via API in three to four days without modifying your ERP configuration, as confirmed by Business Partner Magazine's coverage of Stuut's Series A, and starts executing autonomously from day one. Bishop Lifting deployed Stuut across 45 branches and reduced overdue receivables by 35%, freeing the AR team to focus on complex accounts rather than routine follow-ups, according to Stuut's case studies. This outcome shows what autonomous execution means in practice: AI covers volume while humans manage complex relationships and disputes.
A customer pays on day 28, but your team takes time to match the remittance to invoices and post the entry to the subledger. During that lag, those invoices still appear outstanding in your AR balance, artificially inflating DSO even though the cash is already in your bank account. Everworker's cash application research confirms that reliance on labor-intensive matching leads to a build-up of unapplied cash that distorts AR, frustrates customers who receive follow-up calls after they've already paid, and quietly inflates DSO reporting.
Stuut matches payments to invoices automatically and posts cash application entries to the AR subledger in real time, eliminating the posting lag. Extremely complex multi-entity or intercompany payments may still need human review, but the 95%+ automated match rate removes the bottleneck for the vast majority of transactions, and your month-end close no longer depends on a backlog of team-executed matching work.
Emagia's DSO improvement analysis identifies payment friction as a direct contributor to collection delays because customers move difficult invoices to the bottom of the stack. If a customer needs to log into a separate portal, enter a PO number, and locate an invoice they weren't sent a direct link to, you've added steps that delay payment by days. Make paying easy by including direct payment links in all outbound communications, giving customers immediate access to invoice details, and accepting multiple payment methods (ACH, card, check).
Executing the checklist without measuring results means you can't tell the CFO what's working or defend your investment in Phase 3.
DSO measures how fast you collect. The Collection Effectiveness Index (CEI) measures how much of your collectable receivables you actually collect. Mosaic Tech defines CEI with the formula:
CEI = ((Beginning AR + Monthly Credit Sales - Ending Total AR) ÷ (Beginning AR + Monthly Credit Sales - Ending Current AR)) × 100
Per AccountingTools, a CEI of 80% or above is generally considered good, and it measures quality rather than speed. A team that collects fast from easy accounts but ignores the hard ones will show strong DSO but weak CEI, and weak CEI means bad debt risk is accumulating invisibly. Track both monthly and segment CEI by aging bucket. If your CEI in the 61 to 90 day bucket is declining while DSO looks stable, bad debt write-offs are coming within one to two quarters.
Weekly review focused on exceptions improves outcomes. Daily review of the full aging report does not. Set a standing weekly meeting structure:
This structure keeps your team on judgment-required work while autonomous systems handle the remaining portfolio.
Even with a solid checklist, DSO initiatives stall when teams make these four mistakes:
Treating all customers the same: Sending the same dunning sequence to a strategic $2M account and a $500 long-tail account damages the relationships that matter most. Segment your communication strategy by account tier before you automate anything.
Ignoring the long tail: Large AR portfolios structurally exceed what any human team can contact consistently, no matter how well-organized the workflow. The invoices that age out uncontacted are almost always the smaller ones your team never gets to, and they add up. CFO Tech's Stuut coverage describes this as a core reason autonomous AR agent exist: to cover the volume that human teams structurally cannot reach.
Running the initiative without sales alignment: If sales continues to promise custom terms or tells customers disputes are "being handled" without telling AR, your collections process will always chase decisions made without you. The policy governance from Step 4 must be enforced, not suggested, and it requires explicit CFO backing before you launch the initiative.
Measuring DSO in isolation: A DSO reduction achieved by collecting aggressively from customers who then churn is not a win. Track dispute rates and CEI alongside DSO to confirm you're improving collection quality, not just speed. Stuut's comparison of AR automation approaches highlights communication tone adaptation by customer as a core feature that reduces friction while maintaining consistent follow-up. PerkinElmer reduced overdue invoices from 50% to 15% in one year using this model, per Stuut's case studies.
The biggest difference between teams that reduce DSO in 60 to 90 days and teams that talk about it for 18 months is execution capacity. If your team spends 60 to 70% of their time on payment matching, invoice resends, and routine follow-ups, there's no capacity left to run a systematic improvement initiative. The checklist becomes another item that gets attention once a week between urgent tasks.
Stuut's Series A announcement describes how Stuut collected $1.4B across 74 customers in 2025, delivering 40% cash flow gains and 37% faster DSO by executing the work autonomously so AR teams focus on strategy and exceptions. Bishop Lifting's outcome, a 35% reduction in overdue receivables across 45 branches, came from a six-week go-live that required no IT project or ERP modification.
The checklist gives you the structure. Autonomous execution gives you the capacity to run it at scale.
Ready to operationalize this checklist next week? Book a demo to see how steps 7 through 9 run autonomously from day one.
What is a good DSO for manufacturing companies?
CreditPulse's 2025 industry benchmark data puts the manufacturing benchmark at 45 to 60 days and wholesale distribution at 30 to 50 days. If you're consistently above these ranges, the gap is a measurable working capital cost.
How quickly can process improvements and automation reduce DSO?
Teams that clean contact data, fix invoice delivery gaps, and deploy autonomous collections coverage typically see measurable movement within 60 to 90 days. PerkinElmer reduced overdue invoices from 50% to 15% within one year using Stuut's autonomous agent, per Stuut's case study data. Stuut's API integration completes in three to four days without ERP modification, meaning Phase 3 can be running within a week of starting the checklist.
Does consistent automated follow-up damage customer relationships?
No, when done correctly it improves them. Consistent, professional communications reduce customer confusion and the number of disputes that escalate because customers receive timely reminders rather than a sudden aggressive call 30 days after an invoice was forgotten. The damage happens when communications are inconsistent, not when they're systematic.
How do you calculate the working capital impact of a DSO reduction?
Divide annual revenue by 365 to get daily revenue, then multiply by the number of days reduced. For a $100M company reducing DSO by 5 days: ($100,000,000 ÷ 365) × 5 equals approximately $1.37M freed in working capital.
Days sales outstanding (DSO): The average number of days a company takes to collect cash after a credit sale, calculated as (Accounts Receivable ÷ Net Credit Sales) × Days in Period. A lower DSO means faster conversion of revenue to usable cash.
Collection Effectiveness Index (CEI): A percentage measure of how much of your collectable receivables you actually collect within a period. Unlike DSO, CEI measures quality rather than speed, and a CEI of 80% or above is generally considered healthy.
Aging buckets: Categories that group outstanding invoices by how long they've been unpaid: 0 to 30 days, 31 to 60 days, 61 to 90 days, and 90-plus days. Aging analysis helps prioritize collections effort and identify accounts moving toward bad debt risk.
Cash application: The process of matching incoming payments to the specific invoices they're intended to pay and posting the resulting entries to the AR subledger. Delays in cash application inflate DSO even when customers have already paid.
Dunning: The systematic process of sending payment reminders and escalation communications to customers with outstanding invoices, typically in a structured sequence tied to aging buckets.
Remittance advice: Documentation from a customer explaining which invoices a payment is intended to cover, typically including invoice numbers, amounts, and any deductions or adjustments. Matching remittance to invoices is the core task of cash application.
Bad debt provision: An accounting estimate of receivables unlikely to be collected, recorded as an expense that reduces net AR on the balance sheet. Growing provisions signal deteriorating collection effectiveness.
