AP Aging Report

AP Aging Report is a report that groups outstanding payables by how long they have been unpaid, typically in 30-day buckets (current, 31-60, 61-90, 90+), showing the company's unpaid obligations to vendors. The aging report is also the control for discount capture, since an invoice sitting in the first bucket may still be inside an early payment discount window.

Category: Accounts Payable Automation SoftwareBest Accounts Payable Automation Software

Your CFO asked for a cash forecast on Thursday. Finance pulled the AP aging report. It showed $1.8M in invoices due in the next two weeks, but 14% of those had already been paid and hadn't been matched in the system yet. The aging was running on stale data, so the cash forecast was wrong before it started. An AP aging report is a snapshot of all outstanding vendor invoices, organized by how long they've been unpaid relative to their due date. The standard buckets are current, 1 to 30 days past due, 31 to 60 days, 61 to 90 days, and 90+ days. It's the main tool for seeing what a company owes vendors at a given point in time, which payments are coming up, and whether payables are being managed within agreed terms. What it is not: a reliable cash forecast input until it has been reconciled against the general ledger and unposted payment records. When payments are made but not matched in the AP system, when invoices are in the system but disputed, or when the report runs on stale data, the aging misstates actual obligations. Finance teams that feed aging numbers straight into cash planning without checking the underlying data are working from a number that may be wrong.

How the AP aging report is built

An AP aging report is generated from open invoice records in the accounts payable system. Each invoice carries a due date, and the aging calculation places it in a bucket based on how many days have passed since that due date. The report totals those invoices by vendor and by bucket to show total outstanding payables. That picture is only as accurate as the underlying data, and three kinds of data problems distort AP aging again and again. First, payment timing: when a payment is initiated (a check mailed, an ACH batch sent, a wire released), there's usually a delay before it posts and the invoice is marked cleared in the AP system. During that window, the invoice still shows as outstanding even though the obligation has effectively been met. Second, invoice processing lag: invoices received but not yet entered into the AP system don't appear on the aging report at all. If it takes two to three days from invoice receipt to system entry, the aging will always understate what's owed. Third, invoice holds and disputes: invoices on hold for approval or dispute aren't always flagged differently on the aging report. A $200K invoice in the 61 to 90 day bucket looks the same whether it's overdue because someone missed a payment or because of an unresolved vendor dispute. The first is a cash obligation; the second shouldn't be paid until the dispute is settled.

Aging buckets, early payment discounts

Aging bucket boundaries look simple (current means not yet due, past-due means past the invoice due date), but they get complicated when payment terms include early payment discounts. If a vendor offers 2/10 net 30, the invoice is due in 30 days, but the effective economic due date is day 10 if you want the discount. An aging report using the net 30 due date shows the invoice as current on day 15, even though the discount has already expired. AP teams managing discount capture need to track discount expiry dates separately from invoice due dates, or use an AP system that shows discount windows alongside standard aging. Unapplied payments are the most common cause of aging distortion. When a payment is issued but not matched to specific invoices, because of system timing, missing remittance information, or gaps in cash application, the payment sits in an unapplied account while the original invoices keep aging. The aging report still shows those invoices as outstanding. The GL accounts payable balance, which reflects the unapplied payment, is lower. A difference between the aging total and the GL balance tells you reconciliation is needed before either number is used for planning.

How platforms handle it

AP aging reports in most systems are generated on demand, but what that means varies a lot. Some platforms calculate aging from live invoice and payment data at the moment you run the report. Others calculate it in a scheduled overnight batch, so a report run at 3 PM reflects yesterday's payment activity. For a company processing hundreds of payments per day, that difference matters in any time-sensitive cash planning conversation. The main question when evaluating AP automation software is whether the aging report is point-in-time or as-of-close. A point-in-time report can be run as of any date and reflects the payment and invoice state on that date. As-of-close reports only reflect end-of-period snapshots. For a CFO who wants to know real-time AP exposure on a Wednesday afternoon, the answer should be point-in-time. Drill-down matters just as much: you should be able to click into a bucket and see the specific invoices, their hold status, their associated POs, and their payment history. Aggregate aging numbers without invoice-level detail need manual follow-up before anyone can interpret them.

Questions to ask

Has the AP aging total been reconciled against the GL accounts payable balance, and is the difference explained by unapplied payments or timing?
How current is the underlying data? Is the aging running on live data or overnight batch calculations?
Are invoices on hold or in dispute flagged separately in the aging, or do they blend into the past-due buckets?
Are payments that have been initiated but not yet posted in the system excluded from the outstanding totals?
Does the aging report reflect payment terms including early payment discount windows, or only net due dates?
Is the aging total being used directly as a cash forecast input, or is it validated against payment activity before use?

Common mistakes

The most consequential mistake with AP aging is feeding it directly into cash forecasting without first reconciling it against the GL and unposted payment records. When the aging shows $1.8M due in the next two weeks but $250K of that has already been paid and is waiting to clear, the cash forecast overstates near-term cash needs. Decisions made on that forecast, such as drawing on a credit line, delaying other payments, or changing investment timing, rest on bad data. The second mistake is not reconciling AP aging to the GL accounts payable balance on a regular schedule. The aging-to-GL reconciliation is a basic AP control that should happen at least at month-end, and ideally weekly for companies with high payment volume. The difference between the two is almost never zero, but understanding and explaining it (unapplied payments, timing items, system processing lags) is how AP teams know the numbers are reliable.

Comparing AP automation

AP tools separate on what happens to the exceptions: the invoices that do not match a PO, arrive without one, or need a second approver. Once AP Aging Report is settled as a requirement, read the Accounts Payable Automation Software category guide for how the market splits, then weigh the Stampli profile against the Tipalti profile on that requirement rather than on the feature list. Our Tipalti pricing breakdown records what the vendor publishes and what is quote-based. The BILL against Stampli comparison sets two of them side by side on the same criteria. Before you book demos, put your own numbers through the AP automation savings calculator so the business case is written down before a vendor writes it for you.

AP Aging Report questions

How is AP aging different from AR aging?

AP aging tracks what your company owes vendors, organized by how overdue each invoice is. AR aging tracks what customers owe your company, organized the same way. Both use aging buckets to sort open balances by time elapsed, but the actions they drive are opposite: AP aging drives outgoing payment prioritization, and AR aging drives collections outreach. Looking at both together shows your cash position: when payments need to go out versus when cash is expected to come in.

Why does the AP aging report sometimes not match the accounts payable balance in the general ledger?

The most common cause is unapplied payments: payments that have been issued and posted to the bank and GL but haven't been matched to specific invoices in the AP system yet. Those invoices keep appearing on the aging report as outstanding. Other causes include timing differences between when an invoice is entered in AP and when it posts to the GL, and invoices that exist in one system but not the other because of processing errors. Reconciling aging to GL at month-end, with a documented explanation of the difference, is standard AP practice.

How often should the AP aging report be reviewed?

For most companies, weekly review is the minimum for day-to-day management: catching invoices approaching their due dates before they go late, spotting unexplained overdue payments, and flagging holds that need resolution. Reconcile AP aging to the GL accounts payable balance at least at month-end. Companies with high invoice volume or tight cash management may review aging daily.

ACH Payment, Approval Workflow, and Duplicate Invoice Detection come up in the same workflow as AP Aging Report, and the rest of the AP automation cluster is indexed in the finance operations glossary.