An accounts receivable aging schedule groups unpaid invoices by how late they are and helps management test collectability, cash-flow risk, and data quality. A useful audit re-performs the aging from source data, explains movements between periods, isolates concentration and dispute risk, and connects the evidence to the organization’s documented credit-loss estimate; the report alone does not prove that an invoice is uncollectible.
What an aging schedule is designed to show
An aging schedule is an as-of-date view of open receivables. It typically places balances into ranges such as current, 1–30, 31–60, 61–90, and more than 90 days past due. The ranges are management choices, not universal verdicts on a customer’s ability or willingness to pay.
The schedule answers two different questions:
- Age: How long has each amount remained unpaid under the organization’s documented aging convention?
- Risk: Which balances have characteristics that may affect collection, such as a dispute, a credit hold, a customer-specific event, or repeated migration into older buckets?
Keep those questions distinct. A late balance may be collectible; a current balance can still present risk if it is concentrated with one customer or affected by a known event.
Set the audit population and cut-off first
Start with a report date and preserve the source extract used for testing. The population should identify the customer, invoice or receivable identifier, original amount, open amount, posting date, due date, payment terms, applied cash, credit memos, adjustments, dispute or hold status, and responsible owner. Document whether the organization ages from the contractual due date, invoice date, or another consistently applied date.
Then reconcile the receivables subledger to the general ledger as of the same cut-off. Do not erase differences to make totals agree. Classify each difference—for example, timing, interface failure, unapplied cash, credit memo, foreign-currency treatment, or posting error—and retain the reconciliation. A broader receivables reconciliation review can help put the aging test in context.
Test whether balances are in the right bucket
For a targeted sample and for high-value or unusual items, independently calculate days past due from the documented inputs. The following checks are practical starting points:
- Re-perform the age calculation. Compare the report’s bucket to the due date, report date, and stated rule. Investigate missing terms, invalid dates, and balances placed in a bucket that does not match the rule.
- Trace period-to-period movement. Reconcile opening open balances, invoices or other additions, cash and credits, write-offs or other removals, and closing open balances. A movement that cannot be explained is an exception, not a reason to alter a date.
- Review manual changes. Obtain logs or approvals for edits to invoice dates, due dates, terms, customer status, credits, and dispute flags. Determine whether the change has support in the underlying transaction record.
- Examine partial payments carefully. A partial payment may reduce the open amount, but it should not silently change the audit trail. Define in policy how the system treats the remaining balance and test that the report follows that policy consistently.
- Separate disputed from undisputed balances. A dispute flag should lead to documented follow-up, not an automatic conclusion about collectability. Review the nature of the dispute, the evidence, and the expected resolution date.
Use cohort roll rates to see migration
Aging shows a point in time. A cohort roll-rate analysis shows how balances move over time. Define a starting cohort, choose a measurement period, and calculate the share of its opening amount that enters a later bucket during that period.
Example: If a cohort has $200,000 in the 31–60-day bucket at the start of a month and $40,000 of that same cohort is in the 61–90-day bucket at month-end, the 31–60 to 61–90 roll rate is 20%. The analysis should identify the cohort rather than merely compare two bucket totals, because new invoices, payments, credits, and adjustments can otherwise obscure the movement.
Track roll rates by customer segment, product line, geography, channel, or credit policy only when the grouping is meaningful and sufficiently stable. Compare several periods, investigate material changes, and document whether the movement reflects operational issues, customer events, seasonality, or changes in reporting rules. A rising roll rate is a prompt for investigation; it is not, by itself, proof of a cause or a required reserve percentage.
Assess concentration alongside age
Do not treat a bucket total as a complete risk assessment. Add a customer-level view of aged balances, open exposure, payment history, disputes, credit limits, and related-party status where applicable. A modest total can still be material if a small number of counterparties account for most of it.
A practical review ranks the customers in each aged bucket, calculates each customer’s share of the relevant total, and explains significant changes from the prior period. The purpose is to make decision-makers see where the exposure sits, not to apply an unsupported universal concentration threshold. For further context on older balances, see this discussion of aged receivables and DSO reduction.
Connect the aging evidence to the allowance
For entities reporting under U.S. GAAP, the allowance for credit losses is a valuation account used to present the net amount expected to be collected. The Financial Accounting Standards Board explains that expected-credit-loss measurement uses relevant information about past events, including historical experience, current conditions, and reasonable and supportable forecasts; it does not prescribe one credit-loss method. See the FASB Credit Losses project page.
That means an aging schedule and roll-rate analysis may be useful evidence, but they should be connected to a documented method rather than treated as a mechanical rule. A sound review considers the segmentation of receivables, historical loss and recovery experience, current customer or industry conditions, forecast assumptions when supportable, management overlays, and the reason each input is relevant. Accounting-policy conclusions should be made by the entity’s qualified accounting professionals.
FASB also issued an optional 2025 update addressing the measurement of expected credit losses for certain current accounts receivable and contract assets arising from Topic 606 transactions. Its scope and elections are specific, so an entity should assess applicability rather than assume it changes every aging-based process. Read FASB’s July 2025 announcement of ASU 2025-05 for the stated scope.
For SEC registrants, Regulation S-X requires allowances for doubtful accounts and notes receivable to be set out separately in the balance sheet or a note. The rule also specifies separate presentation categories for accounts and notes receivable. See 17 CFR § 210.5-02. This presentation rule does not substitute for the entity’s accounting-policy analysis or its underlying evidence.
Document exceptions and escalation decisions
The audit workpaper should distinguish a data-quality issue from a credit-risk conclusion. For each material exception, record the affected balance, the test performed, the evidence reviewed, the owner, the proposed correction or follow-up, the due date, and the final disposition. Preserve the original report and the corrected version when a correction is made.
Escalate patterns such as unsupported date changes, unreconciled subledger differences, repeated unapplied cash, growing disputes, large customer concentrations, or significant unexplained roll-rate changes. Where an account may be written off or otherwise removed, connect the action to the organization’s approved policy and supporting documentation. For related accounting context, review the bad-debt and write-off protocol.
Scope and compliance limits
This is an operational and financial-reporting framework, not legal or tax advice. If a portfolio includes consumer obligations, do not use an aging review to prescribe customer contact, dispute handling, credit reporting, litigation, or limitation-period decisions. Those activities require review under the laws, account type, parties, and jurisdictions that apply, as well as the organization’s approved compliance procedures.
Frequently asked questions
Why is accounts receivable management important?
Accounts receivable management helps an organization monitor expected cash collection, identify operational exceptions, and understand where customer exposure is concentrated. An aging audit makes the underlying report more reliable for those decisions.
Which measure can improve accounts receivable management?
No single measure is sufficient. A cohort roll rate can improve monitoring when it is used with an accurate aging schedule, reconciliation, customer-level concentration review, and documented follow-up on exceptions.