What is the days sales outstanding formula?
Days sales outstanding formula: DSO = accounts receivable ÷ credit sales × days in the period. Use credit sales only, not cash sales. If you cannot split them, use total sales and label the result.
Enter receivables, credit sales and days, and read DSO, days beyond terms and cash tied up.
DSO = accounts receivable ÷ credit sales × days in the period.
Book a 30-min callOne example, three methods. It is the example loaded in the calculator above. For ERP-based receivables, see our Business Central AR automation work.
| Step | Calculation | Result | Why it matters |
|---|---|---|---|
| Average credit sales per day | $3,600,000 / 90 days | $40,000 | Base for every cash figure on this page |
| Simple DSO (closing AR) | $1,500,000 / $3,600,000 x 90 | 37.5 days | The standard formula. Fast, and the one most teams report |
| Average-AR DSO (opening AR $1,300,000, illustrative) | ($1,300,000 + $1,500,000) / 2 = $1,400,000; $1,400,000 / $3,600,000 x 90 | 35.0 days | Smooths a balance that grew during the quarter |
| Countback DSO (monthly credit sales $1.0M, $1.2M, $1.4M, illustrative) | $1,400,000 covers month 3 (30 days); $100,000 / $1,200,000 x 30 = 2.5 days | 32.5 days | Sales were rising, so the balance sits in recent, larger months |
| Days beyond terms (terms 30 days) | 37.5 - 30 | 7.5 days | Shows how far customers drift past the agreed terms |
| Cash tied up beyond terms | 7.5 x $40,000 | $300,000 | The amount collected late, in dollars |
| Cash released by taking 5 days out of DSO | 5 x $40,000 | $200,000 | What a 5-day improvement is worth in cash |
Opening AR of $1,300,000 and the monthly sales split are added assumptions for illustration. Ending AR, quarterly credit sales, 90 days and 30-day terms are the calculator's inputs. The three methods differ because they treat a changing balance differently, not because one is wrong.
Countback works backward from the closing balance, one month at a time. This example is illustrative.
Closing receivables are $1,500,000. This is the amount you need to explain with recent sales.
Month 1 was $1,000,000, month 2 was $1,200,000 and month 3 was $1,400,000. Together they equal the quarter's $3,600,000.
Month 3 sales of $1,400,000 are fully covered by the balance. That counts as 30 days. Remaining AR: $100,000.
Divide the remainder by month 2 sales: $100,000 / $1,200,000 x 30 days = 2.5 days.
30 days plus 2.5 days gives a countback DSO of 32.5 days.
The simple formula gave 37.5 days. It averages the whole quarter, so it treats the balance as if sales were flat. Countback follows the actual shape, which is why it suits seasonal businesses.
Report one method consistently, and name it on every report.
Simple DSO suits a stable balance. Sales are flat, terms are steady and the closing balance looks like a normal month. It is quick to compute and easy to audit against the ledger.
Average-AR DSO suits a balance that moved a lot during the period. Averaging opening and closing AR dampens a spike at quarter end. It needs an opening balance, so the figure is only as good as that second number.
Countback suits seasonal or fast-growing sales. It asks which sales the open invoices actually belong to, so a heavy final month does not hide old balances.
In the example the three results are 37.5, 35.0 and 32.5 days. The spread is 5 days, worth $200,000 at $40,000 of daily sales. That is why switching methods between reports can show an improvement that never happened.
A practical rule: use simple DSO for the monthly dashboard, countback for the quarterly review, and days beyond terms to decide where collectors spend their time.
Days beyond terms separates two problems that DSO mixes together.
Best Possible DSO (BPDSO) uses only current receivables, the invoices not yet due: BPDSO = current AR ÷ credit sales × days in the period.
Average Days Delinquent (ADD) is the gap: ADD = DSO - BPDSO.
Take the example. Of the $1,500,000 in receivables, $1,200,000 is current and $300,000 is past due (illustrative split).
BPDSO = $1,200,000 / $3,600,000 x 90 = 30 days. That matches the 30-day terms.
ADD = 37.5 - 30 = 7.5 days. The same 7.5 days the calculator shows as days beyond terms, and the same $300,000 of cash tied up.
Reading it: a high BPDSO with a low ADD means your terms are long. A low BPDSO with a high ADD means customers are paying late.
The fixes differ. Terms are a commercial decision. Lateness is a collections and cash application job.
Run the same split per customer. The top five names usually explain most of the delinquent days.
Cash released = daily credit sales × days of DSO reduction.
On $14.4M of annual credit sales, daily sales are $14,400,000 / 365 = about $39,452. Five days is about $197,000 (illustrative).
On the calculator's example, daily credit sales are $40,000. Five days releases $200,000.
Cost of capital turns that into a yearly figure. At an assumed 8% borrowing rate, $200,000 of released cash saves about $16,000 a year in interest. Use your own rate.
Think of it as two numbers. The cash release happens once. The interest saving repeats every year the lower DSO holds.
If the cash repays a revolving line, the saving is that line's rate. If it sits in a bank account, the benefit is the deposit rate, which is usually lower. Show your finance lead the assumption you chose.
One caution on direction. A lower DSO is not automatically better. DSO depends on the terms you grant, so a company on 60-day terms should not be compared with one on 15-day terms.
This page quotes no industry DSO benchmark. We could not tie a figure to a dated primary source, so we left it out. Compare yourself with your own terms and your own trend.
Each ERP holds both numbers. The trap is what sits inside the balance.
Most wrong DSO figures trace back to one of these six.
Start where the days sit. Days beyond terms tells you whether to fix terms or lateness.
→ Dunning on a schedule. Reminders go out before and after the due date, and the ERP's own aging drives them.
→ Payment links on every invoice. Customers pay when it takes one click.
→ Cash application the same day. An unapplied payment looks like an unpaid invoice and keeps DSO high.
→ Dispute tracking. A short pay with no owner stays open for weeks.
→ Weekly review of the top past-due balances, by person, with a note on the next step.
The biggest lever depends on the business. In distribution, many small invoices and frequent short pays make cash application and deductions the main drivers.
In manufacturing, invoices are large and terms are negotiated, so one disputed shipment can add days on its own.
In logistics and 3PL, missing proof of delivery and accessorial charges hold up payment, so attach the documents to the invoice.
In professional services, the clock starts at invoicing, so billing lag never shows in DSO and needs its own measure.
Measure DSO on the same day each period and keep the method fixed. Changing the method mid-year hides real change.
The agent works inside your ERP and CRM. A person approves every action. It does not move money or change a ledger on its own.
It pulls open items and recent invoices from Business Central, Dynamics GP, NetSuite or another ERP and calculates DSO, BPDSO and days beyond terms for each customer.
It writes the reminder from the invoice, the customer history and the last contact, so a person does not rewrite it every time. See Collections and Disputes.
The collector reads the draft, edits it if needed and approves it. Nothing is sent without that step.
It proposes matches from remittance details and bank lines, and flags unclear ones. See Cash Application.
An accountant reviews the proposed applications and confirms them, so the ledger changes under human control.
We connect the agent to your ERP, define the approval points and test against your own aging, using Human-in-the-Loop Agents.
Simple DSO divides closing AR by credit sales and multiplies by the days in the period. Countback works backward from the closing balance month by month. On the worked example, simple DSO is 37.5 days and countback is 32.5 days, because sales were rising. Use countback when sales are seasonal or growing.
It depends on your terms. A useful rule is to compare DSO with your payment terms: DSO close to terms means customers pay on time. A DSO of 45 on 30-day terms leaves 15 days of drift, while 45 on 45-day terms is on time. The same number can be healthy or a problem. We quote no industry figure here because we found no dated primary source we could verify. Use your own trend and days beyond terms.
They measure the same thing in different units. Receivable turnover is credit sales divided by average receivables, in times per period. DSO is the number of days in the period divided by turnover. The example's $3.6M of credit sales on $1.4M average AR gives turnover of about 2.57 per quarter, and 90 / 2.57 is about 35 days.
Put AR in B1, credit sales in B2 and days in B3. Simple DSO is =B1/B2B3. For the average-AR version, put opening AR in B4 and use =AVERAGE(B1,B4)/B2B3. The example gives 37.5 and 35.0.
Use closing AR, the trailing 12 months of credit sales and the actual day count, usually 365. On $14.4M of annual credit sales and $2.4M of AR (illustrative), DSO is $2,400,000 / $14,400,000 x 365 = about 60.8 days. Also track a monthly figure so a change is visible early.
Book a 30-minute call. We will look at your aging, find where the days are, and show how an approval-first agent would work in your ERP.
Facts on this page checked on 20 November 2026.

Founder and CEO

Chief Sales Officer
Thanks, we’ve got your details. A named member of our team will reply within one business day.
Talk to a QServices solutions architect about your ERP. You'll leave with two or three automation ideas you can act on, even if you never work with us.