There is no single healthy accounts-receivable aging percentage or days sales outstanding (DSO) target for every business in an industry. A useful benchmark compares receivables with a peer group that has similar payment terms, customers, billing practices, and receivable types, then investigates material changes from that comparable baseline.

Start with consistent measures

An accounts-receivable aging report groups unpaid trade invoices by how far they are from their contractual due dates. DSO estimates the average number of days it takes to collect sales. Both measures are useful only when the numerator, denominator, time period, and definition of “past due” are applied consistently.

Core measures for an accounts-receivable benchmark
MeasureSimple calculation or viewWhat it can show
DSOAverage trade receivables divided by net credit sales, multiplied by days in the periodWhether the collection cycle is changing over time
Current receivables shareBalances not yet due divided by total trade receivablesHow much of the balance remains within agreed terms
Past-due aging mixBalances in each past-due bucket divided by total trade receivablesWhere delinquency is concentrating
Dispute and exception rateReceivables flagged for a dispute, credit hold, deduction, or other exception divided by trade receivablesWhether an operational issue may be delaying collection

For example, a business with annual billing or pronounced seasonality should not compare a month-end receivable balance with an annual sales denominator without checking whether the timing makes the ratio misleading. Use average receivables where appropriate, document the calculation, and keep the same approach for internal trend analysis and peer comparisons.

Why broad industry targets can mislead

A sector label is not enough to establish a fair DSO target. Two companies in construction, staffing, manufacturing, wholesale distribution, or subscription software can have very different contractual terms, customer concentration, invoicing cadence, and dispute patterns. A benchmark should therefore be segmented before it is interpreted.

  • Construction and engineering: separate ordinary trade invoices from retainage, unbilled contract amounts, and claims whose realization is uncertain. For registrants subject to SEC Regulation S-X, the balance-sheet rule specifically calls for separate disclosure of certain long-term-contract receivables, including retainage and billed or unbilled amounts subject to uncertainty. See 17 CFR § 210.5-02.
  • Staffing and professional services: group receivables by client type, billing frequency, payment terms, and whether time approvals or purchase-order exceptions commonly delay invoices.
  • Manufacturing and wholesale: distinguish customers, channels, and agreed terms rather than combining short-cycle sales with strategic accounts that have longer negotiated terms.
  • Subscription software and other recurring-revenue models: separate invoiced trade receivables from unbilled contract assets and consider the payment method and billing interval when building the peer group.

These are cohort-design considerations, not recommended day ranges. A comparison becomes informative when like is compared with like and known exceptions are visible instead of being buried in a total.

Build a defensible industry benchmark

  1. Define the population. Specify whether the report includes only trade receivables, which entities and currencies are included, and how credit balances, related-party amounts, retainage, and unbilled amounts are handled.
  2. Normalize the terms. Record contractual due dates and calculate delinquency from those dates. A 30-day-old invoice that is not due yet should not be treated the same as a 30-day-past-due invoice.
  3. Segment before averaging. At a minimum, consider customer type, contractual terms, geography, billing cadence, and risk characteristics. Remove or separately report one-off project balances that would distort a recurring operating measure.
  4. Use a time series. Compare several monthly or quarterly observations rather than a single period-end number. Report the median and distribution of comparable results where the data set is large enough.
  5. Compare to an internal baseline. The prior trend for the same defined portfolio is often more actionable than an unscreened external average. Explain any changes in terms, revenue mix, acquisition activity, or billing process before concluding that collection performance changed.

External data can provide context, but it must match the question. The U.S. Census Bureau Quarterly Financial Report publishes sample-based aggregate financial statements, balance sheets, and operating ratios for covered U.S. corporate industries. It can help identify a relevant public data series, but its survey scope and definitions may not match a company’s DSO calculation, so it should not be treated as a mandatory collection target.

Use aging buckets as a risk-management tool

Use aging buckets that match the organization’s terms and collection workflow. A practical report might show not-yet-due receivables and successive past-due intervals, then tag each balance by its reason for delay. Review the balance and percentage in each bucket together: a small percentage can still be material if it is concentrated in one customer, while a larger late balance may be less concerning when it is supported by a documented dispute-resolution process.

For U.S. GAAP credit-loss estimation, the aging report may be one input but it is not a substitute for the applicable accounting analysis. FASB Accounting Standards Update 2025-05 includes an illustration that classifies trade receivables by days past due and uses historical credit-loss rates for portfolio segments with similar risk characteristics. The illustration is a method example, not an industry-wide set of acceptable aging percentages. The update also addresses optional practical expedient and policy-election provisions for certain current accounts receivable and current contract assets; businesses should assess scope and accounting-policy application with qualified advisers.

Investigate variance before changing credit policy

A worsening DSO or growing older bucket is a prompt to investigate, not proof that every customer needs stricter terms. Start by separating timing effects from recurring problems. Reconcile the aging report to the general ledger, identify the customers and invoices driving the movement, and classify the cause: missing documentation, pricing or quantity dispute, purchase-order mismatch, service acceptance, credit approval, promised payment, or a true payment default.

Then assign an owner and a measurable next step. Billing and documentation defects belong with the operational team that can correct them; credit-limit decisions need a documented risk review; disputed invoices need a resolution path; and collection activity should follow the applicable contract, law, and company policy. This approach protects customer relationships while making real collection risk visible.

Keep operating metrics separate from reporting requirements

An aging dashboard is an operating-control tool. Financial-statement classification, allowances, disclosures, and expected-credit-loss estimates are separate matters that depend on the reporting framework and the facts. SEC presentation requirements apply to registrants within their scope, while FASB guidance may apply differently depending on the entity and accounting policy. Do not use a generic industry benchmark as a substitute for financial-reporting judgment or legal and accounting advice.

Frequently asked questions

What is the accounts receivable collection period?

The accounts receivable collection period is the average time a business takes to collect credit sales. It is commonly monitored with DSO, but a meaningful calculation uses a sales denominator and receivable balance that cover the same population and time period.

Which measure can improve accounts receivable management?

No single measure improves receivables by itself. A consistent aging report, DSO trend, past-due mix, dispute rate, and collection-action follow-through together can show where process, credit, or customer issues need attention.

Related reading

For adjacent operational context, see AR Turnover Ratio: Benchmarking Liquidity & Efficiency and AR Audit Defense: The Reconciliation & Revenue Assurance Protocol.