It is 8:40 a.m. on Tuesday, two days before the weekly vendor payment run. The AP aging report shows $486,200 open, but that number alone does not tell the controller what to release.
One balance is current. Another is 47 days overdue. A third is negative because a credit memo has not been applied. Two invoices are on hold, and one vendor appears under two names. The report is technically complete — but the payment decision is not.
An AP aging report is a point-in-time list of unpaid vendor balances organized by due date and days past due. Finance teams use it to verify what is owed, identify overdue or unusual items, and decide what to pay, schedule, hold, investigate, or correct.
AP aging report key facts
| Question | Practical answer |
|---|---|
| What does it measure? | Open accounts payable as of a specific reporting date |
| What is the preferred aging basis for overdue status? | Due date, because it reflects agreed payment terms |
| What are the common buckets? | Current, 1–30, 31–60, 61–90, and 90+ days past due |
| What must be reconciled? | Invoice-level aging total, AP subledger, and AP general-ledger control balance |
| What needs separate review? | Holds, disputes, duplicate risk, partial payments, unapplied credits, and incorrect terms |
| What should the report produce? | A weekly payment and investigation plan, not only a liability total |
ERP and accounting help documentation commonly describes payable aging as a way to view total outstanding, not-due, and overdue supplier amounts on a specific date. Accounting-system guidance also highlights an important detail: unpaid invoices may be shown net of credit notes, and negative balances can appear when credits remain unapplied. These are useful reminders that an aging report is both a timing report and a data-quality control.
What is an AP aging report?
An accounts payable aging report organizes unpaid supplier invoices into time bands according to an as-of date. A detailed report normally shows each vendor, invoice, due date, original amount, remaining amount, days past due, and aging bucket. A summary report rolls those lines up by vendor or bucket.
In simple terms, it answers three questions:
- Who does the business owe?
- How much remains unpaid as of the report date?
- Is each balance current, overdue, disputed, credited, or otherwise blocked?
Standard payables aging reports illustrate the underlying mechanics: each line usually includes the invoice number, due date, days due, percentage unpaid or remaining amount, and overdue-period allocation. The report then totals the value held in each aging period.
An AP aging report is not the same as a payment run. Aging describes exposure and timing. Payment execution still requires validated bank details, approval evidence, payment controls, and an authorized release process.
AP aging report vs invoice processing vs AR aging
These reports and workflows touch the same invoices, but they answer different operating questions.
| Area | Main question | Unit of analysis | Typical action |
|---|---|---|---|
| AP aging report | What do we owe as of this date, and how overdue is it? | Open vendor balance or invoice | Pay, schedule, hold, investigate, or correct |
| Invoice processing | Is this invoice valid, coded, matched, approved, and ready to pay? | Individual invoice through workflow stages | Capture, validate, match, approve, and release |
| AR aging report | What do customers owe us, and how late are they? | Open customer balance or invoice | Collect, contact, dispute, or write off |
AP aging is a point-in-time liability view. The invoice processing workflow explains how an invoice reaches that open-payables position. AR aging looks in the opposite cash direction — toward expected collections rather than vendor payments.
What data should an AP aging report include?
A useful report needs enough detail to explain both the balance and the action.
| Field | Why it matters | Review check |
|---|---|---|
| As-of date | Defines the point in time represented by the report | Confirm every reviewer is using the same date |
| Vendor name and ID | Groups exposure and links to vendor master data | Merge aliases; keep separate legal entities separate |
| Invoice number | Identifies the payable item | Test duplicates within each vendor |
| Invoice and posting dates | Support cut-off and source-record review | Check future-dated or backdated entries |
| Due date and payment terms | Determine overdue status | Recalculate due date from approved terms |
| Original amount | Shows the starting liability | Confirm currency and tax treatment |
| Applied payments | Reduces the open balance | Match partial payments to the correct invoice |
| Applied credits | Reduces the amount payable | Identify unapplied or unrefunded credits |
| Open amount | Shows the remaining liability | Recalculate from source transactions |
| Hold or dispute status | Explains why an overdue item may not be payable | Require an owner, reason, and review date |
| PO, contract, or receipt reference | Supports the invoice's validity | Trace unresolved matching issues |
| Currency and entity | Prevent misleading consolidated totals | Separate transaction and reporting currencies |
The report should remain invoice-level until the team has finished testing exceptions. Vendor totals are useful for concentration and cash planning, but they can hide a current invoice, an old credit, and a disputed balance inside one net number.
How AP aging buckets work
The report needs three inputs: the as-of date, the aging basis, and the bucket ranges.
For a due-date aging report, days past due should be calculated from the fixed as-of date and the invoice due date. The amount in each bucket should use the remaining open balance after valid payments, credits, discounts, retainage, and adjustments are applied.
| Aging bucket | Rule | Review meaning |
|---|---|---|
| Current | Due date is on or after the as-of date | Not yet overdue; include in forward cash planning |
| 1–30 days | 1 to 30 days past due | Recently overdue; confirm payment or hold status |
| 31–60 days | 31 to 60 days past due | Owner follow-up and vendor communication needed |
| 61–90 days | 61 to 90 days past due | Material overdue exposure; escalate valid balances |
| 90+ days | More than 90 days past due | Investigate dispute, duplicate, credit, payment application, or long-running cash issue |
The familiar 30-day bands are common, not mandatory. Many accounting systems allow user-defined aging intervals or aging by days or calendar months. Whatever ranges the company chooses, the policy should be documented and used consistently so month-to-month movement is meaningful.
Should AP aging use the due date or invoice date?
Use the due date when the question is, “How overdue is this invoice under its agreed payment terms?” A Net 60 invoice and a Net 15 invoice issued on the same day should not become overdue together.
Some systems also support aging by invoice date or posting date. That can be useful for document-age analysis, operational backlog, or a specific accounting policy - but it answers a different question. The report title and methodology should state the aging basis clearly. For overdue analysis, due-date aging is usually more useful because invoice-date aging can make longer-term invoices look late before they are actually due.
How to reconcile an AP aging report before using it
Do not prioritize payments from an unreconciled aging report. A clean-looking dashboard can still carry the wrong control total.
1. Freeze the as-of date
Run every source report for the same cut-off. A historical aging should not include transactions posted after that date unless the reporting method explicitly reconstructs historical open items.
2. Reconcile the control total
Compare the invoice-level aging total with the AP subledger or trial balance and the AP general-ledger control account. Differences often come from unposted transactions, direct journal entries to the control account, timing cut-offs, foreign-currency treatment, or payments applied after the report date.
3. Recalculate open amounts
Verify partial payments, credit memos, discounts, retainage, and adjustments. A paid invoice left open overstates the liability. An unapplied credit can create a negative vendor balance or make old invoices appear larger than the amount actually payable.
4. Validate terms and due dates
Incorrect terms push invoices into the wrong bucket. Review overrides, missing due dates, and vendors whose master-data terms do not match the contract.
5. Separate exceptions from payable items
Label disputes, holds, duplicate risk, missing receipts, and approval gaps. “90+ days” is not a payment instruction — it is an age signal that still needs context.
The useful operating pattern is consistent: use the aging report to identify errors, prioritize available cash, and reconcile vendor balances with source records or the general ledger. Validate the report first, then schedule cash.
A practical AP aging report example
Assume the report is run on August 10, 2026.
| Vendor / invoice | Due date | Open amount | Days past due | Bucket | Status | Recommended action |
|---|---|---|---|---|---|---|
| Northstar Logistics / NL-8041 | Aug 5 | $7,900 | 5 | 1–30 | Valid, critical carrier | Pay in this week's run |
| BrightPath Software / BP-2218 | Jul 1 | $4,800 | 40 | 31–60 | Renewal scope unclear | Hold; owner confirms contract |
| Metro Components / MC-1187 | Jun 4 | $6,450 | 67 | 61–90 | Valid, production supplier | Escalate and schedule payment |
| Apex Office / CM-308 | — | -$950 | — | Credit | Unapplied credit memo | Apply against open invoice |
| Harbor Legal / HL-990 | May 8 | $12,500 | 94 | 90+ | Fee dispute documented | Keep on hold; set resolution date |
| Vector Office / VO-4412 | Aug 24 | $3,120 | 0 | Current | Approved | Schedule for future run |
The table turns one total into six different decisions. Paying every overdue line would release cash against a disputed invoice and ignore an available credit. Paying nothing would put a critical supplier at risk. The value of the aging report is the separation.
Turn the aging report into a weekly payment review
A strong weekly review produces a short action register rather than another static PDF.
| Action | Include when | Required output |
|---|---|---|
| Pay now | Valid overdue item, critical vendor, late-fee or service risk | Payment batch candidate and approver |
| Schedule | Current invoice due before a future payment run | Planned payment week and cash requirement |
| Hold | Dispute, mismatch, blocked vendor, or missing evidence | Hold reason, owner, and next review date |
| Investigate | Old or unusual balance without enough context | Named owner and deadline |
| Correct | Duplicate, paid-open item, wrong term, alias, or unapplied credit | Source-system correction and rerun |
Use this review sequence:
- Confirm the reconciled open-AP total.
- Compare current, overdue, 60+, and 90+ exposure with the prior period.
- Rank vendors by overdue amount and operational importance.
- Remove holds, disputes, and correction items from the payment-ready view.
- Apply available credits before requesting new cash.
- Map valid invoices to the next payment dates.
- Compare the resulting weekly cash requirement with available liquidity.
- Publish owners and deadlines for every exception left behind.
The review should preserve two views: gross exposure by invoice and net cash planned by payment week. Netting everything too early makes reconciliation harder; keeping only gross aging makes cash planning harder.
AP aging metrics worth monitoring
No single benchmark works for every industry, vendor mix, or payment policy. Track internal movement consistently instead.
| Metric | Calculation | What a change may indicate |
|---|---|---|
| Overdue AP ratio | Overdue open AP / total open AP | Payment delays, holds, cash pressure, or bad terms data |
| 60+ day exposure | AP in 61–90 and 90+ buckets | Persistent disputes, unmatched invoices, or supplier risk |
| Vendor concentration | Open AP for top vendors / total open AP | Operational dependency and payment-priority risk |
| Credit utilization | Applied credits / available credits | Whether the team is reducing cash outflow before payment |
| Hold aging | Days since hold opened | Exception-management backlog |
| Scheduled cash coverage | Planned payment cash / available payment cash | Whether the proposed run is fundable |
Treat these as diagnostic signals, not performance scores. A higher overdue ratio can mean cash stress — or one disputed legal invoice. Always drill back to the invoice detail.
Common issues hidden in AP aging
| Issue | What it looks like | Why it matters | First check |
|---|---|---|---|
| Duplicate invoice | Same vendor, invoice number, date, or amount appears twice | Overstates AP and may cause duplicate payment | Compare normalized invoice keys |
| Unapplied credit | Negative amount or old invoices alongside an unused credit | Overstates required cash | Match credit memo to eligible invoices |
| Partial payment error | Original and open amounts do not tie to payment history | Distorts bucket totals | Rebuild remaining balance from applications |
| Wrong payment terms | Invoice ages too early or too late | Creates false urgency | Compare vendor master with contract |
| Vendor alias | One supplier appears under several names | Hides concentration | Map legal name and vendor ID |
| Paid invoice still open | Payment log shows release, aging still shows balance | Overstates liabilities | Check posting and application status |
| Dispute without owner | Old balance has a note but no next action | Creates permanent 90+ clutter | Assign owner and review date |
| Currency mismatch | Local and transaction currency are mixed | Makes totals incomparable | Confirm report currency and FX date |
Negative aging balances can represent outstanding credit notes not yet applied or refunded. Report-date differences can also cause vendor balances and aging reports to disagree. Those two checks belong in every review checklist.
How to create an AP aging report from spreadsheets
Many teams export open invoices from an ERP or accounting system and finish the review in Excel or CSV. The calculation is simple; the control discipline is not.
- Export invoice-level open AP for one as-of date.
- Add payment applications, credit memos, and vendor master data.
- Standardize vendor IDs, names, dates, currencies, and status labels.
- Recalculate each open amount.
- Calculate days past due from the chosen aging basis.
- Assign one bucket to each open invoice.
- Reconcile the total to the AP control balance.
- Add action, owner, payment week, and exception notes.
- Summarize by vendor, bucket, entity, and planned cash date.
For spreadsheet work, keep the as-of date in one visible control cell and calculate days past due from that fixed date. Then assign each invoice to the right bucket based on the company's aging policy. Avoid hard-coding TODAY() into every row, because it makes prior reports difficult to reproduce and can change bucket assignments without a clear audit trail.
How AI can help with AP aging spreadsheets
AI can speed up review when the source data already exists in structured files. It is most useful for comparing fields, grouping invoices, finding patterns, and drafting a review summary.
For example, hiData AI Sheets can analyze AP aging exports, invoice lists, payment logs, and vendor files provided as Excel or CSV. A finance user can ask:
- Recalculate open balances using applied payments and credits.
- Find vendor aliases and possible duplicate invoice keys.
- Show vendors with the largest 60+ day exposure.
- Separate payment-ready invoices from holds and correction items.
- Build a four-week payment cash plan.
- Compare this month's aging buckets with last month's file.
- Draft an owner action list for unresolved 90+ day balances.
The boundary matters. File analysis does not approve an invoice, verify bank details, post an accounting correction, or release a payment. A finance reviewer still owns the source data, policy, judgment, and authorization.
Choosing an AP aging reporting tool
Choose the tool based on the missing control, not the prettiest dashboard.
| Primary need | Tool type | Verify before choosing |
|---|---|---|
| Standard aging from accounting records | Accounting system or ERP | As-of logic, due-date basis, credits, currency, detail drill-down |
| Invoice intake, matching, and approval | AP automation platform | Matching rules, approval evidence, audit trail, exception ownership |
| Vendor payment execution | Payment platform | Authorization, bank controls, payment status, reconciliation |
| Analysis of exported files | Spreadsheet or AI spreadsheet tool | Explainable transformations, editable output, repeatable review steps |
| Month-end control | Reconciliation workflow | AP subledger-to-GL tie-out, sign-off, correction tracking |
If the main issue is choosing among spreadsheet-analysis products, see this comparison of AI spreadsheet tools. If the main issue is intake through approval, evaluate an invoice-processing or AP automation workflow instead.
Frequently asked questions
What is an AP aging report in simple terms?
An AP aging report lists unpaid vendor balances as of a specific date and groups them by how overdue they are. It helps finance decide what to pay, schedule, hold, investigate, or correct.
What are the standard AP aging buckets?
The common buckets are Current, 1–30, 31–60, 61–90, and 90+ days past due. Companies may use different intervals, but the ranges and aging basis should stay consistent across reporting periods.
Should an AP aging report use invoice date or due date?
Use due date when measuring overdue status under agreed payment terms. Invoice-date or posting-date aging can support document-age or backlog analysis, but the report should label that methodology clearly.
Why does an AP aging report show negative balances?
Negative amounts often represent unapplied credit notes, overpayments, or other adjustments. Review the vendor detail before netting the balance or releasing additional cash.
How often should AP aging be reviewed?
Many teams use a working report for weekly payment planning and a formally reconciled report at month-end. Higher invoice volume, tighter liquidity, or sensitive supplier relationships may require more frequent review.
Why does AP aging not match the general ledger?
Common causes include different as-of dates, unposted items, direct entries to the AP control account, future-dated transactions, incorrect payment applications, currency treatment, or cut-off differences. Reconcile the invoice-level detail before using the report for decisions.
Can AI create an AP aging report?
AI can calculate buckets, compare files, identify possible duplicates or credits, and produce payment-review tables from structured data. The result still requires finance validation and does not replace accounting posting, approval, or payment controls.
Sources and methodology
This guide uses a due-date aging approach for overdue status and treats the report as a point-in-time open-payables control. Product capabilities and reporting options vary, so confirm the accounting policy and source-system settings used by your organization.
Editorial references consulted for accuracy:
- SAP Help documentation for payable aging views
- Oracle sample Payables Invoice Aging Report
- Sage Help documentation for accounts payable aging reports
- Public practitioner guides on AP aging, due-date aging, reconciliation, and credit-note review
Conclusion
An AP aging report should do more than total unpaid bills. It should establish a reliable as-of balance, explain where that balance sits in time, and separate payable cash from holds, credits, disputes, and corrections.
The best weekly review has a clear end state: every material line is assigned to Pay, Schedule, Hold, Investigate, or Correct, and valid payments are mapped to a fundable cash plan.
