Insights Contact

Payment Rails

ACH Payments, File by File: NACHA, pain.001, pain.008, Status, Rules and Security

By SP Sankar

⏱ About a 7-minute read. Click “Read more” or “Sample file” whenever you want the details.

Every other Friday, Sree’s payroll system sends one file to the bank, and 200 people get paid by ACH. Here is everything that happens to that file along the way.

  • Not a banker? Just look at the pictures and read the “In one line” boxes. That is enough to get the idea.
  • Work in banking or operations? Open “Read more” under each file and each payment type.
  • Product owner? Read the status codes, the “Status, rules, security and data” boxes and the product owner rows. Those are the decisions that land on your desk.
  • Developer? Open every “Sample file”, then read the data mapping section and the developer rows.
  • Operations or support? Use the “ACH runbook” table: what to watch at each file, and who acts.
  • Tester? Use the “What to test” rows as your starting checklist.
  • Forward deployed engineer? Jump to “For forward deployed engineers”. It covers what to ask the client, set-up, testing, go-live and where things usually go wrong.

How ACH works

In one line: Payments are grouped into batches and sent in a NACHA file a few times a day.

CUSTOMERYOUR BANK · INTERNALOUTSIDE · EXTERNALCompanyERPpayroll · billsGatewaySFTP · APIdecrypt · ackValidate+ mapto one internalpayment recordChecks+ postOFAC · limitsdebit accountFedACHor EPNcut-off timesReceivingbankRDFI postsNACHA file · pain.001 · APINACHA batch fileNACHA fileCOMING BACKReturns R01… · NOC C01…pain.002 · return reportReconcile: bank books vs networkFedACH totals = batch totalsStatementBAI2 · camt.053settlement reportwhat the networksays movedSame-day or next-day · money settles in batches several times a dayledger postings
ACH: what comes in, what goes out, what comes back, and how the bank checks it all matches.
  • Files coming in: NACHA, pain.001 (to pay), pain.008 (to collect), CSV or API.
  • Going out: a NACHA file to FedACH (run by the Fed) or EPN (run by The Clearing House).
  • Coming back: returns (R codes) and notifications of change (C codes). Then the bank sends pain.002 and statements.

Status, rules, security and data

Status flowReceived → Batched → Sent at window → Settled → Return window → Final
Side paths: Returned (R01, R03, R10…), NOC (C01…)
Regulation and rulesThe Nacha Operating Rules. Federal Reserve Operating Circular 4, which covers FedACH. The EPN rules from The Clearing House. Regulation E, for consumer accounts.
Security standardsNacha’s data security rules: protect account numbers when stored and when sent. From 2026, Nacha also requires risk-based fraud monitoring. Phase 1 applies from March 20, 2026, and phase 2 (everyone else) from June 19, 2026. Banks reach FedACH through FedLine, which the Fed checks every year under its Security and Resiliency Assurance Program (Operating Circular 5).
Data governanceKeep the authorizations for debits. Keep the original file, batch and trace numbers. Mask account numbers in logs. When a NOC arrives, update the stored account details.
Read more: ACH

For tech teams, product owners and testers

For developersBuild the NACHA file from the internal record. Check the entry hash and the totals. Read return and NOC files and update STATUS_EVENT.
For product ownersChoose the windows (same-day or next-day), set limits for each client, and decide how returns are shown.
What to testWrong totals. A file sent after the last window. Returns R01, R03 and R10. A NOC that should update the stored account.

Step by step

  1. The company’s payroll or billing system creates the file. It can be a NACHA file, a pain.001 (to pay) or a pain.008 (to collect).
  2. The bank’s gateway receives it by secure file transfer and quickly says “got it”. Then it checks the totals, the format and for duplicates.
  3. Each payment becomes one record inside the bank. Sanctions (OFAC), limits and fraud checks run. For payments going out, the company’s account is debited.
  4. At the next ACH window, the bank builds its own NACHA file and sends it to FedACH (the Fed) or EPN (The Clearing House).
  5. The operator sorts the entries and passes them to each receiving bank. Those banks post them on the effective date.
  6. Returns (R codes) and notifications of change (C codes) come back as NACHA files. The bank updates the status and tells the company with a pain.002 or a return report.
  7. The bank matches the settlement report to the batches it sent. Then the statement goes out as BAI2 or camt.053.

When things go wrong: rejected, returned, cancelled

Not every payment goes through. On ACH, there are three ways a payment can fail. Each one means something different for the money.

ACH: rejected, returned and cancelledRejectedbefore sendingBank finds a problemNothing is sentCompany is toldpain.002Returnedafter sendingOther bank can’t post itNACHA returnMoney comes backCompany is toldpain.002Cancelledby the companyCompany asks to stopcamt.055Bank pulls it backNACHA reversalCompany is toldpain.002Rejected = money never moved · Returned = money moved, then came back · Cancelled = stopped (or recalled) by the sender
Navy: the money never moved. Blue: it moved and came back. Grey: the sender stopped it.

Rejected. The bank catches a problem before the file goes out: totals that don’t add up, a broken format, a file it has seen before, or a client over its limit. Nothing reaches FedACH or EPN, so no money moves. The bank sends a pain.002 with status RJCT (or a reject report), and the company fixes the file and sends it again.

Returned. The payment went out, but the receiving bank can’t post it. Maybe there is not enough money (R01), the account is closed (R02) or it doesn’t exist (R03). The receiving bank sends a return entry back through the operator, normally within 2 banking days. A consumer who says a debit was not authorized has up to 60 days (R10). The money comes back to the company, and the bank updates the status to Returned.

Cancelled. If the file hasn’t gone out yet, the bank can simply pull the batch or the entry. Once it’s sent, there is no “undo” button. The company can send a reversal, but only for a real mistake (a duplicate, the wrong amount or the wrong account) and within 5 banking days. A reversal is a request, not a guarantee: if the money is gone, it can come back as a return instead.

Codes you will see: R01 not enough money · R02 account closed · R03 no account · R04 bad account number · R10 not authorized · R29 business says not authorized

Which files carry the bad news?

Each path has its own file or message. Here is what travels, who sends it, and what is inside.

PathFile or messageFrom → toWhat it says
Rejectedpain.002 (RJCT) or a file reject reportYour bank → companyWhich file or entry failed, and why
ReturnedNACHA return entry + addenda type 99Receiving bank → FedACH/EPN → your bankR code, original trace number, amount
Returnedpain.002, return report or camt.054Your bank → companyThe payment came back and the money is credited
Changed (NOC)NACHA entry + addenda type 98Receiving bank → your bankC code and the corrected account details
CancelledReversal batch (entry description REVERSAL)Your bank → FedACH/EPNPull back an entry sent by mistake
Cancelledcamt.055 or a portal requestCompany → your bankPlease stop this file or payment
Sample file: NACHA return entry (R03)

Fictional data, shortened. Real files carry more fields.

Record 6 = the original payment coming back (transaction code 21)
Record 7, type 99 = return addenda: reason R03, original trace number

6212223334459876543210       0000125050INV-7781       ACME SUPPLIES INC       1123456780000001
799R03222333440000001      12345678                                            123456780000001
Sample file: NACHA reversal batch

Fictional data, shortened. Real files carry more fields.

Batch header must say REVERSAL in the entry description
Entry pulls the same amount back (transaction code 27 = debit checking)

5225SREE CORP                           1234567890CCDREVERSAL  261121261121   1222333440000002
6271234567809876543210       0000125050INV-7781       ACME SUPPLIES INC       0222333440000002
Sample file: pain.002 with RJCT

Fictional data, shortened. Real files carry more fields.

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.002.001.10">
 <CstmrPmtStsRpt>
  <GrpHdr><MsgId>STS-20261120-051</MsgId><CreDtTm>2026-11-20T09:40:00</CreDtTm></GrpHdr>
  <OrgnlGrpInfAndSts>
   <OrgnlMsgId>PAY-20261119-001</OrgnlMsgId>
   <OrgnlMsgNmId>pain.001.001.09</OrgnlMsgNmId>
  </OrgnlGrpInfAndSts>
  <OrgnlPmtInfAndSts>
   <OrgnlPmtInfId>BATCH-01</OrgnlPmtInfId>
   <TxInfAndSts>
    <OrgnlEndToEndId>INV-7781</OrgnlEndToEndId>
    <TxSts>RJCT</TxSts>                                <!-- rejected -->
    <StsRsnInf><Rsn><Cd>AC01</Cd></Rsn>                <!-- wrong account number -->
     <AddtlInf>Account number fails check</AddtlInf></StsRsnInf>
   </TxInfAndSts>
  </OrgnlPmtInfAndSts>
 </CstmrPmtStsRpt>
</Document>

ACH runbook: what to watch at each file

This is the day-to-day runbook for the files above, in the same order. For each step, it shows which file you are looking at, what “good” looks like, what to do when it isn’t, and who acts. L1 is the service desk, L2 is ACH operations and app support, and L3 is engineering.

StepFileCheckIf it goes wrongWho
1. File arrivesNACHA, pain.001, pain.008 or CSVThe file came in on time, decrypts (PGP) and has the expected name.No file by the expected time? Call the client now. Don’t wait for the cut-off.L2 watches, L1 calls the client
2. Gateway checkspain.002 (ACTC or RJCT)Totals, entry hash, format, and that the file isn’t a duplicate.Reject the file with pain.002 RJCT and ask for a new one. Never fix a client’s file by hand.L2
3. Bank checksInternal payment recordSanctions (OFAC) hits, limits, fraud scores and available money.Hold the payment, work the case, then release or reject it before the window.L2 with compliance
4. Send to the operatorOutbound NACHA fileSent before the window, operator acknowledgment received, counts and totals match.No acknowledgment? Check FedLine, then use the backup channel under maker-checker. Never resend before checking what the operator already has.L2, L3 if it’s technical
5. SettlementSettlement report and Fed account statementSettled totals equal the totals you sent.Any difference becomes a reconciliation break, owned until it’s closed.L2 with finance
6. Returns and NOCsNACHA return (addenda 99), NOC (addenda 98)Every return and NOC is loaded, linked to the original and shown to the client the same day.Watch return rates against Nacha’s limits: 0.5% unauthorized, 3% administrative, 15% overall. Apply NOC changes within 6 banking days.L2 with risk
7. Tell the clientpain.002, camt.054, BAI2 or camt.053Statuses and statements go out on time, and every return appears.Late or missing report? Tell the client before they notice.L1 and L2
8. Fix a mistakeNACHA reversal batchOnly for a duplicate, the wrong amount or the wrong account, and within 5 banking days. Maker-checker on every reversal.If the money is already gone, it comes back as a return (R06) or not at all. Tell the client honestly.L2

Golden rules

  • Never roll back a file that has gone to the operator. Fix it with a reversal or a new entry.
  • Never resend a file until you know what the operator already accepted. That is how payments get sent twice.
  • Never edit a client’s file by hand. Reject it and ask for a new one.
  • Never put full account numbers in emails, tickets or chat.

Want the full picture, from requirements to go-live, penny tests, disaster recovery and live support? Read the ACH Payments Runbook: From Requirements to Live Support.

For forward deployed engineers (FDE)

As an FDE, you sit with the client and make the integration actually work. Here is your checklist for this rail.

First call with the clientWhich files will they send: NACHA, pain.001, pain.008 or CSV? Paying out, collecting, or both? Which SEC codes (PPD, CCD, WEB)? Same-day or next-day? How many payments, and on which peak days (payroll Fridays, month end)?
Set up and connectivitySFTP account and keys, PGP encryption, file names, company ID, exposure limits, which ACH windows they will use, and where pain.002 and return files should go.
Test and certifyRun their real payroll file in the bank’s test environment. Check the totals, entry hash and SEC codes. Force R01, R03 and NOC test cases. Make sure their ERP can read the return file.
Go-live and hypercareSend the first live file with a small batch. Watch the first return window, which is 2 banking days. Agree who calls whom if a file is rejected after cut-off.
Where it usually breaksA wrong immediate destination or origin in record 1. Totals that do not match. Files sent after the last window. Debit authorizations not kept. A NOC changes an account number, but the client never updates it in their system.

The files on this rail

Each file below shows how it starts, what is inside, its status codes and a sample. For all the other files, see the full guide: how payment files are processed in US banks.

pain.001: “please pay these people”

In one line: The company telling its bank, “please send these payments.” It can hold one payment or thousands.

  • How it starts: the company’s payments manager approves a payment run, such as Thursday’s payroll, and the company’s ERP or payroll system creates the file.
  • How it gets to the bank: by secure file transfer (SFTP), SWIFT FileAct, an upload on the bank’s portal, or an API call.
  • What is inside: a header with the file ID, the number of payments and the total. Then one or more payment blocks (date, which account pays, ACH or wire). Then one line for each person being paid.
  • What happens next: the bank sends a pain.002 back to say how it went. Then it creates one network message for each payment, such as a NACHA entry or a pacs.008.
Sample file: pain.001

Made-up data, shortened. Real files have more fields.

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.09">
 <CstmrCdtTrfInitn>
  <GrpHdr>
   <MsgId>PAY-20261119-001</MsgId>
   <CreDtTm>2026-11-19T17:05:00</CreDtTm>
   <NbOfTxs>1</NbOfTxs>
   <CtrlSum>1250.50</CtrlSum>
   <InitgPty><Nm>Sree Corp</Nm></InitgPty>
  </GrpHdr>
  <PmtInf>
   <PmtInfId>BATCH-01</PmtInfId>
   <PmtMtd>TRF</PmtMtd>
   <PmtTpInf>
    <SvcLvl><Cd>NURG</Cd></SvcLvl>          <!-- NURG = ACH, URGP = wire -->
    <LclInstrm><Prtry>CCD</Prtry></LclInstrm>
   </PmtTpInf>
   <ReqdExctnDt><Dt>2026-11-20</Dt></ReqdExctnDt>
   <Dbtr><Nm>Sree Corp</Nm></Dbtr>
   <DbtrAcct><Id><Othr><Id>1112223334</Id></Othr></Id></DbtrAcct>
   <DbtrAgt><FinInstnId><ClrSysMmbId><MmbId>222333445</MmbId></ClrSysMmbId></FinInstnId></DbtrAgt>
   <CdtTrfTxInf>
    <PmtId><EndToEndId>INV-7781</EndToEndId></PmtId>
    <Amt><InstdAmt Ccy="USD">1250.50</InstdAmt></Amt>
    <CdtrAgt><FinInstnId><ClrSysMmbId>
      <ClrSysId><Cd>USABA</Cd></ClrSysId><MmbId>123456780</MmbId>
    </ClrSysMmbId></FinInstnId></CdtrAgt>
    <Cdtr><Nm>Acme Supplies Inc.</Nm></Cdtr>
    <CdtrAcct><Id><Othr><Id>9876543210</Id></Othr></Id></CdtrAcct>
    <RmtInf><Ustrd>Invoice INV-7781</Ustrd></RmtInf>
   </CdtTrfTxInf>
  </PmtInf>
 </CstmrCdtTrfInitn>
</Document>
Read more: pain.001

For tech teams, product owners and testers

For developersFirst check the file against the XSD (the official schema). Then check the business rules. NbOfTxs and CtrlSum must match the lines. The MsgId must be new, or it is a duplicate. The date must be a banking day. Finally, use SvcLvl and LclInstrm to pick the rail: NURG + CCD means ACH, URGP means wire.
For product ownersDecide which versions you accept (many US banks take pain.001.001.03 and .09). Set a cut-off time for each rail. And decide: does one bad line reject the whole file, or just that line?
What to testTotals that do not add up. The same MsgId sent twice. A date in the past. A bank holiday. A file with 10,000 lines. A name with & or accents. An amount with three decimals.

pain.008: “please collect from these people”

In one line: The company telling its bank, “please collect money from these people.” This is a direct debit, like a monthly gym fee.

  • How it starts: before each collection date, the company’s billing system creates the file. It only includes customers who signed an authorization.
  • In the US: the bank turns it into ACH debits. The SEC code says what kind: PPD for consumers, CCD for businesses, WEB for authorizations given online.
  • What is inside: the collector’s account and the collection date. Then, for each payer, the amount, their account and the mandate (the authorization ID and the date it was signed).
  • What happens next: the bank sends a NACHA debit file, then pain.002 statuses. Sometimes a debit comes back, for example R10, which means the customer says they never agreed to it.
Sample file: pain.008

Made-up data, shortened. Real files have more fields.

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.008.001.08">
 <CstmrDrctDbtInitn>
  <GrpHdr><MsgId>COLL-20261201-01</MsgId><CreDtTm>2026-11-28T16:00:00</CreDtTm>
   <NbOfTxs>1</NbOfTxs><CtrlSum>49.99</CtrlSum><InitgPty><Nm>FitGym LLC</Nm></InitgPty></GrpHdr>
  <PmtInf>
   <PmtInfId>DD-DEC</PmtInfId>
   <PmtMtd>DD</PmtMtd>
   <PmtTpInf><LclInstrm><Prtry>PPD</Prtry></LclInstrm><SeqTp>RCUR</SeqTp></PmtTpInf>
   <ReqdColltnDt>2026-12-01</ReqdColltnDt>
   <Cdtr><Nm>FitGym LLC</Nm></Cdtr>
   <CdtrAcct><Id><Othr><Id>5556667778</Id></Othr></Id></CdtrAcct>
   <DrctDbtTxInf>
    <PmtId><EndToEndId>MEMBER-2231-DEC</EndToEndId></PmtId>
    <InstdAmt Ccy="USD">49.99</InstdAmt>
    <DrctDbtTx><MndtRltdInf>
     <MndtId>AUTH-2231</MndtId><DtOfSgntr>2026-01-05</DtOfSgntr>
    </MndtRltdInf></DrctDbtTx>
    <DbtrAgt><FinInstnId><ClrSysMmbId><MmbId>123456780</MmbId></ClrSysMmbId></FinInstnId></DbtrAgt>
    <Dbtr><Nm>Sam Lee</Nm></Dbtr>
    <DbtrAcct><Id><Othr><Id>4445556667</Id></Othr></Id></DbtrAcct>
   </DrctDbtTxInf>
  </PmtInf>
 </CstmrDrctDbtInitn>
</Document>
Read more: pain.008

For tech teams, product owners and testers

For developersStore MndtId and DtOfSgntr in your tables. You will need them when a customer disputes a debit. Map SeqTp (first, recurring or final) and LclInstrm to the NACHA SEC code.
For product ownersDebits carry more fraud and return risk than credits. Set limits for each collector, watch their return rates, and decide how long you keep proof of authorization.
What to testNo mandate. A collection on a weekend. Returns R01 (no money), R10 (not authorized) and R29 (the business says it did not authorize). One collector with a very high return rate.

NACHA file: the ACH format

In one line: A plain text file where every line is exactly 94 characters long. US ACH has used it for decades.

  • How it starts: the company builds it in its payroll software, or the bank builds it from a pain.001, pain.008, CSV file or API call.
  • What is inside: each line starts with a record type. 1 is the file header. 5 is the batch header (company, SEC code, date). 6 is one payment. 7 is an addenda with extra details. 8 is the batch total and 9 is the file total. At the end, lines of 9s fill the file up to a multiple of 10 lines.
  • How it travels: from the company to the bank, then from the bank to FedACH or EPN at set times during the day.
Sample file: NACHA file

Made-up data. Every line is exactly 94 characters. The last line of 9s brings the file up to 10 lines (one block).

101 123456780 2223334452611191705A094101RECEIVING BANK         SREE CORP BANK         PAYROLL1
5220SREE CORP                           1234567890CCDPAYMENT   261120261120   1222333440000001
6221234567809876543210       0000125050INV-7781       ACME SUPPLIES INC       1222333440000001
705INVOICE INV-7781 PAID IN FULL                                                   00010000001
822000000200123456780000000000000000001250501234567890                         222333440000001
9000001000001000000020012345678000000000000000000125050                                       
9999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999999
Read more: NACHA file

For tech teams, product owners and testers

For developersEvery field sits at a fixed position. The amount, in cents, is in positions 30–39. The receiving bank is in 4–11, with a check digit in 12. The account is in 13–29, the name in 55–76 and the trace number in 80–94. The entry hash is the sum of the 8-digit routing numbers, keeping only the last 10 digits.
For product ownersDecide whether clients can send you NACHA files directly. It is fast, but you must check them carefully. The alternative is to accept only pain.001 or API and build the NACHA file yourself.
What to testA line with 93 or 95 characters. A wrong entry hash. Wrong totals in record 8 or 9. Lowercase letters. The wrong transaction code for savings versus checking (32 versus 22). Missing 9s at the end.

Flat file and CSV: the bank’s own layout

In one line: A simple spreadsheet-style file. Smaller clients use it when they have no ISO 20022 software.

  • How it starts: the client exports it from their accounting software or a spreadsheet, following the column layout the bank gave them.
  • What the bank does: it maps each column to its internal payment record. From there it builds NACHA or pacs.008, just as it would for a pain.001.
Sample file: Flat file and CSV

Made-up data, shortened. Real files have more fields.

payment_type,value_date,payee_name,payee_aba,payee_account,amount,currency,reference
ACH,2026-11-20,Acme Supplies Inc.,123456780,9876543210,1250.50,USD,INV-7781
WIRE,2026-11-20,Delta Metals LLC,123456780,1231231231,48000.00,USD,PO-5520
Read more: Flat file and CSV

For tech teams, product owners and testers

For developersNever trust a CSV. Check the delimiters, quotes, encoding, header names, date formats and amounts (1,250.50 versus 1250.50). Reject any cell that starts with =, so nobody can sneak in a spreadsheet formula.
For product ownersPublish one clear template with examples. Every “special” layout you agree for one client becomes something you have to maintain forever.
What to testA missing column. An extra column. A comma inside a name. European-style decimals. Blank lines. Excel turning an account number into 9.88E+09.

pain.002: “here is what happened”

In one line: The bank’s reply to the customer: “here is what happened”, for the whole file and for each payment.

  • How it starts: the bank creates it automatically at key moments. That is when the file arrives, when it passes checks, and when each payment is sent, settled or rejected.
  • What is inside: the ID of the original file, one overall status, and a status for each payment with a reason code.
  • Statuses you will see: ACTC (file checked), ACCP (accepted), ACSP (sent, settling), ACSC (settled), PDNG (pending), PART (partly accepted) and RJCT (rejected).
Sample file: pain.002

Made-up data, shortened. Real files have more fields.

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.002.001.10">
 <CstmrPmtStsRpt>
  <GrpHdr><MsgId>STS-20261120-044</MsgId><CreDtTm>2026-11-20T09:12:00</CreDtTm></GrpHdr>
  <OrgnlGrpInfAndSts>
   <OrgnlMsgId>PAY-20261119-001</OrgnlMsgId>
   <OrgnlMsgNmId>pain.001.001.09</OrgnlMsgNmId>
   <GrpSts>PART</GrpSts>                       <!-- some OK, some not -->
  </OrgnlGrpInfAndSts>
  <OrgnlPmtInfAndSts>
   <OrgnlPmtInfId>BATCH-01</OrgnlPmtInfId>
   <TxInfAndSts>
    <OrgnlEndToEndId>INV-7781</OrgnlEndToEndId>
    <TxSts>ACSC</TxSts>                        <!-- settled -->
   </TxInfAndSts>
   <TxInfAndSts>
    <OrgnlEndToEndId>INV-7790</OrgnlEndToEndId>
    <TxSts>RJCT</TxSts>
    <StsRsnInf><Rsn><Cd>AC01</Cd></Rsn>        <!-- wrong account number -->
     <AddtlInf>ACH return R03: no account</AddtlInf></StsRsnInf>
   </TxInfAndSts>
  </OrgnlPmtInfAndSts>
 </CstmrPmtStsRpt>
</Document>
Read more: pain.002

For tech teams, product owners and testers

For developersLink every status back to the original MsgId, PmtInfId and EndToEndId. Each network has its own reason codes (NACHA has R codes, for example). Map them all to one internal list. Then map that list to standard ISO reason codes such as AC01 (wrong account) or AM04 (not enough money).
For product ownersDecide how many pain.002 messages the client gets: one at every step, or only the final one. Agree the reason codes with big clients, because their ERP reads them automatically.
What to testThe whole file is rejected. One line is rejected. An older status arrives after a newer one. A return comes in two days after the payment showed ACSC (settled).

BAI2: the classic US statement

In one line: An older text statement format. Many US companies still use it to reconcile their accounts.

  • How it starts: the bank produces it every morning for the previous day, and sometimes during the day for the current day.
  • What is inside: each line starts with a code. 01 is the file header, 02 the group and 03 the account and balances. 16 is one transaction. 49, 98 and 99 are the account, group and file totals.
  • Type codes tell you what each line is. For example, 010 is the opening balance, 015 the closing balance and 495 an outgoing wire.
Sample file: BAI2

Made-up data, shortened. Real files have more fields.

01,222333445,SREECORP,261120,0600,001,,,2/
02,SREECORP,222333445,1,261119,2400,USD,2/
03,1112223334,USD,010,5000000,,,015,4874950,,/
16,495,125050,0,OUT-000123,INV-7781,WIRE TO ACME SUPPLIES INC/
49,10000000,3/
98,10000000,1,5/
99,10000000,1,7/
Read more: BAI2

For tech teams, product owners and testers

For developersCheck the control totals in records 49, 98 and 99. A line can carry on in an 88 record. Amounts have no decimal point, so 125050 means $1,250.50.
For product ownersBAI2 carries less detail than camt.053. Plan the move for clients who need full remittance data.
What to test88 continuation lines. Totals that do not match. An account with no activity. A negative balance.

Read next

Sources: Federal Reserve Financial Services; The Clearing House; Nacha Operating Rules; Swift. Sample files are fictional and shortened.

Working on a payments project?

I help banks and fintechs deliver real-time payments, ISO 20022, and AI-driven AML and compliance change, from strategy to go-live.

Connect on LinkedInSee how I can help