Accounting · Payables and payment planning

Accounts Payable Aging: Report, Example, and Payment Planning

An accounts payable aging report shows what a business owes vendors and how open balances are distributed by age or due date. It helps the AP team verify obligations, identify overdue bills, resolve disputes, and prepare a supported payment plan. The report is most useful when the vendor detail reconciles to the general ledger and each exception has an owner.

← Accounting hub · Accounts Receivable Aging · Bank Reconciliation

Quick definition: AP is money the business owes its vendors for recorded purchases on credit. Aging organizes the remaining balances into time buckets. It does not authorize payment or establish that every bill is valid.

AP aging versus AR aging

Accounts payable concerns amounts owed to vendors. Accounts receivable concerns amounts owed by customers. Both reports explain a control-account balance through individual transactions, but their operating decisions differ: AP supports verification and payment scheduling; AR supports collection and dispute resolution.

Use both to understand the timing of Working Capital. A large receivable balance is not the same as cash available to pay this week’s bills.

Set the aging basis and cutoff

Invoice age = report date − invoice date. Days past due = report date − contractual due date. The example here uses due-date aging and calendar days. Bills due today or later are current; an unpaid bill enters the 1–30 bucket the day after its due date.

A bill dated September 1 with an October 1 due date is 29 days old at September 30, but it is not overdue. Report settings differ by software, so state the as-of date, aging basis, bucket boundaries, entity, currency, and included AP accounts.

Bucket used hereDefinitionTypical review
CurrentDue today or later.Validate approval and plan payment by the agreed date.
1–30 days past due1–30 calendar days overdue.Check processing delays, missing approvals, and payment status.
31–60 days past due31–60 days overdue.Resolve disputes and escalate material unpaid obligations.
61–90 days past due61–90 days overdue.Review vendor communication, service risk, and authorized payment arrangements.
91+ days past dueMore than 90 days overdue.Investigate validity, unapplied credits, duplicates, and unresolved obligations.

Worked AP aging example

Original hypothetical report as of September 30, 2026: all balances are in one currency and reflect payments and credits posted through cutoff. One open bill per vendor is used for clarity.

Vendor / billDue dateDays past dueBucketOpen balance
North Supply / AP-201October 15, 2026Not yet dueCurrent$6,000
East Services / AP-202September 20, 2026101–30$2,500
West Materials / AP-203August 20, 20264131–60$1,500
South Repair / AP-204July 20, 20267261–90$800
Central Parts / AP-205June 20, 202610291+$200
Total$11,000

The total is $6,000 current plus $5,000 overdue. Overdue share = $5,000 ÷ $11,000 × 100 = approximately 45.5%. This example excludes vendor debit balances and unapplied credits. Define the denominator explicitly when those exist.

East Services originally billed $4,000; an applied $1,500 payment leaves $2,500 open. The remaining balance retains the original due date unless a supported agreement changes the terms. The age of a bill does not restart automatically when a partial payment is made.

Reconcile the AP subledger to the general ledger

  1. Use consistent settings: the aging and GL must share the cutoff, entity, currency basis, accounts, and posting scope.
  2. Compare totals: reconcile the net vendor detail to the AP control account, explaining separately reported debit balances and credits.
  3. Investigate differences: review direct journals, unassigned vendors, unapplied payments or credits, date filters, and report configuration.
  4. Check supporting documents: compare open bills with invoices, purchase evidence, approvals, payment records, and vendor statements.
  5. Correct supported errors: use the system’s bill, payment, credit, or correction workflow and retain the audit trail.
  6. Rerun and sign off: preserve the final report, GL tie-out, exception listing, preparer, and reviewer.

Assume the example AP control account has an $11,000 credit balance at September 30. It agrees with the aging. An arithmetic tie is necessary, but it does not prove that every bill is genuine, approved, or recorded in the correct expense period.

Review duplicates, credits, and unusual balances

  • Potential duplicates: compare vendor, invoice number, amount, date, and source document. Similar amounts alone do not prove duplication.
  • Vendor credits: confirm the credit exists and is applicable, then apply it to the appropriate bill. Keep unapplied credits visible.
  • Debit vendor balances: investigate overpayments, advances, duplicate payments, or misapplications; do not automatically net unrelated vendors.
  • Paid bills still open: trace whether the payment is unapplied, assigned incorrectly, dated after cutoff, or recorded outside the AP workflow.
  • Vendor-statement differences: reconcile missing invoices, timing, credits, and payments rather than booking the statement total without review.

Aging only shows recorded activity. Missing invoices and unrecorded period-end obligations require separate cutoff and completeness procedures. Review received goods or services, later invoices, and other supporting evidence as part of the close rather than assuming the aging contains every liability.

Journal-entry examples: AP decreases with a debit

These simplified accrual-accounting entries omit sales tax and other complications. Use the account supported by the actual purchase: an expense, inventory, prepaid asset, or fixed asset may be appropriate.

EventDebitCredit
Record a valid $1,000 repair bill.Repairs expense $1,000Accounts payable $1,000
Pay $600 against that bill.Accounts payable $600Cash $600
Correct a separately confirmed, unpaid $1,000 duplicate repair bill that was posted to expense.Accounts payable $1,000Repairs expense $1,000

AP is normally a credit-balance liability. Crediting AP increases the obligation; debiting AP reduces it. The duplicate correction above does not involve cash because the duplicate was unpaid. It does not apply unchanged if the duplicate affected inventory, an asset, tax, or a different period.

Use a supported correction with approval and the appropriate period treatment. In systems that track open bills, a standalone journal entry may leave the bill unpaid until properly linked; preserve vendor detail and apply the correction through the intended workflow. Running an aging report alone creates no journal entry.

Turn the report into a payment plan

First verify that each proposed payment is valid, approved, not already paid, and properly credited. Then evaluate contractual due dates, critical-service risk, agreed discounts, disputes, and available cash. Age is one input, not the only ordering rule.

For the example, the team would examine why $5,000 is overdue while reserving visibility of the $6,000 due October 15. It should not assume the oldest $200 is the highest operational risk or that the current $6,000 can be ignored until the next monthly review.

Payment planning record: vendor; bill reference; open amount; due date; approval status; credits; dispute or hold reason; proposed payment date; payment method; cash forecast week; owner; reviewer; confirmation and posting reference.

Put proposed disbursements into the cash forecast alongside expected customer receipts and other commitments. A plan can require negotiating an authorized arrangement or escalating a shortfall; changing the aging date does not change what is owed. Use the Cash Conversion Cycle to understand the broader timing relationship.

Connect payment records to bank reconciliation

A recorded payment can reduce AP before it clears the bank. An outstanding check may therefore be absent from open AP while still appearing as a timing item on the bank reconciliation. Paying it again because the bank has not cleared it would create a new problem.

If a check is lost, voided, or replaced, trace the original liability, payment, cash effect, and vendor application together under the approved workflow. Do not remove an old item merely because it has aged; verify its actual status and treatment.

Useful KPIs and their limits

  • Overdue dollars and share: report the absolute exposure and percentage with the same scope each period.
  • On-time payment rate: define whether the population is bills due or bills paid; include overdue unpaid items when evaluating compliance against due dates.
  • Exception backlog: track unresolved approval, credit, duplicate, and statement differences with owners and age.
  • AP processing time: distinguish receipt-to-entry, entry-to-approval, and approval-to-payment; each identifies a different constraint.

Longer payment timing is not automatically better performance. Compare it with agreed terms, discounts, supplier reliability, and service consequences. See KPIs: Examples and Formulas for consistent measurement practices.

Month-end review checklist

Confirm: report date and aging basis; valid due dates; partial payments and credits; duplicate checks; vendor-statement differences; debit balances; cutoff and missing-invoice review; subledger-to-GL agreement; payment holds and owners; cash forecast impact; reviewer sign-off.

Frequently asked questions

Does AP aging show every future cash payment?

No. It shows recorded AP within the chosen scope. Payroll, debt, taxes, capital commitments, future purchases, and unrecorded obligations may require other forecast inputs.

Should old bills be deleted?

No automatic deletion follows from age. Confirm validity, payment history, credits, and supporting evidence, then use an approved correction or resolution process.

Can AP aging tie while individual vendors are wrong?

Yes. Misapplications can offset across vendors without changing the control-account total. Review the underlying detail and vendor statements as well as the aggregate tie.

Why does the bank reconciliation still show a check after AP is reduced?

The payment was recorded in the books but has not cleared at the bank cutoff. That is a timing difference if the transaction is valid and correctly recorded.

Continue learning

Read Accounts Receivable Aging for the collection side, Bank Reconciliation for cash verification, and Debits, Credits & Journal Entries for the posting logic. Return to the Accounting hub.

Source and example notes

Sage Intacct: Vendor Aging report explains vendor aging, reporting periods, and configuration. The September schedule, calculations, entries, payment-planning workflow, and checklist are original educational illustrations. Actual handling depends on source evidence, system controls, accounting policy, and reporting period.