Advises an account owner that a specific debit has been posted to its account. It is an entry confirmation, not a payment instruction and not proof that the ultimate beneficiary received funds.
DIRECTION: Sent by the account servicing institution to the account owner or an authorised recipient after the relevant debit is booked.
Version + profile: MT900 follows the applicable Standards MT release and service rules. This page is a curated field subset; bilateral practice and annual standards changes can alter permitted content and handling.
EVIDENCE AT ARM'S REACH
Start with the exact message version, then apply the scheme or network profile that governs your implementation.
An XSD checks XML structure. A usage guideline adds profile rules, conditional fields, code restrictions, and business controls. XSD-valid does not mean scheme-compliant.
The annual MT standard and release information. Full field specifications may require an authenticated Swift account.
A fictional single-entry debit advice. SYNTHETIC / TRAINING ONLY; illustrative unvalidated.
crc32:30dc40c8Initiation, serial and cover context, cancellation and correspondence, advices, and statements.
crc32:8b3a20e4Field correspondence, transformation treatment, and data-loss notes for Single debit advice compared with a structured bank-to-customer debit/credit notification.
crc32:96b16a98Curated field requirements, contexts, operational meaning, and implementation cautions.
crc32:cbc473d4Curated teaching subset. The complete Standards MT specification defines all field options, network rules, and party combinations.
| FIELD | NAME | PRESENCE | WHAT IT MEANS |
|---|---|---|---|
:20: | Transaction reference | MANDATORY | Reference assigned to this debit confirmation. |
:21: | Related reference | MANDATORY | Reference of the payment or instruction that produced the debit. |
:25: | Account identification | MANDATORY | Account that was debited. |
:32A: | Value date, currency, amount | MANDATORY | When the debit has value and for how much. |
:52a: | Ordering institution | OPTIONAL | Institution whose instruction produced the debit where relevant. |
:72: | Sender-to-receiver information | OPTIONAL | Additional bank-to-bank information about the entry. |
The whole MT900 laid out as a parent-child tree: every field in its nesting, with a sample value and what it means. Expand a branch to drill in. Values are fictional (SYNTHETIC / TRAINING ONLY); this is a curated practitioner view, not the full schema.
Block 1F01DEMOGB2LAXXX0000000000MandatoryBasic header — identifies the sender and the session (application id, service id, the sender's logical-terminal address built on its BIC, session and sequence numbers).Block 2I900DEMODEFFXXXXNMandatoryApplication header — the message type, the counterparty address, whether it is input or output, and the priority.Block 4—MandatoryText — the business content, as numbered :tag: fields. The only block whose shape changes by message type.:20:DEMO-MT900-001MandatoryReference assigned to this debit confirmation.:20:DEMO20260712:21:DEMO-MT103-001MandatoryReference of the payment or instruction that produced the debit.:25:DE02120300000000202051MandatoryAccount that was debited.:32A:260718EUR1250,00MandatoryWhen the debit has value and for how much.:32A:260712EUR1250,00:52A:DEMOGB2LXXXOptionalInstitution whose instruction produced the debit where relevant.:72:/ACC/DEMO CORPORATE PAYMENTOptionalAdditional bank-to-bank information about the entry.ISO 20022 Catalogue of messages ↗ — ISO 20022 Registration Authority · pain/pacs/camt message-definition elements
Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive.
Cross-Border Payments and Reporting Plus (CBPR+) usage guidelines ↗ — Swift (CBPR+ working group) · cross-border agent chain and structured-data usage
Full guidelines require MyStandards access. Public guidance states that after 14 November 2026 fully unstructured addresses are removed for in-scope CBPR+ traffic, with explicit message exceptions including admi.024, camt.025, camt.052, camt.053, camt.054 and camt.060.
Swift Standards MT (annual standards releases) ↗ — Swift · FIN block structure
Full field-level specifications live in the Swift Knowledge Centre User Handbook behind a swift.com login. Coexistence for in-scope FI-to-FI payment instructions ended on 22 November 2025, but treatment differs by MT: some instructions are NAKed and selected messages can enter temporary, chargeable contingency conversion. Reporting, initiation, investigations and correspondence follow separate roadmaps.
Payments Signal editorial teaching models — Payments Signal
What this simplifies: One-line plain-language descriptions of the commonly-populated elements — a practitioner view, not the authoritative ISO 20022 / MT schema, which defines many more optional elements.
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.
Swift Standards MT (annual standards releases) ↗ — Swift · Category 9 — MT900 Confirmation of Debit
Full field-level specifications live in the Swift Knowledge Centre User Handbook behind a swift.com login. Coexistence for in-scope FI-to-FI payment instructions ended on 22 November 2025, but treatment differs by MT: some instructions are NAKed and selected messages can enter temporary, chargeable contingency conversion. Reporting, initiation, investigations and correspondence follow separate roadmaps.
Payments Signal editorial teaching models — Payments Signal
What this simplifies: One account debit is shown; bilateral advice services vary.
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.
Share an operational observation or ask a concrete payments question. Your name and message are public; your email remains private.
Loading the discussion…