Cash Application is where ERP discipline either begins or breaks.
Apply a Customer Payment to an Open Invoice looks operational from far away. In a real finance team, it is a chain of assertions: the right actor started the work, the required records existed, the control policy was applied, the state change was preserved, and the outcome can be explained later without rebuilding the transaction from emails and spreadsheets.
The expected business outcome is specific: Open invoices are closed or partially reduced; cash account increases; AR aging reflects accurate outstanding amounts immediately after application.
The control flow a finance team actually needs.
Step 1
Payment Be Linkable To Multiple...
Step 2
Partial Payment Leave The Invoice Open...
Step 3
Over-Payment Create A Customer Credit...
Step 4
GL Posting Be Atomic With Match
Step 5
Payment Date Drives Aging
The ERP surface involved.
Module
Cash Application
Actors
AR Clerk, Bank Feed System, Customer
Tier
Tier 0
Finance area
Accounts Receivable & Order-to-Cash
Region lens
US and UK finance teams
Publication date
March 16, 2026
Payment must be linkable to multiple invoices in a single application session; partial payment must leave the invoice open with updated balance_due; over-payment must create a customer credit or unapplied cash record; GL posting must be atomic with match; payment date (not application date) drives aging; the original invoice currency and the payment currency must both be recorded when they differ; non-functional: cash application commit < 2 seconds.
US and UK teams have different compliance hooks, but the same control problem.
US teams usually care about clean evidence for audit support, vendor records, payment controls, tax reporting, and management review. UK teams usually care about VAT-ready records, approval evidence, digital-record discipline, and traceable postings. The country-specific details differ, but the operating pattern is the same: the ERP needs controlled records, explicit ownership, defensible state changes, and evidence that survives beyond the person who completed the task.
The control matrix.
| Control area | Requirement | Acceptance proof |
|---|---|---|
| Control 1 | Payment must be linkable to multiple invoices in a single application session | Given an open sales_invoice with balance_due > 0 and a cash receipt for the customer |
| Control 2 | partial payment must leave the invoice open with updated balance_due | when AR clerk applies the payment to the invoice |
| Control 3 | over-payment must create a customer credit or unapplied cash record | then system posts DR cash CR accounts_receivable, sets invoice status=PAID (or PARTIALLY_PAID if partial), updates balance_due atomically, and aging reflects remaining amount |
| Control 4 | GL posting must be atomic with match | negative) when payment amount exceeds total open balance_due across all selected invoices then 422 OVERPAYMENT_REQUIRES_CREDIT is returned. |
| Control 5 | payment date (not application date) drives aging | Open invoices are closed or partially reduced; cash account increases; AR aging reflects accurate outstanding amounts immediately after application. |
| Control 6 | the original invoice currency and the payment currency must both be recorded when they differ | Open invoices are closed or partially reduced; cash account increases; AR aging reflects accurate outstanding amounts immediately after application. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | A customer payment arrives in the bank feed or is entered manually; the AR clerk opens the cash application screen, selects the customer, and the system presents all open invoices sorted by due date; clerk matches the payment to one or more invoices; the system posts a cash receipt journal entry (DR Cash, CR Accounts Receivable), marks matched invoices as Paid or Partially Paid, and updates the customer's outstanding balance; a remittance confirmation is sent to the customer. |
| Control rules | Payment must be linkable to multiple invoices in a single application session; partial payment must leave the invoice open with updated balance_due; over-payment must create a customer credit or unapplied cash record; GL posting must be atomic with match; payment date (not application date) drives aging; the original invoice currency and the payment currency must both be recorded when they differ; non-functional: cash application commit < 2 seconds. |
| Acceptance proof | Given an open sales_invoice with balance_due > 0 and a cash receipt for the customer; when AR clerk applies the payment to the invoice; then system posts DR cash CR accounts_receivable, sets invoice status=PAID (or PARTIALLY_PAID if partial), updates balance_due atomically, and aging reflects remaining amount; (negative) when payment amount exceeds total open balance_due across all selected invoices then 422 OVERPAYMENT_REQUIRES_CREDIT is returned. |
| Data record | |
| System event | |
| Lifecycle state | |
The useful version of this workflow is not only fast. It is inspectable. A controller, auditor, or operator should be able to move from source event to system record to state transition to final business outcome without guessing.
Implementation contracts.
Reference data model
`customer_payment` { id: pay_*, external_id: string, customer_id: cust_*, payment_date: date, amount_minor: int64, currency_code: char(3), invoice_currency_code: char(3), status: enum }; `payment_application` { payment_id: pay_*, invoice_id: invoice_*, applied_minor: int64, currency_code: char(3) }; one payment may have many payment_applications; (reference, product may differ).API and events
`POST /v1/customer-payments` { customer_id, payment_date, amount_minor, currency_code, external_id } -> 201 { id, status }; `POST /v1/customer-payments/{id}/apply` { applications: [{invoice_id, applied_minor}] } -> 200 { applied_count, unapplied_minor }; emits `ar.payment.applied`; idempotent via `external_id`.State transitions
`UNAPPLIED -> PARTIALLY_APPLIED -> FULLY_APPLIED`; terminal `REVERSED`; guard: REVERSED blocked if bank reconciliation is complete; FULLY_APPLIED requires sum(applied_minor) = amount_minor.Common implementation traps.
Treating the workflow as data entry
If the ERP only stores the final record, the team loses the decision trail that explains how the record became valid.
Hiding exception logic
Exceptions need owners, reason codes, and time stamps. A vague pending state is not a control.
Posting without recovery design
Retries, duplicate submissions, and partial failures must be explicit so the system does not create inconsistent records.
Skipping evidence design
A workflow that cannot produce evidence on demand will eventually push finance teams back into manual screenshots and spreadsheets.
Where Rivane fits.
Rivane is built for finance workflows where automation must stay tied to source documents, approvals, state transitions, ledger impact, reporting, and audit evidence. Use this guide as a checklist for evaluating whether an ERP workflow is merely digitized or actually controlled.
References and source basis.
These sources provide the standards, regulatory, or government context around the flow. They are included so the guide is useful to finance operators, auditors, and implementation teams, not only buyers reading software copy.