Refunds is where ERP discipline either begins or breaks.
Process a Customer Refund 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: Customer receives cash refund; credit balance is cleared; GL reflects accurate cash and AR position.
The control flow a finance team actually needs.
Step 1
Refund Reference A Credit Memo Or...
Step 2
Refund Amount Not Exceed The Credit...
Step 3
Approval Workflow Be Configurable By...
Step 4
Refund Status Be Trackable
Step 5
GL Entry Post On Disbursement...
The ERP surface involved.
Module
Refunds
Actors
AR Manager, Treasury/AP Team, Customer
Tier
Tier 1
Finance area
Accounts Receivable & Order-to-Cash
Region lens
US and UK finance teams
Publication date
March 20, 2026
Refund must reference a credit memo or unapplied cash record; refund amount must not exceed the credit balance; approval workflow must be configurable by amount threshold; refund status must be trackable (Pending, Approved, Disbursed, Voided); GL entry must post on disbursement confirmation, not on initiation; refund to original payment method must be distinguishable from check/ACH refund; non-functional: approval workflow notification < 30 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 | Refund must reference a credit memo or unapplied cash record | Given a customer credit memo or unapplied cash balance on account |
| Control 2 | refund amount must not exceed the credit balance | when AR manager initiates a refund request |
| Control 3 | approval workflow must be configurable by amount threshold | then system creates a refund record in PENDING_APPROVAL status, routes to approver if above threshold, and on approval posts GL entry DR accounts_receivable_credit CR cash |
| Control 4 | refund status must be trackable (Pending, Approved, Disbursed, Voided | negative) when refund amount exceeds available credit balance then 422 REFUND_EXCEEDS_CREDIT is returned. |
| Control 5 | GL entry must post on disbursement confirmation, not on initiation | Customer receives cash refund; credit balance is cleared; GL reflects accurate cash and AR position. |
| Control 6 | refund to original payment method must be distinguishable from check/ACH refund | Customer receives cash refund; credit balance is cleared; GL reflects accurate cash and AR position. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | A credit memo exists on the customer account (from a return, billing error, or overpayment) and the customer requests a cash refund rather than credit against future invoices; AR manager initiates a refund request referencing the credit memo; the system creates a refund record and routes it for approval if it exceeds the refund approval threshold; once approved, the refund is handed off to the AP/payment team to disburse via ACH or check; on confirmation of disbursement the system posts the refund journal entry (DR Accounts Receivable Credit, CR Cash) and closes the credit memo. |
| Control rules | Refund must reference a credit memo or unapplied cash record; refund amount must not exceed the credit balance; approval workflow must be configurable by amount threshold; refund status must be trackable (Pending, Approved, Disbursed, Voided); GL entry must post on disbursement confirmation, not on initiation; refund to original payment method must be distinguishable from check/ACH refund; non-functional: approval workflow notification < 30 seconds. |
| Acceptance proof | Given a customer credit memo or unapplied cash balance on account; when AR manager initiates a refund request; then system creates a refund record in PENDING_APPROVAL status, routes to approver if above threshold, and on approval posts GL entry DR accounts_receivable_credit CR cash; (negative) when refund amount exceeds available credit balance then 422 REFUND_EXCEEDS_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_refund` { id: ref_*, external_id: string, customer_id: cust_*, credit_memo_id: cm_*, amount_minor: int64, currency_code: char(3), refund_method: enum, status: enum, approved_by: string, disbursed_at: timestamp }; references customer credit_memo or unapplied cash; (reference, product may differ).API and events
`POST /v1/customer-refunds` { customer_id, credit_source_id, amount_minor, currency_code, refund_method, external_id } -> 201 { id, status: PENDING_APPROVAL }; `POST /v1/customer-refunds/{id}/approve` -> 200; `POST /v1/customer-refunds/{id}/disburse` -> 200; emits `ar.refund.disbursed`; idempotent via `external_id`.State transitions
`PENDING_APPROVAL -> APPROVED -> DISBURSED`; terminal `VOIDED`; guard: GL posts on DISBURSED confirmation, not on initiation; VOIDED reverses and reopens credit balance.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.