Receivables aging

Every accounting system produces an aging report, and it is the backbone of collections work: it shows how much each customer owes, how long that money has been waiting, and which items will drive the doubtful-debt provision discussion. Its accuracy depends entirely on the open items underneath it. The report measures nothing by itself; it simply slices what the ledger currently believes into buckets. The same logic runs on the payables side, where aging of open supplier balances becomes an input to payment planning.

The link to reconciliation is direct. An item can age not only because it was never collected, but because the collection was never applied to the right invoice. Partial payments, one transfer covering several invoices, exchange differences, transfers arriving short by the bank charge, and credit notes never linked to the original invoice all make an item look older than it is. Read without item-level matching, aging measures posting delay rather than collection risk. Comparing the oldest bucket against the counterparty's own statement is what separates a genuine risk line from a bookkeeping gap.

The most common misreading is that aging can be validated against the total balance. The total can be right while the distribution across buckets is wrong: an unapplied receipt leaves the same customer with both an aged receivable and an ownerless collection, and the total still agrees. The second misreading is that the report date is a detail. Aging is always produced as of a cut-off date, and two reports pulled on different dates will show different buckets even if no cash moved in between, which is why aging comparisons must use the same cut-off. A third is that the oldest bucket names the worst customer. One disputed line can keep an otherwise punctual payer at the top of the list for years, which is why aging ranks what needs to be discussed rather than deciding anything by itself.