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.
| What it counts | applied_receipt_amount / total_receipt_amount over the window, where applied = matched to specific Receivables transactions. Unapplied = received but not yet allocated. On-account = received but no specific invoice match found. |
| Currency | Reporting ledger consolidated. |
| Business Unit scope | Respects dashboard filter. |
| Time window | 30D |
| Alert trigger | <85% |
| Sentiment key | cash_app_rate |
| 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 distributor on Oracle ERP Cloud. 30D window 14 Mar 26 to 12 Apr 26.| Status | Receipt amount |
|---|---|
| Applied (auto-matched to invoices) | $186,200,000 |
| Unapplied (awaiting match) | $14,800,000 |
| On-account (no invoice match) | $9,400,000 |
| Total receipts | $210,400,000 |
| Application rate | 88.5% |
- 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.
- **24M of customer payments are received but not yet credited to the customer’s account, which can trigger phantom past-due aging.
- 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.
- 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.
- 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
| Card | Why pair it with Cash Application Rate |
|---|---|
| Cash Collected | Total cash; this card measures application efficiency on it. |
| Cash Applied Today | Daily intraday tracking. |
| DSO | Application backlog inflates DSO artificially. |
| A/R Aging Detail | Unapplied receipts can mask aged invoices. |
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 AreaWhy our number may legitimately differ:
| Reason | Direction | Why |
|---|---|---|
| In-progress receipts | Either | Receipts mid-processing may temporarily appear unapplied. |
| Multi-currency rounding | Tiny | FX-driven micro-mismatches between receipt amount and invoice amount. |
| Card | Notes |
|---|---|
| Stripe / PayPal settlement timing | If commerce payments flow through Stripe→bank→Oracle, lag affects this rate. |