Number of Overdue Accounts KPI

Number of Overdue Accounts serves as a critical cost control metric that reflects the financial health of an organization.

High overdue accounts can lead to cash flow constraints, impacting operational efficiency and strategic alignment.

By tracking this KPI, companies can improve forecasting accuracy and enhance data-driven decision-making, ultimately driving better business outcomes.

How Number of Overdue Accounts Connects to Your Strategy

Number of Overdue Accounts is one of the few metrics that sits on both sides of the same ledger. It belongs to KPI Depot's Accounts Payable KPI group, whose priority order is led by Days Payable Outstanding (DPO), Payment Timeliness, and Payment Accuracy, then Invoice Processing Time, Cost per Invoice Processed, Average Payment Period, Accounts Payable Turnover, and Number of Invoices Processed per Month. It also belongs to the Accounts Receivable KPI group, where Days Sales Outstanding (DSO) leads, followed by Collection Efficiency, Average Collection Period, Receivables Turnover Ratio, Cash Conversion Efficiency, Payment Delinquency Rate, Write-Off Rate, and Bad Debt to Sales Ratio. In payables an overdue account is one the business has failed to pay. In receivables it is one that has failed to pay the business. Same name, opposite owner, opposite remedy, and anyone pulling this KPI onto a finance dashboard should be explicit about which of the two they mean.

It ranks eleventh in the Accounts Payable priority order and eighteenth in Accounts Receivable, so it is a supporting metric in both groups and a further-back one in receivables. The Accounts Payable group still singles it out in its own summary of headline KPIs, where the instruction is to compare Payment Timeliness against the Number of Overdue Accounts to see whether late payment is systemic or a handful of exceptions. That is a diagnostic role, not a headline one. The count is most useful as the thing that explains a movement in a higher-priority metric.

Its balanced scorecard placement is the customer perspective, which is worth pausing on because the counterparty differs by group. In payables, the party whose experience the metric describes is the supplier. In receivables it is the account holder who owes. Either way the customer perspective puts this KPI in a lagging position relative to the internal process metrics in each group: Payment Timeliness and Invoice Processing Time in payables, Collection Efficiency in receivables. It confirms what those metrics predicted rather than warning ahead of them.

The sharpest tension in the Accounts Payable group is with Days Payable Outstanding (DPO), the group's top-priority metric. Stretching DPO to hold cash longer works by paying later, and past a point paying later means paying past the due date, so the group's leading financial metric can improve precisely by driving this count up. The group's own best-practice guidance flags the same trap from the supplier side, warning against reading DPO without watching vendor satisfaction. The reconciling read is straightforward: DPO extended through renegotiated terms leaves this count flat, while DPO extended by simply paying late shows up here within a cycle or two.

In the Accounts Receivable group the tension is with Write-Off Rate. A written-off account stops being overdue, because it stops being an account. A collections team that clears aged balances by writing them off improves this count while Write-Off Rate and Bad Debt to Sales Ratio both deteriorate. Payment Delinquency Rate is the metric in the same group that reconciles the two, since it carries a denominator and therefore cannot be improved by shrinking the population it is measured over.

Measuring Number of Overdue Accounts in Practice

The count comes off the aging report on a subledger, payables or receivables, and it inherits every weakness in the open item table underneath. Two joins do most of the damage. The first is open items to the vendor or customer master: where that master holds duplicate records for one counterparty, a legacy record kept alive for a closed division, or a second setup under a slightly different legal name, a single overdue counterparty presents as several. Match on the master account identifier, never on name. The second is invoices to their payment terms. Terms often live on the master record while individual invoices carry an override, and a report that reads the wrong one computes the wrong due date for exactly the renegotiated and disputed items a reader most wants to see.

Five definitional forks decide the size of the number before any measurement happens.

• The aging threshold. Is an invoice overdue the day after its due date, or only once it clears the first aging bucket? Both are defensible. A count built on the first is much larger and much noisier than one built on the second, because it captures ordinary payment run timing as delinquency.
• The anchor date. Past due measured from the due date, or from the invoice date. Where invoices are received or entered days after they were issued, the two definitions disagree most about the accounts that matter, and a receivables ledger with inconsistent invoice dating will produce a stable-looking count that hides a real drift.
• Disputes and credit holds. An invoice held pending a genuine dispute, or a vendor account frozen on credit hold, is unpaid but is not a payment decision. Leave those in and the metric measures billing quality and dispute handling as much as payment behaviour. Take them out and the dispute queue becomes a convenient place to park bad news.
• Partial payments. Does an account carrying a part-paid invoice count as overdue, and does the size of the residual matter? Aging reports usually keep the item open at its remaining balance, which quietly holds small residuals in the count long after the substance of the transaction was settled.
• The unit of count. The formula names accounts, but nearly every system reports on invoices. One customer sitting on many overdue invoices is either one overdue account or a long list of overdue items, and the same underlying data will give two numbers that are not close to each other.

Then there is the structural problem: this is a count with no denominator, so it moves with the size of the base it is drawn from. Win new customers or onboard new suppliers and the count rises with no change in payment discipline. Prune dormant records out of the master and it falls without a single payment arriving. Report it beside a rate, and the Accounts Receivable group already supplies the right companion in Payment Delinquency Rate, or at minimum beside the count of active accounts, so growth and housekeeping stay visible.

Segmentation should follow exposure, not tidiness. Many small overdue accounts and one very large one are not the same problem, and a count treats them identically, so break it out by aging bucket and by balance band. Split it by cause as well: accounts late because of a dispute, a missing purchase order reference, or a billing error need a different intervention from accounts late because the counterparty is short of cash. Where a shared service centre runs several ledgers, segment by legal entity and currency too, since standard terms often differ per entity and a blended count hides which one is deteriorating.

The instrumentation traps are mostly about timing and about items that are settled in substance but open in the system. A count taken the day before the weekly payment run and one taken the day after describe the same operation and disagree, so fix the snapshot date and hold it. Unapplied credit memos and unallocated cash receipts are the most common reason the count looks worse than the cash position, because the invoice stays open until someone matches it. Postings that land during close arrive after the snapshot and land in the wrong period. And watch removals: moving an aged balance onto a payment plan, consolidating it into a new invoice, or writing it off all take an account out of the count with no cash collected, so track removals by reason next to the count itself or the metric can be improved administratively.

Common Pitfalls

Overlooking the nuances of overdue accounts can lead to misinformed strategies that exacerbate cash flow issues.

• Failing to segment overdue accounts by customer type can obscure underlying issues. Different segments may require tailored approaches to collections and risk assessment.
• Neglecting to analyze trends over time can mask persistent problems. Regular variance analysis helps identify patterns that warrant deeper investigation.
• Inadequate communication with customers about payment terms can lead to confusion and delays. Clear expectations and reminders can significantly reduce overdue accounts.
• Ignoring the impact of economic conditions on customer behavior can skew expectations. External factors often influence payment patterns, necessitating adjustments to credit policies.

Improvement Levers

Enhancing overdue account management involves proactive strategies that address both customer behavior and internal processes.

• Implement automated reminders for upcoming and overdue payments to enhance collections efficiency. Timely notifications can significantly reduce overdue accounts.
• Regularly review and adjust credit policies based on customer payment history. Tailoring terms to risk profiles can mitigate future overdue accounts.
• Invest in training for collections teams to improve negotiation skills and customer interactions. Well-trained staff can foster better relationships and expedite payments.
• Utilize business intelligence tools to analyze overdue account data for actionable insights. Data-driven decision-making can lead to more effective collections strategies.

KPI Depot is trusted by consulting, strategy, finance, and analytics teams at leading organizations worldwide, including those listed below.

Number of Overdue Accounts Benchmarks

We have 3 relevant benchmarks in our benchmarks database.

Browse the Top Benchmarked KPIs in Accounts Payable

Reading the Benchmarks for Number of Overdue Accounts

Three sources are tracked for this KPI: Creditsafe, Intrum, and IDC / Dun & Bradstreet. Before comparing them to each other, there is a mismatch with the KPI itself that matters more. This KPI's formula is a plain count of accounts. All three tracked records carry a metric type of average, and all three are computed over populations of invoices rather than accounts. So none of them publishes the quantity this KPI defines. An invoice and an account are different units: one account holder can carry many open invoices, and any figure averaged across invoices leans toward whoever bills most often. Importing one of these figures as a target for a count of overdue accounts means crossing two unit changes at once, from a rate to a count and from invoices to accounts.

The populations then differ from each other. Intrum's report is explicitly restricted to business-to-business invoices at small and mid-sized companies. Creditsafe and the IDC / Dun & Bradstreet material both describe their population simply as invoices, cross-industry and mixed company size, which leaves room for consumer and large-enterprise portfolios inside the same figure. Company size is not a cosmetic dimension here, because credit control capacity scales with it. A small supplier chasing a much larger debtor works with different terms, less leverage, and often nobody dedicated to collections at all.

The measurement methods diverge more than the numbers would suggest. Intrum's European report is built from a survey of companies, so what it captures is what finance leaders say about their own payment experience. The IDC and Dun & Bradstreet material draws on trade payment records observed across a very large commercial business file. Self-reported lateness and observed lateness are not the same measurement, and they fail in opposite directions: survey responses are subject to who chose to answer and to how a respondent's own systems define past due, while observed trade data is limited to the transactions that get reported into it. Neither is wrong. Averaging them together is.

Geography changes the contractual clock the metric is measured against. Creditsafe's records cover the United States, Intrum's cover Europe, and the IDC / Dun & Bradstreet material is global. Standard payment terms and statutory late payment rules differ by country, so overdue does not start at the same point in each. A global figure blends jurisdictions where roughly a month is the default term with ones where far longer terms are normal commercial practice, and it also blends places where late payment interest is statutory with places where it is only ever contractual.

Vintage is a real issue for a metric this sensitive to credit conditions. Intrum's edition in this set predates the other two, and the period it describes was shaped by pandemic-era support schemes and supplier forbearance. The later Creditsafe and IDC / Dun & Bradstreet material sits in a different credit environment. Payment behaviour can shift inside a couple of quarters when credit tightens, so a year of separation between reports is not a rounding detail.

The last thing to check is the one none of these records answers. Not one of the three tracked rows carries a stated formula, which means the record itself cannot tell a customer what counted as overdue: the threshold in days, whether lateness was measured from the invoice date or the due date, and whether disputed invoices stayed in. Those choices move a late-payment figure more than industry mix does. Read each publication's own methodology notes before treating any two of these as comparable, and treat source, population, geography, and date as part of the figure rather than as labels attached to it.

OKRs That Use Number of Overdue Accounts

The Accounts Payable KPI group names this KPI in its own OKR material. Under the objective to elevate vendor experience through reliable and transparent payment operations, reducing the Number of Overdue Accounts appears as a key result beside Payment Timeliness, Vendor Satisfaction with the Billing and Payment Process, and the group's aging of accounts payable key result. The group's stated rationale is that consistent on-time payment and fewer overdue accounts build vendor confidence, while aged payables strain relationships and risk service interruption. A team adopting that framing is better served by a directional key result, bringing the number of overdue vendor accounts down across the quarter, than by a fixed target, and it should hold Payment Accuracy flat at the same time, since the group's guidance warns that clearing a payment backlog in a hurry raises error rates.

The Accounts Receivable KPI group does not name this KPI in any of its key results, but one of its objectives is the natural home for it: minimize credit risk by proactively managing delinquency and bad debt, which already carries Payment Delinquency Rate and Write-Off Rate. Used there, the count is the operational companion to the rate. The rate says how much of the ledger is late; the count says how many conversations that represents, which is what actually sizes a collections team's week. Pairing a directional key result on reducing overdue customer accounts with that objective's existing Write-Off Rate key result also closes the obvious loophole, where the count falls because balances were written off rather than collected.

See OKR Examples for Accounts Payable

Free Whitepaper

Want to achieve performance excellence in Accounts Payable? Download our in-depth whitepaper: Definitive Guide to Accounts Payable KPIs.

Download the Free Guide

KPI Categories

This KPI is associated with the following categories and industries in our KPI database: