| Field | Meaning | Required |
|---|---|---|
:20: | A unique reference assigned by the sending bank for this credit confirmation. It identifies the confirmation in both banks systems and lets operations teams tra | M |
:21: | The reference of the underlying instruction that caused the credit, such as the transaction reference of the original payment. It links the confirmation to the | M |
:25: | The account that was credited, identified by account number and sometimes by the account owner name. It tells the receiver exactly which account received the fu | M |
:32A: | The value date, ISO currency code and amount of the credit, for example 261106USD367574,90. The receiver compares it with its own expected credit to confirm rec | M |
:52a: | The institution that ordered the underlying transfer, when it differs from the sender of the MT910. It identifies the true originator of the credit instruction. | O |
:56a: | An intermediary bank in the chain that handled the funds before they reached the crediting bank. It identifies the previous bank in the settlement route. The re | O |
:72: | Additional information from sender to receiver, such as a narrative explaining the credit or a code for the credit type. It can carry the reason for the funds o | O |
:50a: | The customer who ordered the underlying payment, when the credit relates to a customer instruction. It gives the account and name of the originator. The receive | O |
:59a: | The beneficiary of the underlying payment, when the credit relates to a customer transfer. It gives the account and name of the recipient. The receiver uses it | O |
:71B: | Details of any charges deducted before the credit, with the charge type and amount in free text. It explains why the credited amount differs from the original i | O |
Banco Santander Madrid sends an MT910 to BNP Paribas Paris confirming a credit of USD 367,574.90 on 6 November 2026 to account 44098712, reference COV77812. The related reference matches the cover payment, the value date matches the settlement date, and BNP Paribas reconciles the credit against its expected nostro receipt.
Valid example from the message catalogue. Scheme rules: MT910 follows the SWIFT message rules for credit confirmations and remains in use for account reporting alongside camt.054 in ISO 20022 flows. No CBPR+ rule replaces it for customer reporting, because
MT910 Confirmation of Credit in Detail
What you will learn
Your objective. By the end of this lesson, you will be able to explain MT910 confirmation of credit. The MT910 Confirmation of Credit is sent by an account servicing bank to its account holder to advise that a specified amount has been credited to a specified account.
Why it matters. If the MT910 arrives but the statement line is missing, the operations team must raise a query with the bank the same day.
Chapter objective: Learner explains MT940 and MT950 statements, MT910 confirmations, and how opening, closing booked, closing available and forward balances are calculated. Learner uses real examples with amounts, banks and message names to show how the topic works in practice.
Key learning points
- MT910 Confirmation of Credit
- Single credit advice
- Field 50A or 50K
- Without Field 21 and Field 50K
- Bank may send an MT910 automatically
- Credit must still appear
Key terms
Reconciliation: The process of comparing records from two sources, such as a bank statement and an internal ledger, to confirm they agree.
Value date: The date on which funds become available to the beneficiary and on which interest starts to accrue. It is the date used for settlement and for nostro posting.
pacs.008: An ISO 20022 message for a financial institution to financial institution customer credit transfer. It replaces MT103 in cross border payments and carries structured debtor, creditor, charges and...
SWIFT MT message viewer showing MT910 Confirmation of Credit in Detail.
Practise this lesson
Exercise
Apply the concept in this lesson to a real banking scenario.
Use the definition, the example and the key points in this lesson.
- What to do. Explain the concept in your own words, give a banking example with an amount, and state what goes wrong if it is misunderstood.
Correct result. A correct answer names the concept accurately, uses a realistic banking example with a concrete amount, and identifies the consequence of getting it wrong.
Why. Understanding is not memorising a definition. It is being able to explain it, apply it, and spot the failure it prevents.
Check your understanding
Practice question
Which of the following best describes MT910 confirmation of credit?
Takeaway and next step
What to remember
If the MT910 arrives but the statement line is missing, the operations team must raise a query with the bank the same day.
Open the message type from this lesson and inspect its fields, then find the field that carries the amount.
Open the ISO 20022 Message Explorer →
Builds on "Why Reporting Messages Matter".
Transcript and full text
Show transcript
The MT910 Confirmation of Credit is sent by an account servicing bank to its account holder to advise that a specified amount has been credited to a specified account. The sender is the bank that holds the account, for example Barclays in London, and the receiver is the customer, for example a UK importer whose euro account has just received EUR 180,000 from a customer in France. The message is sent when the credit is posted, not when the payment instruction is received, so the receiver can rely on the funds being in the account. It is a single credit advice, not a statement of all activity. The MT910 carries a compact set of fields that identify the credit precisely. Field 20 gives the transaction reference number assigned by the sender. Field 21 gives the related reference, usually the reference of the original payment instruction, such as the MT103 reference that caused the credit. Field 25 gives the account number that was credited. Field 32A gives the value date, the currency and the amount credited, for example 4 November 2026, EUR 180,000. Field 50A or 50K gives the ordering customer, and Field 52A gives the ordering institution, so the receiver can see who sent the money. A typical MT910 might read as follows for a real trade receipt. Field 20 reads CREDIT 2026 1188. Field 21 reads pacs.008 REF FR 99214. Field 25 reads GB29 BARC 2030 0488 1234 56. Field 32A reads 4 November 2026, EUR 180,000. Field 50K reads Lefevre Textiles SA, Lyon, France, and Field 52A reads BNP Paribas, Paris. The London importer can now match EUR 180,000 to the Lefevre invoice for EUR 180,000, mark that invoice as paid, and release the goods held against it. Without Field 21 and Field 50K, the treasurer would have to guess which invoice the credit belongs to. The MT910 is used when a customer needs immediate confirmation of a single credit, rather than waiting for the end of day statement. A supplier who will only release goods on proof of payment may ask the buyer bank to send an MT910 as soon as the EUR 250,000 is credited. A treasury team managing a large acquisition may ask for MT910 advices on each incoming tranche, so it can track the funding build up during the day. A bank may also send an MT910 automatically for credits above a threshold, such as EUR 100,000, while smaller credits appear only on the statement. The arrangement is agreed in the account terms. The MT910 has a counterpart, the MT900 Confirmation of Debit, which advises that a specified amount has been debited from an account. Together the two messages give real time confirmation of single entries, while the MT940 and MT950 give the full statement picture. A treasurer should treat an MT910 as a notification, not as a substitute for reconciliation. The credit must still appear on the MT940 statement for the same value date, with the same amount and reference, and the reconciliation process must match the two records. If the MT910 arrives but the statement line is missing, the operations team must raise a query with the bank the same day.
The MT910 Confirmation of Credit is sent by an account servicing bank to its account holder to advise that a specified amount has been credited to a specified account. The sender is the bank that holds the account, for example Barclays in London, and the receiver is the customer, for example a UK importer whose euro account has just received EUR 180,000 from a customer in France. The message is sent when the credit is posted, not when the payment instruction is received, so the receiver can rely on the funds being in the account. It is a single credit advice, not a statement of all activity.
The MT910 carries a compact set of fields that identify the credit precisely. Field 20 gives the transaction reference number assigned by the sender. Field 21 gives the related reference, usually the reference of the original payment instruction, such as the MT103 reference that caused the credit. Field 25 gives the account number that was credited. Field 32A gives the value date, the currency and the amount credited, for example 4 November 2026, EUR 180,000. Field 50A or 50K gives the ordering customer, and Field 52A gives the ordering institution, so the receiver can see who sent the money.
A typical MT910 might read as follows for a real trade receipt. Field 20 reads CREDIT 2026 1188. Field 21 reads pacs.008 REF FR 99214. Field 25 reads GB29 BARC 2030 0488 1234 56. Field 32A reads 4 November 2026, EUR 180,000. Field 50K reads Lefevre Textiles SA, Lyon, France, and Field 52A reads BNP Paribas, Paris. The London importer can now match EUR 180,000 to the Lefevre invoice for EUR 180,000, mark that invoice as paid, and release the goods held against it. Without Field 21 and Field 50K, the treasurer would have to guess which invoice the credit belongs to.
The MT910 is used when a customer needs immediate confirmation of a single credit, rather than waiting for the end of day statement. A supplier who will only release goods on proof of payment may ask the buyer bank to send an MT910 as soon as the EUR 250,000 is credited. A treasury team managing a large acquisition may ask for MT910 advices on each incoming tranche, so it can track the funding build up during the day. A bank may also send an MT910 automatically for credits above a threshold, such as EUR 100,000, while smaller credits appear only on the statement. The arrangement is agreed in the account terms.
The MT910 has a counterpart, the MT900 Confirmation of Debit, which advises that a specified amount has been debited from an account. Together the two messages give real time confirmation of single entries, while the MT940 and MT950 give the full statement picture. A treasurer should treat an MT910 as a notification, not as a substitute for reconciliation. The credit must still appear on the MT940 statement for the same value date, with the same amount and reference, and the reconciliation process must match the two records. If the MT910 arrives but the statement line is missing, the operations team must raise a query with the bank the same day.
Full lesson text (all scenes)
Completing a lesson updates your progress dashboard on the homepage.
Scene timestamps are estimated by allocating the narration text proportionally across the real audio length. The audio playback position is the source of truth: pause freezes the visual, seeking restores the correct scene, replay restarts the scene animation.