Banking / Payment Controls is where ERP discipline either begins or breaks.
Stop Payment Issuance and Tracking 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: All stop payment requests are tracked end-to-end with bank confirmation, eliminating lost stops and duplicate payments from re-presented checks.
The control flow a finance team actually needs.
Step 1
Electronic Stop Payment Instruction Via...
Step 2
Generate Standardized Stop Payment...
Step 3
Record Bank Confirmation Reference...
Step 4
Alert If Check Status Remains Stop...
Step 5
Prevent Reissue Of Same Payment Without...
The ERP surface involved.
Module
Banking / Payment Controls
Actors
AP Manager, Bank, GL
Tier
Tier 1
Finance area
Cash Management, Treasury & Banking
Region lens
US and UK finance teams
Publication date
March 29, 2026
Support electronic stop payment instruction via bank API for connected banks; generate standardized stop payment letter PDF for manual transmission; record bank confirmation reference number and confirmation date; alert if check status remains "Stop Requested" for >24 hours without bank confirmation; prevent reissue of same payment without explicit override with supervisor authorization; track stop payment fee charged by bank in a configurable expense account; maintain stop payment register filterable by date, amount, bank, and status; void the original check GL entry and create void journal entry automatically on confirmation.
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 | Support electronic stop payment instruction via bank API for connected banks | Given an AP manager opens a check record and requests a stop payment with reason code and effective date |
| Control 2 | generate standardized stop payment letter PDF for manual transmission | when the stop instruction is transmitted electronically or via PDF |
| Control 3 | record bank confirmation reference number and confirmation date | then the check status advances to STOP_PAYMENT_REQUESTED, the bank confirmation reference is recorded on confirmation, and the void GL entry is created automatically |
| Control 4 | alert if check status remains "Stop Requested" for >24 hours without bank confirmation | negative) when a reissue of the same payment is attempted without supervisor override then the request is rejected with 409 STOP_PAYMENT_ACTIVE. |
| Control 5 | prevent reissue of same payment without explicit override with supervisor authorization | All stop payment requests are tracked end-to-end with bank confirmation, eliminating lost stops and duplicate payments from re-presented checks. |
| Control 6 | track stop payment fee charged by bank in a configurable expense account | All stop payment requests are tracked end-to-end with bank confirmation, eliminating lost stops and duplicate payments from re-presented checks. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | An AP manager identifies a check that must be stopped (lost, incorrect amount, cancelled vendor relationship). The manager opens the check record, selects "Issue Stop Payment," and enters the reason code and effective date. The system generates a stop payment instruction and transmits it to the bank electronically or produces a PDF confirmation form. The check record is updated to status "Stop Payment Requested." When the bank confirms the stop is in place the record advances to "Stop Payment Confirmed." If the bank reports the check was paid before the stop was processed, the check moves to "Stop Failed - Paid" and triggers an exception alert. The AP team then coordinates with the bank for return and reissue. |
| Control rules | Support electronic stop payment instruction via bank API for connected banks; generate standardized stop payment letter PDF for manual transmission; record bank confirmation reference number and confirmation date; alert if check status remains "Stop Requested" for >24 hours without bank confirmation; prevent reissue of same payment without explicit override with supervisor authorization; track stop payment fee charged by bank in a configurable expense account; maintain stop payment register filterable by date, amount, bank, and status; void the original check GL entry and create void journal entry automatically on confirmation. |
| Acceptance proof | Given an AP manager opens a check record and requests a stop payment with reason code and effective date; when the stop instruction is transmitted electronically or via PDF; then the check status advances to STOP_PAYMENT_REQUESTED, the bank confirmation reference is recorded on confirmation, and the void GL entry is created automatically; (negative) when a reissue of the same payment is attempted without supervisor override then the request is rejected with 409 STOP_PAYMENT_ACTIVE. |
| 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
`stop_payment` { stop_id: string, check_id: string, bank_account_id: string, reason_code: string, requested_at: timestamp, confirmed_at: timestamp, bank_reference: string, status: enum(REQUESTED, CONFIRMED, FAILED_PAID), stop_fee_minor: int64, currency_code: char(3), external_id: string }; linked to void `journal_entry` on confirmation; (reference, product may differ).API and events
`POST /v1/banking/checks/{check_id}/stop-payment` { reason_code, effective_date, external_id } -> 201 { stop_id, status: "REQUESTED" }; `POST /v1/banking/stop-payments/{id}/confirm` { bank_reference, confirmed_at } -> 200 { status: "CONFIRMED" }; emits `banking.stop_payment_confirmed` and `banking.stop_payment_failed` events; idempotent via external_id.State transitions
`REQUESTED -> CONFIRMED | FAILED_PAID`; terminal `CONFIRMED` (void JE posted) or `FAILED_PAID` (exception alert); guard: 24-hour unconfirmed alert fires on REQUESTED without bank confirmation.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.