Payment Processing & Disbursements is where ERP discipline either begins or breaks.
Payment Run Execution (ACH / Wire / Check) 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: 100 % of approved payments processed on scheduled payment date; payment posting errors < 0.1 %; same-day exception notification for all failed/returned payments.
The control flow a finance team actually needs.
Step 1
Payment Run ACH, Domestic Wire,...
Step 2
Group Payments By With Configurable...
Step 3
Apply Discount If Payment Date ≤...
Step 4
Produce NACHA File For ACH, PAIN.001...
Step 5
Dual-Authorization Before File...
The ERP surface involved.
Module
Payment Processing & Disbursements
Actors
AP Manager, Treasury Officer, Bank / Payment Rail, ERP Payment Engine
Tier
Tier 0
Finance area
Accounts Payable & Procure-to-Pay
Region lens
US and UK finance teams
Publication date
March 11, 2026
Payment run must support ACH, domestic wire, international wire (SWIFT), and check simultaneously in one batch; group payments by (vendor, currency, payment method) with configurable consolidation; apply discount if payment_date ≤ discount_due_date and discount_amount > 0; produce NACHA file for ACH, PAIN.001 XML for SWIFT, or PCL/PDF for checks; dual-authorization required before file transmission (maker-checker); bank confirmation numbers written back to payment records within 24 hours of settlement; payment posting must be atomic: AP debit + cash credit + bank reconciliation record in one transaction; failed ACH returns (R-codes) auto-route to exception with vendor notification; payment amounts stored as *_minor + currency_code per ADR-001.
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 run must support ACH, domestic wire, international wire (SWIFT), and check simultaneously in one batch | Given a set of approved invoices is selected for a payment run |
| Control 2 | group payments by (vendor, currency, payment method) with configurable consolidation | when the AP manager and a second checker dual-authorize the batch |
| Control 3 | apply discount if payment_date ≤ discount_due_date and discount_amount > 0 | then a NACHA/PAIN.001/check file is generated and transmitted, and on bank confirmation each invoice status becomes PAID with cash and AP GL lines posted atomically |
| Control 4 | produce NACHA file for ACH, PAIN.001 XML for SWIFT, or PCL/PDF for checks | negative) when the maker attempts to also act as checker on the same batch then 403 with error code MAKER_CHECKER_VIOLATION is returned. |
| Control 5 | dual-authorization required before file transmission (maker-checker | 100 % of approved payments processed on scheduled payment date; payment posting errors < 0.1 %; same-day exception notification for all failed/returned payments. |
| Control 6 | bank confirmation numbers written back to payment records within 24 hours of settlement | 100 % of approved payments processed on scheduled payment date; payment posting errors < 0.1 %; same-day exception notification for all failed/returned payments. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | The AP manager selects invoices due within a date range and generates a proposed payment run. The system groups invoices by vendor and payment method, applies early-payment discount eligibility, and calculates net amounts. The manager reviews and approves the payment batch. The system generates the bank file (NACHA ACH, ISO 20022 wire, or check print file) and transmits it to the bank or check printer. Confirmation numbers from the bank feed are matched back to payment records, updating invoice status to PAID and posting the debit to AP and credit to the cash account. Failed or returned payments trigger an exception workflow. |
| Control rules | Payment run must support ACH, domestic wire, international wire (SWIFT), and check simultaneously in one batch; group payments by (vendor, currency, payment method) with configurable consolidation; apply discount if payment_date ≤ discount_due_date and discount_amount > 0; produce NACHA file for ACH, PAIN.001 XML for SWIFT, or PCL/PDF for checks; dual-authorization required before file transmission (maker-checker); bank confirmation numbers written back to payment records within 24 hours of settlement; payment posting must be atomic: AP debit + cash credit + bank reconciliation record in one transaction; failed ACH returns (R-codes) auto-route to exception with vendor notification; payment amounts stored as *_minor + currency_code per ADR-001. |
| Acceptance proof | Given a set of approved invoices is selected for a payment run; when the AP manager and a second checker dual-authorize the batch; then a NACHA/PAIN.001/check file is generated and transmitted, and on bank confirmation each invoice status becomes PAID with cash and AP GL lines posted atomically; (negative) when the maker attempts to also act as checker on the same batch then 403 with error code MAKER_CHECKER_VIOLATION 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
`payment_batches` { id: string, status: enum(PROPOSED|APPROVED|TRANSMITTED|SETTLED|FAILED), total_amount_minor: int64, currency_code: char(3), payment_method: enum(ACH|WIRE_DOMESTIC|WIRE_INTERNATIONAL|CHECK), file_type: string, maker_id: string, checker_id: string, external_id: string }; `payments` { id: string, batch_id: string, vendor_id: string, amount_minor: int64, currency_code: char(3), bank_confirmation_ref: string, status: enum, external_id: string }; (reference, product may differ).API and events
`POST /v1/payment-batches` { invoice_ids: [], payment_date, payment_method, external_id } -> 201 { id, status, total_amount_minor }; `POST /v1/payment-batches/{id}/approve` { checker_id } -> 200; `GET /v1/payment-batches/{id}`; emits `ap.payment_batch.approved` and `ap.payment.settled` events; idempotent via `external_id`.State transitions
`PROPOSED -> PENDING_APPROVAL -> APPROVED -> TRANSMITTED -> SETTLED`; branch `TRANSMITTED -> FAILED -> EXCEPTION`; terminal `VOID`; guard: SETTLED batch cannot be modified; failed ACH return auto-routes to EXCEPTION.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.