MT910 — Confirmation of Credit
Confirms to an account owner that its account with the sender has been credited. It is an advice for a single credit — typically an incoming cover payment or another expected receipt — sent close to the event, not a periodic statement.
DIRECTION: Sent by the account-servicing institution (for example, a nostro correspondent) to the account owner or to a party the owner has authorised to receive it.
WHO IS INVOLVED
- Account-servicing institutionCredits the account it services and sends the confirmation.
- Account ownerTypically a bank maintaining a nostro mirror: it uses the advice to update expected funds and release payments waiting on the credit.
KEY FIELDS
Curated subset of the fields practitioners meet first — the official SWIFT Standards MT documentation is the complete specification.
| FIELD | NAME | PRESENCE | WHAT IT MEANS |
|---|---|---|---|
:20: | Transaction Reference Number | MANDATORYSWIFT Standards MT | The sender's unique reference for this confirmation.References the advice itself, not the payment that caused the credit — that link lives in field 21. |
:21: | Related Reference | MANDATORYSWIFT Standards MT | The reference of the transaction that produced the credit, as known to the sender.This is what the account owner's reconciliation matches against expected receipts. Its usefulness depends entirely on what reference the crediting transaction carried.⚠ If the underlying payment's reference was lost or replaced along the chain, the advice arrives but nothing matches. |
:25a: | Account Identification | MANDATORYSWIFT Standards MT | Which account, held with the sender, was credited.Option P adds the account owner's BIC alongside the account number for disambiguation. |
:13D: | Date/Time Indication | OPTIONALSWIFT Standards MT | When the credit was applied, with a timezone offset.Valuable for intraday liquidity monitoring — without it the advice only tells you the value date, not when the funds actually became available. |
:32A: | Value Date / Currency / Amount | MANDATORYSWIFT Standards MT | The value date, currency, and amount of the credit.The amount is the credit as booked by the account servicer — after any of its charges — which is what reconciliation must match, not the amount the counterparty originally sent. |
:50a: | Ordering Customer | CONDITIONALSWIFT Standards MT | The customer that originated the transaction which led to this credit, when there was one.The standard requires ordering-party information on the advice — in practice at least one of 50a or 52a appears; the exact conditional rules are in the SWIFT Standards MT reference.⚠ Sparse ordering-party data makes it hard to connect the credit to a business event without opening a query. |
:52a: | Ordering Institution | CONDITIONALSWIFT Standards MT | The bank that ordered the transaction which produced the credit.For bank-to-bank receipts (for example, an incoming MT202) this is usually the party shown; for customer payments 50a carries the originator instead. |
:56a: | Intermediary | OPTIONALSWIFT Standards MT | A bank the funds passed through on their way to the account servicer.Useful when tracing where a payment's references or charges changed en route. |
COMMON ERRORS
- Treating credit advices as a substitute for the statement.Consequence: Double counting when both the MT910 and the MT940 entry are booked, or gaps when an advice never came for a given credit.Avoid it: Reconcile advices and statement lines as two views of the same event, with the statement as the authoritative record.
- Processing a duplicate advice as a second credit.Consequence: Expected-funds positions overstate liquidity; payments may be released against money that arrived only once.Avoid it: Deduplicate on sender, account, amount, value date, and related reference before updating positions.
- Assuming every correspondent sends MT910s for every credit.Consequence: Monitoring built on advices silently misses receipts from correspondents that only send statements.Avoid it: Document per correspondent which advices are contracted, and fall back to intraday or end-of-day statement processing where they are not.
USAGE CONTEXTS
- Cover receipt confirmationIn the cover method, the beneficiary bank often waits for the MT910 on its nostro before crediting the customer payment announced by the MT103 — the advice is the trigger that releases the funds.
- Intraday liquidity and expected fundsCredit advices feed expected-versus-actual position monitoring during the day, ahead of the end-of-day statement. Whether a correspondent sends MT910s at all, and for which credits, is a service-level agreement, so coverage varies by relationship.
- ISO 20022 equivalentsThe camt.054 credit notification is the ISO 20022 counterpart. Category 9 messages remained usable on the FIN network after the November 2025 retirement of cross-border MT payment instructions, and migration to camt reporting is proceeding on institution-specific timelines.
SEE IT IN A PLAYABLE FLOW
Sources for this reference2
- Official requirement
Swift Standards MT (annual standards releases) ↗ — Swift · Category 9 — MT 910
Full field-level specifications live in the Swift Knowledge Centre User Handbook behind a swift.com login; content here relies on public summaries. Swift ended MT-to-ISO 20022 coexistence for in-scope cross-border payment instructions (for example MT103 and MT202) in November 2025; MT statement messages are being phased out on a separate timeline.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
What this simplifies: Field list curated for learning; national and bilateral usage rules omitted.
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.