camt.054 Bank to Customer Debit Credit Notification

When camt.054 is used

An account servicing bank sends a camt.054 when it books, or is about to book, a debit or a credit that the account owner should know about at once: an incoming payment the owner is waiting for, a debit on a nostro account, a returned payment. A broker can release a client’s trade on the credit notification, and a bank’s nostro team can confirm a cover payment arrived.

One message holds a group header and one or more notifications (Ntfctn), each for one account with its entries (Ntry). There are no balances in a camt.054: it reports movements, not positions. Balances come in the camt.052 during the day and the camt.053 at the end of the day.

Banks also use camt.054 to give the details behind a single batch booking on the statement: the statement shows one total, and a camt.054 lists the individual transactions. The entry’s AddtlInfInd can point to the message that carries those details.

Like the other reporting messages, camt.054 was not part of the 22 November 2025 deadline for payment instructions, and MT900 and MT910 continue to be supported on Swift beyond that date. Which notifications a bank sends, and in which format, is agreed with the account owner.

Versions in common use

camt.054 key elements

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

Rules worth knowing

• camt.054 has no balance element. Never derive a balance from notifications alone; use camt.052 or camt.053.
• Entry status decides what a notification means: BOOK is a booked movement, PDNG an expected one that may still change, INFO information only. MT900 and MT910 always confirm a debit or credit already made.
• Every booked entry notified in a camt.054 also appears in the camt.053 for the day. Match them on AcctSvcrRef so they are posted once.
• For batch bookings, the camt.053 can carry one entry with AddtlInfInd pointing to a camt.054 that lists the individual transactions.
• CBPR+ uses camt.054.001.08 with a Business Application Header, and limits text fields to the FIN X character set except names, addresses and remittance information.

camt.054 XML example

At 11:05 Dubai time on 20 October 2026, ZagTrader Test Bank (ZAGTAEADXXX) credits the broker’s USD account with USD 250,000.00 that a client, Al Noor Investments LLC, paid from its account at BANKGB2LXXX, and notifies the broker at once. This is the same credit that appears in the camt.052 and camt.053 examples, with the same bank reference ZAG26293000102. In MT it would have been an MT910.

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.054.001.08">
  <BkToCstmrDbtCdtNtfctn>
    <GrpHdr>
      <MsgId>CDT2610200102</MsgId>
      <CreDtTm>2026-10-20T11:06:00+04:00</CreDtTm>
    </GrpHdr>
    <Ntfctn>
      <Id>CDT2610200102</Id>
      <Acct>
        <Id>
          <IBAN>AE070331234567890123456</IBAN>
        </Id>
        <Ccy>USD</Ccy>
        <Svcr>
          <FinInstnId>
            <BICFI>ZAGTAEADXXX</BICFI>
          </FinInstnId>
        </Svcr>
      </Acct>
      <Ntry>
        <NtryRef>CDT2610200102</NtryRef>
        <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>
              <DbtrAcct>
                <Id>
                  <IBAN>GB42BANK40051587654321</IBAN>
                </Id>
              </DbtrAcct>
            </RltdPties>
            <RltdAgts>
              <DbtrAgt>
                <FinInstnId>
                  <BICFI>BANKGB2LXXX</BICFI>
                </FinInstnId>
              </DbtrAgt>
            </RltdAgts>
            <RmtInf>
              <Ustrd>CLIENT DEPOSIT ACCOUNT 88213</Ustrd>
            </RmtInf>
          </TxDtls>
        </NtryDtls>
      </Ntry>
    </Ntfctn>
  </BkToCstmrDbtCdtNtfctn>
</Document>

Status BOOK: the credit is booked, so the broker can treat the funds as received.

BICs, names, references, the IBANs and the UETR are made up; the IBANs carry valid check digits.

camt.054 and its MT equivalent

camt.054 is the ISO 20022 equivalent of the MT900 Confirmation of Debit and the MT910 Confirmation of Credit. One camt.054 can notify several entries, debits and credits, where each MT900 or MT910 confirms one.

A notification can carry far more about the underlying payment than an MT910: structured debtor and creditor, the UETR, end-to-end and instruction identifications, purpose and remittance information. Translating a camt.054 to an MT910 loses most of it.

Common errors and rejects

1. Pending notification posted as a final credit

   A camt.054 can report an entry before it is booked (PDNG) or for information only (INFO). Releasing funds or trades on such an entry is a risk. Act on BOOK, and on PDNG only if your agreement with the bank says so.

2. Same movement posted twice

   The credit appears in the camt.054, in the camt.052 and again in the camt.053. Use AcctSvcrRef to post it once and to tick the notification off against the statement.

   How to fix it

3. Credit cannot be matched to the expected receipt

   Match on EndToEndId first, then the UETR, then amount and value date with the debtor name. If the payer’s bank translated the payment from MT, references may be cut to 16 characters.

   How to fix it

4. Balance built from notifications

   Notifications are not sent for every entry unless agreed, and charges or corrections may only appear on the statement. A balance summed from camt.054 messages drifts; take balances from camt.052 or camt.053.

   How to fix it

5. Parser fails on the version

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

Related messages

• camt.053Bank to Customer Statement
• camt.052Bank to Customer Account Report
• MT900Confirmation of Debit
• MT910Confirmation of Credit
• pacs.008FI to FI Customer Credit Transfer
• pacs.009Financial Institution Credit Transfer
• pacs.004Payment Return

camt.054 questions

What is camt.054 used for?

To advise individual debits and credits on an account as they happen, for example an incoming client payment or a debit on a nostro account, and to give the details of batch bookings shown as one total on the statement.

What is the MT equivalent of camt.054?

The MT900 Confirmation of Debit and the MT910 Confirmation of Credit. One camt.054 can carry both debits and credits, and many entries.

What is the difference between camt.054 and camt.053?

camt.054 notifies single movements and has no balances. camt.053 is the end-of-day statement with opening and closing balances and every booked entry.

Does a camt.054 mean the money is booked?

Only when the entry status is BOOK. A camt.054 can also report pending (PDNG) or information-only (INFO) entries.

Which camt.054 version does CBPR+ use?

camt.054.001.08, with the Business Application Header.