Integration via ISO - Step 5: Account Status
ISO 20022 Account Status
Within the ISO 20022 standard, camt.052 and camt.053 are Cash Management messages designed for bank-to-customer reporting, superseding SWIFT MT940 and MT942. Adopting the camt message format supports richer data sets, larger field sizes, and structured information, which will become mandatory for many payment types starting November 2026.
-
camt.052: Bank-to-Customer Account Report provides intraday updates regarding account activity, offering interim insights into cash flows throughout the business day. The report contains an Interim Available Balance (ITAV), in addition to booked transactions, thereby supporting Widget Co.’s Treasury team in the proactive management of liquidity as transactions occur. TxB enables recipients to receive reports at 15-minute intervals, at specified times during the day (such as midday), and only when account activity is detected.
-
camt.053: Bank-to-Customer Statement serves as an end-of-day electronic bank statement, providing a comprehensive and legally compliant record of all entries posted to an account during the previous business day. This statement includes detailed opening and closing balances, extensive transaction data—such as fees, taxes, and exchange rates—and structured remittance information designed to support automated reconciliation processes. The camt.053 statement is generated by TxB once daily after the close of business, adhering to the established business date close schedule in UTC.
Get Account Balances
Account Identification <Acct>
Identifies the bank account being reported and it is consistent in both camt.052 and camt.053:
- IBAN
<Id><IBAN>: The International Bank Account Number, providing a globally standardized identifier for your account. - Other Identification
<Id><Othr><Id>: Used for non-IBAN accounts, typically containing a proprietary or domestic account number. - Currency
<Ccy>: The three-letter ISO currency code (e.g., USD, EUR) in which the account is denominated.
Balance Information <Bal>
The balance block provides a snapshot of your liquidity at specific points in time.
- Balance Type Code
<Tp><Cd>: Specifies the type of balance being reported.- OPBD: Opening Booked - The settled balance at the start of the reporting period.
- CLBD: Closing Booked - The final settled balance at the end of the period, reflecting all posted transactions.
- CLAV: Closing Available - The funds immediately available for use at the end of the period (may differ from CLBD due to holds or floats).
- ITBD: Interim Booked - An intra-day snapshot of settled transactions (common in camt.052).
- ITAV: Interim Available - Interim Available An intra-day snapshot of funds currently available for use.
- Amount
<Amt Ccy="[Code]">: The numerical value of the balance and its associated currency. - Credit/Debit Indicator
<CdtDbtInd>: Specifies if the balance is a credit (CRDT, positive/long) or a debit (DBIT, negative/overdrawn). - Date
<Dt>: The specific calendar date to which the balance applies.
Get Account Transactions <Ntry>
The <Ntry> block provides the core data for each individual movement on the account, essential for automated reconciliation.
- Amount and Currency
<Amt Ccy=[Currency Code]>: The value of the transaction. - Credit/Debit Indicator
<CdtDbtInd>: Indicates if the transaction is a credit (CRDT - incoming funds) or debit (DBIT - outgoing funds). Crucial for AR/AP reconciliation. - Booking Date
<BookgDt>: The date on which the transaction is entered into the bank’s ledger. For instance,<BookgDt>may correspond to a weekend for a transaction that is reported on the following Monday. - Bank Transaction Code
<BkTxCd>: A proprietary and ISO-standardized code used to categorize the transaction (e.g., Wire, Return, Interest, Fees). Full description of TxB Proprietary<BkTxCd><Prty>and ISO 20022 Domain<BkTxCd><Domn>, Family<BkTxCd><Domn><Fmly>, and Sub Family<BkTxCd><Domn><Fmly><SubFmly>transaction codes can be found in this link.
Granular Transaction Details <NtryDtls><TxDtls>
For further details , this block contains the rich data that distinguishes ISO 20022 from other formats (e.g., BAI2).
- References
<Refs>: A collection of identifiers used to link the statement entry back to the original instruction.- End-to-End ID
<EndToEndId>: The unique ID created by the payment originator (e.g., Widget Co.). This ID remains unchanged throughout the entire payment chain, making it a reliable field for AR and AP reconciliation. Note: This field may be empty for batch rails (e.g., US ACH) where transactions are posted as a single batch. In case of incoming payment credits, this attribute may or may not be present depending on how and with what details that incoming payment was initiated externally. - Transaction ID
<TxId>: A unique identifier assigned to the specific transaction by TxB. Widget Co. uses this number when opening a case with TxB Client Services. - Payment Information ID
<PmtInfId>: This identifier is the unique batch-id created by the payment originator (e.g., Widget Co.) for a payment or a group of payments. This ID is particularly important for reconciling batch payments like the ACH, which are batch posted for the bulk amount.
- End-to-End ID
- Remittance Information
<RmtInf>: Contains the "purpose of payment" or invoice details provided by the payment originator. This may be Structured (specific invoice numbers/dates) or Unstructured (free-form text).
Following are examples for transaction entries showing the Batch posting and the individual payment porting.
Batch Posting - US ACH Payment
<Ntry>
<NtryRef>82095300</NtryRef>
<Amt Ccy="USD">406.00</Amt>
<CdtDbtInd>DBIT</CdtDbtInd>
<RvslInd>false</RvslInd>
<Sts>BOOK</Sts>
<BookgDt>
<DtTm>2026-01-21T05:31:32.000Z</DtTm>
</BookgDt>
<ValDt>
<Dt>2026-01-21</Dt>
</ValDt>
<BkTxCd>
<Domn>
<Cd>PMNT</Cd>
<Fmly>
<Cd>ICDT</Cd>
<SubFmlyCd>ACDT</SubFmlyCd>
</Fmly>
</Domn>
<Prtry>
<Cd>ACH Credit Payment</Cd>
</Prtry>
</BkTxCd>
<NtryDtls>
<TxDtls>
<Refs>
<MsgId>GSEWNXMYR9UIH</MsgId>
<AcctSvcrRef>GPB2518416516112</AcctSvcrRef>
<PmtInfId>PaymentReqID0000001</PmtInfId> <!-- Widget Co. provided Batch ID -->
<TxId>GPB2518416516112</TxId> <!-- TxB generated Transaction ID -->
</Refs>
<AmtDtls>
<InstdAmt>
<Amt Ccy="USD">406.00</Amt>
</InstdAmt>
<TxAmt>
<Amt Ccy="USD">406.00</Amt>
</TxAmt>
</AmtDtls>
<Purp>
<Prtry>BILLPYMENT</Prtry>
</Purp>
<AddtlTxInf>SEC Code: CCD,Desc: Entry Description: BILLPYMENT; -, SEC: CCD, Client Ref ID: PaymentReqID0000001, GS ID: GPB2518416516112</AddtlTxInf>
</TxDtls>
</NtryDtls>
</Ntry>
Individual Payment Posting - Wire Payment
<Ntry>
<NtryRef>82095400</NtryRef>
<Amt Ccy="USD">4012.00</Amt>
<CdtDbtInd>DBIT</CdtDbtInd>
<RvslInd>false</RvslInd>
<Sts>BOOK</Sts>
<BookgDt>
<DtTm>2026-01-21T05:31:32.000Z</DtTm>
</BookgDt>
<ValDt>
<Dt>2026-01-21</Dt>
</ValDt>
<BkTxCd>
<Domn>
<Cd>PMNT</Cd>
<Fmly>
<Cd>ICDT</Cd>
<SubFmlyCd>DMCT</SubFmlyCd>
</Fmly>
</Domn>
<Prtry>
<Cd>Outgoing Wire</Cd>
</Prtry>
</BkTxCd>
<NtryDtls>
<TxDtls>
<Refs>
<MsgId>GS0E3C497CU6C90</MsgId>
<PmtInfId>PaymentReqID0000002</PmtInfId>
<EndToEndId>TxE2EID000021</EndToEndId> <!-- Widget Co. provided End-to-End ID -->
<TxId>GI2602100161081</TxId> <!-- TxB generated Transaction ID -->
</Refs>
<AmtDtls>
<InstdAmt>
<Amt Ccy="USD">4012.00</Amt>
</InstdAmt>
<TxAmt>
<Amt Ccy="USD">4012.00</Amt>
</TxAmt>
</AmtDtls>
<RltdPties>
<Cdtr>
<Nm>ABC Corp.</Nm>
</Cdtr>
</RltdPties>
<RltdAgts>
<CdtrAgt>
. . .
</CdtrAgt>
</RltdAgts>
<RmtInf>
<Ustrd>Invoice 9999</Ustrd>
</RmtInf>
<AddtlTxInf>Desc: To: ABC Corp., Remittance Info: "Invoice 9999", Client Ref ID: TxE2EID000021, GS ID: GI2602100161081, Clearing Ref: FED313114000QQQ</AddtlTxInf>
</TxDtls>
</NtryDtls>
</Ntry>
Additional Information
- ISO Transaction Type Codes
- Payment Status and Reports ISO XML File naming convention
- Examples of camt05x
| 1: Connect | 2: Create Account | 3: Payout | 4: Payout Status | 5: Account Status | 6: Reconcile |
|---|
Was this page useful?
Give feedback to help us improve developer.gs.com and serve you better.