ZagTrader

camt: Cash management

camt.052 Bank to Customer Account Report

Written and maintained by ZagTrader. Last reviewed . How this page is sourced and checked

camt.052 is the ISO 20022 account report a bank sends during the day: it shows entries on an account and, optionally, interim balances, so the account owner can manage cash before the end-of-day statement. It is the successor of the MT942 interim transaction report, and in CBPR+ the version is camt.052.001.08.

Message
BankToCustomerAccountReport
Root element
BkToCstmrAcctRpt
Common version
camt.052.001.08
MT equivalent
MT942

When camt.052 is used

Treasury, cash management and broker funding teams use camt.052 to follow an account during the business day: which client payments have arrived, which outgoing transfers have been debited, and what the booked and available balances are now. The bank sends it at agreed times or in answer to a request.

The structure is the same as camt.053: a group header, then a report (Rpt) per account with balances (Bal), optional totals (TxsSummry) and entries (Ntry). The differences are in purpose and rules: balances are optional in the base message, and entries can be pending (PDNG) or information only (INFO) as well as booked, because the day is not closed yet.

Unlike the MT942, which has no balance fields, camt.052 can carry interim balances. The CBPR+ guideline recommends that every camt.052 with entries also carries the interim booked (ITBD) and interim available (ITAV) balances, because regulators in more markets want the bank, not the client, to provide the intraday position.

The CBPR+ guideline states that camt.052 covers both the bank-to-bank and the bank-to-customer legs. Reporting messages were not part of the 22 November 2025 deadline for payment instructions and continue to be supported on Swift beyond it, so the move from MT942 is agreed with each bank.

Versions in common use

VersionWhere it is used
camt.052.001.08CBPR+ (cross-border payments and reporting on Swift), with the Business Application Header head.001.001.02 mandatory and one report per message.
camt.052.001.09 and laterISO 20022 has published newer versions. Each market practice chooses its own, so confirm the version with your bank and read the namespace of every file.

camt.052 key elements

Paths are relative to Document/BkToCstmrAcctRpt. Occurrence is from the base message (camt.052.001.08); market practice such as CBPR+ or a CSD’s rules can make an optional element mandatory or forbid it.

ElementOccursMeaning
GrpHdrGroup Header[1..1]Information about the message as a whole.
MsgIdMessage Identification[1..1]The sender’s reference for this message.
CreDtTmCreation Date Time[1..1]When the message was created, with time zone offset.
MsgIdOriginal Business Query Message Identification[1..1]Reference of the request this report answers, when it was requested. Inside an optional OrgnlBizQry block.
RptReport[1..n]One report for one account. CBPR+ restricts it to one per message.
IdIdentification[1..1]The bank’s unique identification of this report.
RptPgntnReport Pagination[0..1]Page number and last-page flag when one report needs several messages.
ElctrncSeqNbElectronic Sequence Number[0..1]Running number of electronic reports for the account.
CreDtTmCreation Date Time[0..1]When the report was created: the equivalent of MT942 field 13D.
FrToDtFrom To Date[0..1]The period the report covers, for example since the last report.
AcctAccount[1..1]The account reported on.
IBANIBAN[0..1]The account as an IBAN, or Othr/Id for other account numbers.
OwnrOwner[0..1]The account owner, for example by AnyBIC. Corresponds to the BIC in MT942 field 25P.
BalBalance[0..n]Balances at the time of the report. Optional in the base message; recommended by CBPR+ whenever entries are reported.
CdBalance Type Code[0..1]Usually ITBD (interim booked) and ITAV (interim available); also possible are OPBD, OPAV, XPCD (expected), FWAV and INFO.
AmtAmount[1..1]Balance amount, never negative, with the Ccy attribute.
CdtDbtIndCredit Debit Indicator[1..1]CRDT or DBIT.
DtTmDate Time[0..1]Date and time of an interim balance. A choice with Dt.
TxsSummryTransactions Summary[0..1]Totals of the reported entries.
NbOfNtriesNumber Of Entries (debit)[0..1]Number of debit entries: the count in MT942 field 90D.
SumSum (debit)[0..1]Total of the debit entries: the amount in field 90D. TtlCdtNtries holds the same for credits (field 90C).
NtryEntry[0..n]One entry on the account, the equivalent of MT942 field 61 with its field 86.
AmtAmount[1..1]Amount of the entry with the currency attribute.
CdtDbtIndCredit Debit Indicator[1..1]CRDT or DBIT.
RvslIndReversal Indicator[0..1]true when the entry reverses an earlier one.
CdStatus Code[0..1]BOOK booked, PDNG pending (booking not completed), INFO information only (no booking), FUTR future value. Only BOOK entries count in the booked balance.
DtTmBooking Date Time[0..1]When the entry was posted, or the expected booking time for a pending entry.
ValDtValue Date[0..1]Value date; for a pending entry, the expected or requested value date.
AcctSvcrRefAccount Servicer Reference[0..1]The bank’s reference for the entry. Use it to match the intraday entry to the same entry in the end-of-day camt.053.
BkTxCdBank Transaction Code[1..1]Transaction type as domain, family and sub-family (for example PMNT, RCDT, XBCT) and/or a proprietary code.
EndToEndIdEnd To End Identification[0..1]The originator’s reference of the underlying payment.
UETRUETR[0..1]Unique end-to-end transaction reference of the underlying Swift payment. Lets you link the entry to payment tracking.
DbtrDebtor[0..1]Who paid, for an incoming credit.
UstrdUnstructured Remittance Information[0..n]Remittance text such as an invoice or client account number.
AddtlNtryInfAdditional Entry Information[0..1]Free text about the entry.

Rules worth knowing

  • CBPR+: one report per message, Business Application Header head.001.001.02 mandatory, and the number of entries per message agreed between the parties.
  • CBPR+ recommendation: when a camt.052 carries entries, it should also carry the interim booked (ITBD) and interim available (ITAV) balances.
  • Entry status matters: only BOOK entries are on the books. PDNG entries may still change or disappear, and INFO entries are for information only. Do not post pending or information entries as final.
  • There is no floor limit element in the report. Which entries are included is agreed with the bank, whereas the MT942 states the limit in field 34F.
  • Base message rule: message pagination and report pagination must not both be used.

camt.052 XML example

At 13:00 Dubai time on 20 October 2026, ZagTrader Test Bank (ZAGTAEADXXX) reports the broker’s USD account: one outgoing transfer of USD 480,000.00 and one incoming client payment of USD 250,000.00 booked since the morning. From the opening balance of USD 1,250,000.00 the interim booked and available balances are USD 1,020,000.00. This is the same report as the MT942 example, with the balances the MT942 cannot carry.

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.052.001.08">
  <BkToCstmrAcctRpt>
    <GrpHdr>
      <MsgId>INTR261020USD03</MsgId>
      <CreDtTm>2026-10-20T13:00:00+04:00</CreDtTm>
    </GrpHdr>
    <Rpt>
      <Id>207-20261020-1300</Id>
      <RptPgntn>
        <PgNb>1</PgNb>
        <LastPgInd>true</LastPgInd>
      </RptPgntn>
      <ElctrncSeqNb>3</ElctrncSeqNb>
      <CreDtTm>2026-10-20T13:00:00+04:00</CreDtTm>
      <Acct>
        <Id>
          <IBAN>AE070331234567890123456</IBAN>
        </Id>
        <Ccy>USD</Ccy>
        <Svcr>
          <FinInstnId>
            <BICFI>ZAGTAEADXXX</BICFI>
          </FinInstnId>
        </Svcr>
      </Acct>
      <Bal>
        <Tp>
          <CdOrPrtry>
            <Cd>ITBD</Cd>
          </CdOrPrtry>
        </Tp>
        <Amt Ccy="USD">1020000.00</Amt>
        <CdtDbtInd>CRDT</CdtDbtInd>
        <Dt>
          <DtTm>2026-10-20T13:00:00+04:00</DtTm>
        </Dt>
      </Bal>
      <Bal>
        <Tp>
          <CdOrPrtry>
            <Cd>ITAV</Cd>
          </CdOrPrtry>
        </Tp>
        <Amt Ccy="USD">1020000.00</Amt>
        <CdtDbtInd>CRDT</CdtDbtInd>
        <Dt>
          <DtTm>2026-10-20T13:00:00+04:00</DtTm>
        </Dt>
      </Bal>
      <TxsSummry>
        <TtlCdtNtries>
          <NbOfNtries>1</NbOfNtries>
          <Sum>250000.00</Sum>
        </TtlCdtNtries>
        <TtlDbtNtries>
          <NbOfNtries>1</NbOfNtries>
          <Sum>480000.00</Sum>
        </TtlDbtNtries>
      </TxsSummry>
      <Ntry>
        <Amt Ccy="USD">480000.00</Amt>
        <CdtDbtInd>DBIT</CdtDbtInd>
        <Sts>
          <Cd>BOOK</Cd>
        </Sts>
        <BookgDt>
          <DtTm>2026-10-20T09:42:00+04:00</DtTm>
        </BookgDt>
        <ValDt>
          <Dt>2026-10-20</Dt>
        </ValDt>
        <AcctSvcrRef>ZAG26293000101</AcctSvcrRef>
        <BkTxCd>
          <Domn>
            <Cd>PMNT</Cd>
            <Fmly>
              <Cd>ICDT</Cd>
              <SubFmlyCd>FICT</SubFmlyCd>
            </Fmly>
          </Domn>
        </BkTxCd>
        <NtryDtls>
          <TxDtls>
            <Refs>
              <InstrId>BRK2610200017</InstrId>
              <UETR>fbf98c4f-3a79-49d0-a030-5d6bb29aaca9</UETR>
            </Refs>
            <Amt Ccy="USD">480000.00</Amt>
            <CdtDbtInd>DBIT</CdtDbtInd>
          </TxDtls>
        </NtryDtls>
      </Ntry>
      <Ntry>
        <Amt Ccy="USD">250000.00</Amt>
        <CdtDbtInd>CRDT</CdtDbtInd>
        <Sts>
          <Cd>BOOK</Cd>
        </Sts>
        <BookgDt>
          <DtTm>2026-10-20T11:05:00+04:00</DtTm>
        </BookgDt>
        <ValDt>
          <Dt>2026-10-20</Dt>
        </ValDt>
        <AcctSvcrRef>ZAG26293000102</AcctSvcrRef>
        <BkTxCd>
          <Domn>
            <Cd>PMNT</Cd>
            <Fmly>
              <Cd>RCDT</Cd>
              <SubFmlyCd>XBCT</SubFmlyCd>
            </Fmly>
          </Domn>
        </BkTxCd>
        <NtryDtls>
          <TxDtls>
            <Refs>
              <InstrId>PAY2610200388</InstrId>
              <EndToEndId>DEP-88213-1020</EndToEndId>
              <UETR>ad60d86d-1d33-4493-977b-a90383e679fd</UETR>
            </Refs>
            <Amt Ccy="USD">250000.00</Amt>
            <CdtDbtInd>CRDT</CdtDbtInd>
            <RltdPties>
              <Dbtr>
                <Pty>
                  <Nm>AL NOOR INVESTMENTS LLC</Nm>
                </Pty>
              </Dbtr>
            </RltdPties>
          </TxDtls>
        </NtryDtls>
      </Ntry>
    </Rpt>
  </BkToCstmrAcctRpt>
</Document>
Decode this example in the parser

The interim balances use a date and time (DtTm), because they change during the day.

BICs, names, references, the IBAN and the UETRs are made up; the IBAN carries valid check digits.

camt.052 and its MT equivalent

camt.052 is the ISO 20022 equivalent of the MT942 Interim Transaction Report. It can also carry the balance information that the MT941 Balance Report provides.

Translating a camt.052 into an MT942 drops the interim balances, the entry statuses and most of the transaction detail, and pending or information-only entries have no clean MT942 equivalent beyond the EC and ED marks.

ISO 20022 elementMT fieldNote
GrpHdr/MsgId20
GrpHdr/OrgnlBizQry/MsgId21When the report answers a request.
Rpt/Acct/Id, Rpt/Acct/Ownr25 / 25P
Rpt/ElctrncSeqNb, Rpt/RptPgntn/PgNb28C
No element34FFloor limits are agreed with the bank, not carried in the report.
Rpt/CreDtTm13D
Rpt/Ntry (Amt, CdtDbtInd, RvslInd, ValDt, BookgDt, BkTxCd, AcctSvcrRef, NtryDtls/TxDtls/Refs)61Same subfield mapping as MT940 to camt.053.
Rpt/Ntry/Sts/Cd61 mark EC / EDExpected entries are closest to a status other than BOOK, for example PDNG.
TxDtls/RltdPties, TxDtls/RmtInf, TxDtls/AddtlTxInf, Ntry/AddtlNtryInf86 (per entry)
Rpt/TxsSummry/TtlDbtNtries (NbOfNtries, Sum)90D
Rpt/TxsSummry/TtlCdtNtries (NbOfNtries, Sum)90C
Rpt/AddtlRptInf86 (final)

Common errors and rejects

  1. Pending or information entries posted as booked

    A camt.052 can list PDNG and INFO entries. Posting them to the ledger as if booked makes the intraday position wrong and creates duplicates when the camt.053 arrives. Filter on Sts/Cd BOOK for postings.

  2. Intraday entries counted again at end of day

    Every booked entry reported in a camt.052 appears again in the day’s camt.053. Match them on AcctSvcrRef (or NtryRef) and replace the provisional entries with the statement.

    How to fix it
  3. Interim balance treated as closing balance

    ITBD and ITAV are snapshots at the time in Dt/DtTm and change during the day. The closing booked balance is CLBD in the camt.053.

    How to fix it
  4. No balances in the report

    Balances are optional in the base message. If your system needs them, ask the bank to send ITBD and ITAV, as the CBPR+ guideline recommends.

  5. Parser fails on the version

    Read the namespace (for example urn:iso:std:iso:20022:tech:xsd:camt.052.001.08) and agree the version with each bank before go-live.

camt.052 questions

What is camt.052 used for?
Intraday reporting. The bank tells the account owner during the day which entries have hit the account and, usually, the interim booked and available balances, so cash can be managed before the end-of-day camt.053.
What is the difference between camt.052 and camt.053?
camt.053 is the statement for a closed period and contains only booked entries with opening and closing balances. camt.052 reports during the day, may include pending or information-only entries, and carries interim balances such as ITBD and ITAV.
What is the MT equivalent of camt.052?
The MT942 Interim Transaction Report. Unlike the MT942, camt.052 can carry balances and entry statuses.
What do ITBD and ITAV mean?
Interim booked balance and interim available balance: the booked and the available balance at a moment during the business day, subject to change until the day closes.
Which camt.052 version does CBPR+ use?
camt.052.001.08, with a mandatory Business Application Header and one report per message.

All ISO 20022 messages · MT messages · MT to ISO 20022 migration