Accounts Payable Aging Report: How to Read and Fix It

An accounts payable aging report lists unpaid supplier invoices by how long they have been outstanding, usually in current, 1-30, 31-60, 61-90, and 90+ day buckets. In practice, it is a control report built from your accounts payable subledger that shows which obligations are still current, which ones are overdue, and which balances need someone to investigate before the next payment run or month-end close.

That is why the report matters beyond basic accounting definitions. Finance teams use it to prioritize payments, monitor overdue balances, and surface problems such as incorrect due dates, unapplied credits, or items that no longer reconcile to the AP control account. A controller may look at it to understand payment exposure. An AP supervisor may use it to decide which suppliers need follow-up. A staff accountant may use it to spot open items that should not still be sitting on the ledger.

The report is only as reliable as the records feeding it. If payment terms were set incorrectly, if the wrong due date was captured, or if vendor balances are split across duplicate records, the AP aging report can look orderly while telling the wrong story. That is why knowing how to read an AP aging report means more than knowing what each bucket is called. You need to understand what the balances represent, which date logic is being used, and where the report can become misleading in day-to-day AP operations.

How Aging Buckets Work, and Why the Date Basis Changes the Story

The standard accounts payable aging buckets are straightforward on paper: current, 1-30 days overdue, 31-60, 61-90, and 90+ days. What trips teams up is not the bucket labels but the date logic underneath them. An aged payables report does not simply ask how old an invoice is. It asks how old that invoice is according to the basis chosen by the report.

In most AP workflows, due-date aging is the most useful basis because it shows what is actually payable now versus what is not yet due. If an invoice was issued on March 1 with net-30 payment terms, it may be 19 days old on March 20, but it is still current if the due date is March 31. That distinction matters because a team deciding which invoices to pay or escalate should care about the due date first, not just the invoice date.

Some systems also offer aging by invoice date or transaction date. That can be useful for certain reporting views, but it answers a different question. Invoice-date aging tells you how long it has been since the document was issued. Due-date aging tells you whether the supplier should have been paid already. If you confuse the two, you can overstate how overdue your liabilities are, chase vendors too early, or misread whether payment performance is slipping.

Before you judge any bucket balance, confirm the report basis. If your AP aging due date vs invoice date setting changed, or if two reports use different logic, the balances may look inconsistent even when the underlying transactions are the same. Good AP review starts by asking not only which invoices sit in each bucket, but why the system placed them there.

How Finance Teams Use Summary and Detail Aging to Decide What Matters First

Summary aging and detail aging answer different operational questions. The summary view rolls balances up by vendor or bucket so you can quickly see where exposure is concentrated. The detail view breaks that balance back into individual invoices, credits, and open items so you can understand what is driving it. You usually need both. Summary tells you where to look. Detail tells you what to do next.

In practice, teams use summary aging to set priorities for the payment cycle. Large current balances may signal cash requirements coming due soon. Growing 31-60 or 61-90 balances may point to approval bottlenecks, disputed invoices, or suppliers who are starting to carry real credit risk. This is one reason payment discipline matters beyond supplier goodwill. According to APQC's benchmark for supplier invoices paid on time, the median organization pays 80.0% of supplier invoices on time, which gives you a useful reference point when overdue balances start becoming routine rather than exceptional.

Detail aging becomes essential when the summary no longer makes sense. A single vendor total might include one genuinely overdue invoice, one unapplied credit, and several items that are still current but grouped in a way that makes the account look riskier than it is. Detail lets the AP team separate timing issues from true exceptions, decide which suppliers need contact, and prepare cleaner support for the controller during close.

If you want to place aging review in a wider performance context, the accounts payable metrics and benchmark scorecard helps connect overdue balances to broader AP measurement. Used well, accounts payable aging analysis is not just a static report review. It is a decision tool for payment timing, supplier management, and exception handling.

---

Why an Aged Payables Report Stops Matching the General Ledger

When an aged payables report does not match the general ledger, the problem is usually a break between the AP subledger and the AP control account rather than a mysterious failure in the report itself. If you need to reconcile aged payables to the general ledger, the goal is to find where that break was introduced and whether it is a timing difference or a real posting error.

Start with a disciplined tie-out sequence.

1. Confirm the report date and the ledger date are the same.
2. Compare the total aged payables balance to the AP control account balance for that date.
3. Decide whether the difference is timing, such as items posted after the cutoff, or a true discrepancy that existed on the report date.
4. Trace the difference down to vendor and invoice detail instead of staying at the summary level.

This is where software-agnostic troubleshooting matters. A mismatch often comes from direct journal entries posted to the AP control account, transactions booked to the wrong period, partially applied payments, or credits that sit in the subledger without offsetting the invoices the way the aging expects. In other cases, the ledger is right but the report includes stale open items that should have been cleared long ago. Either way, you do not fix the issue by staring at the total. You fix it by moving from control-account balance to subledger detail and isolating the transactions that created the gap.

If the difference is concentrated in disputed or unsettled supplier balances, a structured vendor statement reconciliation workflow can help verify whether the problem sits in your records, the supplier's records, or both. The key is to treat reconciliation as a traceable process: match the control account, inspect the detailed aging, and then test the transactions causing the mismatch instead of assuming the report itself is wrong.

The Data Problems That Distort AP Aging Even When the Math Looks Right

Some of the most frustrating AP aging issues are not calculation errors at all. The report can be mathematically consistent and still be operationally misleading because the underlying data is wrong. Whether your system calls it an AP aging report or an aged creditors report, the symptom is the same: the balances look official, but they do not reflect what your team should actually pay, chase, or explain.

The most common distortions show up in a few patterns.

• Wrong due dates or terms: If invoices were assigned incorrect payment terms, current items can appear overdue or overdue items can look current. That distorts payment prioritization immediately.
• Duplicate vendors in the vendor master: Credits may sit on one supplier record while invoices sit on another, making exposure look larger than it really is.
• Old paid items left open: A payment may have posted, but the invoice was never properly cleared or applied, so the report keeps carrying a balance the team thinks is gone.
• Unapplied credits and credit notes: These often reduce what is truly owed, but until they are matched correctly, the report can overstate liabilities or hide the real age of the remaining invoices.
• Foreign exchange revaluation effects: Multi-currency balances can move for valuation reasons even when no supplier activity changed, which can create confusion if the team expects the aged balance to behave like a pure invoice listing.
• Migration residue: After an ERP change or historical cleanup, legacy transactions may be carried into the new system without proper settlement history, leaving long-aged balances that are artifacts rather than current obligations.

These issues are why AP aging should never be treated as a standalone screen. It is the output of upstream invoice capture, terms maintenance, credit handling, vendor governance, and close discipline. The same weak controls that create noisy aging often sit behind broader duplicate payment prevention controls, because both problems start when invoice and vendor data stop behaving consistently. If your aging looks wrong, investigate the source data before assuming the bucket logic is the real problem.

---

A Cleanup Cadence That Keeps the Report Useful

An accounts payable aging report stays useful when teams review it at the same rhythm they review cash requirements and close risk. That usually means a light review every week, a focused review before each payment run, and a deeper cleanup during month-end close. The aim is to catch small data issues before they harden into recurring exceptions.

A practical cleanup cadence usually includes the following checks.

• Confirm the report is aging by the basis you intend to use, especially due date versus invoice date.
• Review overdue balances in detail, not only in summary, so you can separate true late items from timing noise.
• Clear old paid invoices that still appear open.
• Apply credits and credit notes to the right invoices and vendor records.
• Correct vendor master issues that split balances across duplicate suppliers.
• Investigate any gap between the aging total and the AP control account before close is finalized.

This routine does more than clean up one report. It protects payment prioritization, supplier communication, and the credibility of your close process. If recurring exceptions trace back to inconsistent invoice intake or poorly maintained terms, improving the upstream invoice processing workflow helps keep due dates, invoice dates, and credits consistent before they show up in aging. That does not replace review discipline, but it gives the report cleaner source data to work with.

The useful test is simple: when someone asks why a balance is overdue, why a vendor total looks unusual, or why the aging does not tie to the ledger, your team should be able to trace the answer quickly. If you cannot, the report does not need a new definition. It needs better maintenance.