From 45-Day DSO to 22 Days: How to Reduce DSO Without Adding Headcount, an Order-to-Cash Example
To reduce DSO without adding headcount, remove billing lag, invoice errors, slow follow-up and unapplied cash. A worked 45-to-22-day example shows how.

You reduce DSO without adding headcount by removing the delays between a closed deal and cash in the bank that nobody on a lean team has time to chase: invoices sent days late, invoices that are wrong and get disputed, overdue invoices with no follow-up, and payments that sit unapplied. Each of those delays is a handoff between systems, the CRM, the ERP, the inbox and the bank file, and handoffs are what automation and AI agents can take over.
This page walks through an illustrative order-to-cash example, a B2B company moving from 45 days of DSO to 22, to show where the days usually hide and which change removes which days. The company and its figures are an example, not a customer story; use the method on your own numbers.
Where engini fits: engini connects the systems an order-to-cash process runs through: the CRM (Salesforce, HubSpot), the ERP (NetSuite, SAP S/4HANA, SAP Business One, QuickBooks), email, bank and lockbox files, and finance systems behind your firewall. Workflows and AI agents built in engini move a closed deal into the ERP, follow up on overdue invoices, and record what customers reply, with every run recorded. Start with the engini docs index.
Key Takeaways
- DSO measures how many days of sales are sitting in accounts receivable: receivables divided by credit sales, multiplied by the days in the period.
- Most excess DSO comes from four delays: billing lag, days paid late, disputes caused by billing errors, and unapplied cash.
- Each delay is a handoff between systems, so it can be automated without hiring: CRM to ERP, ERP to customer, inbox to ERP, bank to ERP.
- Payment terms set the floor. Automation shrinks the days above the terms; it does not change what you agreed with customers.
- Measure progress with DSO and with average days delinquent, so you can see whether collections or terms are driving the change.
What Is DSO and How Do You Calculate It?
Days sales outstanding (DSO) is the average number of days it takes to collect cash after a credit sale. The standard formula is accounts receivable at the end of the period, divided by credit sales for the period, multiplied by the number of days in the period.
In the example, a B2B company bills $18 million on credit in a 90-day quarter and ends the quarter with $9 million in receivables:
At the same sales, cutting DSO from 45 to 22 days means about $4.6 million less tied up in receivables. That cash is the reason CFOs care about DSO: it is working capital the company does not have to borrow.
Note: DSO moves with sales. A strong last month of the quarter raises receivables and DSO even if collections are healthy, so compare the same periods and watch the trend, not one number.
Where Do the Extra Days Come From?
The extra days come from a small number of delays, and each one has its own cause. DSO is not a strict sum of parts, but breaking it into the stages an invoice goes through is the practical way to see where the days go. In the illustrative example, the average customer terms work out to 15 days (a mix of due on receipt and net 30):
Two things stand out. First, the terms did not move: this example does not ask customers to pay faster than they agreed. Second, the largest single block is days paid late, and on a small team that is almost always a follow-up problem, not a customer problem.
Lever 1: Send the Right Invoice on the Day the Deal Closes
Billing lag and billing disputes shrink when the invoice is created from the deal itself, not retyped from it. In many B2B companies a closed-won opportunity in Salesforce or HubSpot becomes an email to finance, someone creates the customer and the sales order in the ERP, and the invoice goes out days later, sometimes with the wrong price tier or billing contact.
Automating that handoff removes both problems at once:
- A trigger fires when the deal is marked closed won.
- The flow looks up the customer in the ERP and creates it if it does not exist.
- It creates the sales order with the products, prices and terms from the deal.
- It checks the order against the deal (totals, currency, billing contact) and stops with a clear message if anything does not match.
- The ERP's own billing creates the invoice on schedule.
For the full handoff between sales and finance, read our guide to GTM to operations handoff automation. If your contracts mix tiers, amendments or usage, the mismatches that cause disputes are covered in why HubSpot and ERP syncs leak revenue.
Lever 2: Follow Up on Every Overdue Invoice
Days paid late shrink when every overdue invoice gets a timely, specific reminder and a defined escalation, which is exactly the work a team without collections staff skips. Start with what your ERP already does.
Oracle NetSuite, for example, offers the Dunning Letters SuiteApp, which "enables you to set up an automated dunning process in NetSuite to help manage the collection of your accounts receivable, and send reminder letters before payment is due." Dunning levels "define the thresholds for overdue amounts and days overdue, and which letter templates to use for each level," and procedures can be assigned to customers, invoices or invoice groups (Oracle NetSuite: Dunning Overview). If reminder letters are your only gap, turn that on first.
What dunning letters do not do is handle the replies. Collections work is mostly what happens after the reminder:
An AI agent step can read each reply, classify it and take the matching action in the ERP and the CRM, so collectors handle the cases that need a person. For a step-by-step build, see how to build an AI collections workflow without code.
Tip: Escalate by amount and age, not by age alone. A $90,000 invoice 10 days late deserves a call from the account owner before a $900 invoice 40 days late.
Lever 3: Apply Cash the Day It Arrives
Unapplied cash inflates DSO because the invoice still looks open after the customer has paid. It also wastes collections effort, since reminders go to customers who already paid.
The fix is daily matching: bring in the bank or lockbox file and the remittance emails, match each payment to its invoices by invoice number, amount and customer, apply the clean matches, and send the rest to a person with the likely candidates attached. The details, including partial payments and one payment for many invoices, are in the unapplied cash trap.
A 20-Week Rollout, in Order of Impact
A team without spare people should fix the delays in the order that removes the most days for the least effort. This is an illustrative sequence, not a guaranteed timeline; your own volumes and systems set the pace.
- Weeks 1 to 2: baseline. Calculate DSO and average days delinquent for the last four quarters, and split open receivables into the delay buckets above.
- Weeks 3 to 6: reminders and escalation. Turn on your ERP's dunning or a reminder workflow, and route unanswered invoices to the account owner.
- Weeks 7 to 10: replies. Add the step that reads customer replies and records promises, disputes and contact changes.
- Weeks 11 to 14: deal to invoice. Automate the closed-won handoff into the ERP, with the check against the deal.
- Weeks 15 to 20: cash application. Match bank files and remittances daily, and review the exceptions queue weekly.
Collections comes first because days paid late is usually the largest bucket and needs the least integration work. Billing fixes take longer but stop new disputes from being created.
How to Measure DSO Improvement
Measure DSO monthly and pair it with average days delinquent, so you know whether the change came from collections or from a different sales mix. Average days delinquent (ADD) is DSO minus best possible DSO, where best possible DSO uses only current, not-yet-due receivables in the same formula.
If DSO falls but average days delinquent does not, the change probably came from shorter terms or a different customer mix, not from your process.
How engini Supports Order-to-Cash Automation
engini connects the systems an order-to-cash process crosses and runs the workflows and AI agents that move work between them. It does not replace your ERP's billing or dunning; it fills the handoffs around them.
Deal to invoice. In Salesforce, engini triggers on a record created or updated, or in real time from Salesforce outbound messages; in NetSuite it creates, updates, upserts, deletes and gets records (Salesforce and NetSuite connector docs). The tutorial closed won in Salesforce creates the customer and sales order in NetSuite shows the pattern; the same works with HubSpot, SAP S/4HANA, SAP Business One or QuickBooks, and in either direction, for example invoice and payment status back to the CRM.
Collections and replies. Workflows read Gmail or Outlook, and an AI agent step with a model and tools can classify a customer's reply and pass the result to the next step: a promise-to-pay date written to a custom field on the invoice, a dispute record, or a task for the account owner in the CRM. engini reads each system's custom fields and custom objects live.
Cash application inputs. Bank and lockbox files arrive over FTP, SFTP or CSV. For banks, credit unions and finance teams that keep systems and databases on their own servers, the on-prem agent runs inside your network and connects out over HTTPS, so you open no inbound ports.
Control and evidence. Workflow run history shows each run, its status and who ran it. Developers can call the same actions from the REST API, SDKs, CLI or MCP, and a toolset limits an agent to the tools and the connection it may use, for example read-only access to invoices. The audit log can be exported or streamed to your SIEM.
When you do not need engini. If your ERP's dunning covers your reminders, your bank feed already applies payments, and deals reach the ERP through a native sync that works, start there. engini fits when the delays sit between systems, the CRM, the ERP, the inbox and the bank, and nobody on the team has time to carry the work across. See how engini handles order to cash.
Frequently Asked Questions
How do I reduce DSO without adding headcount?
Automate the handoffs that create late days: deal to invoice, reminders and escalation, customer replies, and cash application. Start with follow-up on overdue invoices, which is usually the largest and simplest gain.
Then fix billing accuracy, so fewer invoices are disputed, and match payments daily, so paid invoices stop looking open.
What tools automate collections and escalate overdue accounts?
Your ERP's dunning feature is the first tool to check, for example NetSuite's Dunning Letters SuiteApp. Workflow and AI agent platforms add what letters cannot: reading replies, recording promises and routing disputes.
What is a realistic DSO reduction timeline?
A realistic timeline is one to two quarters for visible change, because DSO lags behind the process. Reminders affect invoices already open; billing fixes only affect invoices issued after the change.
How does reducing DSO with AI work in practice?
In practice, AI agents read the unstructured parts of collections, customer emails and remittances, and turn them into structured updates in the ERP and CRM. The decisions about terms, credit and disputes stay with your team.
Can you reduce DSO without NetSuite?
Yes, the same levers work with any ERP or accounting system, including SAP, QuickBooks and Microsoft Dynamics. What matters is that invoices, payments and customer replies flow into one place on time.