An accounts payable aging view buckets what you owe by how overdue it is, and on its own it merges two things that need different responses. Some of the balance is deliberate: within terms, or held on purpose. The rest is stuck: awaiting approval, in exception, disputed. Only the second is a problem, and the view cannot distinguish them without a status.
Why the raw number misleads
An invoice sits in a bucket because of its due date, whatever the reason it is unpaid. A disputed invoice, an unapproved one and one you are deliberately holding to terms look identical. Presenting the total overdue as a payables performance figure therefore mostly measures somebody else's payment policy.
Splitting it by status
Approved and scheduled, awaiting approval, in exception, disputed. The report then answers how much is overdue because of us, which is the figure payables can actually move and the one worth reporting weekly. It is usually a small fraction of the headline and a far more useful conversation.
Where it is genuinely useful
Cash planning, and spotting a supplier relationship about to become a phone call. A supplier whose overdue balance is growing is a problem forming, and the aging view finds them earlier than the complaint does. Those are the uses to build the report for.
Questions people ask about accounts payable aging
What buckets should we use?
Ones aligned to your terms. Buckets that do not match your terms make everything look better or worse than it is.
Should overdue ever be zero?
Rarely, since disputes exist. What should be near zero is the amount overdue because of your own process.
How does this relate to days payable outstanding?
Aging is a snapshot by age; days payable outstanding is a ratio over a period. Both are influenced by deliberate policy.