For most AR teams, debtor days is not just a number on a board pack. It shows up in the pressure of month-end, in overdue balances that keep rolling forward, and in the daily friction of trying to collect cash while handling invoice queries, disputes, deductions and broken promises to pay.
Controllers watch it because it affects working capital and cash flow visibility. CFOs watch it because a rising DSO can signal wider problems across order-to-cash. AR and finance operations teams live it more directly. When the finance inbox is full, disputes are unresolved, and follow-ups are inconsistent, debtor days tends to rise long before anyone discusses it in a meeting.
That is why debtor days matters. It is not simply a collections metric. It is a practical measure of how well the business turns invoiced revenue into cash.
What is debtor days?
Debtor days measures the average number of days it takes customers to pay after an invoice is issued.
It is a core working capital metric because it shows how quickly receivables are converted into cash. For finance leaders, AR teams and shared services teams, that matters because reported revenue does not fund payroll, suppliers or investment. Cash does.
A lower debtor days figure usually points to:
Stronger cash flow
Faster collections
Fewer overdue invoices
Better working capital efficiency
Debtor days is often used interchangeably with DSO. In most finance contexts, they mean the same thing.
Debtor days formula
The standard formula is:
Debtor Days = (Average Accounts Receivable ÷ Revenue) × 365
What each part of the formula means
Average accounts receivable (AR)
This is the average amount customers owed during the period being measured.
Most finance teams calculate it as:
Average AR = (Opening AR + Closing AR) ÷ 2
Revenue
This should be revenue for the same period.
In many B2B businesses, revenue is used as a practical proxy for credit sales because most sales are made on invoice. Where cash sales are material, credit sales is the better input.
365
This represents the number of days in a year. If you are calculating debtor days for a quarter, use 90 or 91. For a month, use the number of days in that month. The key point is that the period used for AR, revenue and days must match.
Step-by-step debtor days example
Here is a realistic example for a mid-market B2B company.
Inputs
Annual revenue: £12,000,000
Opening accounts receivable: £1,500,000
Closing accounts receivable: £2,100,000
Step 1: Calculate average accounts receivable
Average AR = (1,500,000 + 2,100,000) ÷ 2
Average AR = 1,800,000
Step 2: Apply the debtor days formula
Debtor Days = (1,800,000 ÷ 12,000,000) × 365
Debtor Days = 0.15 × 365
Debtor Days = 54.75
Result
Debtor days = approximately 55 days
This means the company takes about 55 days on average to collect cash after invoicing customers.
What debtor days actually tells you
A debtor days figure is useful, but only up to a point. It shows the average time cash is tied up in receivables. It does not explain why.
A business with 55 debtor days may be performing well if most customers are on 60-day terms. Another with the same figure may have a serious collections problem if standard terms are 30 days.
That is why debtor days should be reviewed alongside:
Agreed payment terms
Ageing by overdue bucket
Dispute volume
Deduction trends
Promise-to-pay performance
Customer and regional segmentation
Backlogs in the finance inbox or shared inbox
For AR and finance operations teams, debtor days is rarely just a collections number. It is usually a reflection of how well the wider order-to-cash process is functioning.
6 factors that affect debtor days
Debtor days is shaped by far more than how often the team sends a reminder. In most businesses, the main drivers sit across billing, dispute handling, credit management and everyday AR execution.
1. Payment terms
A business invoicing on Net 60 will usually report higher debtor days than one invoicing on Net 30. That part is expected.
The more important issue is term leakage. If customers routinely pay later than agreed, debtor days rises even when formal payment terms look reasonable.
2. Invoice accuracy
Invoices with missing or incorrect information are often paid late. Common problems include:
Missing PO numbers
Incorrect legal entity details
Wrong tax or VAT treatment
Pricing discrepancies
Missing supporting documents
Incorrect billing contacts
These issues may look small, but they often delay payment more than the follow-up itself.
3. Dispute volume and resolution speed
Disputes are one of the most common reasons invoices remain unpaid. A pricing issue, short payment, service complaint or missing document can stop payment until the matter is resolved.
When disputes are managed through long email threads without clear ownership, debtor days usually starts to drift upwards.
4. Customer mix
A small number of large slow-paying customers can materially skew the overall figure. This is one reason a single blended debtor days number often hides the real problem.
5. Industry and country payment norms
Some sectors and markets have structurally longer payment cycles. Retail, manufacturing, construction and public sector environments often behave differently from SaaS or professional services.
That does not mean higher debtor days should be accepted without question, but it does mean benchmarking needs context.
6. AR workflow maturity
Manual processes, inconsistent dunning, weak invoice inquiry management and poor coordination between AR, sales and operations all slow cash collection.
This often becomes most visible in the finance inbox, where invoice copy requests, remittance queries, deductions, disputes and payment promises all arrive in one place and compete for attention.
Common mistakes when calculating debtor days
Debtor days is straightforward to calculate, but it is also easy to misread.
Using closing AR instead of average AR
A single closing balance can distort the metric, especially in seasonal businesses or around quarter-end. Average AR is usually the better measure because it smooths timing effects.
Mixing time periods
Revenue and accounts receivable must relate to the same period. Annual revenue with month-end AR will produce a number, but not one you should rely on.
Using total revenue when cash sales are significant
If a meaningful share of revenue is paid immediately, total revenue will understate true debtor days. In that case, credit sales is the better denominator.
Ignoring credit notes, write-offs and ledger clean-up activity
Debtor days can appear to improve because old balances were written off or moved, not because collection performance improved. Finance teams need to separate operational improvement from accounting clean-up.
Treating debtor days as an AR-only metric
DSO is influenced by commercial terms, order accuracy, billing discipline, dispute handling, credit decisions and customer responsiveness. AR owns part of the outcome, but not the whole of it.
Relying on a single blended number
A headline debtor days figure can hide the real issue. Segmenting by customer type, region, business unit, payment terms and dispute status usually gives a far more useful view.
How to analyse debtor days properly
Calculating debtor days is the easy part. The harder and more useful task is understanding what is driving it.
A stronger review of debtor days should include:
Segment by payment terms: Compare 30-day, 45-day and 60-day customers separately.
Split disputed and non-disputed invoices: This shows how much delay is linked to issue resolution rather than normal payment behaviour.
Review overdue balances by customer concentration: Large accounts can distort the average quickly.
Track broken promises to pay: A high rate of missed promises usually points to weak follow-up discipline.
Review finance inbox backlog: Unanswered billing queries often sit upstream of delayed cash.
Compare DSO trend with ageing trend: A flat debtor days number can still hide worsening old debt.
For controllers and CFOs, this matters because debtor days is not only a reporting metric. It is also an operational signal.
How AI agents can help reduce debtor days
In many finance teams, debtor days stays high not because nobody is chasing, but because too much of the order-to-cash process is still managed manually through shared inboxes, spreadsheets and disconnected systems.
When the AR inbox becomes the place where everything happens, a familiar pattern starts to form. Customer queries wait too long for a reply. Disputes sit unresolved. Follow-ups depend on who remembers to send them. Payment blockers are hard to see early. Collections becomes reactive rather than controlled.
That is how DSO rises even when the team is working hard.
How Paraglide supports lower debtor days
Paraglide is built for the work that usually slows payment down: billing query responses, collections follow-ups, dispute handling, promise-to-pay tracking, deductions, and more.
These can help reduce debtor days in five ways:
1. Faster responses to customer billing queries
When customers ask for invoice copies, statements, remittance confirmation or clarification on balances, slow responses delay payment. AI agents can triage the request, identify the relevant invoice or account context, and help resolve routine queries faster.
2. Better dispute handling and ownership
Disputes often disappear into inboxes because there is no clear routing, status tracking or follow-up discipline. AI-supported workflows can categorise disputes, route them to the right owner and maintain visibility until resolution.
3. More consistent collections follow-up
Collections performance often drops when follow-up depends entirely on manual effort. AI agents help maintain structured follow-up cadences and reduce missed actions across high invoice volumes.
4. Stronger prioritisation of AR work
Not every invoice needs the same treatment. Prioritising by invoice value, overdue status, customer risk, dispute status and promise-to-pay signals helps AR teams focus effort where it will have the greatest cash impact.
5. Better visibility into what is blocking cash
High debtor days is often the symptom. The underlying issue is usually unresolved operational friction such as invoice errors, disputes, deductions, missing remittance, broken promises or unanswered emails. Better visibility into those blockers makes the DSO number more actionable.
Even a modest reduction in debtor days can have a meaningful working capital impact. For businesses operating at scale, recovering five to ten days of DSO can release a significant amount of cash without increasing AR headcount.
Conclusion
Debtor days is one of the most useful metrics in accounts receivable because it links revenue to cash collection speed. The formula is simple, but the number only becomes useful when it is interpreted in context.
If debtor days is rising, the answer is rarely to chase harder. More often, the root cause sits elsewhere in the order-to-cash process: invoice errors, weak dunning, unresolved disputes, inconsistent follow-up, poor promise-to-pay tracking or a finance inbox that has become too manual to manage effectively.
For AR teams, finance operations leaders and CFOs, reducing debtor days means improving the work that delays payment, not simply reporting the outcome more often.