Insights and Updates

Debtor Days: What It Measures and Why It Lags
Best Practices
|
June 18, 2026

Debtor Days: What It Measures and Why It Lags

Debtor days measures how long customers take to pay, the UK term for DSO. Here is how to calculate it, what benchmarks to use, and why it is a trailing metric rather than a real-time credit signal.

Debtor days is the average number of days a business waits to collect payment after issuing an invoice. In the UK, it is the standard term for what US finance teams call DSO (days sales outstanding) and it is calculated the same way. The formula and the limitation are identical: debtor days tells you how long customers took to pay last month. It tells you nothing about whether the customer paying 45 days today will still be paying at 45 days in three months.

What Are Debtor Days?

Debtor days measures the average time between issuing an invoice and receiving payment, expressed in days and calculated from your accounts receivable balance and revenue figures.

Debtor Days = (Accounts Receivable / Revenue) x Number of Days in Period

A business with 200,000 in receivables and 1,000,000 in annual revenue has debtor days of 73, meaning customers take an average of 73 days to pay.

Debtor Days vs. DSO: Same Metric, Different Accent

The calculation is identical. The only difference is geography: UK finance teams say debtor days, US teams say DSO. If you are benchmarking against US data or working with a US-based credit management system, treat DSO figures as equivalent.

Most credit management platforms report this metric as DSO. Our DSO guide covers the same calculation in depth, including how to interpret it by industry.

How to Calculate Debtor Days

There are two common versions.

Method 1: using annual revenue
Debtor Days = (Accounts Receivable / Annual Revenue) x 365

Method 2: using revenue for a specific period
Debtor Days = (Accounts Receivable / Period Revenue) x Days in Period

Method 2 is more accurate for businesses with seasonal revenue, because it avoids distortion from comparing a receivables snapshot against 12 months of revenue that may not reflect current trading conditions.

What Is a Good Debtor Days Number?

It depends on your payment terms. A business with net 30 terms that collects in 35 days is performing well. A business with net 60 terms collecting in 35 days is collecting faster than agreed. The number only means something relative to your stated terms.

General benchmarks by sector:

  • Construction: 50 to 70 days (long project cycles, slower payment culture)
  • Manufacturing: 40 to 55 days
  • Professional services: 35 to 50 days
  • Retail and distribution: 20 to 35 days
  • SaaS and technology: 30 to 45 days

These are medians, not targets. A business running 20 days below its sector median might be collecting too aggressively from customers who should have more breathing room. One running 20 days above might have a single large slow-paying account distorting the average.

The Problem With Debtor Days as a Risk Signal

Debtor days is a trailing metric. By the time it rises, the problem is already 60 to 90 days old. A customer who started paying slowly showed up in your receivables the moment they stopped paying on time. They showed up in your debtor days figure at month end. On a quarterly review cycle, you are reading a crime scene from last quarter.

The teams that catch deteriorating accounts early are not watching debtor days more carefully. They monitor individual accounts: tracking which customers have stretched from net 30 to net 45, which invoices are paid in the final days of the grace period, which accounts have started disputing amounts they never disputed before.

Aggregate metrics like debtor days are useful for board reporting. They are not useful for credit decisions.

How to Improve Debtor Days

Tighten credit terms at onboarding. Many businesses extend 60-day terms by default because the sales team is under pressure to close. A structured credit application process that assesses payment history and financial health before agreeing terms takes this out of the salesperson's hands. If a customer's risk profile justifies net 30, start there.

Send invoices immediately. Debtor days starts the moment an invoice is issued, but some teams batch invoices at month end. That decision adds 15 days to debtor days before a single customer has done anything.

Follow up before due dates, not after. A reminder sent three days before an invoice is due is not aggressive. An AR team that only follows up after an invoice is overdue concedes 30 days of collection time before a single invoice is late.

Resolve disputes faster. A customer who disputes an invoice stops the payment clock until the dispute clears. Finance teams that let disputes sit for two weeks because the account manager is out of office add 14 days to debtor days on every disputed invoice.

Monitor accounts individually, not just in aggregate. A flat debtor days number can hide a portfolio where 90% of customers pay in 28 days and 10% pay in 120 days. The aggregate looks fine; the credit risk is concentrated in that 10%. Accounts receivable management at the customer level is where the actual risk work happens.

Debtor Days vs. Creditor Days

Creditor days measures the opposite: how long your business takes to pay its own suppliers. The US equivalent is days payable outstanding (DPO). A business with debtor days of 45 and creditor days of 60 collects in 45 days and pays in 60. That 15-day gap is a cash flow benefit from the payment cycle.

Our DPO guide covers this in full, including how to calculate it and what it signals to suppliers assessing your creditworthiness.

How Credit Pulse Tracks This

Credit Pulse pulls accounts receivable aging data continuously and surfaces individual accounts that are drifting toward late payment before they appear in your aggregate debtor days figure. The shift is from reading last month's number to acting on this week's signals.

Most credit management platforms, including HighRadius, Bectran, and NetNow, report DSO or debtor days at the portfolio level. The metric appears; the account-level signal does not. Knowing your debtor days is 48 does not tell you which three accounts drove the number up this month.

Frequently Asked Questions

What is the difference between debtor days and DSO?

No difference in calculation or meaning. Debtor days is the term used in UK and Commonwealth accounting. DSO (days sales outstanding) is the US equivalent. Both measure average time to collect payment from customers after invoicing.

What debtor days figure is considered good?

Good relative to your payment terms. If you sell on net 30 terms, debtor days of 32 to 38 is solid performance. Debtor days of 65 on net 30 terms points to a collection problem, a disputes backlog, or financially stressed customers. Compare to your stated terms first, then to your sector median.

How do you reduce debtor days?

Send invoices immediately, follow up before due dates rather than after, resolve disputes without delay, and review credit terms at onboarding rather than extending 60-day terms by default. The fastest improvement usually comes from fixing the dispute resolution process, where invoices can sit unpaid for weeks over a minor discrepancy.

Can debtor days be too low?

In theory. If debtor days sits well below your stated terms, you may be collecting faster than customers agreed, which creates friction. In practice, most finance teams are not concerned about collecting too fast. The more common issue is that very low debtor days reflects a customer base on very short terms, which can limit sales to credit-constrained buyers.

Is debtor days the same as debtor collection period?

Yes. Debtor days, debtor collection period, and average debtor days all refer to the same metric. The terminology varies by textbook and region but the formula is identical.

Jordan Esbin

Founder & CEO
Related Articles

Transform your credit process today.

Meet with our team or try us free for 30 days.

Book a Demo
White six-pointed starburst shape on a black background.White six-pointed starburst shape on a black background.