Reading an aging extract for exception signals

An aging extract is often treated as a compliance printout. For an accounts receivable exception review, it is the first map.

Start with concentration, not colour coding

Sort by balance descending within the 60+ and 90+ buckets. A handful of large invoices usually explain more risk than hundreds of small past-due lines. Note customers who appear across multiple aging columns with no recent credit activity — that pattern often signals stalled disputes rather than simple late payment.

Columns that mislead

“Days overdue” calculated from invoice date can hide agreed extended terms. If your extract lacks a terms column, ask sales for the true contractual dates before labelling something an exception. Equally, customer names duplicated with slight spelling differences fracture aging and create false “new” overdue balances.

Early systemic signals

• Sudden growth in a single aging bucket after a system cut-over
• Credit balances sitting inside AR without a matching open debit
• Customers with large unapplied cash and large overdue invoices (classic matching gap)

What we do next

Once signals are listed, materiality thresholds decide what enters detailed sampling. That hand-off — from map to sample — is where most of the review’s cost sits, so a careful first read saves days later.

If your aging already looks noisy, a full exception review may be more honest than another internal spreadsheet pass.