What is an AP Aging Report?

Quick Answer: An AP aging report groups every unpaid vendor invoice by how long it has been outstanding, normally in 30-day buckets. The useful version of the report does one more thing: it attaches a decision to each bucket and names the record that decision depends on. A bucket that only tells you how old something is has not helped you, because nobody schedules work off an age.

Most finance teams can produce this report in one click. Far fewer can say what they did differently because of it last month. That gap is not a reporting problem, and adding a chart will not close it. It is that the report answers a question — how old is this — that sits one step away from any decision a person can act on.

A bucket is only useful if it names a decision

Here is the same standard bucket structure, rewritten around what you do rather than what it signals. The third column matters most: it is the record without which the decision cannot be made, and it is usually the reason a team stares at the report and does nothing.

Bucket	The decision it lets you make	The record that decision depends on
Current, not yet due	Whether to pay early for a discount or hold for cash	Payment terms captured per invoice, not per vendor
1-30 days past due	Whether this is a process slip or an unanswered question	A timestamp for when the invoice entered approval
31-60 days past due	Who is being chased, and by whom, this week	A named owner on the invoice, not on the vendor
61-90 days past due	Whether to escalate to the vendor or resolve internally	Whether a dispute was ever formally raised
90 days and over	Whether to settle, write off, or accept a supply risk	The original goods receipt and the match result

Read the third column down the page. Every one of those is a field, not an insight. If your report cannot support the decision in the middle column, the fix is upstream in capture, not in the report.

The two reasons an invoice ages, and why the report cannot tell them apart

An invoice sitting at 45 days is in one of two completely different situations, and they need opposite responses.

It is waiting on a person. Nobody disagrees about anything. The invoice went to an approver who was on leave, or it arrived without a purchase order and stalled while somebody worked out who owned it. This is a queue problem. The response is to chase, delegate or re-route, and it should take minutes.

It is genuinely disputed. The quantity does not match the receipt, the price is not the price that was agreed, or the goods were returned. This is a resolution problem. The response involves the vendor, it takes days or weeks, and chasing your own approver will do nothing at all.

A standard aging report shows both as 45 days. That is the single biggest reason aging reports get reviewed and then closed: half the rows need a different response from the other half and the report does not say which is which, so the reviewer defers the whole thing.

Telling them apart is not analysis. It is a field. Somewhere in the invoice record there has to be a status that separates awaiting action from held pending resolution, set by whoever put the invoice into that state, with a date. Once that exists the aging report splits into two lists with two owners and two cadences, and it stops being a document nobody can act on.

If you have to choose one change to make after reading this, make that one.

Two aging methods, and which question each answers

Due date aging counts from when payment was due. It measures payment performance, which is what most AP teams want and what a vendor is looking at from their side.

Invoice date aging counts from when the invoice was issued. It measures your own processing speed from receipt to payment, which is a different question and a more useful one when you are trying to find where invoices get stuck rather than how late you are.

Run due date aging for vendor management. Run invoice date aging when you are diagnosing your own process, and expect the two to disagree — the gap between them is roughly the time your process is adding.

A worked report, read row by row

Seven rows from a report that looks normal. What each one is actually telling you:

Vendor	Invoice	Days past due	Amount	What it tells you
Northfield Packaging	INV-4471	Not yet due, 6 days to term	12,400	Inside a 2/10 discount window — this is a cash decision, today
Northfield Packaging	INV-4402	34	9,850	Same vendor, two buckets: something is inconsistent, not merely late
Alder Components	INV-2288	41	3,200	Sitting in approval with no owner named — a queue problem
Alder Components	INV-2301	12	3,150	Newer invoice moving faster than an older one: the older one is stuck, not slow
Ridgeway Logistics	INV-9910	67	28,700	Large, old, single vendor — the concentration risk on this page
Ridgeway Logistics	INV-9884	96	4,150	Over 90 days with no dispute flag: nobody owns this
Vantage Print	INV-0771	58	640	Small and old — almost certainly a dispute nobody thinks is worth the call

Three patterns are worth naming because they recur:

• The same vendor in two buckets is the most informative row pair on any aging report. It rules out a payment run problem, since the vendor is clearly getting paid, and points at something specific to those invoices.
• A newer invoice paid before an older one from the same vendor means the older one is blocked rather than queued. Sequence tells you more than age here.
• Small and very old is nearly always an unresolved dispute that never justified anyone's time. These are worth a monthly sweep precisely because they will never be urgent enough to fix individually.

Reading it in four passes

Reading top to bottom is the mistake. Use this order, and stop when you have found the work.

Distribution. What share of the balance is past due at all? You do not need an industry benchmark for this, and you should distrust any you are offered, because the honest comparison is against your own last three months. A past-due share that is stable is a process running at its natural rate. One that is climbing is a process losing ground, and that is true whatever the absolute number.

The oldest bucket. Every invoice over 90 days needs a name and a resolution date, and it needs them this week. If any of those rows has no dispute flag and no owner, that is the finding.

Vendor concentration. If one vendor holds a large share of the past-due balance, the risk is not the money. It is a credit hold that stops something arriving. Sort by vendor before you sort by amount.

Direction. One snapshot tells you where you are. Two tell you which way you are moving. Keep last month's totals by bucket somewhere you can see them, because the trend changes what you do about the level.

The discount arithmetic, written out

Terms of 2/10 net 30 mean you may take 2 percent off if you pay within 10 days instead of 30. The return on paying 20 days early works out as follows: the 2 percent discount is earned on the 98 percent you actually pay, so that is 2 divided by 98, or about 2.04 percent for 20 days. There are 18.25 such periods in a year, so the annualised figure is roughly 37 percent.

That number is worth writing out rather than quoting because it changes with your terms, and because it only applies if you have the cash to pay early. Cross-reference the Current bucket against discount windows before every payment run — a discount missed by two days is the most expensive thing on an aging report, and it never appears in a past-due bucket at all.

AP aging versus AR aging

Aspect	AP aging report	AR aging report
Tracks	Money you owe vendors	Money customers owe you
Risk of ageing	Late fees, credit holds, supply disruption	Cash shortfall, bad debt
Action	Pay, chase internally, or resolve a dispute	Collect or escalate
Cash effect	Outflows	Inflows

They are mirror images: your AP aging report is somebody else's AR aging report. The bucket structure is identical and the actions are opposite, which is worth remembering when a vendor calls about an invoice you have at 60 days — they are reading the same row.

The invoices that never appear on it

An aging report is a report on what got entered. Everything that did not is invisible to it, and the omissions are systematic rather than random.

Invoices still sitting in a mailbox. An invoice emailed to a project manager who has not forwarded it does not exist as far as your report is concerned. It is not late, because it has no due date yet. It becomes an emergency the day it is entered, already at 50 days. The size of this pool is worth measuring once: take a month of entered invoices and compare invoice date to entry date. The gap is your blind spot, and it is usually larger than anyone expects.

Goods received without an invoice. The stock arrived, the liability exists, and no invoice has been raised. This belongs in accruals rather than aging, but it is the same money, and a vendor who has not billed you for four months will eventually bill you for four months at once.

Credit notes not yet applied. These reduce a balance the report is showing in full, so a vendor can appear to be owed far more than they are. Any 90-plus row for a vendor you frequently return goods to should be checked against open credits before anyone escalates.

Invoices on hold outside AP. A disputed invoice parked in a shared inbox by a budget holder, rather than flagged in the system, is the case the previous section is about. It ages without ageing.

None of these is a reporting flaw. They are the boundary of what the report can see, and the useful habit is to say out loud, each time you read it, that this is the position on entered invoices only.

What to change if the report is not producing decisions

1. Add the held-versus-waiting status before anything else. Without it, every other improvement is cosmetic. This is one field and it changes what the report is for.
2. Put owners on invoices, not on vendors. A vendor-level owner is a person who receives a list. An invoice-level owner is a person who can be asked about one thing.
3. Reconcile the report total to the ledger every time. If the aging total does not equal the AP balance on the trial balance, you have unrecorded invoices, posting errors or timing differences, and every conclusion drawn from the report is provisional until that is closed.
4. Set thresholds by bucket, not on the total. A total balance tells you almost nothing. A 60-plus bucket that doubled since last month tells you where to spend Tuesday.
5. Run it weekly, and daily only during close. Weekly catches slippage before it reaches 60 days. Daily outside close produces a report nobody reads.

Key Takeaways

• Definition: An AP aging report groups unpaid invoices by days outstanding, normally in 30-day buckets
• The change that matters: separate invoices waiting on a person from invoices held pending resolution — they need opposite responses and the standard report shows both as the same age
• Reading order: past-due share, then the oldest bucket, then vendor concentration, then the direction of travel against last month
• Ownership rule: every invoice past 30 days needs a named owner on the invoice itself, and every invoice past 90 needs a resolution date
• Benchmark honestly: compare against your own trailing three months rather than a published industry figure

Related Terms

• AP Spend Analysis - Where the vendor concentration you spot in aging gets examined properly
• Days Payable Outstanding - The single figure that aging data rolls up into, and its limits
• Invoice Approval Workflow - The queue that produces most of the 1-30 and 31-60 buckets
• Accounts Payable KPIs - Metrics like cost per invoice that aging feeds
• Three-Way Matching - Where disputed invoices are usually created, long before they age