AP Aging 60+ Days, Oracle ERP Cloud

AP Aging 60+ Days is the share of your total Accounts Payable balance that is 60 or more days old. A cash-conservation and supplier-relationship gauge sourced from Oracle Payables.

Metrics type: Supporting Metrics • Category: Ecommerce Platform

The percentage of your total Accounts Payable balance that is 60 or more days old. High AP aging can mean disciplined cash conservation, or it can mean strained suppliers and missed discounts.

At a glance

AP Aging 60+ Days expresses, as a single percentage, how much of your open Accounts Payable sits in the 60-plus-day aging band relative to the whole AP balance. Read it alongside intent: a controller deliberately stretching terms to preserve cash will show high aging on purpose, but the same number can signal a stalled approval queue, lost early-payment discounts, or suppliers about to put you on hold. The figure is sourced from Oracle Payables and recomputed against the live subledger.

What it counts	The open Accounts Payable amount whose aging (measured from invoice due date) is 60 days or greater, divided by the total open AP balance, across every in-scope Business Unit and ledger. Numerator and denominator both come from unpaid and partially-paid Payables invoices in Oracle Fusion Payables.
Currency	Computed as a ratio so the headline is currency-neutral, but the underlying numerator and denominator are consolidated in the reporting ledger’s functional currency (typically USD or the parent legal entity’s currency) using Oracle’s GL Translation cadence before the ratio is taken.
Business Unit scope	Respects the dashboard’s selected Business Unit filter. By default rolls up every Business Unit the connected role can see across all primary ledgers.
Time window	30D vsP (default 30D vs the prior 30D), so you see the trend in the aging band, not just a static snapshot.
Alert trigger	Fires when AP Aging 60+ Days exceeds 30% of the total AP balance.
Roles	owner, finance

Calculation

Calculated automatically from your Oracle ERP Cloud data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

Worked example

A US Fortune 500 omnichannel speciality retailer running Oracle ERP Cloud across three Business Units (US Retail Inc, UK Retail Plc, EU DTC NV) under two primary ledgers. The 30-day window covers 23 May 26 to 21 Jun 26. The reporting ledger is the US ledger (USD), so all bands below are shown after translation.

AP aging band	Open balance (USD)	Share of total AP
Current (not yet due)	$14,200,000	47.3%
1 to 30 days	$6,900,000	23.0%
31 to 60 days	$2,600,000	8.7%
61 to 90 days	$3,950,000	13.2%
90+ days	$2,350,000	7.8%
Total open AP	$30,000,000	100%
AP Aging 60+ Days (this card)	$6,300,000	21.0%

Five things to notice:

1. The 60+ band is the last two rows combined. $3.95M (61 to 90) plus$2.35M (90+) gives $6.3M, which is 21.0$30M total. The card reports the percentage, not the dollar figure, but Vortex Mind keeps the underlying value for drill-down.
2. 21.0% is below the 30% alert threshold, so the Nerve Centre stays quiet. The trendline still renders on the card, and last period read 18.4%, so the band is creeping up. That is the kind of slow drift the 30D vsP window is designed to surface before it trips the alert.
3. High aging here is not automatically bad. This retailer negotiated Net-60 terms with two large apparel suppliers, so a chunk of the 61-to-90 bucket is contractually on-time, not delinquent. Pair this card with Vendor Payment On-Time Rate to separate deliberate stretching from genuine lateness.
4. Missed early-payment discounts hide in here. Several of the 90+ invoices carried 2/10 Net 30 terms. By drifting past 60 days the team forfeited the 2% discount, a real margin leak that the aging percentage alone does not show.
5. The denominator moves too. A large invoice batch posted on 20 Jun 26 inflated total AP, which mathematically lowered the 60+ percentage even though no old invoice was paid. Always read the ratio with the absolute balance in mind, which is why this card pairs naturally with AP balance and DPO views.

Sibling cards merchants should reference together

AP Aging 60+ Days is one half of the working-capital picture. Pair it with these to see the full payables-and-receivables cycle.

Card	Why pair it with AP Aging 60+ Days
AR Aging 60+ Days	The mirror image on the receivables side. Comparing AP and AR aging tells you whether you are funding your business on suppliers’ money or on customers’ lateness.
Vendor Payment On-Time Rate	Separates deliberate term-stretching from genuine delinquency. High aging with high on-time rate is healthy; high aging with low on-time rate is a problem.
Active Suppliers	Context for the AP base. A growing supplier count naturally grows the denominator.
Cash Collected	What is coming in to fund what is going out. Aging AP is only safe if collections keep pace.
AR Balance (live, by Business Unit)	The receivables counterweight to your payables position, sliced by Business Unit.
Oracle Fusion Health Score	The composite roll-up that AP aging feeds into alongside other integrity signals.

Reconciling against Oracle ERP Cloud

Where to look in Oracle ERP Cloud:

The closest native equivalents in the Oracle Fusion UI are:

Navigator → Payables → Reports → Payables Aging Report (by Aging Period) Navigator → Payables → Invoices → Manage Invoices (transaction-level view of unpaid invoices) Reports and Analytics → OTBI → Financials → Payables Invoices Real Time Subject Area

The Payables Aging Report grouped into your standard aging buckets should reconcile to this card when you select the same as-of date and the same Business Unit scope. Sum the 61-to-90 and 90+ columns, divide by the report’s grand total, and you have the card’s percentage. Most Fortune 500 finance teams reproduce this in OTBI against the Payables Invoices Real Time Subject Area so they can pivot by supplier and Business Unit.

Common mistakes when comparing against Oracle’s own reports:

• Aging by invoice date vs due date. Oracle’s Payables Aging Report can age from either the invoice date or the due date. This card ages from the due date. A report run on invoice-date basis will look older than the card.
• Including invoices on payment hold. Invoices placed on hold still sit in AP and still age. If your report excludes held invoices, it will show a lower 60+ percentage than the card.
• Prepayments and credit memos. Supplier credit memos and applied prepayments reduce the net AP balance. A report that lists only standard invoices, ignoring negative lines, overstates the denominator and skews the ratio.

Why our number may legitimately differ from Oracle’s reports:

Reason	Direction	Why
Aging basis (due date vs invoice date)	Either	The card ages from due date. An Oracle report run on invoice-date basis ages everything earlier and inflates the 60+ band. Match the basis before comparing.
Held invoices included or excluded	Either	Invoices on payment hold age but may be filtered out of a custom report. The card includes them in the open AP balance.
Business Unit and ledger scope	Either	A report run for a single Business Unit will not match a consolidated card view. Always align scope with the dashboard filter.
FX translation timing	Small	The card translates foreign-currency invoices into the reporting currency before taking the ratio. A report run in a single ledger currency can differ slightly on mixed-currency AP.
Subledger vs GL timing	Small	This card reads the Payables subledger. A short backlog in Create Accounting can leave the GL trial balance momentarily out of step with the subledger aging.

Known limitations / merchant FAQs

Is a high AP Aging 60+ percentage always a warning sign? No. A controller deliberately preserving cash by paying to terms (Net-60 with key suppliers, for example) will legitimately carry a high 60-plus band. The number becomes a warning only when it is involuntary: stalled approvals, disputed invoices, or genuine cash shortage. Read it next to Vendor Payment On-Time Rate to tell the two apart.

Does the percentage age from the invoice date or the due date? From the due date, which is the relevant economic point for delinquency. An invoice with Net-60 terms is not “60 days old” in the sense that matters until 60 days after its due date. Oracle’s Payables Aging Report can be configured either way, so align the basis before reconciling.

Why did the percentage drop when I did not pay anything off? Because the denominator (total open AP) grew. A large batch of fresh invoices posting via AutoInvoice or a supplier import lowers the 60-plus share arithmetically even though no old invoice was cleared. This is why the card is best read with the absolute AP balance and with the trend over the 30D vsP window.

Are invoices on payment hold counted? Yes. Invoices placed on hold (price hold, quantity hold, matching hold) still represent money you owe and still age, so they remain in both the numerator and denominator while held. Releasing a long-held invoice for payment is the usual way a stubborn 90-plus balance clears.

Does this card capture missed early-payment discounts? Not directly as a dollar figure, but it is the leading indicator. Invoices with 2/10 Net 30 terms that drift into the 60-plus band have already forfeited their discount window. Pair the aging trend with your discount-capture reporting in Oracle Payables to quantify the leak.

How fresh is the data? Vortex IQ reads the Oracle Fusion Payables data through the Fusion REST API with a short cache, so the percentage reflects the AP state as of the last sync window. For a live intraday check, the native Payables Aging Report is always real-time.

Does this include intercompany payables? By default the card reflects whatever sits in the Payables subledger for the in-scope Business Units, which can include intercompany AP. If you view a consolidated reporting ledger that eliminates intercompany balances, those lines net out. Confirm your scope matches the question you are asking.

---

Tracked live in Vortex IQ Nerve Centre

AP Aging 60+ Days is one of hundreds of KPI pulses Vortex IQ tracks across Oracle ERP Cloud and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English.

Start for free or book a demo to see this metric running on your own data.