Skip to main content
Metrics type: Supporting Metrics • Category: Ecommerce Platform
Share of received cash that has been auto-matched to invoices. Low rates mean manual reconciliation backlog.

​
At a glance

Share of received cash receipts that Oracle’s Cash Application module has auto-matched to open invoices vs the share sitting in unapplied/on-account status awaiting manual reconciliation. The Operations efficiency gauge for the cash team.

​
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 distributor on Oracle ERP Cloud. 30D window 14 Mar 26 to 12 Apr 26. Five things to notice:
  1. 88.5% above the 85% alert threshold. Healthy auto-match rate. Most receipts come in via lockbox or ACH with remittance data that Oracle’s Cash Application program matches to invoices.
  2. **24.2Munapplied+on−account.∗∗Thisisthemanual−reconciliationbacklog.Cashteamisprocessingthroughitbutthelagmeans24.2M unapplied + on-account.** This is the manual-reconciliation backlog. Cash team is processing through it but the lag means 24M of customer payments are received but not yet credited to the customer’s account, which can trigger phantom past-due aging.
  3. On-account ($9.4M) typically means a customer paid a round number for multiple invoices and the Cash Application could not parse the remittance. Manual cash app effort.
  4. Lockbox vs wire vs ACH matching success differs. Lockbox bank-side OCR typically achieves 90%+ auto-match; wires often have minimal remittance and drop to 50-60% auto-match.
  5. Action playbook: Improve customer remittance instructions (push for remittance details on every payment), upgrade to Oracle’s AI-powered cash application or a third-party cash-app tool, set SLA on unapplied/on-account aging.

​
Sibling cards merchants should reference together

​
Reconciling against the vendor’s own dashboard

Where to look in Oracle ERP Cloud:
Receivables → Manage Receipts filter status OTBI → Receivables Receipts Real Time Subject Area
Why our number may legitimately differ: Cross-connector reconciliation:

​
Known limitations / merchant FAQs

Healthy benchmark? Best-in-class lockbox + ACH: 92-97% auto-match. Manual / wire-heavy: 75-85%. Below 75% indicates either remittance-instruction issues with customers or under-investment in cash-app tooling. Oracle’s AI-powered cash application, does it help? Yes. Newer Fusion releases include ML-driven match suggestion that learns customer remittance patterns. Customers who enable it typically see 5-10pp improvement in auto-match rate within 6 months. On-account vs unapplied difference? Unapplied: receipt has not been touched yet (queue). On-account: receipt processed, customer identified, but no specific invoice could be matched (ambiguous remittance). SAP equivalent? SAP F-32 / FB05 cash application. Same concept; SAP has its own ML add-on (S/4HANA Cash Management). Multi-currency, FX timing impact? Rare cause of legitimate mismatch. The card sums receipt amounts in reporting currency at corporate rate.

​
Tracked live in Vortex IQ Nerve Centre

Cash Application 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 or book a demo to see this metric running on your own data.