Share of received cash that has been auto-matched to invoices. Low rates mean manual reconciliation backlog.
At a glance
Share of received cash that has been applied (matched to Invoices) within the period. Low rates mean unapplied-cash backlog and AR reconciliation problems.
| What it counts | applied_cash ÷ total_cash_received, where applied_cash is Customer Payments fully or partially applied, and total_cash_received includes unapplied receipts (Customer Deposits, Unapplied Payments). |
| Tax treatment | n/a (ratio). |
| Subsidiary scope | Respects dashboard filter. |
| Time window | 30D |
| Alert trigger | <85%, sentiment cash_app_rate |
| Roles | owner, finance |
Calculation
Calculated automatically from your NetSuite 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 wholesale distributor on NetSuite. 30-day window 14 Mar 26 to 12 Apr 26.| Amount (USD) | |
|---|---|
| Total cash received | $7,180,000 |
| Applied to Invoices | $6,984,000 |
| Unapplied (Customer Deposits, holding accounts) | $196,000 |
| Cash Application Rate (this card) | 97.3% |
- 97.3% is healthy. Above the 85% alert threshold by a wide margin. AR reconciliation is keeping up.
- $196K unapplied is the queue length. That’s typically wires received without enough remittance info to match, plus customer prepayments not yet billed against.
- Stripe + PayPal contribute ~99%+ application rates because they pre-match Invoice IDs at settlement. ACH and cheque drag the rate down to ~93-95%.
- The 85% alert threshold reflects industry norms. Below 85% means cash is sitting in a holding account for >2 days on average; above 95% means same-day reconciliation.
- A drop from 97% to 88% is the warning signal, even though both are above threshold. Trend matters: the AR clerk’s queue is growing.
Sibling cards merchants should reference together
| Card | Why pair it with Cash Application Rate |
|---|---|
| Cash Collected | The dollar side. |
| Cash Applied Today | Daily heartbeat. |
| DSO | Slow application inflates DSO mechanically. |
| Invoice Aging Summary | Aging includes “applied” Invoices closing. |
| stripe.stripe_total_revenue | Auto-applied subset. |
Reconciling against the vendor’s own dashboard
Where to look in NetSuite:Reports → Receivables → Customer Deposit Detail (unapplied side) Saved search: ratio of CustPymt to (CustPymt + CustomerDeposit + Unapplied)NetSuite doesn’t expose the rate directly; most accounts compute it monthly. Why our number may legitimately differ:
| Reason | Direction | Why |
|---|---|---|
| Definition of “applied” | Either | Some accounts count partially-applied as applied; some require fully-applied. Card uses partially-applied threshold. |
| Customer Deposit treatment | Either | Customer Deposits intended as future-billing prepayments may be excluded by some teams. |
| Subsidiary scope | Either | Card defaults to all subs. |
Known limitations / merchant FAQs
What’s a healthy rate?95% is excellent (typical for Stripe-heavy operations). 85-95% is acceptable. <85% suggests AR understaffing or remittance-data quality issues.How do I improve the rate? Three levers: (1) require Invoice number on customer remittance emails / wire references; (2) deploy NetSuite Lockbox or third-party AR automation (HighRadius, Tesorio); (3) push customers to Stripe / auto-pay where the application is automatic. Why is Stripe near 100% but ACH lower? Stripe’s SuiteApp passes Invoice ID with the settled charge, so NetSuite auto-applies. ACH receipts arrive with bank-defined memo fields that don’t necessarily contain the Invoice number; the AR clerk has to figure out the match. Customer Deposits, are they “unapplied” forever? Until billed. A customer who pays a $5K deposit before the SO bills is correctly in the unapplied bucket. Once the Invoice generates, the deposit auto-applies (if SuiteApp configured). The card excludes deposits intended for future billing if the field map registers the carve-out. Why does the rate vary by season? Year-end and quarter-end see lower rates because customers send larger lump-sum payments that don’t tie to single Invoices. AR clerks then split the receipt across multiple Invoices, which takes time. Subsidiary differences? Big variances. US subsidiary on Stripe might run 99%; APAC subsidiary on wire transfers might run 80%. The card surfaces the per-sub breakdown. Multi-currency, FX impact? None on the rate. Both numerator and denominator are in same units. Single-subsidiary vs OneWorld? Identical formula.