Banking / Bank Transfers is where ERP discipline either begins or breaks.
Bank Transfer Between Internal Accounts 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 internal cash movements have a complete audit trail and are immediately reflected in the cash position with no manual journal entries.
The control flow a finance team actually needs.
Step 1
Enforce Dual-Control: Initiator And...
Step 2
Same-Day And Future-Dated Value Dates
Step 3
Generate ACH CCD Or Wire SWIFT MT103...
Step 4
Post Balanced GL Entries Atomically...
Step 5
Intra-Entity And Intercompany Transfers
The ERP surface involved.
Module
Banking / Bank Transfers
Actors
Treasury Manager, Approval Workflow, Payment Processor, GL
Tier
Tier 1
Finance area
Cash Management, Treasury & Banking
Region lens
US and UK finance teams
Publication date
March 25, 2026
Enforce dual-control: initiator and approver must be different users; support same-day and future-dated value dates; generate ACH CCD or wire SWIFT MT103 instruction file; post balanced GL entries atomically with transfer record in single transaction; support intra-entity and intercompany transfers (intercompany triggers due-to/due-from entries per the related workflow); maintain transfer status lifecycle: Draft → Pending Approval → Approved → Sent → Confirmed → Reconciled; idempotent on re-submission with same external_id.
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 | Enforce dual-control: initiator and approver must be different users | Given a treasury manager initiates a bank transfer with source account, destination account, amount_minor, currency_code, and value date |
| Control 2 | support same-day and future-dated value dates | when the transfer exceeds the approval threshold and is approved by a different user |
| Control 3 | generate ACH CCD or wire SWIFT MT103 instruction file | then two balanced GL journal entries (debit destination cash / credit source cash with offsets) are posted atomically on value date, the transfer status advances to CONFIRMED after bank receipt, and intercompany transfers post due-to/due-from entries |
| Control 4 | post balanced GL entries atomically with transfer record in single transaction | negative) when the initiator and approver are the same user then the request is rejected with 422 DUAL_CONTROL_VIOLATION. |
| Control 5 | support intra-entity and intercompany transfers (intercompany triggers due-to/due-from entries per the related workflow | All internal cash movements have a complete audit trail and are immediately reflected in the cash position with no manual journal entries. |
| Control 6 | maintain transfer status lifecycle: Draft → Pending Approval → Approved → Sent → Confirmed → Reconciled | All internal cash movements have a complete audit trail and are immediately reflected in the cash position with no manual journal entries. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | A treasury manager initiates a bank transfer specifying source account, destination account, amount, currency, value date, and memo. If the transfer exceeds the configurable approval threshold, an approval request is routed to the treasury director. Upon approval the system generates the appropriate payment instruction (wire, ACH, internal book transfer) and posts it to the outgoing payment queue. On the value date the transfer is marked sent and two GL journal entries are created: a debit to the destination account and credit to the source account with matching offset entries. When the bank confirms receipt, both sides are reconciled automatically. |
| Control rules | Enforce dual-control: initiator and approver must be different users; support same-day and future-dated value dates; generate ACH CCD or wire SWIFT MT103 instruction file; post balanced GL entries atomically with transfer record in single transaction; support intra-entity and intercompany transfers (intercompany triggers due-to/due-from entries per the related workflow); maintain transfer status lifecycle: Draft → Pending Approval → Approved → Sent → Confirmed → Reconciled; idempotent on re-submission with same external_id. |
| Acceptance proof | Given a treasury manager initiates a bank transfer with source account, destination account, amount_minor, currency_code, and value date; when the transfer exceeds the approval threshold and is approved by a different user; then two balanced GL journal entries (debit destination cash / credit source cash with offsets) are posted atomically on value date, the transfer status advances to CONFIRMED after bank receipt, and intercompany transfers post due-to/due-from entries; (negative) when the initiator and approver are the same user then the request is rejected with 422 DUAL_CONTROL_VIOLATION. |
| 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
`bank_transfer` { transfer_id: string, entity_id: string, source_account_id: string, destination_account_id: string, amount_minor: int64, currency_code: char(3), value_date: date, status: enum(DRAFT, PENDING_APPROVAL, APPROVED, SENT, CONFIRMED, RECONCILED), initiator_user_id: string, approver_user_id: string, external_id: string }; linked to `journal_entry` on GL posting; (reference, product may differ).API and events
`POST /v1/banking/transfers` { source_account_id, destination_account_id, amount_minor, currency_code, value_date, memo, external_id } -> 201 { transfer_id, status: "DRAFT" }; `POST /v1/banking/transfers/{id}/approve` { approver_comment } -> 200 { status: "APPROVED" }; emits `banking.transfer_approved` and `banking.transfer_confirmed` events; idempotent via external_id.State transitions
`DRAFT -> PENDING_APPROVAL -> APPROVED -> SENT -> CONFIRMED -> RECONCILED`; terminal `VOID`; guard: APPROVED blocked if initiator_user_id = approver_user_id; SENT blocked on value date not reached.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.