> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Vendor Payment On-Time Rate, Oracle ERP Cloud > Vendor Payment On-Time Rate is the share of supplier invoices paid on or before their due date over the trailing 30 days. A supplier-relationship and discount-capture metric from Oracle Payables. **Card class:** [Non-Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type) > The percentage of supplier invoices paid on or before their due date over the trailing 30 days. A supplier-relationship and early-payment-discount-capture metric, sourced from Oracle Payables. ## At a glance > Vendor Payment On-Time Rate measures the proportion of supplier invoices that were paid on or before their due date across the trailing 30 days. It is the cleanest read on payables discipline: a high rate protects supplier relationships, keeps you eligible for early-payment discounts, and signals an AP process that is keeping up. A falling rate is an early warning of a stalled approval queue or a cash squeeze. It pairs with AP aging to separate deliberate term-stretching from genuine lateness. Sourced from Oracle Payables across all in-scope Business Units. | | | | ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | The number of supplier invoices paid on or before their due date divided by the total number of supplier invoices paid in the trailing 30 days, across every in-scope Business Unit and ledger. Measures payment events from Oracle Fusion Payables, comparing payment date against invoice due date. | | **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 trailing 30D vs the prior 30D), so you see whether payment discipline is improving or slipping. | | **Alert trigger** | Fires when the on-time rate falls below `90%`. | | **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 under two primary ledgers. The trailing 30-day window covers 23 May 26 to 21 Jun 26. The figures below count payment events from Oracle Fusion Payables, comparing each payment's date against the invoice due date. | Payment timing | Invoices paid | Share | | ------------------------------------------- | ----------------- | --------- | | Paid early or on due date | 4,180 | 88.0% | | Paid 1 to 5 days late | 410 | 8.6% | | Paid 6+ days late | 160 | 3.4% | | **Total invoices paid** | **4,750** | **100%** | | **Vendor Payment On-Time Rate (this card)** | **4,180 / 4,750** | **88.0%** | Five things to notice: 1. **The rate counts invoices, not dollars.** 4,180 of 4,750 invoices were paid on time, giving 88.0%. A few large late payments would not move this percentage much; it is a process-discipline measure, not a value-weighted one. 2. **88.0% is below the 90% alert threshold, so the Nerve Centre fires.** Last period read 92.5%, so discipline slipped inside the `30D vsP` window. This is the kind of move that usually traces back to a backlog in invoice approval rather than a deliberate decision. 3. **On-time is measured against the due date, not the invoice date.** A supplier on Net-60 terms paid on day 58 counts as on time. The metric respects whatever terms each invoice carries, so legitimately stretched terms do not drag it down. 4. **Late payments threaten discounts and relationships.** Several of the 6+ days-late invoices carried 2/10 Net 30 terms, so the lateness forfeited the early-payment discount. Persistent lateness with key suppliers also erodes goodwill and can tighten terms in future. Pair this with [AP Aging 60+ Days](/nerve-centre/kpi-cards/oracle-erp/ap-aging-60-days) to see the aging consequence. 5. **A dip can be approval-queue, not cash.** Drilling in, most of the lateness clustered around one Business Unit where an approver was on leave, not a company-wide cash issue. The fix was a delegation rule in the approval workflow, not more cash. ## Sibling cards merchants should reference together Vendor Payment On-Time Rate is the payables-discipline gauge. Pair it with these to read the full supplier and working-capital picture. | Card | Why pair it with Vendor Payment On-Time Rate | | ----------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [AP Aging 60+ Days](/nerve-centre/kpi-cards/oracle-erp/ap-aging-60-days) | The aging consequence of payment timing. High on-time rate with high aging means deliberate term-stretching; low on-time rate with high aging means a problem. | | [Active Suppliers](/nerve-centre/kpi-cards/oracle-erp/active-suppliers) | The supplier base behind the rate. Helps judge whether a dip is concentrated or broad. | | [Cash Collected](/nerve-centre/kpi-cards/oracle-erp/cash-collected) | The inflow that funds payments. A falling on-time rate alongside falling collections points to a cash squeeze, not a process gap. | | [AR Balance (live, by Business Unit)](/nerve-centre/kpi-cards/oracle-erp/ar-balance-live-by-business-unit) | The receivables counterweight. Read together to understand net working capital. | | [Oracle Fusion Health Score](/nerve-centre/kpi-cards/oracle-erp/oracle-fusion-health-score) | The composite roll-up that payables discipline contributes to alongside other integrity signals. | | [Top Findings Across Business Units](/nerve-centre/kpi-cards/oracle-erp/top-findings-across-business-units) | Surfaces whether a payment-timing dip is isolated to one Business Unit or systemic. | ## Reconciling against Oracle ERP Cloud **Where to look in Oracle ERP Cloud:** The closest native equivalents in the Oracle Fusion UI are: > **Navigator → Payables → Payments → Manage Payments** > **Navigator → Payables → Reports → Payables Payment Register** > **Reports and Analytics → OTBI → Financials → Payables Payments Real Time Subject Area** The Payables Payment Register lists payment events with their invoice due dates. To reconcile, count payments made on or before the due date over the trailing 30 days and divide by total payments in the window, for the same Business Unit scope. Most Fortune 500 teams build this comparison in OTBI against the Payables Payments Real Time Subject Area, which lets them pivot the on-time rate by supplier and Business Unit. Common mistakes when comparing against Oracle's own reports: * **Measuring against invoice date instead of due date.** On-time means on or before the due date, which incorporates terms. A report comparing payment date to invoice date will count Net-60 payments as wildly late. * **Counting payment batches instead of invoices.** A single payment run can settle many invoices. Counting batches rather than individual invoices changes the denominator and the rate. * **Including voided or reissued payments.** A voided and reissued payment can appear twice. A report that does not net these out double-counts and distorts the rate. **Why our number may legitimately differ from Oracle's reports:** | Reason | Direction | Why | | -------------------------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **On-time basis (due date vs invoice date)** | Either | The card measures against the due date, which respects terms. A report comparing to the invoice date counts term-based payments as late and shows a far lower rate. | | **Invoice count vs payment-batch count** | Either | The card counts individual invoices. A report counting payment batches uses a different denominator. | | **Voided and reissued payments** | Either | The card nets out voids and reissues. A raw payment register that lists both can double-count. | | **Business Unit and ledger scope** | Either | A single-Business-Unit report will not match a consolidated card view. Align scope with the dashboard filter. | | **Window boundary** | Small | A payment on the edge of the trailing 30-day window can fall inside or outside depending on the exact cutoff time, moving the rate slightly. | ## Known limitations / merchant FAQs **Is "on-time" measured against the due date or the invoice date?** Against the due date, which already reflects each invoice's payment terms. A supplier on Net-60 paid on day 58 is on time; the same payment compared against the invoice date would look 58 days late. Always reconcile on a due-date basis or the rate will not match. **Does this count invoices or dollars?** Invoices. It is the share of invoice payment events made on time, not a value-weighted figure. This makes it a clean process-discipline measure, but it does mean a few large late payments will not move the percentage much. For value impact, read it alongside AP aging. **A high on-time rate but high AP aging, how can both be true?** Easily. If you have negotiated long terms (Net-60, Net-90) with major suppliers, those invoices age into the 60-plus band while still being paid on time. High on-time rate with high aging is the signature of deliberate, disciplined term-stretching, which is healthy. The warning case is low on-time rate with high aging. **Why did the rate drop without a cash problem?** Often it is the approval queue, not cash. An approver on leave, a stuck workflow step, or a delegation gap can delay payments enough to miss due dates even when funds are available. Drilling into where the lateness clusters usually points to a process fix rather than a cash decision. **Does paying late always lose us money?** When invoices carry early-payment discount terms (such as 2/10 Net 30), drifting past the discount window forfeits the discount, which is a direct margin leak. Beyond discounts, persistent lateness erodes supplier goodwill and can lead to tighter terms or stricter credit at renewal. Not every late payment costs cash today, but the pattern carries a real cost. **Does it include payments still pending approval?** No. The rate is computed on payments actually made in the trailing 30 days, comparing each settlement against its due date. Invoices still awaiting payment are not yet a payment event, though a growing backlog of them is exactly what later drags the rate down. **How fresh is the data?** Vortex IQ reads Oracle Fusion Payables through the Fusion REST API with a short cache, so the rate reflects payment activity as of the last sync window. For a live view, the native Payables Payment Register is always real-time. *** ### Tracked live in Vortex IQ Nerve Centre *Vendor Payment On-Time Rate* 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](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.