Skip to main content
    SplashBI
    Finance Analytics

    What Is an Accounts Payable Aging Report? In-Depth Guide and Example

    Learn how to age unpaid supplier balances correctly, reconcile AP to the ledger, and connect due dates with cash planning.

    SplashBI Editorial
    SplashBI Editorial
    Product Intelligence Team
    ·October 7, 2026·7 min read·
    Controller and accounts payable manager reviewing account payable aging report
    Finance Analytics

    An accounts payable aging report is a point-in-time schedule of recorded, unpaid supplier balances grouped by supplier and days relative to each installment's due date. It shows upcoming and overdue obligations, helping finance teams manage payments, forecast cash, investigate exceptions, and reconcile Payables to the general ledger.

    What Does an Accounts Payable Aging Report Show?

    An AP aging report shows recorded supplier invoices, credit memos, and other open items that remain unpaid as of a defined date. It organizes those balances by supplier and due-date bucket so finance teams can see upcoming obligations and overdue exposure.

    A summary report shows totals by supplier. A detail report should add the invoice and installment number, invoice date, due date, payment terms, original and remaining amounts, currency, and aging bucket. Approval status, holds, discounts, PO references, planned payment dates, entities, liability accounts, and exception owners make those balances actionable.

    The report covers recorded AP transactions. Accrued expenses, unbilled receipts, missing invoices, and liabilities posted only to the general ledger may sit outside the AP aging and require separate close controls.

    How Do AP Aging Buckets Work?

    AP aging buckets group each open installment according to the number of days between its due date and the report's as-of date.

    Days past due = As-of date - Contractual due date

    Days Past Due Recommended Bucket Interpretation
    0 or negative Current Due today or in the future
    1 to 30 1-30 Up to 30 days overdue
    31 to 60 31-60 Between 31 and 60 days overdue
    61 to 90 61-90 Between 61 and 90 days overdue
    91 or more 91+ More than 90 days overdue

    Use 91+ after a 61-90 bucket. Labeling the last column 90+ would place day 90 in two ranges unless the preceding bucket ended at 89.

    Worked AP aging example

    Assume the report date is September 30 and all values are in the reporting currency.

    Supplier Open Installment Due Date Days Past Due Bucket Remaining Amount
    Supplier A INV-1041-1 October 15 -15 Current $35,000
    Supplier B INV-2087-1 September 20 10 1-30 $18,500
    Supplier C INV-3302-2 August 14 47 31-60 $12,000
    Supplier D INV-4110-1 July 15 77 61-90 $7,500
    Supplier E INV-5048-1 June 15 107 91+ $4,000

    If an invoice has been partly paid, only its remaining amount belongs in the bucket. Show open credits and flag payment holds rather than silently excluding them from supplier exposure.

    How Do You Create an Accounts Payable Aging Report?

    Create the report by defining its scope, identifying open installments as of the report date, applying due-date logic, and reconciling the resulting total.

    Step Activity Control Check
    1. Define scope Select the date, entities, accounts, suppliers, and currencies Parameters are repeatable
    2. Extract open items Retrieve installments, credits, payments, and adjustments Reversals are treated correctly
    3. Calculate open amounts Determine each unpaid balance as of the selected date Partial activity is reflected
    4. Confirm due dates Use the due date derived from payment terms Invoice age remains separate
    5. Assign buckets Apply one bucket to each open amount No gaps or overlaps exist
    6. Add context Attach holds, status, disputes, discounts, and planned payments Exceptions remain visible
    7. Translate currency Retain transaction currency and apply the reporting rule Mixed currencies are not added
    8. Reconcile Compare aging with the AP trial balance and GL Differences are explained

    Today's amount remaining does not necessarily show what was open at an earlier month-end. Historical aging needs an as-of report, retained snapshots, or logic that reconstructs activity through the selected date.

    How Do You Build AP Aging from Oracle Payables?

    Oracle provides separate reports for aging, historical supplier balances, cash requirements, and reconciliation. Choosing the report that matches the question prevents valid but differently scoped totals from being treated as errors.

    • The Payables Invoice Aging Report lists unpaid invoices across four configured aging periods and can convert amounts to ledger currency.
    • The Supplier Balance Aging Report can be generated for a specific date. Oracle states that it considers invoices that are accounted and transferred to the general ledger, allowing its balances to align with the trial balance.
    • The Payables Cash Requirement Report forecasts payment needs using payment-process parameters such as pay-through date, payment date, approval, and validation status.

    For custom Oracle reporting, use the payment schedule as the analytical grain. AP_INVOICES_ALL supplies invoice information, while AP_PAYMENT_SCHEDULES_ALL holds installment due dates, remaining amounts, payment status, discount dates, and hold status. Payments, credits, prepayments, and holds complete the view.

    In Fusion Cloud, table names explain the model but do not imply direct database access. Reporting routes include Oracle Analytics Publisher, OTBI, extracts, APIs, and approved integrations. The Payables Invoices - Installments Real Time subject area uses payment-schedule grain.

    Oracle identifies unaccounted transactions, non-Payables journals, unposted subledger journals, filter differences, rounding, and later activity as possible reconciliation differences. See its Payables-to-Ledger reconciliation guidance.

    How Do You Build AP Aging from SAP FI-AP?

    In SAP, build aging from supplier open items, remaining amounts, and net due dates, with company-code, currency, clearing, and payment-block context.

    A practical S/4HANA model should include supplier, company code, journal reference, baseline and due dates, payment terms, currencies, open amount, clearing status, and payment-block reason.

    SAP's Aging Analysis Cube aggregates payables by net due interval and account, including company code or supplier. The Manage Supplier Line Items workflow supports reviewing open line items and payment blocks.

    Extraction differs between SAP ECC and S/4HANA. Use supported Fiori, CDS, API, or reporting content appropriate to the deployed release rather than treating one legacy table combination as universal.

    AP Aging vs. Cash Forecast vs. DPO

    AP aging, a cash forecast, and days payable outstanding use related data but answer different questions.

    Measure Question It Answers Primary Basis
    AP aging Which recorded supplier balances are due or overdue? Open installment amount and due date
    Payment cash forecast What is likely or eligible to be paid in the forecast period? Approvals, holds, discounts, payment runs, and planned dates
    DPO How long does the organization take, on average, to pay suppliers? Average trade AP relative to purchases or COGS over a period

    When reliable credit-purchase data is available:

    DPO = (Average trade accounts payable / Credit purchases) × Days in period

    COGS is often used as a proxy when credit purchases are unavailable. Disclose and apply the method consistently. DPO is not the average age of today's open invoices.

    APQC recommends evaluating DPO with payment terms, on-time payments, discounts, liquidity, supplier relationships, and relevant peers. There is no universal target.

    For a wider liquidity view, see how AP aging contributes to working-capital analysis.

    What Makes an AP Aging Report Reliable During Close?

    A reliable report uses controlled definitions, reconciled data, transparent exceptions, and a drill path to supporting transactions.

    Common Error Why It Distorts the Report Control
    Aging from invoice date Makes valid long-term invoices appear delinquent Age from due date and show invoice age separately
    Using original invoice value Overstates exposure after partial payment Use the remaining installment balance
    Excluding held invoices Hides recorded liabilities Show holds as a separate status
    Combining currencies Produces meaningless totals Translate through a governed rate and date
    Ignoring credits and prepayments Overstates supplier balances Display and reconcile open credit positions
    Treating aging as proof of completeness Misses unrecorded invoices and accruals Perform cut-off and unrecorded-liability controls
    Skipping AP-to-GL reconciliation Leaves unexplained accounting differences Reconcile scope, status, period, and control accounts

    An accounts payable aging report can support an accounts payable internal audit, but it does not guarantee compliance or audit readiness by itself. Reviewers still need evidence of completeness, authorization, cut-off, payment controls, and exception resolution.

    How SplashBI Connects Oracle AP Aging Analysis

    An AP aging report can be mathematically correct and still be difficult to use when it is a static export with no route back to the invoice, journal, payment status, or GL balance.

    SplashBI Finance Solutions provides Oracle reporting content across AP, AR, GL, cash flow, procurement, and period close. Documented capabilities include AP aging, payment timing, custom aging logic, role-aware access, and transaction drill paths.

    For teams that work in Excel, GL Connect supports Oracle E-Business Suite, Oracle Fusion Cloud ERP, and Oracle Cloud EPM. Users can refresh reports and drill from GL balances into journal and subledger detail.

    For broader reporting context, explore general ledger reporting and the capabilities of modern financial reporting software.

    Turn Supplier Balances Into Controlled Payment Decisions

    An effective accounts payable aging report does more than sort invoices into columns. It shows the correct remaining balance, explains why an item is due or blocked, reconciles to Finance, and connects contractual obligations with expected cash outflows. That combination gives Controllers, AP managers, and Treasury a shared view without confusing aging, payment forecasting, and DPO.

    Tags
    Accounts PayableAP AgingFinance AnalyticsOracle PayablesSAPCash Management
    SplashBI Editorial
    SplashBI Editorial
    Product Intelligence Team

    The SplashBI Editorial team covers enterprise analytics, AI-driven decision-making, and the future of Finance and HR intelligence.

    Frequently Asked Questions

    What is the difference between an AP aging report and an AP trial balance?

    An AP aging report groups open supplier installments by due-date bucket for payment and exception management. An AP trial balance organizes accounted, unpaid or partially paid invoices by supplier and liability account to support reconciliation with the general ledger. Their totals may differ when scope or accounting status differs.

    Should AP aging use the invoice date or due date?

    Use the contractual due date when measuring whether an invoice is overdue. Invoice-date aging measures how long the document has existed and can be useful for process analysis, but it may classify invoices as old even when they remain within agreed payment terms.

    Why does the AP aging report not match the general ledger?

    Common causes include unaccounted invoices, payments not transferred or posted, manual journals in AP control accounts, different as-of dates, currency conversion, excluded entities or accounts, intercompany filters, rounding, and activity recorded after one report was prepared.

    Can an accounts payable aging report be used as a cash forecast?

    It is an input, not a complete forecast. Due dates show contractual obligations, while expected cash outflows also depend on approval, validation, holds, payment runs, discount decisions, bank calendars, available liquidity, and planned payment dates.

    Does a higher DPO mean accounts payable is performing better?

    Not necessarily. Higher DPO can preserve cash, but it may also indicate late payments, missed discounts, disputes, or supplier strain. Evaluate it against negotiated terms, on-time payment performance, industry context, liquidity strategy, and supplier criticality.

    More from the SplashBI blog

    Stop waiting for reports. Just ask