Average Days Delinquent Calculator
Average days delinquent (ADD) answers a narrower question than days sales outstanding: not “how long until we get paid”, but “how many days past due are we, on average”. It is the gap between your actual DSO and your best possible DSO, the DSO you would post if every customer paid exactly on terms. A business on Net 60 terms with perfect payers has a DSO of 60 and an ADD of 0. A business on Net 15 terms with the same 60-day DSO has an ADD of 45 and a collections problem. Same DSO, opposite story: ADD strips your own payment terms out of the number so only lateness remains.
The calculator below computes ADD three ways: the standard DSO minus best possible DSO method, with both DSO figures computed for you from your receivables and sales; an invoice-weighted average taken straight from an aging report; and a delinquent-balance shortcut that the tool labels honestly as a legacy estimate, not the standard ADD. Every mode ends with the same verdict scale, so the number arrives with its meaning attached.
Or enter DSO and best possible DSO directly
List each past-due invoice from your aging report. Blank rows are ignored, and each amount weights its days, so a large old invoice counts more than a small fresh one.
This shortcut produces delinquent DSO, a rough scale check on the overdue balance. It is not the industry-standard ADD; use the DSO method for the number you report.
Verdict scale used by the result: 10 days or under is healthy for most B2B books, 11 to 30 days deserves a review of the aging report, and above 30 days usually signals a collections problem. Your terms and industry shift the bands; the trend matters more than any single reading.
Quick Answer
Key takeaways
- ADD = DSO − best possible DSO. It measures lateness only, because best possible DSO already contains the effect of the payment terms you granted.
- You do not need DSO precomputed: enter receivables, credit sales, days, and current receivables, and the calculator builds both DSO figures itself.
- Read the trend, not the snapshot. An ADD climbing month over month means the collections process is losing ground even if DSO looks flat.
- The delinquent-balance tab is a legacy shortcut (delinquent DSO), labelled as such in its own result. Report the DSO-method figure.
- Quick Answer
- The standard formula: DSO minus best possible DSO
- Worked example: from receivables to a 38-day verdict
- The other two modes: invoice weighting and the legacy shortcut
- ADD vs DSO, and reading the trend
- What competing calculators miss
- Frequently asked questions
- Add This Calculator to Your Website
- References
The standard formula: DSO minus best possible DSO
Subtract best possible DSO from actual DSO. The remainder is the average number of days invoices sit past due across the whole receivables book.
Best possible DSO is the floor set by your own terms: if every customer paid on the due date, receivables would still be outstanding for the length of the terms, and current receivables are exactly the balance that would remain. That is why ADD isolates the collections function so cleanly. Lengthen your terms from Net 15 to Net 30 and DSO rises mechanically, but best possible DSO rises with it, so ADD only moves if payment behaviour actually changes. The collection-period figure on its own, without the subtraction, is what the average debtor days calculator reports; this page exists for the gap between the two.
Worked example: from receivables to a 38-day verdict
The DSO method tab is pre-filled with this case, and these are the exact lines it returns.
| Step | Working | Result |
|---|---|---|
| DSO | ($25,000 ÷ $15,000) × 30 days | 50.00 days |
| Best possible DSO | ($6,000 ÷ $15,000) × 30 days | 12.00 days |
| Average days delinquent | 50.00 − 12.00 | 38.00 days |
Read the bars as a split of the 50-day collection cycle: 12 days are the terms doing their normal work, and 38 days, more than three quarters of the cycle, are pure lateness. That split is the conversation to have with a collections team. Arguing about the 50 helps nobody; the 38 is the part they control.
The other two modes: invoice weighting and the legacy shortcut
The invoice-weighted mode answers the same question from the bottom up. Weight each past-due invoice's days by its amount, then divide by the total past-due amount: ADD = Σ(days past due × invoice amount) ÷ Σ(invoice amounts). It is the natural mode when you are staring at an aging schedule rather than period totals, and it punishes large old invoices properly, where a simple mean of days would let a $50 invoice at 90 days count the same as a $30,000 invoice at 90 days.
The pre-filled invoice rows make the weighting visible: $1,000 at 15 days, $2,000 at 40 days, $500 at 70 days, and $3,000 at 100 days. The weighted sum is 15,000 + 80,000 + 35,000 + 300,000 = 430,000, the total amount is $6,500, and 430,000 ÷ 6,500 = 66.15 days. The unweighted mean of the same four invoices would be 56.25 days; the $3,000 invoice at 100 days is why the honest figure is higher. Do not confuse either mode with the average days late calculator, which takes the plain mean of days past due across payments with no amount weighting and no DSO framework.
The third tab divides the total delinquent balance by average daily sales: $45,000 ÷ $1,500 = 30.00 days. Older texts call this delinquent DSO. It is a quick scale check on how big the overdue pile is relative to daily selling, nothing more, and the tool says so inside its own result rather than dressing it up as ADD.
ADD vs DSO, and reading the trend
DSO mixes two things, the terms you chose and the lateness you did not. ADD separates them, which is why the pair belongs together in reporting. Watch what happens across a terms change: move a book from Net 15 to Net 30 while customers keep paying exactly as before, and DSO jumps by roughly 15 days while ADD stays put. A dashboard showing only DSO would report a collections collapse that never happened.
The trend is the second use. In a published example from Invoiced, one manufacturer's DSO rose from 60 to 82 days in a month while best possible DSO barely moved, 31 to 32: ADD went from 29 days to 50 days, which correctly pinned the problem on a new dunning process rather than on terms or sales mix. Enter 60 and 31, then 82 and 32, in the direct-entry fields of the DSO method tab and the calculator reproduces both readings. For the wider settlement picture across payables as well as receivables, the average settlement period calculator covers the companion framing.
What competing calculators miss
For this keyword, the striking fact is that the top results are all explainers. Versapay, Chaser, Invoiced, and Altline each present the formula well, and none of them gives you a tool. You are expected to compute DSO and best possible DSO yourself, elsewhere, and then do the subtraction, which is exactly where readers stall.
Winning move 1: the hard steps are done for you. Enter the four raw figures from your ledger and both DSO values are computed inline, with each line shown in the result. Direct DSO entry remains available for teams that already track it.
Winning move 2: one consistent period, enforced. Chaser's otherwise good guide trips over its own method: its DSO step uses the period's 90 days while its best-possible-DSO step switches to annual credit sales times 365. Subtract figures built on different periods and the result is noise. This calculator forces one period, one sales total, and one day count through both halves of the subtraction.
Winning move 3: the shortcut is labelled, not laundered. Plenty of quick tools divide the delinquent balance by daily sales and present the answer as average days delinquent. That figure is delinquent DSO, a different and cruder metric. Here it lives on its own tab with its nature stated in the tab, the prose, and the result itself.
Frequently asked questions
The average number of days invoices are paid past their due date, computed as DSO minus best possible DSO. It isolates lateness from payment terms: a company on Net 60 terms with perfect payers has an ADD of 0, while a company on Net 15 terms with the same DSO has a large ADD and a real collections problem.
The DSO your company would post if every customer paid exactly on terms: (current, not-yet-due receivables ÷ credit sales) × days in the period. It is the floor your terms impose on DSO, and subtracting it from actual DSO leaves only the delinquency component.
No. A negative result means the inputs are inconsistent, most often a best possible DSO larger than the actual DSO, which happens when the two figures were built from different periods or different sales totals. The calculator flags a negative result instead of presenting it as a real reading.
For most B2B businesses, 10 days or under is healthy, 11 to 30 days deserves a review of the aging report, and a sustained reading above 30 days usually signals a collections problem worth fixing. Industries with long customary terms judge against their own history; the trend matters more than any universal line.
An aging report buckets overdue invoices, current, 1 to 30, 31 to 60 days, and so on, and shows where the money sits. ADD compresses the same book into a single average lateness figure you can trend month to month and compare across periods, terms changes, and collections initiatives. Use the aging report to act on accounts and ADD to judge whether the process is working.
The levers that move it: invoice immediately and accurately, send reminders before the due date rather than after, follow up personally in the first week past due, offer a small early-payment discount where margins allow, and tighten terms or require deposits for chronically late accounts. Measure ADD monthly while you change one thing at a time, so you can see which lever worked.
Exclude invoices on hold or under genuine dispute from the receivables inputs. They distort the metric, because their lateness is a negotiation, not a collections failure, and they belong in a separate dispute workflow with its own tracking.
Monthly for most businesses, quarterly at the very least. ADD is a trend metric: a single reading tells you where you are, but three readings in a row tell you whether collections are improving or slipping, and whether a process change did anything.
Add This Calculator to Your Website
References
- Versapay, "Average Days Delinquent Explained" - the standard ADD definition, DSO and best possible DSO formulas, and a worked example. Versapay: Average Days Delinquent Explained. Accessed October 2026.
- Chaser, "Average Days Delinquent (ADD): Formula, Calculation and Reduction Guide" - practitioner treatment of the same three-step method. Chaser: Average Days Delinquent Guide. Accessed October 2026.
- Invoiced, "Average Days Delinquent: Definition, Formula, and More" - ADD in the context of DSO variants, including the month-over-month trend example used in the article. Invoiced: Average Days Delinquent. Accessed October 2026.
- Altline (SOBACO), "What Is Average Days Delinquent (ADD) in Accounting?" - the formula with a compact worked example and interpretation guidance. Altline: Average Days Delinquent in Accounting. Accessed October 2026.
- Investopedia, "Days Sales Outstanding (DSO)" - the reference definition of the DSO component of the ADD formula. Investopedia: Days Sales Outstanding. Accessed October 2026.
- Investopedia, "Accounts Receivable (AR)" - what receivables balances contain, the input side of both DSO figures. Investopedia: Accounts Receivable. Accessed October 2026.
- NetSuite, "What Is Days Sales Outstanding (DSO)?" - DSO calculation and benchmarking in an accounting systems context. NetSuite: Days Sales Outstanding. Accessed October 2026.
- Stripe, "Days Sales Outstanding: What It Is and How to Calculate It" - DSO as a cash-flow health metric for growing businesses. Stripe: Days Sales Outstanding. Accessed October 2026.
- QuickBooks (Intuit), "Days Sales Outstanding: How to Calculate DSO" - small-business guidance on computing and improving DSO. QuickBooks: Days Sales Outstanding. Accessed October 2026.
- Calculator200, "Accounts Receivable Calculator Guide: Formulas and Metrics" - DSO, collection effectiveness index, and ADD presented as one metric family. Calculator200: Accounts Receivable Metrics Guide. Accessed October 2026.