
⏱ About a 6-minute read. Click “Read more” or “Sample file” whenever you want the details.
Sree has to pay $48,000 for a new machine today, and the seller wants money that cannot be pulled back. So the bank sends a Fedwire.
- 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 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 Fedwire works
In one line: One large payment at a time. The Fed settles it straight away, and it is final.
- Coming in: a pain.001 marked urgent (URGP), an entry on the bank’s portal, or an API call. Two people approve it.
- Going out: a pacs.008 for a customer’s payment, or a pacs.009 when the bank pays another bank. It travels over FedLine.
- Coming back: a pacs.002 with the status. camt.056 and camt.029 if someone asks for the money back, and pacs.004 when it is returned.
Status, rules, security and data
| Status flow | Entered → Approved (2 people) → Sent → Acknowledged → Settled, final Side paths: Rejected by Fed, Recall requested, Returned (pacs.004) |
| Regulation and rules | Regulation J (subpart B) and UCC Article 4A, which set the legal rules for wires. Federal Reserve Operating Circular 6. OFAC sanctions. And the Bank Secrecy Act “travel rule” for transfers of $3,000 or more. |
| Security standards | Banks connect through FedLine and must pass the Fed’s yearly Security and Resiliency Assurance Program (Operating Circular 5). Inside the bank: one person enters, another approves, and users sign in with strong authentication. |
| Data governance | Fedwire moved to ISO 20022 on July 14, 2025, so names and addresses are now much fuller. Store the full payer and payee details for the travel rule, and keep them for at least 5 years. |
Read more: Fedwire
For tech teams, product owners and testers
| For developers | Build the pacs.008 or pacs.009 following the Fedwire guidelines, with the business application header. Handle pacs.002 and returns. |
| For product owners | Cut-off times, approval limits and fees. And what clients see when a wire is held for a sanctions review. |
| What to test | Long addresses. A recall on a wire that has already settled. A drawdown request. A wire sent after cut-off. The same wire sent twice. |
Step by step
- A payments clerk at the company enters the wire on the bank’s portal. Or the company sends a pain.001 marked urgent (URGP), or calls the API.
- The company’s payments manager approves it (this is called maker-checker). The bank checks limits.
- Sanctions screening runs. If a name looks like a possible match, the wire goes to a review queue before it is released.
- The bank debits the customer’s account and builds the message. A pacs.008 for a customer payment, or a pacs.009 for a bank payment, each with its business application header.
- The message goes over FedLine. The Fed settles it immediately, moving money between the two banks’ accounts at the Fed, and sends back a pacs.002.
- The receiving bank credits the payee’s account.
- The customer gets a camt.054 notice and a pain.002, and the bank reconciles its Fed account. If there was a mistake, the bank uses camt.056 (“please return it”) and pacs.004 (the money coming back).
When things go wrong: rejected, returned, cancelled
Not every payment goes through. On Fedwire, there are three ways a payment can fail. Each one means something different for the money.
Rejected. A wire can be stopped before it is released: the second approver says no, the client is over its limit, sanctions screening blocks or rejects it, or the Fed refuses a badly formed message. The money doesn’t move (or the debit is reversed straight away), and the client gets a pacs.002 with the reason.
Returned. Once the Fed settles a wire, it is final. If the receiving bank can’t apply it (closed or wrong account), it sends the money back as a new payment, a pacs.004, linked to the original. The bank credits the client and marks the wire Returned. The amount can be smaller if a fee was taken.
Cancelled. Before release, a wire can be cancelled in the queue or at approval. After release, you can only ask. The bank sends a camt.056 (“please return it”). The other bank answers with a camt.029, and if it agrees, the money comes back as a pacs.004. Nobody has to say yes.
Codes you will see: AC04 closed account · AC01 wrong account · AM04 not enough money · RR04 regulatory reason · FOCR returned after a recall request
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.
| Path | File or message | From → to | What it says |
|---|---|---|---|
| Rejected | pain.002 (RJCT) | Bank → client | Wire refused before release, with reason |
| Rejected | pacs.002 (RJCT) or admi.002 | Fed → bank | Payment refused, or message badly formed |
| Returned | pacs.004 | Receiving bank → Fed → your bank | Money sent back, linked to the original |
| Returned | camt.054 and pain.002 | Bank → client | Credit notice for the returned money |
| Cancelled | camt.055 | Client → bank | Please cancel my wire |
| Cancelled | camt.056, then camt.029 | Your bank ↔ receiving bank | “Please return it” and the answer |
Sample file: pacs.002 with RJCT
Fictional data, shortened. Real files carry more fields.
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pacs.002.001.10">
<FIToFIPmtStsRpt>
<GrpHdr><MsgId>FED-STS-88120</MsgId><CreDtTm>2026-11-20T10:02:11</CreDtTm></GrpHdr>
<TxInfAndSts>
<OrgnlInstrId>SND-20261120-0007</OrgnlInstrId>
<OrgnlEndToEndId>INV-7781</OrgnlEndToEndId>
<OrgnlUETR>3f1c9d2e-7b4a-4c1e-9a55-2d8e6f0b1a77</OrgnlUETR>
<TxSts>RJCT</TxSts>
<StsRsnInf><Rsn><Cd>AC04</Cd></Rsn></StsRsnInf> <!-- account closed -->
</TxInfAndSts>
</FIToFIPmtStsRpt>
</Document>Sample file: pacs.004 payment return
Fictional data, shortened. Real files carry more fields.
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pacs.004.001.10">
<PmtRtr>
<GrpHdr>
<MsgId>RTN-20261120-0031</MsgId><CreDtTm>2026-11-20T14:20:00</CreDtTm>
<NbOfTxs>1</NbOfTxs><SttlmInf><SttlmMtd>CLRG</SttlmMtd></SttlmInf>
</GrpHdr>
<TxInf>
<RtrId>RTN-0031-1</RtrId>
<OrgnlInstrId>SND-20261120-0007</OrgnlInstrId>
<OrgnlEndToEndId>INV-7781</OrgnlEndToEndId> <!-- links to the original -->
<OrgnlUETR>3f1c9d2e-7b4a-4c1e-9a55-2d8e6f0b1a77</OrgnlUETR>
<RtrdIntrBkSttlmAmt Ccy="USD">1250.50</RtrdIntrBkSttlmAmt>
<IntrBkSttlmDt>2026-11-20</IntrBkSttlmDt>
<RtrRsnInf><Rsn><Cd>AC04</Cd></Rsn></RtrRsnInf> <!-- account closed -->
</TxInf>
</PmtRtr>
</Document>Sample file: camt.056 “please return it”
Fictional data, shortened. Real files carry more fields.
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.056.001.08">
<FIToFIPmtCxlReq>
<Assgnmt>
<Id>CXL-20261120-0004</Id>
<Assgnr><Agt><FinInstnId><ClrSysMmbId><MmbId>222333445</MmbId></ClrSysMmbId></FinInstnId></Agt></Assgnr>
<Assgne><Agt><FinInstnId><ClrSysMmbId><MmbId>123456780</MmbId></ClrSysMmbId></FinInstnId></Agt></Assgne>
<CreDtTm>2026-11-20T11:15:00</CreDtTm>
</Assgnmt>
<Undrlyg><TxInf>
<CxlId>CXL-0004-1</CxlId>
<OrgnlEndToEndId>INV-7781</OrgnlEndToEndId>
<OrgnlUETR>3f1c9d2e-7b4a-4c1e-9a55-2d8e6f0b1a77</OrgnlUETR>
<OrgnlIntrBkSttlmAmt Ccy="USD">1250.50</OrgnlIntrBkSttlmAmt>
<CxlRsnInf><Rsn><Cd>DUPL</Cd></Rsn></CxlRsnInf> <!-- sent twice by mistake -->
</TxInf></Undrlyg>
</FIToFIPmtCxlReq>
</Document>Sample file: camt.029 the answer
Fictional data, shortened. Real files carry more fields.
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.029.001.09">
<RsltnOfInvstgtn>
<Assgnmt><Id>ANS-20261120-0019</Id><CreDtTm>2026-11-20T16:40:00</CreDtTm></Assgnmt>
<Sts><Conf>RJCR</Conf></Sts> <!-- RJCR = request refused, CNCL = accepted -->
<CxlDtls><TxInfAndSts>
<OrgnlEndToEndId>INV-7781</OrgnlEndToEndId>
<CxlStsRsnInf><Rsn><Cd>NOAS</Cd></Rsn></CxlStsRsnInf> <!-- payee did not answer -->
</TxInfAndSts></CxlDtls>
</RsltnOfInvstgtn>
</Document>Sample file: admi.002 message rejected
Fictional data, shortened. Real files carry more fields.
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:admi.002.001.01">
<admi.002.001.01>
<RltdRef><Ref>SND-20261120-0007</Ref></RltdRef>
<Rsn>
<RjctgPtyRsn>FF01</RjctgPtyRsn> <!-- message format not valid -->
<RsnDesc>Mandatory element missing</RsnDesc>
</Rsn>
</admi.002.001.01>
</Document>Fedwire 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: the 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 payment operations and app support, and L3 is engineering.
| Step | File | Check | If it goes wrong | Who |
|---|---|---|---|---|
| 1. Wire request arrives | pain.001 (URGP), portal or API | Request is complete: full names, structured address, purpose. | Missing data? Send it back to the client with pain.002 RJCT. Don’t guess. | L2 |
| 2. Approval | Internal record (maker-checker) | A bank payments operations manager approved it, within their approval limit. | Approval stuck near cut-off? Call the approver, or tell the client it goes tomorrow. | L1 and L2 |
| 3. Sanctions and limits | Internal record, screening case | No open OFAC hit, limits OK, money available. | Possible match? Hold it, work the case, document the decision. Never release to beat a cut-off. | L2 with compliance |
| 4. Send to the Fed | pacs.008 or pacs.009 over FedLine | Sent before cut-off, pacs.002 received, debit posted. | No pacs.002? Check FedLine status before anything else. Never resend a wire until you know the Fed didn’t get it. | L2, L3 if it’s technical |
| 5. Confirm and report | camt.054, pain.002 | Client sees the debit and the final status the same day. | Missing notice? Send it manually and log why. | L1 and L2 |
| 6. Returns and recalls | pacs.004, camt.056, camt.029 | Every return is linked to the original wire, and every recall gets an answer. | Recall with no answer? Chase the other bank. Tell the client a wire is final and a recall is only a request. | L2 |
| 7. Reconcile | Fed account statement | Sent and received wires equal the Fed account movement. | Any break becomes a reconciliation item, owned until it’s closed. | L2 with finance |
Golden rules
- A wire is final once the Fed settles it. Never promise a client you can pull it back.
- Never resend a wire until you have confirmed the Fed didn’t receive the first one.
- Never release a sanctions hold to beat a cut-off.
- Keep full payer and payee data for the travel rule, at least 5 years.
Want the full picture, from building it to running it live? Read the Wire Payments Runbook (Fedwire and CHIPS).
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 client | Who enters wires and who approves them? Will they use the portal, a pain.001 (URGP) or the API? What are the daily limits? Do they need drawdowns or saved templates for repeat wires? |
| Set up and connectivity | User access with maker-checker, approval limits, tokens or certificates, the pain.001 channel, and where pain.002 and camt.054 should go. |
| Test and certify | Send test wires end to end, including one that gets held for sanctions and one that is returned. Check that full names and structured addresses come through the ISO 20022 mapping intact. |
| Go-live and hypercare | Send the first live wires early in the day, well before cut-off. Make sure the client sees the status and the debit notice the same day. |
| Where it usually breaks | Approvals stuck after cut-off. Addresses cut short. Missing purpose or remittance details. A wire sent twice because someone double-clicked or re-sent a file. |
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 developers | First 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 owners | Decide 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 test | Totals 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. |
pacs.008 and pacs.009: bank-to-bank payment
In one line: The message one bank sends to the network to move money. pacs.008 is for a customer’s payment. pacs.009 is when the bank pays for itself.
- How it starts: your bank creates it once all checks pass. It is built from the bank’s own internal payment record, not copied from the customer’s file.
- Who uses it: Fedwire, CHIPS, RTP, FedNow and SWIFT for cross-border payments.
- What is inside: the amount, the settlement date, the sending and receiving banks, who pays, who gets paid, the customer’s EndToEndId and a UETR (a unique tracking ID).
Sample file: pacs.008 and pacs.009
Made-up data, shortened. Real files have more fields.
<!-- Business Application Header (head.001) is sent with it -->
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pacs.008.001.08">
<FIToFICstmrCdtTrf>
<GrpHdr>
<MsgId>20261120BANKOUT000123</MsgId><CreDtTm>2026-11-20T10:01:07</CreDtTm>
<NbOfTxs>1</NbOfTxs>
<SttlmInf><SttlmMtd>CLRG</SttlmMtd></SttlmInf>
</GrpHdr>
<CdtTrfTxInf>
<PmtId>
<InstrId>OUT-000123</InstrId>
<EndToEndId>INV-7781</EndToEndId> <!-- from the customer -->
<UETR>8a562c67-ca16-48ba-b074-65581be6f001</UETR>
</PmtId>
<IntrBkSttlmAmt Ccy="USD">1250.50</IntrBkSttlmAmt>
<IntrBkSttlmDt>2026-11-20</IntrBkSttlmDt>
<ChrgBr>SLEV</ChrgBr>
<InstgAgt><FinInstnId><ClrSysMmbId><MmbId>222333445</MmbId></ClrSysMmbId></FinInstnId></InstgAgt>
<InstdAgt><FinInstnId><ClrSysMmbId><MmbId>123456780</MmbId></ClrSysMmbId></FinInstnId></InstdAgt>
<Dbtr><Nm>Sree Corp</Nm>
<PstlAdr><TwnNm>Edison</TwnNm><CtrySubDvsn>NJ</CtrySubDvsn><Ctry>US</Ctry></PstlAdr></Dbtr>
<DbtrAcct><Id><Othr><Id>1112223334</Id></Othr></Id></DbtrAcct>
<DbtrAgt><FinInstnId><ClrSysMmbId><MmbId>222333445</MmbId></ClrSysMmbId></FinInstnId></DbtrAgt>
<CdtrAgt><FinInstnId><ClrSysMmbId><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>
</FIToFICstmrCdtTrf>
</Document>Read more: pacs.008 and pacs.009
For tech teams, product owners and testers
| For developers | Every network has its own rules for which fields are allowed, how long they can be and which characters are OK. Write one formatter per network, all fed from the same internal record. Keep a copy of the exact message you sent, for audit. |
| For product owners | Better data, such as structured addresses and remittance details, means fewer false sanctions alerts and easier reconciliation. Decide how much of it your clients must give you. |
| What to test | Each network’s required fields. Very long names and addresses. A missing UETR. A duplicate InstrId. A message sent after the network’s cut-off. |
pacs.002: the network’s answer
In one line: The network’s answer about a bank-to-bank payment: accepted, settled, or rejected (with a reason).
- How it starts: the network or the receiving bank sends it back. On instant rails it takes seconds. On wires it takes minutes.
- Statuses: ACSC (settled), ACSP (in progress), ACWP (accepted, waiting to be posted) and RJCT (rejected, with a reason such as AC04, closed account).
Sample file: pacs.002
Made-up data, shortened. Real files have more fields.
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pacs.002.001.10">
<FIToFIPmtStsRpt>
<GrpHdr><MsgId>NET-ACK-778899</MsgId><CreDtTm>2026-11-20T10:01:09</CreDtTm></GrpHdr>
<TxInfAndSts>
<OrgnlInstrId>OUT-000123</OrgnlInstrId>
<OrgnlEndToEndId>INV-7781</OrgnlEndToEndId>
<OrgnlUETR>8a562c67-ca16-48ba-b074-65581be6f001</OrgnlUETR>
<TxSts>ACSC</TxSts> <!-- or RJCT with <StsRsnInf><Rsn><Cd>AC04</Cd> -->
</TxInfAndSts>
</FIToFIPmtStsRpt>
</Document>Read more: pacs.002
For tech teams, product owners and testers
| For developers | Match it to the message you sent using OrgnlInstrId, OrgnlEndToEndId or OrgnlUETR. Be ready for statuses that arrive late, twice, or in the wrong order. |
| For product owners | Decide what the customer sees at each status, and at what point you tell them the money is gone for good. |
| What to test | A reject after a timeout. An answer that never arrives. Two answers for one payment. A reject reason you have never seen before. |
camt.056, camt.029 and pacs.004: asking for money back
In one line: How one bank asks another to send a payment back, and how the money returns.
- How it starts: the customer or the bank spots a mistake, such as a duplicate, a wrong amount or fraud, and asks for a recall.
- camt.056 says “please return this payment.” camt.029 is the answer, and it is often “no.” pacs.004 is the money actually coming back, linked to the original payment.
- Remember: wires and instant payments are final. The other bank does not have to say yes.
Sample file: camt.056, camt.029 and pacs.004
Made-up data, shortened. Real files have more fields.
<!-- Step 1: the sending bank asks for the money back (camt.056) -->
<FIToFIPmtCxlReq>
<Undrlyg><TxInf>
<CxlId>CXL-0042</CxlId>
<OrgnlEndToEndId>INV-7781</OrgnlEndToEndId>
<OrgnlUETR>8a562c67-ca16-48ba-b074-65581be6f001</OrgnlUETR>
<CxlRsnInf><Rsn><Cd>DUPL</Cd></Rsn></CxlRsnInf> <!-- sent twice by mistake -->
</TxInf></Undrlyg>
</FIToFIPmtCxlReq>
<!-- Step 2a: the other bank says no (camt.029) ... -->
<!-- Step 2b: ... or sends the money back (pacs.004) -->
<PmtRtr>
<TxInf>
<RtrId>RTN-5511</RtrId>
<OrgnlEndToEndId>INV-7781</OrgnlEndToEndId>
<OrgnlUETR>8a562c67-ca16-48ba-b074-65581be6f001</OrgnlUETR>
<RtrdIntrBkSttlmAmt Ccy="USD">1250.50</RtrdIntrBkSttlmAmt>
<RtrRsnInf><Rsn><Cd>FOCR</Cd></Rsn></RtrRsnInf> <!-- following cancellation request -->
</TxInf>
</PmtRtr>Read more: camt.056, camt.029 and pacs.004
For tech teams, product owners and testers
| For developers | A pacs.004 has to find the original payment using its EndToEndId and UETR. Then it reverses the posting and updates the status. The amount that comes back can be smaller if fees were taken. |
| For product owners | Set up the recall process: who can ask for one, how fast it happens, and how the customer is told. With fraud, every minute counts. |
| What to test | A recall that is accepted. One that is refused. A partial return. A return for a payment you cannot find. A return in a different currency. |
camt.052, camt.053 and camt.054: reports and statements
In one line: How the bank tells the customer what came in and what went out.
- camt.052: a report during the day, sent several times.
- camt.053: the end-of-day statement, with opening and closing balances.
- camt.054: a notice for each debit or credit, sent as it happens.
- Each line is either BOOK (posted) or PDNG (pending).
Sample file: camt.052, camt.053 and camt.054
Made-up data, shortened. Real files have more fields.
<!-- camt.054: one notice, sent as soon as the account is debited -->
<BkToCstmrDbtCdtNtfctn>
<Ntfctn>
<Acct><Id><Othr><Id>1112223334</Id></Othr></Id></Acct>
<Ntry>
<Amt Ccy="USD">1250.50</Amt>
<CdtDbtInd>DBIT</CdtDbtInd>
<Sts><Cd>BOOK</Cd></Sts>
<BookgDt><Dt>2026-11-20</Dt></BookgDt>
<ValDt><Dt>2026-11-20</Dt></ValDt>
<NtryDtls><TxDtls><Refs><EndToEndId>INV-7781</EndToEndId></Refs></TxDtls></NtryDtls>
</Ntry>
</Ntfctn>
</BkToCstmrDbtCdtNtfctn>
<!-- camt.053: the end-of-day statement adds opening and closing balances -->
<Bal><Tp><CdOrPrtry><Cd>OPBD</Cd></CdOrPrtry></Tp><Amt Ccy="USD">50000.00</Amt><CdtDbtInd>CRDT</CdtDbtInd></Bal>
<Bal><Tp><CdOrPrtry><Cd>CLBD</Cd></CdOrPrtry></Tp><Amt Ccy="USD">48749.50</Amt><CdtDbtInd>CRDT</CdtDbtInd></Bal>Read more: camt.052, camt.053 and camt.054
For tech teams, product owners and testers
| For developers | Put the customer’s EndToEndId and the bank’s reference on every entry. That is what the customer’s ERP uses to match payments. Use the standard bank transaction codes (BkTxCd). |
| For product owners | Pick the format and timing for each type of client. For example, camt.053 for large companies, BAI2 for others and PDF for small businesses. |
| What to test | Opening balance plus entries equals the closing balance. A reversal. A pending entry that books later. A day with no activity (the statement should still go out). |
Read next
- All payment files, one by one (pain.001, pain.002, pain.008, NACHA, ISO 20022)
- Related runbook on this site
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