MT910 — Confirmation of Credit

The credit ticket: the account-servicing bank confirms to its customer (bank or corporate) that an amount has been credited, with value date, ordering party when available, and originating reference. Exact counterpart of MT900.

Purpose

MT910 confirms a one-off credit on an account held by the sending bank for its customer. The customer can be:

• another bank (nostro / vostro correspondent);
• a corporate, particularly a treasury team with a direct account with the bank;
• a broker, asset manager, fund.

MT910 enables immediate recognition of an incoming settlement: the receiving treasury can post entries, feed reconciliation systems, trigger downstream actions (release stock for a paid supplier, finalise a trade). That is why MT910 is one of the most SLA-monitored flows on the corporate side.

Block 4 structure

:20:    Transaction Reference Number               (mandatory)
:21:    Related Reference                          (mandatory)
:25:    Account Identification                     (mandatory)
:32A:   Value Date, Currency, Amount               (mandatory)
:50a:   Ordering Customer                          (optional — option A, F or K)
:52a:   Ordering Institution                       (optional — option A or D)
:56a:   Intermediary                               (optional)
:72:    Sender to Receiver Information             (optional)

Tags in detail

• :20:: reference of the MT910 ticket itself.
• :21:: reference of the originating flow (the :20: of the received MT103 or MT202).
• :25:: credited account.
• :32A:: value date + ISO 4217 + amount.
• :50a:: ordering customer when known and distinct from the ordering institution (50A = BIC of another bank, 50F = structured identifier, 50K = account + name + address).
• :52a:: ordering institution. More frequent than :50a:: the other bank that initiated the send.
• :56a:: any intermediary bank.
• :72:: free information — often the business purpose for the corporate recipient.

Real-world example

BNP Paribas confirms to ACME SARL that account FR7630… has been credited 8,750.50 EUR on 14 May 2026, originating from Hans Mueller GmbH (account DE89… at Deutsche Bank), linked to originating MT103 REF20260515009:

{1:F01BNPAFRPPAXXX0000000000}{2:I910ACMECORPXXXXN}{3:{121:9e8d7c6b-5a4f-3e2d-1c0b-9a8b7c6d5e4f}}{4:
:20:CRD20260514001
:21:REF20260515009
:25:FR7630006000011234567890189
:32A:260514EUR8750,50
:50K:/DE89370400440532013000
HANS MUELLER GMBH
HAUPTSTRASSE 12
60313 FRANKFURT
:52A:DEUTDEFFXXX
:72:/BNF/INVOICE 2026-202 REIMBURSEMENT
-}{5:{CHK:1234567890AB}}

• :20:CRD20260514001 — credit ticket reference.
• :21:REF20260515009 — reference of the MT103 that generated the credit.
• :25:FR76… — credited account (ACME IBAN).
• :32A:260514EUR8750,50 — credit 14 May 2026, 8,750.50 EUR.
• :50K: — ordering customer (Hans Mueller GmbH) with IBAN and address.
• :52A:DEUTDEFFXXX — ordering bank (Deutsche Bank).
• :72:/BNF/… — business purpose (invoice 2026-202 reimbursement).

Common errors

• :50a: absent when it should be present: when the ordering customer is known (standard case for an incoming client MT103), it must be carried for corporate reconciliation. Omitting it forces treasury to wait for the MT940 to identify the payer.
• :21: = last bank's reference instead of originating reference: an intermediary bank may "rewrite" :21: with its own reference. This violates the data carry-over principle: :21: must be the :20: of the originating client flow.
• Latency > 30 min: a bank that does not send MT910 within minutes of the credit defeats the message's value in corporate cash management.
• :32A: currency ≠ account currency: often seen with FX conversion. MT910 carries the currency actually credited. The conversion must be documented in :72: or via a separate MT199.
• Unescaped reserved characters in :50K:: the ordering party's name and address sit in a pipe-delimited block within the tag. A ^ or | in the company name breaks parsing.
• Character set x: same as MT103.

MX equivalent — camt.054

Same as MT900: camt.054.001.08 with Ntry/CdtDbtInd = CRDT. MT910 specifics vs MT900:

Related messages

• MT900 — Confirmation of Debit (debit counterpart).
• MT940 — Customer Statement (EOD, contains the day's MT900/MT910).
• MT942 — Interim Transaction Report (intraday statement).
• MT103 / MT202 — flows that typically generate the credit.
• camt.054 — ISO 20022 equivalent.