DBT
Days Beyond Terms (DBT) is the average number of days a customer pays after the agreed invoice due date. Unlike DSO which includes the negotiated payment period, DBT isolates the overdue portion of the payment cycle, giving a cleaner view of customer payment discipline.
DSO is the AR team's most-cited metric, but it has a structural limitation: it mixes the negotiated payment period (net 30, net 60, net 90) with the discretionary overdue portion. A customer with net 90 terms paying on day 90 has DSO of 90 but is paying on time. A customer with net 30 paying on day 50 has DSO of 50 but is 20 days late. Days Beyond Terms separates these by measuring only the overdue portion, giving a cleaner read on customer payment discipline.
The standard formula uses paid invoices:
DBT = Average of (Payment Date - Due Date) across paid invoices in the period
A worked example: a customer paid 5 invoices in the month. Days beyond terms for each: 0, 12, 5, 18, 3. Average DBT for this customer this month: 7.6 days. The customer pays roughly a week past due on average.
DBT can also be calculated weighted by invoice amount rather than by count, giving more weight to larger invoices that drive cash position. Weighted DBT is generally more useful for treasury cash forecasting; unweighted DBT is more useful for customer behaviour analysis.
The two metrics answer different questions:
For multi-customer portfolios with different payment terms (some customers on net 30, others on net 90), DBT normalises the comparison and exposes which customers are actually disciplined versus structurally enabled to pay late by their terms.
Mistake 1: Treating DBT as a substitute for DSO. The two metrics serve different purposes. DBT supplements DSO; it doesn't replace it. Treasury still needs DSO for working capital and cash forecasting.
Mistake 2: Using point-in-time DBT. A single month's DBT is noisy due to invoice mix and timing. Trailing 90-day or 365-day DBT is more reliable for trend analysis.
Mistake 3: Ignoring weighting. Unweighted DBT treats a 10,000 euro invoice the same as a 1 million euro invoice. For cash position implications, weighted DBT is more meaningful.
Mistake 4: Not tracking DBT trend by customer. Aggregate DBT is useful but the customer-level trend is where actionable signal lives. A customer shifting from 5 days DBT to 25 days DBT over four quarters signals deteriorating payment behaviour that warrants credit limit review.
DBT is more useful than DSO for collections prioritisation because it normalises for payment term differences:
AI-native AR platforms compute DBT continuously by customer, enabling automated escalation when individual customers shift behaviour.
AI-native collections platforms use DBT as one of multiple signals for risk scoring and collections prioritisation:
Mid-market collections teams typically improve aggregate DBT by 3 to 8 days within 90 days of agentic deployment, with the largest gains coming from earlier intervention on customers shifting from prompt to chronic late payment.
Days Beyond Terms (DBT) is the average number of days a customer pays after the agreed invoice due date. Unlike DSO which includes the negotiated payment period, DBT isolates the overdue portion of the payment cycle, giving a cleaner view of customer payment discipline.
DSO measures the entire AR cycle from sale to collection, including the negotiated payment period (net 30, net 60, etc.) plus any overdue delay. DBT measures only the overdue portion. A customer with net 90 terms paying on day 90 has DSO of 90 but DBT of zero; they are paying on time. DBT normalises for payment term differences.
Healthy DBT typically runs 5 to 15 days for B2B customers. DBT above 30 days indicates significant collection or credit issues. The exact benchmarks vary by industry: CPG selling to large retailers often runs higher DBT structurally because retailers stretch terms; SaaS subscription businesses run very low DBT due to automated billing.
DBT is more useful for collections prioritisation because it normalises for payment term differences. A customer with high DBT is exhibiting payment indiscipline regardless of their negotiated terms. A customer with high DSO but low DBT is simply on long terms; collections effort there is misplaced.
No, the two serve different purposes. DSO is needed for working capital management, CCC analysis, and treasury cash forecasting because it captures the full payment cycle. DBT supplements DSO for collections prioritisation and credit risk monitoring. Best practice uses both.
AI-native collections platforms continuously track DBT by customer, detect behaviour shifts before they become problematic, and adapt dunning sequences to customer payment patterns. Disciplined customers get gentler treatment; chronic late payers get firmer escalation earlier. Mid-market teams typically improve aggregate DBT by 3 to 8 days within 90 days of agentic deployment.