Accounts Payable Aging Report: What It Is, How to Read It, and How to Build One

An accounts payable aging report lists every unpaid supplier invoice sorted by how long it has been outstanding, usually in buckets that run from current out past 90 days. It shows what you owe, to whom, and how overdue each bill already is.

That makes it one of the few finance reports that does three jobs at once. It forecasts near-term cash outflows, it grades the health of your supplier relationships, and it quietly flags the invoices nobody can explain. Most AP teams run it because the controller asks for it at close. The teams that get real value out of it read it as a diagnostic rather than a status update, and that shift in how you read the report is where most of the value sits.

Key Takeaways

• An AP aging report groups unpaid supplier invoices into age buckets so you can see overdue obligations and near-term cash outflows at a glance.

• The standard buckets are current, 1-30, 31-60, 61-90, and 90+ days, and each one carries a different operational meaning rather than just a different age.

• A persistent 90+ balance is rarely just slow payment. It usually means a dispute nobody closed, a coding error, or an invoice that should never have entered the ledger.

• Building the report by hand is a six-step exercise, and the result is accurate only for the moment it was pulled.

• The aging report is the raw input to days payable outstanding and AP turnover, so a stale report quietly corrupts both metrics.

• Automated capture, coding, matching, and ERP sync keep the buckets current, which is what turns the report from a month-end artifact into something you can act on.

What is an accounts payable aging report?

An accounts payable aging report is a scheduled summary of outstanding payables grouped by how long each invoice has been open, measured either from the invoice date or from the due date. You'll also see it called an AP aging schedule or an aged payables report, and the three terms mean the same thing.

A usable report carries at least five fields per line:

• Vendor name and invoice number, so a disputed item can be traced back to a document

• Invoice date and due date, which together determine the bucket

• Invoice amount, and the aging bucket calculated from the date you choose as your "as of" point

Some teams add the payment terms and the GL account, which helps when you start asking why a particular vendor keeps drifting.

It exists because a raw AP subledger is nearly unreadable. A list of 900 open invoices tells you almost nothing. The same 900 invoices sorted into five age columns tells you immediately whether your payables are behaving normally or whether something has gone sideways with a specific supplier. It's the same reason the accounts payable process has a defined close step at all, and it fits into the broader picture of what accounts payable actually covers as the reporting layer on top of the transaction flow.

What is the aging schedule for accounts payable?

The aging schedule is the set of buckets used to classify each open payable by age, and the standard set is current, 1-30, 31-60, 61-90, and 90+ days. "Current" means not yet due. Everything after that is measured in days past the due date.

The bucket boundaries aren't arbitrary. They map to the payment terms that dominate US B2B trade, where net 30 and net 60 do most of the work. An invoice sitting in the 31-60 bucket on net-30 terms is one full cycle late, which is a different conversation than an invoice that's four days past due. If your business runs mostly on net 45 or net 60, it's worth redrawing the buckets to match rather than inheriting the QuickBooks default and then misreading your own report every month.

How does AP aging differ from AR aging?

AP aging tracks what you owe to suppliers; AR aging tracks what customers owe you. The mechanics are nearly identical and the implications are opposite, which is why the two reports get confused constantly.

A large 90+ balance on the receivables side is a collections problem and a revenue-quality problem. The same balance on the payables side is a liquidity signal, a supplier-relationship signal, or a control failure, depending on what's underneath it. The full comparison of payables and receivables is worth reading if you're building both reports for the first time.

What does an accounts payable aging report look like?

A standard AP aging report puts vendors in rows and age buckets in columns, with a total per row and a total per column. Here's a small one.

Illustrative example. Figures are not drawn from a specific company.

Read a row and you get one vendor's exposure. The Initech Services line is a single invoice that has been open more than 90 days, and it's the only thing sitting in that column. Read a column and you get a timing picture for the whole payables book, and here the oldest bucket holds more than any other. In a real ledger that's the first thing a controller asks about.

The empty 61-90 column is worth noticing too. A gap like that usually means the oldest balance is an isolated item that stopped moving rather than the leading edge of a slow-payment trend, which points at a dispute or a coding error rather than a cash constraint.

How do you read an accounts payable aging report?

You read it bucket by bucket, because each bucket carries a different operational meaning. Age is the variable, but what you do about it changes completely as the age increases.

Current and 1-30. These are healthy payables behaving as designed. The only question worth asking here is whether you're leaving discount money on the table. If a vendor offers 2/10 net 30 and your invoices consistently clear on day 28, you're paying a premium for two and a half weeks of float that your working-capital position may not need.

31-60. This is the watch zone. On net-30 terms these invoices are late, and the vendor has probably noticed even if they haven't called. Individual items here are normal. A pattern here, especially concentrated in one vendor or one approver, means something upstream is broken, and the usual culprit is an approval that never routed. Designing a routing path that doesn't strand invoices is most of what invoice approval workflows are for.

61-90. This is the action zone. Late payments at this depth start costing real money through late fees, credit holds, and the loss of preferential treatment when a supplier has to allocate scarce inventory. The cost of chasing and being chased is measurable. Growth Corporates lose roughly 4.1% of revenue on overdue B2B payment friction, according to PYMNTS Intelligence's 2026 Growth Corporates Working Capital Index.

90+. Treat this as an exception queue, not an age bucket. Genuine cash-constrained late payment at 90 days is rare in a solvent mid-market business. What's usually in there is a disputed invoice that nobody closed out, a duplicate that was caught and then abandoned in place, or something that shouldn't be in the ledger at all.

Across the whole report, the totals row is a cash forecast you already own. Sum the current and 1-30 columns and you have a reasonable picture of what's leaving in the next month without building anything new.

Protect cash flow with modern AP

Modernize AP to cut costs, speed approvals, and mitigate payment risk — gaining the real-time visibility to protect cash flow and scale with confidence.

Download the whitepaper

What does a growing 90+ bucket tell you?

A growing 90+ bucket tells you that items are entering the exception queue faster than anyone is clearing it, and the cause is almost always one of three things. Chronic dispute backlog, a cash constraint that AP is managing informally by sitting on invoices, or fraud exposure hiding inside a column nobody reconciles.

The fraud case deserves more weight than it usually gets. Billing schemes accounted for 22% of occupational fraud cases with a median loss of $100,000, and check and payment tampering carried a median loss of $155,000, according to the ACFE's Occupational Fraud 2024: A Report to the Nations. Both schemes depend on invoices that look slightly wrong and never get examined closely. An aging bucket that nobody reads is exactly that environment, which is why the AP fraud patterns worth knowing overlap so heavily with aging-report hygiene.

The attempt rate supports treating it as a live risk rather than a theoretical one. AFP's 2026 Payments Fraud and Control Survey Report found that 76% of US organizations experienced attempted or actual payments fraud in 2025.

Here's the practitioner version of this. Ask whoever owns the 90+ column to name every item in it from memory. If they can, the balance is a backlog you can work down. If they can't, you have a control problem, and a duplicate payment detection pass on that column is the fastest way to find out how big it is.

How does the aging report relate to DPO and AP turnover?

The aging report is the raw input to both metrics, which is why its accuracy matters more than its presentation. Days payable outstanding measures how long you take to pay on average; the aging report shows you where that average is coming from.

A DPO of 42 days looks fine on a dashboard and can be built two very different ways. It can be a book paying consistently at 42 days, or it can be a book paying most vendors at 30 with a tail of 120-day items dragging the average. The first is a working-capital strategy. The second is a process failure wearing a strategy's clothes. Pulling the aging report next to the days payable outstanding calculation is the only way to tell them apart, and the same logic applies to the accounts payable turnover ratio, which suffers from exactly the same averaging problem.

How do you build an accounts payable aging report?

You build it in six steps, and every one of them depends on the open-invoice data already being clean. The report is arithmetic. Getting the inputs right is the actual work.

How to build an AP aging report step by step

1. Pull every open, unpaid supplier invoice with its invoice date, due date, and amount.

2. Choose the "as of" date. Period end is conventional; today is more useful if you're diagnosing something.

3. Calculate days outstanding for each invoice against your chosen date.

4. Assign each invoice to a bucket using your real payment terms, not a default schedule.

5. Group by vendor, then total each vendor row and each bucket column.

6. Review the totals row, then work the 90+ column item by item before you look at anything else.

Step six is the one teams skip. A report you scan for the grand total is a report that has told you nothing you didn't already know.

How do you run an AP aging report in QuickBooks?

In QuickBooks, the report lives under Reports, in the "Who owes you" and "What you owe" grouping, under A/P Aging Summary or A/P Aging Detail. The summary version gives you the vendor-by-bucket grid; the detail version drops to individual invoices, which is what you want when you're working the 90+ column.

Both versions behave the same way as a spreadsheet build in one respect that matters. They report the ledger as it stands at the moment you press the button, and they inherit every coding error, every unposted invoice sitting in somebody's inbox, and every duplicate that was entered twice under slightly different vendor names.

Why do manual aging reports go stale?

A manually built aging report goes stale immediately because it's a snapshot of a dataset that keeps moving. An invoice approved an hour after you export the file doesn't exist in your report, and one keyed with a transposed due date sits in the wrong bucket until someone catches it by hand.

The cost of that staleness shows up as effort rather than as an obvious error. PYMNTS Intelligence and WEX's July 2026 Business Payments Tracker Series reported that 78% of AP professionals cited employee stress caused by weak AP processes, and 67% spend at least five days a month processing invoices. A team spending a quarter of the month on invoice mechanics is not a team that rebuilds the aging report weekly, and that's the real reason most aging reports are month-end artifacts.

The rails themselves are moving in a direction that helps here. Check volume fell to 9.2 billion payments worth $24.45 trillion in 2024, down 1.8 billion payments and $1.92 trillion from 2021, according to the Federal Reserve's 2025 Federal Reserve Payments Study. Electronic rails clear faster and settle more predictably, so the gap between "paid" in your ledger and "paid" in the vendor's ledger narrows, and the aging report stops disagreeing with the vendor's own statement quite so often.

How does AP automation keep the aging report accurate?

Automation keeps the report accurate by removing the human step between an invoice arriving and the ledger knowing about it. Capture, coding, and matching happen on receipt, so the aging buckets reflect the current state of the payables book rather than the state of it whenever someone last did data entry.

Three mechanisms do most of the work. Automated capture and coding get invoices into the subledger within hours instead of days, which is what makes a mid-month pull meaningful. Bidirectional ERP sync means the aging report and the general ledger stop diverging, so nobody has to reconcile two versions of the same number. And automated duplicate detection catches the second copy of an invoice at entry rather than 90 days later, which is where a meaningful share of stubborn 90+ balances come from.

The efficiency ceiling here is higher than most teams assume. The Hackett Group's 2025 Accounts Payable Digital World Class Matrix put average touchless invoice processing at 60%, found that organizations above 30% touchless adoption show 3.5X higher AP productivity, and measured AP cycle times improving 59% after implementation. The same firm's 2025 Digital World Class Finance research found those organizations operate at 45% lower cost as a percentage of revenue, with close cycles 35% to 57% shorter.

Once the report is trustworthy, it becomes a decision tool. You can pay to terms deliberately, capture discounts where the math supports it, and shift eligible spend onto card rails for rebate income. That last option has been scaling for years. Corporate virtual-card spending grew from $221 billion in 2019 to $314 billion in 2021, according to RPMG Research and Mastercard's 2022 Virtual Card Benchmark Survey. The mechanics of turning that into cash-flow improvement through AP automation are worth working through before you assume the rebate is the whole story.

One caution before you treat automation as a fix for interpretation. A real-time aging report still needs someone to read the 90+ column, and I've seen teams go live with a live dashboard and keep exactly the same monthly habits. The tooling changes what's possible; it doesn't change what anyone does. Whether it helps often comes down to who owns the column, and that's a staffing question rather than a software one. The same logic runs through the signs an AP process is costing more than it should and shows up again in the way auditors approach an accounts payable audit, where the aging report is one of the first artifacts requested.

Turn your aging report into a real-time view with Corpay

If your aging report is only true on the day you build it, the fix is upstream of the report. Corpay's fully managed AP service handles invoice capture, coding, matching, supplier enrollment, and payment delivery, so the payables data behind the report stays current without anyone maintaining it by hand.

That matters for the three failure points this article keeps coming back to. Automated capture and matching keep the buckets accurate instead of approximately accurate. Bidirectional sync across 100+ ERP integrations, including NetSuite, Sage Intacct, Business Central, and Acumatica, keeps the aging report and the GL telling the same story. And because Corpay pays through virtual card, ACH, and check on a single managed rail, acting on what the report shows doesn't mean opening three separate payment processes.

Customers typically save about 40% of AP team time, go live in weeks rather than quarters, and collectively earn more than $800 million in rebates per year on spend they were already committed to. Single-use virtual cards close the loop on the fraud exposure that stubborn aging balances tend to hide, since a card number that works once for one amount is a poor target.

Start with the AP automation overview, or go straight to AP and invoice automation if capture and matching are where your report breaks down.

Frequently Asked Questions

What is an accounts payable aging report?

It's a summary of unpaid supplier invoices sorted by how long they've been outstanding, grouped into current, 1-30, 31-60, 61-90, and 90+ day buckets. Finance teams use it to see near-term cash outflows, overdue obligations, and vendor-level exposure in one view.

What is the aging schedule for accounts payable?

The aging schedule is the set of buckets used to classify each open payable by age, typically current, 1-30, 31-60, 61-90, and 90+ days. The boundaries should match your actual payment terms, so a business running mostly net 60 is better served by a redrawn schedule than the default.

How do you create an accounts payable aging report?

Pull all open invoices with dates and amounts, pick an "as of" date, calculate days outstanding, assign each invoice to a bucket, group by vendor, and total the rows and columns. The arithmetic takes minutes; making sure every open invoice is actually in the ledger takes longer.

How do you run an accounts payable aging report in QuickBooks?

Open Reports and look under the "What you owe" grouping for A/P Aging Summary or A/P Aging Detail. The summary gives you the vendor-by-bucket grid and the detail version drops to individual invoices, which is the one you want for investigating old balances.

What are aged payables?

Aged payables are unpaid supplier invoices that have passed their due date and now sit in one of the older buckets of the aging report. The term is used interchangeably with overdue payables, and it excludes invoices that are open but not yet due.

What does a growing 90+ day balance mean?

It usually means disputes that were never closed, duplicates abandoned in place, or invoices that shouldn't be in the ledger, rather than deliberate slow payment. Work those items individually before drawing any conclusion about your cash position.

How is the AP aging report different from the AR aging report?

AP aging tracks what you owe suppliers; AR aging tracks what customers owe you. The report structures are nearly identical, but a heavy old bucket means a collections problem on the AR side and a liquidity or control problem on the AP side.

How does AP automation keep the aging report accurate?

Automated capture, coding, and matching post invoices to the ledger on receipt, and real-time ERP sync keeps the report and the general ledger aligned. Duplicate detection at entry removes a common source of permanent 90+ balances.

David Luther

Product Marketing Program Manager

David Luther, MBA is a product marketing program manager with years of experience in commercial banking, finance, and technology sectors, with research and writing appearing in financial publications.

AP Automation