Category 7: Documentary credits, guarantees and standby letters of credit
MT707 Amendment to a Documentary Credit
Written and maintained by ZagTrader. Last reviewed . How this page is sourced and checked
The MT707 is the Swift message that amends a documentary credit (letter of credit) issued with an MT700. The issuing bank sends it to the advising bank, and an advising or transferring bank uses it to pass the amendment on to the next bank. Since the 2018 release it carries every changed term in its own field, and long text changes continue in the MT708.
- Message type
- MT707
- Category
- 7
- Structure
- 47 fields listed
- ISO 20022
- No direct equivalent
When MT707 is used
Letters of credit are amended all the time: shipment slips, so the latest shipment date and the expiry move; the buyer orders more, so the amount goes up; a document is added or dropped. The applicant asks the issuing bank, the issuing bank sends an MT707 to the advising bank, and the advising bank advises the amendment to the beneficiary. When the credit was passed on by an MT710 or transferred by an MT720, the bank in the middle sends its own MT707 to the next bank, quoting the issuing bank and its credit number.
Under UCP 600 article 10 an irrevocable credit can be amended or cancelled only with the agreement of the issuing bank, any confirming bank and the beneficiary. Until the beneficiary accepts, the original terms still apply to it, and accepting only part of an amendment counts as a rejection. Field 22A says what the sender is doing: ISSU when the issuing bank issues the amendment, ADVI when an advising bank passes it on, ACNF when it passes it on and adds its confirmation to the amendment. A cancellation is an amendment too: field 23S carries CANCEL.
The November 2018 release (SR2018) rebuilt the message. Before it, an MT707 had a handful of “new” fields and a 79 narrative that described everything else. Since then every term of the MT700 that can change has its own field in the MT707: applicable rules (40E), expiry (31D), applicant (50), beneficiary (59), tolerance (39A), availability (41a), drafts and payment terms (42C, 42a, 42M, 42P), shipment (43P to 44D), confirmation (49, 58a), reimbursing bank (53a) and so on. Only the fields that change are sent. Field 34B (new amount after amendment) and 79 were removed, and the long text fields became 45B, 46B, 47B, 49M and 49N, which carry the codes /ADD/, /DELETE/ and /REPALL/ to say how the text changes.
Field 23 carries the issuing bank’s credit number, mandatory since 2018, so that every bank in a chain can match the amendment to the credit even when field 20 and 21 hold other banks’ references. Field 26E numbers amendments from 1 to 999, and 31C repeats the original date of issue.
When the changes do not fit in one message, the rest of the 45B, 46B, 47B, 49M and 49N text goes in one or more MT708 messages, with field 27 numbering the series. The advising bank usually acknowledges the amendment with an MT730, and questions with no dedicated message go in an MT799.
MT707 format: sequences and fields
Message text (block 4)Mandatory
The MT707 has no sequences. Fields are listed in the order of the 2018 release layout, which is still current in SR 2025. Every field after 22A is optional, but at least one must be present. Fields marked C are optional but tied to a network rule.
| Tag | Name | Status | Format | Meaning |
|---|---|---|---|---|
| 27 | Sequence of Total | M | 1!n/1!n | Which message of the series this is. In the MT707 the first number is always 1; 1/1 means no MT708 follows. |
| 20 | Sender's Reference | M | 16x | The sender’s reference for this message. It must not start or end with a slash or contain two slashes in a row. |
| 21 | Receiver's Reference | M | 16x | The receiver’s reference for the credit, typically from its acknowledgement of the original credit. NONREF when it is not known. |
| 23 | Issuing Bank's Reference | M | 16x | The credit number given by the issuing bank, field 20 of the original MT700. Mandatory since 2018. |
| 52a | Issuing BankOptions A or D | C | A: [/1!a][/34x] 4!a2!a2!c[3!c] D: [/1!a][/34x] 4*35x | The issuing bank, when the sender passes on an amendment to a credit issued by another bank (ADVI or ACNF). Not together with 50B. |
| 50B | Non-Bank Issuer | C | 4*35x | The issuer of the credit when it is not a bank. Not together with 52a. |
| 31C | Date of Issue | M | 6!n | The date (YYMMDD) on which the credit was originally issued, as in the MT700. It does not change with each amendment. |
| 26E | Number of Amendment | M | 3n | The running number of this amendment, from 1 up to 999. |
| 30 | Date of Amendment | M | 6!n | The date (YYMMDD) on which the issuing bank considers the credit amended. |
| 22A | Purpose of Message | M | 4!c | ISSU (issuance of the amendment by the issuing bank), ADVI (advice of the amendment) or ACNF (advice of the amendment with confirmation added). |
| 23S | Cancellation Request | O | 6!a | CANCEL when the amendment asks for the credit to be cancelled. The cancellation needs the beneficiary’s agreement like any other amendment. |
| 40A | Form of Documentary Credit | O | 24x | A new form of credit, if it changes, for example from IRREVOCABLE to IRREVOCABLE TRANSFERABLE. |
| 40E | Applicable Rules | O | 30x[/35x] | New applicable rules, if they change, with the same codes as in the MT700 (UCP LATEST VERSION, UCPURR LATEST VERSION, EUCP LATEST VERSION, EUCPURR LATEST VERSION, ISP LATEST VERSION or OTHR). |
| 31D | Date and Place of Expiry | O | 6!n29x | The new expiry date and place for presenting documents, for example 270228LONDON. |
| 50 | Changed Applicant Details | O | 4*35x | New name or address of the applicant, if they change. |
| 59 | Beneficiary | O | [/34x] 4*35x | New beneficiary details, if they change. Before 2018 this field held the beneficiary before the amendment and was mandatory; now it is sent only for a change. |
| 32B | Increase of Documentary Credit Amount | C | 3!a15d | The amount by which the credit increases (not the new total). Not together with 33B. |
| 33B | Decrease of Documentary Credit Amount | C | 3!a15d | The amount by which the credit decreases (not the new total). Not together with 32B. |
| 39A | Percentage Credit Amount Tolerance | O | 2n/2n | New tolerance above and below the amount, in percent, for example 10/10. |
| 39C | Additional Amounts Covered | O | 4*35x | New additional amounts the beneficiary may claim, such as freight or insurance. |
| 41a | Available With ... By ...Options A or D | O | A: 4!a2!a2!c[3!c] 14x D: 4*35x 14x | A new nominated bank or availability, with the same codes as in the MT700 (BY PAYMENT, BY DEF PAYMENT, BY ACCEPTANCE, BY NEGOTIATION, BY MIXED PYMT). |
| 42C | Drafts at ... | O | 3*35x | New tenor of the drafts, if it changes. |
| 42a | DraweeOptions A or D | O | A: [/1!a][/34x] 4!a2!a2!c[3!c] D: [/1!a][/34x] 4*35x | New drawee of the drafts, if it changes. It must be a bank. |
| 42M | Mixed Payment Details | O | 4*35x | New mixed payment terms, if they change. |
| 42P | Negotiation/Deferred Payment Details | O | 4*35x | New deferred payment or negotiation terms, if they change. |
| 43P | Partial Shipments | O | 11x | New rule on partial shipments: ALLOWED, NOT ALLOWED or CONDITIONAL. |
| 43T | Transhipment | O | 11x | New rule on transhipment: ALLOWED, NOT ALLOWED or CONDITIONAL. |
| 44A | Place of Taking in Charge/Dispatch from .../Place of Receipt | O | 140z | New place of receipt or dispatch, if it changes. |
| 44E | Port of Loading/Airport of Departure | O | 140z | New port or airport of loading, if it changes. |
| 44F | Port of Discharge/Airport of Destination | O | 140z | New port or airport of discharge, if it changes. |
| 44B | Place of Final Destination/For Transportation to .../Place of Delivery | O | 140z | New final destination, if it changes. |
| 44C | Latest Date of Shipment | O | 6!n | New latest shipment date (YYMMDD). Usually moved together with the expiry date in 31D. |
| 44D | Shipment Period | O | 6*65x | New shipment period in words, if the credit uses a period instead of a latest date. |
| 45B | Description of Goods and/or Services | O | 100*65z | Changes to the goods description. Each change starts with a code: /ADD/ (text added), /DELETE/ (text removed) or /REPALL/ (the text that follows replaces the whole field as it stands after earlier amendments). |
| 46B | Documents Required | O | 100*65z | Changes to the documents required, with /ADD/, /DELETE/ or /REPALL/. The most common amendment after dates and amount. |
| 47B | Additional Conditions | O | 100*65z | Changes to the additional conditions, with /ADD/, /DELETE/ or /REPALL/. |
| 49M | Special Payment Conditions for Beneficiary | O | 100*65z | Changes to field 49G of the credit, with /ADD/, /DELETE/ or /REPALL/. |
| 49N | Special Payment Conditions for Receiving Bank | O | 100*65z | Changes to field 49H of the credit (conditions for the receiving bank only, not shown to the beneficiary), with /ADD/, /DELETE/ or /REPALL/. |
| 71D | Charges | O | 6*35z | New charges for the beneficiary’s account, in words or with codes such as /COMM/ or /TELECHAR/. |
| 71N | Amendment Charge Payable By | O | 4!c [6*35z] | Who pays the charges for this amendment: APPL (applicant), BENE (beneficiary) or OTHR (described on the next lines). |
| 48 | Period for Presentation in Days | O | 3n[/35x] | New presentation period in calendar days, for example 21, with text after the slash only when it counts from a date other than shipment. |
| 49 | Confirmation Instructions | O | 7!x | New confirmation instructions: CONFIRM, MAY ADD or WITHOUT. |
| 58a | Requested Confirmation PartyOptions A or D | O | A: [/1!a][/34x] 4!a2!a2!c[3!c] D: [/1!a][/34x] 4*35x | The bank asked to confirm, or allowed to confirm, if this changes. |
| 53a | Reimbursing BankOptions A or D | O | A: [/1!a][/34x] 4!a2!a2!c[3!c] D: [/1!a][/34x] 4*35x | A new reimbursing bank, if it changes. A new reimbursing bank also needs its own reimbursement authorisation (MT740) from the issuing bank. |
| 78 | Instructions to the Paying/Accepting/Negotiating Bank | O | 12*65x | New instructions for the nominated bank, if they change. |
| 57a | 'Advise Through' BankOptions 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 | The bank, other than the receiver, through which the amendment is to be advised to the beneficiary. |
| 72Z | Sender to Receiver Information | O | 6*35z | Bank-to-bank remarks, for example /PHONBEN/ (contact the beneficiary by phone) or /TELEBEN/ (advise the beneficiary by the fastest means). |
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
- At least one field must follow field 22A: an MT707 that only identifies the credit is rejected.
- Either 32B (increase) or 33B (decrease) may be present, not both. Both carry the change, never the new total: the new amount after amendment (old field 34B) was removed in 2018.
- Fields 52a and 50B identify the issuer of the credit; they are alternatives and may not both be present.
- Terms that the MT707 does not mention stay unchanged. Repeating unchanged terms makes the amendment harder to read and can be taken as a change.
- In 45B, 46B, 47B, 49M and 49N each change starts with /ADD/, /DELETE/ or /REPALL/. REPALL replaces the whole field text as it stands after all earlier amendments, so it should hold the complete new text.
- Information given in a field of the MT707 must not be repeated in an MT708, and nothing in an MT708 may conflict with the MT707.
- Keep the credit as amended consistent with the MT700 combination rules: 42C with 42a, or 42M alone, or 42P alone; and either a latest shipment date (44C) or a shipment period (44D), not both.
MT707 example
The pump shipment under credit ZTLC2610200001 (see the MT700 example) is delayed. Gulf Trading LLC asks ZagTrader Test Bank (ZAGTAEADXXX) to extend the latest shipment date to 15 January 2027 and the expiry to 28 February 2027, to increase the credit by USD 25,000.00 for 50 extra pumps, and to add a beneficiary’s certificate to the documents. The issuing bank sends amendment number 1 to the advising bank BANKGB2LXXX. The applicant pays the amendment charges.
{1:F01ZAGTAEADAXXX0000000000}{2:I707BANKGB2LXXXXN}{4:
:27:1/1
:20:ZTAM2611050001
:21:ADVLC26001234
:23:ZTLC2610200001
:31C:261020
:26E:1
:30:261105
:22A:ISSU
:31D:270228LONDON
:32B:USD25000,00
:44C:270115
:45B:/ADD/+50 ADDITIONAL INDUSTRIAL PUMPS MODEL ZP-200 AS PER
PROFORMA INVOICE PI-2026-131 DATED 02 NOV 2026
:46B:/ADD/+BENEFICIARY CERTIFICATE STATING THAT ONE SET OF
NON-NEGOTIABLE DOCUMENTS HAS BEEN SENT TO THE APPLICANT BY
COURIER WITHIN 5 DAYS AFTER SHIPMENT
:71N:APPL
:72Z:/PHONBEN/
-}Decode this example in the parserLine by line
| Line | What it says |
|---|---|
| {1:F01ZAGTAEADAXXX0000000000}{2:I707BANKGB2LXXXXN}{4: | Sender ZAGTAEADXXX (the issuing bank), input MT707 to BANKGB2LXXX (the advising bank). |
| :27:1/1 | No MT708 follows. |
| :20:ZTAM2611050001 | The issuing bank’s reference for this amendment message. |
| :21:ADVLC26001234 | The advising bank’s reference for the credit, from its MT730 acknowledgement. |
| :23:ZTLC2610200001 | The credit number from field 20 of the MT700. |
| :31C:261020 | Original date of issue, unchanged. |
| :26E:1 | First amendment. |
| :30:261105 | Amended on 5 November 2026. |
| :22A:ISSU | The issuing bank issues the amendment. |
| :31D:270228LONDON | New expiry date and place. |
| :32B:USD25000,00 | Increase by USD 25,000.00. The new amount (USD 275,000.00) is not sent. |
| :44C:270115 | New latest shipment date. |
| :45B:/ADD/+50 ADDITIONAL INDUSTRIAL PUMPS MODEL ZP-200 AS PER | Added to the goods description. |
| PROFORMA INVOICE PI-2026-131 DATED 02 NOV 2026 | |
| :46B:/ADD/+BENEFICIARY CERTIFICATE STATING THAT ONE SET OF | A new document added to the documents required. |
| NON-NEGOTIABLE DOCUMENTS HAS BEEN SENT TO THE APPLICANT BY | |
| COURIER WITHIN 5 DAYS AFTER SHIPMENT | |
| :71N:APPL | Amendment charges are for the applicant. |
| :72Z:/PHONBEN/ | Please contact the beneficiary by phone. |
| -} | End of block 4. |
The BICs, names and references are made up.
Everything not mentioned (amount tolerance, ports, presentation period, confirmation and so on) stays as in the original MT700. Because BANKGB2LXXX confirmed the credit, it must decide whether to extend its confirmation to the amendment and tell the beneficiary.
The beneficiary can accept or reject the amendment as a whole. Until it does, the original credit terms still apply to it.
Common errors and rejects
Both 32B and 33B present, or the new total sent
An amendment either increases or decreases the amount, and the field holds the difference. Sending the new total in 32B (for example USD275000,00 for an increase of 25,000) silently overstates the credit at the advising bank.
Nothing after 22A
An MT707 that identifies the credit but carries no changed field fails validation. Every amendment, including a cancellation request with 23S, must carry at least one field after 22A.
Text changes without ADD, DELETE or REPALL
A 46B that just lists the documents again, without a code, is unclear: is it added, replacing, or a restatement? Start each change with /ADD/, /DELETE/ or /REPALL/, and use REPALL only with the complete new text.
Pre-2018 template still in use
Fields 31E (new date of expiry), 34B (new amount), 39B and 79 no longer exist, and 23, 26E, 30 and 31C are mandatory. Templates built before November 2018 that still produce them are rejected; update the template rather than each message.
Issuing bank and non-bank issuer both given
52a and 50B are alternatives. An advising bank passing on an amendment names the issuing bank in 52a, or the non-bank issuer in 50B, never both.
Amount format in 32B or 33B
The amount needs a comma as the decimal mark and no thousands separators:
How to fix itUSD25000,00, notUSD25,000.00.
ISO 20022
There is no ISO 20022 replacement for the MT707 in use on the Swift network. Documentary credit messages in category 7 were not part of the November 2025 move of payment instructions to ISO 20022 and are still exchanged in MT format.
Swift’s MT and MX equivalence table (May 2024) gives no ISO 20022 equivalent for the MT707, nor for any other documentary credit message. The ISO 20022 trade services set covers guarantees and standbys (the MT767 maps to tsrv.005), not commercial documentary credits. Payments made under the credit, however, travel as ISO 20022 payment messages such as pacs.009.
MT707 questions
- What is an MT707?
- It is the Swift message used to amend a documentary credit (letter of credit). The issuing bank sends it to the advising bank, which advises the change to the beneficiary. It can change any term of the credit, or request its cancellation.
- What is the difference between MT700 and MT707?
- The MT700 issues the credit with all its terms. The MT707 changes some of those terms later and carries only the fields that change, together with the credit number (23), the amendment number (26E) and the amendment date (30).
- What is an MT708?
- The MT708 is the continuation of an MT707. When the changes to the goods, documents, conditions or special payment conditions are too long for one message, the rest goes in one or more MT708 with the same references.
- How do you cancel a letter of credit by Swift?
- The issuing bank sends an MT707 with
:23S:CANCEL. Under UCP 600 the cancellation of an irrevocable credit needs the agreement of the beneficiary and of any confirming bank, so it takes effect only once they consent. - What do ADD, DELETE and REPALL mean in field 46B?
- They say how the text changes. /ADD/ adds the text that follows, /DELETE/ removes it, and /REPALL/ replaces the whole field, as amended so far, with the text that follows. The same codes are used in 45B, 47B, 49M and 49N.
- Does the beneficiary have to accept an MT707 amendment?
- Yes, for it to bind the beneficiary. Under UCP 600 article 10 the beneficiary stays bound by the original terms until it accepts the amendment, and partial acceptance counts as rejection. Presenting documents that comply with the amended credit is treated as acceptance.
All MT messages · Category 7 messages · ISO 20022 messages · Codes · Troubleshooting