Get a personalized demo of Stuut and see how it can help with AR automation.
Most AR teams obsess over which customers pay late while ignoring the operational gaps that make every invoice slower to collect. Missing PO numbers, outdated AP contacts, unapplied cash sitting in a lockbox, and manual payment matching that delays month-end close all inflate your Days Sales Outstanding (DSO) before a single customer picks up the phone.
By diagnosing the specific bottlenecks in your order-to-cash process, from incomplete remittance data to coverage gaps in your collections cadence, you can deploy autonomous AI to handle the routine work and reduce DSO by up to 37%.
Days Sales Outstanding (DSO) measures how long it takes your company to collect cash after a sale. For manufacturers and distributors, where cash funds production cycles and inventory, every extra day of DSO is working capital tied up in invoices you've already earned but haven't collected.
The standard DSO formula is:
DSO is typically calculated as: (Accounts Receivable / Total Credit Sales) x Number of Days in the Period
For example: a company with $50,000 in average AR and $280,000 in credit sales over a 90-day quarter calculates DSO as ($50,000 / $280,000) x 90 = 16 days. If AR climbs to $150,000 while sales stay flat, DSO jumps to 48 days and your cash conversion cycle triples.
DSO benchmarks vary by industry, so comparing your number to the wrong baseline misleads decision-making. Based on 2025 DSO benchmark data, the most recently published industry figures available at time of writing, here are the ranges to measure yourself against:
If your DSO sits above these ranges, the six causes below are where to start your investigation. The DSO by company size guide covers mid-market and enterprise comparisons in depth.
Inaccurate invoices are highly preventable and far more common than most AR teams realize. When an invoice arrives with a wrong purchase order number, a mismatched ship-to address, or an incorrect line item, the customer's AP team sets it aside. It sits in a queue until someone on your side tracks down the discrepancy and resubmits, adding weeks to your collection cycle before collections even begins.
Common invoice delay causes include wrong or missing PO numbers, invoices routed to the wrong department, incorrect dollar amounts from manual data entry, and missing payment terms. Getting invoices to the right AP contact on the first attempt is the fastest fix, and this pre-submission checklist prevents most rejections:
Vague payment terms create ambiguity that customers exploit, intentionally or not. "Net 30" without a clear start date, a late payment penalty, or an accepted payment method leaves room for short-pays. Customers who apply early payment discounts without notification generate deductions your team then has to investigate and reconcile manually.
Review your existing contracts for these common vague phrases: "Payment due upon receipt" (no calendar date), "Net 30" without specifying from invoice date or receipt date, "Standard terms apply" with no attached schedule, and discount clauses without a cutoff date. Replace these with a specific due date calculation, a late payment penalty, accepted payment methods, and a precise discount window. State these on every invoice, not just in the master agreement.
Align sales and AR before a contract is signed. Sales reps who offer extended terms or custom discount schedules without notifying AR create deductions that look like disputes but are simply undocumented agreements. The DSO improvement checklist covers the full order-to-cash alignment process if you want a step-by-step implementation guide.
Some customers are slow payers by design, running approval chains that add weeks to every payment cycle. These factors exist, but the more common problem is that your AR team doesn't have the capacity to follow up consistently, so routine slow payers slip past 60 days without a single outbound contact.
Pull your aging report and segment it by days outstanding. For every account sitting in the 61-to-90 day bucket, check the communication log: how many outbound touches has your team made? In most mid-market AR teams, smaller accounts in the long tail of the portfolio receive zero follow-up because the team is too busy working the top accounts. These aging invoices aren't customer behavior problems. They're a coverage problem.
Customer portals like Ariba, Coupa, and Tungsten add friction to your submission process. Logging in, navigating to the correct vendor account, uploading the required invoice format, and confirming submission multiplies across a portfolio and consumes a meaningful share of every analyst's week.
When a customer disputes an invoice, the manual process is slow by default: your team identifies the dispute, creates a case record, attaches backup documentation, routes it to the right internal contact, and waits.
Stuut helps manage dispute cases by categorizing them by reason code, attaching supporting documentation, and routing them into your existing workflow systems. More importantly, the dispute data surfaces upstream problems: pricing errors from specific sales reps, recurring shipping delays, damaged goods patterns. These insights help finance teams fix the root cause, not just the invoice.
Payment history analysis identifies which customers consistently pay late, so you can contact them earlier in the cycle, before the due date. Stuut's self-learning intelligence tracks these patterns automatically and adjusts outreach timing accordingly, without manual rule updates.
Manual dunning is the single biggest contributor to high DSO for AR teams with flat headcount. When revenue grows but team size stays flat, smaller accounts go uncontacted. Invoices age past 60 days not because customers refused to pay, but because nobody called.
Before you rebuild your collections process, answer these diagnostic questions:
Stuut contacts customers before invoices go overdue, sending reminders across email, SMS, and AI-powered voice calls based on each customer's communication preferences and account history. As documented in the Stuut Series A announcement, Andreessen Horowitz described this capability as AI agents that handle routine invoice outreach at scale so collections teams focus on judgment-based work like disputes, payment plans, and strategic accounts. Voice calling is a specific differentiator because Stuut's call agent pulls customer account context and payment history into each outreach, so calls are informed by what's actually happening on the account rather than following a generic script.
For a deeper look at how each channel contributes to faster collection cycles, the AI and DSO improvement guide walks through the multi-channel approach in practice.
Segment your portfolio into three tiers: high-value accounts that require human attention, mid-tier accounts where AI-assisted outreach covers the routine cadence, and long-tail accounts where AI handles all routine contacts independently. Bishop Lifting applied this approach across 45 branches and achieved a 35% reduction in overdue receivables within seven months.
DSO alone doesn't tell you whether your collections team is performing well or whether portfolio composition changed. The Collection Effectiveness Index (CEI) is a more reliable measure: CEI = ((Beginning Receivables + Monthly Credit Sales - Ending Total Receivables) ÷ (Beginning Receivables + Monthly Credit Sales - Ending Current Receivables)) × 100. Higher CEI percentages generally indicate more effective collections. Tracking DSO alongside CEI and aging bucket distribution gives you a complete picture of where your collection process breaks down.
Unapplied cash is one of the most underestimated drivers of high DSO. When a payment arrives without remittance detail, or when a bulk wire covers 40 invoices without specifying which ones, your cash application team has to research the match manually. Until that research is complete, the invoices stay open, inflating your AR balance and giving finance a distorted view of cash flow.
Manual payment matching remains a significant challenge for AR teams. Checks sent to lockboxes arrive with missing invoice information and custom file formats. Electronic payments require pulling remittance from email attachments and entering it manually. A single bulk deposit covering dozens of transactions can consume hours of manual work before month-end close can proceed.
Stuut's cash application engine matches payments to invoices using bank data, remittance files, and ERP invoice records simultaneously. It learns remittance patterns to handle scenarios including partial payments and short-pays. The target is a 95%+ automated match rate, which means cash application takes minutes instead of days and month-end close no longer waits on manual reconciliation.
To build toward automated cash application:
Bad customer master data wastes collection effort systematically. Invoices sent to outdated email addresses never reach AP. Collection calls go to contacts who left the company years ago. Duplicate customer accounts split payment history across multiple records, making credit limit enforcement unreliable.
Customer data decays over time as contacts change roles, companies update email domains, and AP departments restructure, which means a portfolio that was clean 12 months ago likely has outdated records today.
If your 61-to-90 day aging bucket is growing despite consistent outreach, run a simple check: for every invoice in that bucket, how many outbound attempts bounced or went unanswered? High bounce rates point directly to stale contact records.
Stuut's self-learning intelligence updates contact preferences automatically based on response patterns, tracking which AP contacts respond to email versus SMS and which portal credentials still work. This institutional knowledge, which currently lives in analysts' heads and personal spreadsheets, gets captured in the system and improves every future interaction.
Static Excel exports pulled from the ERP at end of day are a lagging indicator of what happened yesterday. A real-time exception dashboard shows which accounts the AI is actively working, which require human escalation, and which have gone silent.
This shifts your team from reacting to an aging report to managing a live queue of exceptions that actually need judgment. The AR platform comparison checklist includes dashboard requirements to evaluate against any platform you're considering.
Use this table to map your symptoms to the most likely root cause:
Hiring more AR analysts provides short-term relief but creates long-term scaling problems. Adding new AR staff involves significant ongoing compensation costs, and new hires require months to build the institutional knowledge your current team carries.
Autonomous AR automation processes your full account portfolio from go-live, scales without additional headcount, and becomes more accurate over time as it analyzes historical payment patterns across your customer base. The Stuut vs. HighRadius comparison details how implementation timelines and autonomy levels differ if you're evaluating platforms.
Stuut runs at mid-market and enterprise scale without requiring separate implementations or additional headcount. Bishop Lifting rolled out across 45 branches and reduced overdue receivables by 35%, while PerkinElmer collected $300M and cut overdue invoices from 50% to 15% in one year, and Honeywell uses Stuut to cover high-volume routine collections across its quote-to-cash function, which means the same approach that works for a regional distributor also holds at global industrial scale.
A sudden spike in DSO doesn't always signal a collections problem. Revenue fluctuations directly impact DSO calculations: when revenue surges, DSO can increase temporarily even when collection performance remains consistent. Before escalating to leadership, check whether the DSO increase tracks a revenue spike, and look at CEI alongside DSO to separate formula effects from genuine collection slowdowns.
Standard AR platform implementations typically require significant time before delivering measurable results. Stuut's API integration with SAP, Oracle, NetSuite, or Dynamics completes in three to four days for standard ERP environments. PerkinElmer reduced overdue invoices from 50% to 15% in one year using Stuut's AI-powered collections approach. For a full comparison of implementation approaches, the Stuut vs. Versapay implementation guide covers team adoption and change management in detail.
The concern that AI will replace AR analysts or damage customer relationships is understandable, but the data from live deployments shows the opposite. Razvan Bratu, Honeywell's Quote to Cash lead, described the shift directly:
"We're collecting faster from the in-scope customers, our cash flow is improving, and our team has more time to focus on white gloves service for top customers. The platform handles the routine work so our people drive increased real business value."
The practical shift looks like this:
Stuut handles routine account outreach, covers the long tail your team never reaches, and escalates situations that require human judgment such as payment plan negotiations, complex deductions, and VIP relationship calls. Your institutional knowledge of your customer base makes you more effective at those escalations, not less relevant.
Over $1B collected to date across customers including ZoomInfo, Bishop Lifting, Honeywell, and PerkinElmer. 40% average cash flow increase. 37% reduction in past-due AR. 70% reduction in manual tasks. These come from live deployments, not projections.
Book a demo with the Stuut team to see how the AI handles routine collections autonomously and walk through what your team's exception queue would look like after go-live.
While DSO targets in manufacturing vary based on customer mix, contract terms, and order complexity, keeping collections under 60 days is a common goal. If your DSO is above 60 days, the six causes in this article are the most likely operational drivers to investigate first.
Stuut's onboarding completes in three to four days for standard ERP environments, with full go-live in six to ten days. PerkinElmer reduced overdue invoices from 50% to 15% in one year, and Stuut customers see an average 37% DSO reduction across live deployments.
No. AI handles the repetitive tasks: routine dunning emails, portal submissions, payment matching, and invoice re-sends. Your role shifts toward the work that requires judgment: complex dispute negotiations, payment plans, VIP account relationships, and credit analysis. Honeywell's Head of Quote to Cash describes the team as having "more time to focus on white gloves service for top customers" after deploying Stuut.
DSO measures how many days it takes to collect receivables on average, while the Collection Effectiveness Index (CEI) measures how much of collectible receivables were actually collected in a period. Top-performing AR teams target a CEI of 90%+ as a benchmark for strong collection performance.
Days Sales Outstanding (DSO): The average number of days it takes a company to collect payment after a sale. Higher DSO means more cash tied up in unpaid invoices.
Cash application: The process of matching incoming payments to the correct open invoices in your ERP. Manual cash application is the most common cause of unapplied cash and month-end close delays in mid-market AR teams.
Remittance data: Information provided by a customer alongside a payment that identifies which invoices the payment covers. Incomplete or missing remittance data is the primary cause of unmatched payments and inflated DSO.
Collection Effectiveness Index (CEI): A KPI that measures the percentage of collectible receivables your team actually collected in a period. Formula: [(Beginning AR + Credit Sales - Ending AR) / (Beginning AR + Credit Sales)] x 100. A more reliable measure of collection performance than DSO alone.
