Accounts Receivable Aging Report: Build & Use It

An accounts receivable aging report groups unpaid customer balances by how long they have been outstanding or overdue. Its practical purpose is to show which invoices need action and whether expected collections support the cash plan. Choose one aging basis and label it clearly. This guide uses days past the contractual due date, which differs from aging based on the original invoice date.

An invoice issued thirty days ago with net-thirty terms may be due today, not thirty days overdue. Confusing those dates can lead to an inappropriate collection message and an inaccurate cash forecast. Preserve the invoice date, due date, report date, original amount, credits, payments and remaining balance. A summary without that detail is difficult to reconcile or defend when a customer disputes it.

Start with open invoices at a defined cutoff date and reconcile their total to the receivables control account. Apply posted payments and approved credit notes before calculating the remaining amount. Separate unapplied cash, deposits and disputed items so they do not inflate the apparent collection problem. A customer-level net balance can conceal an overdue invoice when a separate credit remains unallocated.

Keep one row per invoice in the working file, then summarize by customer and aging bucket. Use a unique invoice identifier rather than names alone. Similar customer names and duplicate imports can cause collection staff to contact the wrong party. The report should be traceable to the accounting system, with the preparation date and the person responsible for reviewing exceptions recorded.

Days overdue equals the report date minus the due date, with a minimum of zero for amounts not yet overdue. A useful grouping is current, one to thirty days overdue, thirty-one to sixty, sixty-one to ninety, and more than ninety. These are working categories, not a universal legal collection timetable. Adapt the workflow to the agreement, customer circumstances and applicable requirements.

In a hypothetical report dated October 12, an invoice due September 27 is fifteen days overdue. An invoice due October 20 is current. Keep the actual dates in the worksheet so anyone can reproduce the classification. If the customer has agreed a revised due date, record the agreement and distinguish it from a unilateral change made only to make the report look better.

Suppose receivables total $50,000: $30,000 current, $10,000 one to thirty days overdue, $6,000 thirty-one to sixty, and $4,000 more than sixty. The report shows $20,000 overdue, or 40% of the total. That percentage is a starting point, not a prediction that all overdue amounts will be lost. The age, documentation, dispute status and customer's payment history matter.

Concentration can be more important than the average. If one customer owes $18,000, a single delay can affect payroll even when the rest of the book pays normally. Review large balances individually and connect expected receipts to the cash forecast. Avoid entering every overdue amount as next week's cash simply because a reminder has been sent. Record the evidence supporting the expected payment date.

For each material overdue invoice, confirm that the customer received it, that the amount and purchase reference are correct, and that delivery or acceptance evidence is available. A missing purchase-order number may be an administrative issue rather than refusal to pay. Route factual discrepancies to the person who can resolve them before escalating the tone of the collection message.

Use a concise contact record: date, person reached, issue, agreed action and next review. Send the invoice and relevant supporting documents through a known channel. Never change payment instructions in response to an unverified email. If the customer requests bank details, follow the business's verification process. A collection effort should not create a new opportunity for invoice fraud.

A disputed balance requires a decision about the underlying commercial issue. Record whether the dispute concerns price, quantity, service quality, delivery or another obligation. Assign an owner with authority to investigate. Leaving the invoice in a generic overdue queue while reminders repeat can damage the relationship without increasing the chance of payment.

Payment plans and settlements should be documented and approved under the company's policy. Do not silently extend terms, waive a charge or promise a concession that the collector is not authorized to offer. For material or legally sensitive disputes, obtain appropriate advice. This operating framework does not establish a right to add fees, contact third parties or use a particular collection method.

An aging report identifies individual unpaid amounts and their timing. Days sales outstanding, or DSO, is an aggregate measure commonly calculated from receivables and credit sales over a period. The two tools answer different questions. A stable DSO can hide one large old invoice if newer sales and collections offset it, while an aging report makes the individual exception visible.

Use comparable periods and definitions when tracking either measure. A seasonal company can show a changing ratio because sales rose sharply near the reporting date. Cash sales should not be mixed into a credit-sales denominator without explaining the method. Do not replace invoice-level follow-up with a ratio that cannot tell the team which customer to contact or which document is missing.

Agree terms before delivery, identify the customer's billing contact, issue invoices promptly and include the information needed for approval. Match the invoice to the contract and record any acceptance milestone. For projects with a long delivery cycle, a deposit or milestone payment may improve timing if it is commercially appropriate and agreed in advance.

Review the aging report regularly with sales, delivery and finance. Track whether the same preventable issue recurs: incorrect scope, missing documents, late invoicing or a customer repeatedly exceeding agreed terms. The worksheet provides a practical exception register. Its value comes from resolved causes and reliable collection estimates, not merely a visually tidy report with every balance moved into a newer bucket.