Treasury / Payment File Generation is where ERP discipline either begins or breaks.
Outbound Payment File Generation - NACHA ACH 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: AP payments to vendors and employees processed via ACH with zero manual file construction, full bank compliance, and automatic return handling.
The control flow a finance team actually needs.
Step 1
Generate Syntactically Valid NACHA...
Step 2
Validate ABA Routing Numbers Via Check...
Step 3
Compute Batch Hash Total And File...
Step 4
PPD, CCD, And CTX SEC Codes
Step 5
Include Addenda Records For CTX...
The ERP surface involved.
Module
Treasury / Payment File Generation
Actors
AP Manager, Treasury Analyst, NACHA File Generator, Bank
Tier
Tier 1
Finance area
Cash Management, Treasury & Banking
Region lens
US and UK finance teams
Publication date
March 26, 2026
Generate syntactically valid NACHA 94-character fixed-width file; validate ABA routing numbers via check digit algorithm; compute batch hash total (sum of routing numbers mod 10) and file control totals; support PPD, CCD, and CTX SEC codes; include addenda records for CTX remittance up to 9999 addenda; enforce ODFI cutoff time warning when submission is within 30 minutes of bank cutoff; handle ACH return codes R01 - R33 with automatic reversal creation; file generation for 10,000 payments in <30 seconds; store transmitted file for 7 years.
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 | Generate syntactically valid NACHA 94-character fixed-width file | Given approved payment batches with valid ABA routing numbers and SEC codes |
| Control 2 | validate ABA routing numbers via check digit algorithm | when a NACHA ACH file is generated |
| Control 3 | compute batch hash total (sum of routing numbers mod 10) and file control totals | then the output is a syntactically valid 94-character fixed-width file with correct batch hash totals (sum of routing numbers mod 10), file control totals, CTX addenda up to 9999 records, and 10,000-payment generation in <30 seconds |
| Control 4 | support PPD, CCD, and CTX SEC codes | negative) when an ACH return file contains R01 - R85 codes then each return is matched by 15-digit trace number, payment status is set to RETURNED, and a reversal GL entry is created atomically. |
| Control 5 | include addenda records for CTX remittance up to 9999 addenda | AP payments to vendors and employees processed via ACH with zero manual file construction, full bank compliance, and automatic return handling. |
| Control 6 | enforce ODFI cutoff time warning when submission is within 30 minutes of bank cutoff | AP payments to vendors and employees processed via ACH with zero manual file construction, full bank compliance, and automatic return handling. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | At payment run completion the AP manager selects approved payment batches for ACH processing. The system groups payments by company entry description, effective date, and SEC code (PPD, CCD, CTX). The NACHA file generator produces a balanced ACH file with File Header (1 record), Company Batch Headers (5 records), Individual Detail records (6 records), Addenda (7 records where needed), Batch Control (8 records), and File Control (9 record). The file is validated against NACHA rules: routing number check digit, amount format, batch hash totals. The treasury analyst downloads and transmits the file to the bank's ACH origination portal. The system marks each payment as "Transmitted" and monitors for bank ACH return codes. |
| Control rules | Generate syntactically valid NACHA 94-character fixed-width file; validate ABA routing numbers via check digit algorithm; compute batch hash total (sum of routing numbers mod 10) and file control totals; support PPD, CCD, and CTX SEC codes; include addenda records for CTX remittance up to 9999 addenda; enforce ODFI cutoff time warning when submission is within 30 minutes of bank cutoff; handle ACH return codes R01 - R33 with automatic reversal creation; file generation for 10,000 payments in <30 seconds; store transmitted file for 7 years. |
| Acceptance proof | Given approved payment batches with valid ABA routing numbers and SEC codes; when a NACHA ACH file is generated; then the output is a syntactically valid 94-character fixed-width file with correct batch hash totals (sum of routing numbers mod 10), file control totals, CTX addenda up to 9999 records, and 10,000-payment generation in <30 seconds; (negative) when an ACH return file contains R01 - R85 codes then each return is matched by 15-digit trace number, payment status is set to RETURNED, and a reversal GL entry is created atomically. |
| 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_file` { file_id: string, entity_id: string, file_type: enum(NACHA_ACH, ISO20022, SEPA), generated_at: timestamp, payment_count: int, total_amount_minor: int64, currency_code: char(3), status: enum(GENERATED, TRANSMITTED, CONFIRMED), external_id: string }; `ach_return` { return_id: string, payment_id: string, trace_number: string, return_code: string, return_date: date, external_id: string }; (reference, product may differ).API and events
`POST /v1/treasury/payment-files/nacha` { payment_batch_ids: [string], effective_date, sec_code } -> 201 { file_id, download_url }; `POST /v1/treasury/payment-files/ach-returns` { file: multipart } -> 202 { return_count }; emits `treasury.nacha_file_generated` and `treasury.ach_return_processed` events; idempotent via external_id on payments.State transitions
`GENERATED -> TRANSMITTED -> CONFIRMED`; terminal `FAILED`; guard: re-transmission of a RETURNED payment blocked without updated bank info confirmed.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.