Category 7: Documentary credits, guarantees and standby letters of credit
MT756 Advice of Reimbursement or Payment
Written and maintained by ZagTrader. Last reviewed . How this page is sourced and checked
The MT756 is the Swift message an issuing bank sends to the bank that sent it documents, or a reimbursing bank sends to the bank that claimed from it, to advise that a drawing under a documentary credit has been reimbursed or paid. It states the amount claimed, the amount actually paid with its value date, and the route of the funds. It is used where the credit gave no specific reimbursement instructions or payment provisions.
- Message type
- MT756
- Category
- 7
- Structure
- 8 fields listed
- ISO 20022
- No direct equivalent
When MT756 is used
A drawing under a documentary credit ends with money moving to the bank that paid, accepted or negotiated. How it gets there depends on the credit. If the MT700 named a reimbursing bank in field 53a, the nominated bank claims from that bank with an MT742 under the reimbursement authorisation the issuing bank gave in an MT740, usually under the ICC rules for bank-to-bank reimbursements (URR 725). If the credit gave no specific reimbursement instructions, the nominated bank sends the documents and its claim to the issuing bank, typically with an MT754, and waits to be paid.
The MT756 is the paying side’s advice that the money has been, or will be, sent. Three senders are possible: the issuing bank, to the bank from which it received documents; a reimbursing bank, to the bank from which it received a reimbursement claim; or a nominated bank, to a bank that presented documents to it.
Field 32B repeats the amount claimed and field 33A gives the amount actually reimbursed or paid, with its value date. When the two differ, for example because the payer deducted charges, the difference must be explained in field 72Z. Fields 53a and 54a describe the route of the funds. Without them the single direct account relationship between the two banks in the currency of the credit is used.
For the presenting bank the MT756 is a reconciliation message: it closes the drawing on its books and lets the bank credit the beneficiary if it has not done so already. The funds themselves arrive by a separate bank-to-bank payment, or by a credit to an account the receiver services. The MT756 does not move money on its own.
MT756 format: sequences and fields
Message text (block 4)Mandatory
The MT756 has no sequences: block 4 is one list of fields in the order of the SR 2025 structure. Older templates use field 72 (x character set) and have no 79Z.
| Tag | Name | Status | Format | Meaning |
|---|---|---|---|---|
| 20 | Sender's Reference | M | 16x | When the issuing bank or a nominated bank sends the message: the documentary credit number assigned by the issuing bank. When a reimbursing bank sends it: its own reference. It must not start or end with a slash or contain two slashes in a row. |
| 21 | Presenting Bank's Reference | M | 16x | The reference of the bank that presented the documents or the claim. When a reimbursing bank answers an MT742, this is field 20 of that MT742 (the claiming bank’s reference) or an equivalent reference. |
| 32B | Total Amount Claimed | M | 3!a15d | The currency and total amount the receiver claimed, for example field 34a of its MT754 or field 34a of its MT742. |
| 33A | Amount Reimbursed or Paid | M | 6!n3!a15d | The value date (YYMMDD), currency and net amount reimbursed or paid. If it differs from 32B, the difference must be explained in 72Z. |
| 53a | Sender's CorrespondentOptions A, B or D | O | A: [/1!a][/34x] 4!a2!a2!c[3!c] B: [/1!a][/34x] [35x] D: [/1!a][/34x] 4*35x | Where required, the account or branch of the sender, or another bank, through which the sender reimburses the receiver. |
| 54a | Receiver's CorrespondentOptions A, B or D | O | A: [/1!a][/34x] 4!a2!a2!c[3!c] B: [/1!a][/34x] [35x] D: [/1!a][/34x] 4*35x | Where required, the branch of the receiver or another bank at which the funds are made available to the receiver. |
| 72Z | Sender to Receiver Information | O | 6*35z | Extra information for the receiver, in particular the explanation of any difference between 32B and 33A. The code RCB may be used only when both 53a and 54a are present. |
| 79Z | Narrative | O | 35*50z | Longer free text about the reimbursement or payment. |
Format notation: n digits, a upper-case letters, c upper-case letters and digits, x any character of the Swift character set, d a decimal number with a comma, ! fixed length, [ ] optional, 4*35x up to 4 lines of 35 characters. M mandatory, O optional, C conditional (a rule decides).
Rules worth knowing
- The currency in 32B and 33A must be the same (error C02).
- Any difference between the amount claimed in 32B and the amount paid in 33A must be explained in 72Z.
- Without 53a and 54a, the single direct account relationship between sender and receiver in the currency of the credit is used. The code RCB in 72Z may be used only when both 53a and 54a are present.
- Fields 20 and 21 must not start or end with a slash and must not contain two consecutive slashes (error T26).
- The MT756 is an advice. The funds move separately, as a bank-to-bank payment or an account entry.
MT756 example
ZagTrader Test Bank, Dubai (ZAGTAEADXXX) issued credit ZTLC2609150007 for USD 120,000.00, available at BANKGB2LXXX in London, with no reimbursing bank named. BANKGB2LXXX paid the beneficiary against complying documents under its reference BGLX2610140031 and claimed USD 120,000.00 with an MT754. On 22 October 2026 the issuing bank pays through its New York branch ZAGTUS33XXX to BANKGB2LXXX’s correspondent BANKUS33XXX, net of its USD 150.00 payment commission, and sends this MT756.
{1:F01ZAGTAEADAXXX0000000000}{2:I756BANKGB2LXXXXN}{4:
:20:ZTLC2609150007
:21:BGLX2610140031
:32B:USD120000,00
:33A:261022USD119850,00
:53A:ZAGTUS33XXX
:54A:BANKUS33XXX
:72Z:DIFFERENCE OF USD150,00 IS OUR
PAYMENT COMMISSION PER CREDIT
-}Decode this example in the parserLine by line
| Line | What it says |
|---|---|
| {1:F01ZAGTAEADAXXX0000000000}{2:I756BANKGB2LXXXXN}{4: | Sender ZAGTAEADXXX (issuing bank), receiver BANKGB2LXXX (the bank that sent the documents). |
| :20:ZTLC2609150007 | Sent by the issuing bank, so the credit number. |
| :21:BGLX2610140031 | The presenting bank’s reference from its MT754. |
| :32B:USD120000,00 | Amount claimed. |
| :33A:261022USD119850,00 | Paid on 22 October 2026, net of charges. |
| :53A:ZAGTUS33XXX | The sender pays through its New York branch... |
| :54A:BANKUS33XXX | ...to the receiver’s correspondent in New York. |
| :72Z:DIFFERENCE OF USD150,00 IS OUR | Required explanation of the difference between 32B and 33A. |
| PAYMENT COMMISSION PER CREDIT | |
| -} | End of block 4. |
The BICs, names and references are made up.
The USD transfer from ZAGTUS33XXX to BANKUS33XXX travels separately, as a bank-to-bank payment (pacs.009 on Swift today).
Common errors and rejects
Different currencies in 32B and 33A (C02)
The amount paid must be in the currency of the claim. If the payer converts, it pays in the claim currency and explains the conversion in 72Z.
Unexplained difference between 32B and 33A
Not a network reject, but a breach of the usage rule and the main source of follow-up queries: the presenting bank cannot close the drawing until it knows why it received less. Put the reason in 72Z.
Wrong reference in field 21
A reimbursing bank must quote the claiming bank’s reference from field 20 of the MT742, not its own file number or the credit number, or the claiming bank cannot match the payment.
RCB used without both correspondents
The code RCB in 72Z names the receiver’s correspondent bank when there is an intermediary. It is allowed only when 53a and 54a are both present.
Amount or date format
33A is date, currency and amount with no separators:
How to fix it261022USD119850,00. A dot as decimal mark or a four-digit year fails validation.
ISO 20022
There is no ISO 20022 equivalent of the MT756: Swift’s MT and MX equivalence tables (May 2024 edition) list none for it. Category 7 trade finance messages were not part of the November 2025 end of MT/MX coexistence, which covered cross-border payment instructions.
The payment the MT756 announces is a different matter: a bank-to-bank transfer on Swift is now a pacs.009 rather than an MT202, and an MT202 still sent is converted by Swift contingency processing, charged since 1 January 2026. Reconciliation teams therefore match MT756 advices against ISO 20022 payments and statements.
MT756 questions
- What is an MT756?
- It is the Advice of Reimbursement or Payment: the issuing bank, a reimbursing bank or a nominated bank tells the bank that presented documents or a claim that the drawing has been reimbursed or paid, for how much and with what value date.
- What is the difference between MT754 and MT756?
- The MT754 goes from the bank that paid, accepted or negotiated to the issuing bank, saying documents complied and claiming the money. The MT756 goes the other way and says the money has been paid.
- Who sends an MT756 when there is a reimbursing bank?
- The reimbursing bank may send it to the claiming bank after honouring an MT742 reimbursement claim. Field 21 then carries the claiming bank’s reference from the MT742.
- Why is the amount in 33A lower than 32B?
- Usually because the payer deducted charges. The reason must be given in field 72Z.
- Does the MT756 transfer the money?
- No. It advises the payment. The funds move by a separate bank-to-bank payment or an account entry, according to fields 53a and 54a or the direct account relationship.
All MT messages · Category 7 messages · ISO 20022 messages · Codes · Troubleshooting