An AP aging report shows what you owe, bucketed by how overdue it is, and on its own it conflates two entirely different things. Some of what appears there is deliberate: not yet due, or held to terms. The rest is stuck: awaiting approval, in exception, disputed. Only the second kind is a problem, and the report as usually produced cannot tell you which is which.
What the buckets do and do not say
An invoice appears in a bucket because of its due date, regardless of why it is unpaid. A disputed invoice, an unapproved one and one you are deliberately holding all look identical. That is why the total overdue figure so often produces an unproductive conversation: it is a number nobody can act on directly.
Add status and it becomes operational
Break each bucket by status: approved and scheduled, awaiting approval, in exception, disputed. The report then answers how much is overdue because of us, which is the number payables can actually move. It is usually a fraction of the headline and a much more useful thing to put in front of a manager.
What it is genuinely good for
Cash planning, and spotting a supplier relationship about to become a phone call. A supplier with a growing overdue balance is a problem forming. Used for those purposes it is valuable; used as a performance measure for payables without status alongside, it mostly measures the payment terms somebody else negotiated.
Questions people ask about ap aging report
Should the overdue figure be zero?
Rarely realistic and rarely desirable, since disputes exist and some invoices should not be paid yet. What should be near zero is the amount overdue because of your own process.
What buckets should we use?
Ones that align with your terms. Buckets that do not match make everything look better or worse than it is.
Who should read it?
Finance for cash, payables for the stuck items, broken down by status. The same report serves both only if the status is there.