MT700
MT700
MT700
31 August 2007
Copyright
Copyright © S.W.I.F.T. SCRL ("SWIFT"), Avenue Adèle 1, B-1310 La Hulpe, Belgium, or its licensors, 2007.
All rights reserved. You may copy this publication within your organisation. Any such copy must include these legal notices.
Confidentiality
This publication may contain SWIFT or third-party confidential information. Do not disclose this publication outside your
organisation without the prior written consent of SWIFT.
Disclaimer
The information in this publication may change from time to time. You must always refer to the latest available version.
SWIFTStandards are licensed subject to the terms and conditions of the SWIFTStandards IPR Policy - End-User License
Agreement available at www.swift.com > Standards > More information.
Translations
SWIFT, S.W.I.F.T., the SWIFT logo, Sibos, SWIFTNet, SWIFTAlliance, SWIFTStandards, SWIFTReady, and Accord are
trademarks of S.W.I.F.T. SCRL. Other SWIFT-derived service and product names, including SWIFTSolutions,
SWIFTWatch, and SWIFTSupport are tradenames of S.W.I.F.T. SCRL.
Other product or company names in this publication are tradenames, trademarks, or registered trademarks of their respective
owners.
31 August 2007
Table of Contents
Table of Contents
Introduction ........................................................................................................................... 1
Documentary Credit Message Types..................................................................................... 6
MT 791 Request for Payment of Charges, Interest and Other Expenses .......................... 236
Introduction
Overview
Category 7 supports messages which are exchanged between banks involved in the documentary credit and
guarantee business.
Applying the principles of the ICC UCP, the rules and basic text of these message types are given in English.
Users are however, free to use any language they choose for individual credits and parts thereof.
When sending messages in this category, the following general rules apply:
• the cancellation of a documentary credit, an authorisation to reimburse, or a guarantee, take the form of an
amendment. An MT 792 Request for Cancellation must therefore not be used, but rather an MT 707
Amendment to a Documentary Credit, MT 747 Amendment to an Authorisation to Reimburse, or MT 767
Guarantee Amendment, respectively.
Note: The examples used in this category do not always use the total number of characters available for a
SWIFT message or specific field. In some cases, multiple messages are shown, eg, MT 700/701, to
demonstrate the use of these messages/fields when the maximum input message length/field length is
exceeded.
Changes
This volume incorporates the following change to Category 7 - Documentary Credits and Guarantees as noted
in the Standards Release Guide (SRG) 2007:
• amendment to the usage guidelines to deal with new ICC market practice rules for documentary credits
(UCP 600)
• some editorial enhancements throughout the document
IMPORTANT
This volume contains information effective as of the October 2007 Standards Release. Therefore the
September 2006 edition of the User Handbook Standards volumes remains effective until October 2007.
31 August 2007 1
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
N
Status Tag Field Name Content/Options
o.
-----|
M = Mandatory O = Optional
• MT nnn (Message Type Name) provides the message type number and name
• Status indicates if the field is
- M - Mandatory
- O - Optional
The status M for fields in optional (sub)sequences means that the field must be present if the
(sub)sequence is present and is otherwise not allowed.
• Tag is the field identification.
• Field Name is the detailed name of the field tag, for this message type.
• Content/Options provides permitted field length and characteristics. For information concerning field
structure, notation and character restrictions, please see SWIFTStandards MT General Information.
• No. identifies the number of the field in the Field Specifications for the message type.
Some messages are separated into sequences of fields, as shown above. An arrow indicates that a sequence of
fields may be repeated.
MT Usage Rules
Usage rules are not validated on the network, ie, rules for which no error code is defined, but are nevertheless
mandatory for the correct usage of the message. Rules specified in this section affect more than one field in the
message, or more than one SWIFT message.
MT Guidelines
Guidelines are not validated on the network and are not mandatory for the correct usage of the message. They
concern good practices. Guidelines specified in this section affect more than one field in the message, or more
than one SWIFT message.
MT Field Specifications
The rules for the use of each field in the message are specified in this section. Each field is identified by its
index number (as shown in the No. column of the MT Format Specifications), field tag and detailed field
name, followed by a description of the field, which may contain some or all of the following:
• FORMAT specifies the field formats which are allowed for the field.
• PRESENCE indicates if the field is mandatory, optional or conditional in its sequence.
• DEFINITION specifies the definition of the field in the message type.
• CODES lists all codes available for use in the field. If there is more than one subfield for which codes are
defined, each separate code list will be identified with a CODES heading. When a list of codes is validated
by the network, the error code will be specified.
• NETWORK VALIDATED RULES specifies rules that are validated on the network, ie, rules for which an
error code is defined. Generally, rules specified in this section affect only the field in which they appear. In
some cases, rules which are validated at the message level, ie, rules which affect more than one field, are
repeated in this section. This is the case when the rule does not affect the presence of the field, but
information within several fields, eg, a currency which must be the same for more than one field in the
message.
• USAGE RULES specifies rules that are not validated on the network, ie, rules for which no error code is
defined, but are nevertheless mandatory for the correct usage of the field. Rules specified in this section
affect only the field in which they appear.
• EXAMPLES provides one or more examples of the field as it will be formatted/used.
MT Mapping
MT mapping provides an explanation of how to map the fields of the message into another SWIFT message,
either of the same or a different message type.
MT Examples
Examples are provided to illustrate the correct use of a message. Examples always include the following
information:
• Narrative provides a brief description of a transaction
• Information Flow illustrates the relationships between the parties involved in the message. An
explanation of the flow diagram can be found in SWIFTStandards MT General Information.
• SWIFT Format provides the message using the defined SWIFT format, and providing an explanation,
where necessary, of the fields which have been used.
31 August 2007 3
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
The following table lists all Documentary Credit message types defined in Category 7.
For each message type, there is a short description, an indicator whether the message type requires
authentication (Y or N), the maximum message length for input (2,000 or 10,000 characters) and whether the
use of the message requires registration with SWIFT for use in a message user group (Y or N).
710 Advice of a Third Advises the Receiver of the terms and Y 10,000 N
Bank's Documentary conditions of a documentary credit
Credit
Note: A Message User Group (MUG), for the purposes of this book, is a group of users who have voluntarily
agreed to support the specified message type and have registered with SWIFT to send or receive the
specified message type. These messages are indicated in the preceding table in the column MUG.
Registration is free of charge. To register to use one or more message types, submit a registration request
(Register to a Message User Group) through www.swift.com. To withdraw from a MUG, use the
Deregister from a Message User Group request.
These forms are available on www.swift.com > Ordering & Support > Ordering.
To get the list of other members of a particular MUG, send an MT 999 to the Customer Implementation
team (SWHQBEBBCOS).
31 August 2007 7
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
MT 700 Scope
This message is sent by the issuing bank to the advising bank.
It is used to indicate the terms and conditions of a documentary credit which has been originated by the Sender
(issuing bank).
M 50 Applicant 4*35x 9
M 59 Beneficiary [/34x] 10
4*35x
O 42a Drawee A or D 17
M = Mandatory, O = Optional
31 August 2007 9
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
• The advising bank must advise a documentary credit, including all its details, in a way that is clear and
unambiguous to the beneficiary.
PRESENCE
Mandatory
DEFINITION
This field specifies the number of this message in the series of messages sent for a documentary credit, and the
total number of messages in the series.
PRESENCE
Mandatory
DEFINITION
This field specifies the type of credit.
CODES
One of the following codes must be used (Error code(s): T60):
USAGE RULES
Details of any special conditions applying to the transferability of the credit and/or the bank authorised to
transfer the credit in a freely negotiable credit should be included in field 47A Additional Conditions.
PRESENCE
Mandatory
DEFINITION
This field specifies the documentary credit number which has been assigned by the Sender.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
PRESENCE
Optional
DEFINITION
This field specifies if the documentary credit has been pre-advised.
USAGE RULES
This field must contain the code PREADV followed by a slash '/' and a reference to the pre-advice, eg, by date.
PRESENCE
Optional
DEFINITION
This field specifies the date on which the issuing bank (Sender) considers the documentary credit as being
issued.
NETWORK VALIDATED RULES
Date must contain a valid date expressed as YYMMDD (Error code(s): T50).
USAGE RULES
The absence of this field implies that the date of issue is the date this message is sent.
PRESENCE
Mandatory
DEFINITION
This field specifies the rules the credit is subject to.
CODES
One of the following codes must be used (Error code(s): T59)
31 August 2007 11
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
EUCP LATEST VERSION The credit is subject to the version of the Supplement of the ICC
Uniform Customs and Practice for Documentary Credits for
Electronic Presentations, International Chamber of Commerce, Paris,
France, which is in effect on the date of issue.
EUCPURR LATEST VERSION The credit is subject to the version of the Supplement of the ICC
Uniform Customs and Practice for Documentary Credits for
Electronic Presentations, International Chamber of Commerce, Paris,
France, which is in effect on the date of issue. The reimbursement is
subject to the version of the Uniform Rules for Bank-to-Bank
Reimbursements, International Chamber of Commerce, Paris, France,
which is in effect on the date of issue.
ISP LATEST VERSION The standby letter of credit is subject to the version of the ICC
International Standby Practices, International Chamber of Commerce,
Paris, France, which is in effect on the date of issue.
OTHR The credit is subject to any other rules.
UCP LATEST VERSION The credit is subject to the version of the ICC Uniform Customs and
Practice for Documentary Credits, International Chamber of
Commerce, Paris, France, which is in effect on the date of issue.
UCPURR LATEST VERSION The credit is subject to the version of the ICC Uniform Customs and
Practice for Documentary Credits, International Chamber of
Commerce, Paris, France, which is in effect on the date of issue. The
reimbursement is subject to the version of the Uniform Rules for
Bank-to-Bank Reimbursements under documentary credits,
International Chamber of Commerce, Paris, France, which is in effect
on the date of issue.
PRESENCE
Mandatory
DEFINITION
This field specifies the latest date for presentation under the documentary credit and the place where
documents may be presented.
NETWORK VALIDATED RULES
Date must contain a valid date expressed as YYMMDD (Error code(s): T50).
PRESENCE
Optional
DEFINITION
This field specifies the bank of the applicant customer, if different from the issuing bank.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28,
T29, T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more
information about BEIs. This error code applies to all types of BICs referenced in a FIN message including
SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations
(Error code(s): C05).
PRESENCE
Mandatory
DEFINITION
This field specifies the party on behalf of which the documentary credit is being issued.
PRESENCE
Mandatory
DEFINITION
This field specifies the party in favour of which the documentary credit is being issued.
PRESENCE
Mandatory
DEFINITION
This field contains the currency code and amount of the documentary credit.
NETWORK VALIDATED RULES
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma ',' is mandatory and is
included in the maximum length. The number of digits following the comma must not exceed the maximum
number allowed for the specified currency (Error code(s): C03, T40, T43).
31 August 2007 13
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
USAGE RULES
Special information relative to the amount of the credit must be specified in field 39A Percentage Credit
Amount Tolerance, field 39B Maximum Credit Amount or field 39C Additional Amounts Covered.
PRESENCE
Conditional (see rule C1)
DEFINITION
This field specifies the tolerance relative to the documentary credit amount as a percentage plus and/or minus
that amount.
USAGE RULES
Tolerance 1 specifies a positive tolerance, the Tolerance 2 specifies a negative tolerance.
PRESENCE
Conditional (see rule C1)
DEFINITION
This field further qualifies the documentary credit amount.
CODES
The following code must be used (Error code(s): T01):
PRESENCE
Optional
DEFINITION
This field specifies any additional amounts available to the beneficiary under the terms of the credit, such as
insurance, freight, interest, etc.
PRESENCE
Mandatory
DEFINITION
This field identifies the bank with which the credit is available (the place for presentation) and an indication of
how the credit is available.
CODES
In option A, or D, Code must contain one of the following codes (Error code(s): T68)
BY ACCEPTANCE
BY DEF PAYMENT
BY MIXED PYMT
BY NEGOTIATION
BY PAYMENT
31 August 2007 15
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
PRESENCE
Conditional (see rules C2 and C3)
DEFINITION
This field specifies the tenor of drafts to be drawn under the documentary credit.
PRESENCE
Conditional (see rules C2 and C3)
DEFINITION
This field identifies the drawee of the drafts to be drawn under the documentary credit.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28,
T29, T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more
information about BEIs. This error code applies to all types of BICs referenced in a FIN message including
SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations
(Error code(s): C05).
USAGE RULES
The drawee must be a bank. If drafts on the applicant are required, they are to be listed as documents in field
46A.
The Party Identifier must not be present.
PRESENCE
Conditional (see rule C3)
DEFINITION
This field specifies the payment dates, amounts and/or method for their determination in a documentary credit
which is available by mixed payment.
PRESENCE
Conditional (see rule C3)
DEFINITION
This field specifies the payment date or method for its determination in a documentary credit which is
available by deferred payment only.
PRESENCE
Optional
DEFINITION
This field specifies whether or not partial shipments are allowed under the documentary credit.
PRESENCE
Optional
DEFINITION
This field specifies whether or not transshipment is allowed under the documentary credit.
PRESENCE
Optional
DEFINITION
This field specifies the place of taking in charge (in case of a multimodal transport document), the place of
receipt (in case of a road, rail or inland waterway transport document or a courier or expedited delivery service
document), the place of dispatch or the place of shipment to be indicated on the transport document.
PRESENCE
Optional
31 August 2007 17
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
DEFINITION
This field specifies the port of loading or airport of departure to be indicated on the transport document.
PRESENCE
Optional
DEFINITION
This field specifies the port of discharge or airport of destination to be indicated on the transport document.
PRESENCE
Optional
DEFINITION
This field specifies the final destination or place of delivery to be indicated on the transport document.
PRESENCE
Conditional (see rule C4)
DEFINITION
This field specifies the latest date for loading on board/dispatch/taking in charge.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).
PRESENCE
Conditional (see rule C4)
DEFINITION
This field specifies the period of time during which the goods are to be loaded on board/despatched/taken in
charge.
PRESENCE
Optional
DEFINITION
This field contains a description of the goods and/or services.
USAGE RULES
Terms such as FOB, CIF, etc. should be specified in this field.
To cater for lengthy documentary credits, up to three MT 701s may be sent in addition to an MT 700.
However, field 45a may appear in only one message, ie, either in the MT 700 or in one MT 701.
This means that in any documentary credit, there is a limit of 100 lines of 65 characters to specify the
description of goods and/or services.
Some examples of valid combinations:
• MT 700 contains field 45A, 46A, and 47A.
• MT 700 contains field 45A; the subsequent MT 701 contains fields 46B and 47B.
• MT 700 contains field 46A; the subsequent MT 701 contains fields 45B and 47B.
• MT 700 contains field 46A; the first MT 701 contains field 45B; the second MT 701 contains field 47B.
• MT 700 does not contain fields 45A, 46A or 47A; the first MT 701 contains field 45B; the second MT 701
contains field 46B; the third MT 701 contains field 47B.
Some examples of invalid combinations:
• MT 700 contains field 45A; the first MT 701 contains fields 45B and 46B; the second MT 701 contains
field 47B (INVALID because there are two fields 45a).
• MT 700 contains field 45A; the first MT 701 contains field 45B; the second MT 701 contains fields 45B,
46B and 47B (INVALID because there are three fields 45a).
The specification of each new item should begin on a new line, preceded by the sign '+'.
PRESENCE
Optional
DEFINITION
This field contains a description of any documents required.
USAGE RULES
When the ultimate date of issue of a transport document is specified, it is to be specified with the relative
document in this field.
For credits subject to eUCP, the format in which electronic records are to be presented must be specified in this
field.
31 August 2007 19
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
To cater for lengthy documentary credits, up to three MT 701s may be sent in addition to an MT 700.
However, field 46a may appear in only one message, ie, either in the MT 700 or in one MT 701.
This means that in any documentary credit, there is a limit of 100 lines of 65 characters to specify the
documents required.
Some examples of valid combinations:
• MT 700 contains field 45A, 46A, and 47A.
• MT 700 contains field 45A; the subsequent MT 701 contains fields 46B and 47B.
• MT 700 contains field 46A; the subsequent MT 701 contains fields 45B and 47B.
• MT 700 contains field 46A; the first MT 701 contains field 45B; the second MT 701 contains field 47B.
• MT 700 does not contain fields 45A, 46A or 47A; the first MT 701 contains field 45B; the second MT 701
contains field 46B; the third MT 701 contains field 47B.
Some examples of invalid combinations:
• MT 700 contains field 46A; the first MT 701 contains fields 45B and 46B; the second MT 701 contains
field 47B (INVALID because there are two fields 46a).
• MT 700 contains field 46A; the first MT 701 contains field 46B; the second MT 701 contains fields 45B,
46B and 47B (INVALID because there are three fields 46a).
The specification of each new item should begin on a new line, preceded by the sign '+'.
PRESENCE
Optional
DEFINITION
This field contains a description of further conditions of the documentary credit.
USAGE RULES
In case the documentary credit is subject to any rules for which no code words are provided in field 40E,
further details should be specified in this field.
To cater for lengthy documentary credits, up to three MT 701s may be sent in addition to an MT 700.
However, field 47a may appear in only one message, ie, either in the MT 700 or in one MT 701. This means
that in any documentary credit, there is a limit of 100 lines of 65 characters to specify the additional
conditions.
Some examples of valid combinations:
• MT 700 contains field 45A, 46A, and 47A.
• MT 700 contains field 47A; the subsequent MT 701 contains fields 45B and 46B.
• MT 700 contains field 46A; the subsequent MT 701 contains fields 45B and 47B.
• MT 700 contains field 46A; the first MT 701 contains field 45B; the second MT 701 contains field 47B.
• MT 700 does not contain fields 45A, 46A or 47A; the first MT 701 contains field 45B; the second MT 701
contains field 46B; the third MT 701 contains field 47B.
Some examples of invalid combinations:
• MT 700 contains field 47A; the first MT 701 contains fields 45B and 46B; the second MT 701 contains
field 47B (INVALID because there are two fields 47a).
• MT 700 contains field 47A; the first MT 701 contains field 47B; the second MT 701 contains fields 45B,
46B and 47B (INVALID because there are three fields 47a).
Where applicable, for credits subject to eUCP:
• If presentation of both electronic records and paper documents is allowed, the place for presentation of the
electronic records (ie, the electronic address to which presentation must be made) as well as the place for
presentation of the paper documents must be specified in this field.
• If presentation of only electronic records is allowed, the place for presentation of the electronic records (ie,
the electronic address to which presentation must be made) must be specified in this field.
• If not already part of the original documentary credit, the advising bank, ie, the receiver of the message,
must provide the beneficiary or another advising bank with the electronic address of the issuing bank.
Furthermore, the advising bank must provide the beneficiary or another advising bank with the electronic
address where they wish the electronic records to be presented.
• In case the electronic address contains the "@" sign, the latter should be replaced by "(AT)".
In case the electronic address contains the "_", the latter should be replaced by "(UNDERSCORE)".
Examples:
- [email protected] should be shown as
EUCP(AT)DRESDNER-BANK.COM
- [email protected] should be shown as
EUCP(UNDERSCORE)RECS(AT)DRESDNER-BANK.COM
The specification of each new item should begin on a new line, preceded by the sign '+'.
EXAMPLE
:47A:+NOT SUBJECT TO ICC UCP500
:47A:+SUBJECT TO ICC EUCP VERSION 1.0
PRESENCE
Optional
DEFINITION
This field may be used only to specify charges to be borne by the beneficiary.
CODES
One or more of the following codes may be used, followed by the currency code and amount:
31 August 2007 21
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
USAGE RULES
In the absence of this field, all charges, except negotiation and transfer charges, are to be borne by the
applicant.
Any code used in this field must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
PRESENCE
Optional
DEFINITION
This field specifies the period of time after the date of shipment within which the documents must be
presented for payment, acceptance or negotiation.
USAGE RULES
The period of time is expressed in number of days.
The absence of this field means that the presentation period is 21 days, where applicable.
PRESENCE
Mandatory
DEFINITION
This field contains confirmation instructions for the Receiver.
CODES
One of the following codes must be used (Error code(s): T67):
PRESENCE
Optional
DEFINITION
This field specifies the name of the bank which has been authorised by the Sender to reimburse drawings
under the documentary credit. This may be a branch of the Sender or the Receiver, or an entirely different
bank.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28,
T29, T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more
information about BEIs. This error code applies to all types of BICs referenced in a FIN message including
SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations
(Error code(s): C05).
USAGE RULES
With the exception of a credit valid for negotiation, if there is a single direct account relationship, in the
currency of the credit, between the Sender and the Receiver, the absence of field 53a means that this account
relationship will be used for reimbursement.
PRESENCE
Optional
DEFINITION
This field specifies instructions to the paying, accepting or negotiating bank. It may also indicate if pre-
notification of a reimbursement claim or pre-debit notification to the issuing bank is required.
USAGE RULES
When used to indicate pre-notification of a reimbursement claim or pre-debit notification to the issuing bank is
required, the number and type, ie, banking or calendar, of days within which the issuing bank has to be
notified should also be indicated.
31 August 2007 23
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
PRESENCE
Optional
DEFINITION
This field identifies the bank, if different from the Receiver, through which the documentary credit is to be
advised/confirmed to the beneficiary.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28,
T29, T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more
information about BEIs. This error code applies to all types of BICs referenced in a FIN message including
SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations
(Error code(s): C05).
In addition to narrative text, structured text with the following line formats may be used:
Line 1 /8c/[additional information]
Lines 2-6 [//continuation of additional information]
or
[/8c/[additional information]]
PRESENCE
Optional
DEFINITION
This field specifies additional information for the Receiver.
CODES
One or more of the following codes may be used:
USAGE RULES
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
MT 700 Examples
Narrative
ABC Company, Kaerntnerstrasse 3, Vienna, imports beer from Amdam Company, PO Box 123, Amsterdam,
under a documentary credit.
ABC Co.'s bank is Oesterreichische Laenderbank, Vienna. Amdam Co.'s bank is Bank Mees en Hope,
Amsterdam.
In addition to the above information, the documentary credit is comprised of the following:
Documents are to be presented within 6 days after the date of issuance of the Forwarding Agent's Certificate of
Receipt (FCR).
Confirmation is requested.
Taking in charge at Amsterdam for transportation to Vienna.
Transshipment and partial shipments are permitted.
The documentary credit has been pre-advised on 10 May 2003.
31 August 2007 25
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
Information Flow
MT 700
Explanation Format
Sender OELBATWW
Receiver AMRONL2A
Message Text
Explanation Format
Transshipment :43T:ALLOWED
31 August 2007 27
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
MT 701 Scope
This message is sent by the issuing bank to the advising bank.
It is used to indicate the terms and conditions of a documentary credit which has been originated by the Sender
(issuing bank).
This message is sent in addition to an MT 700 Issue of a Documentary Credit, when the information in the
documentary credit exceeds the maximum input message length of the MT 700.
M = Mandatory, O = Optional
PRESENCE
Mandatory
DEFINITION
This field specifies the number of this message in the series of messages sent for a documentary credit, and the
total number of messages in the series.
PRESENCE
Mandatory
DEFINITION
This field specifies the documentary credit number which has been assigned by the Sender.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
PRESENCE
Optional
DEFINITION
This field contains a description of the goods and/or services.
USAGE RULES
Terms such as FOB, CIF, etc. should be specified in this field.
To cater for lengthy documentary credits, up to three MT 701s may be sent in addition to an MT 700.
However, field 45a may appear in only one message, ie, either in the MT 700 or in one MT 701.
This means that in any documentary credit, there is a limit of 100 lines of 65 characters to specify the
description of goods and/or services.
Some examples of valid combinations:
• MT 700 contains field 45A; the subsequent MT 701 contains fields 46B and 47B.
• MT 700 contains field 46A; the subsequent MT 701 contains fields 45B and 47B.
• MT 700 contains field 46A; the first MT 701 contains field 45B; the second MT 701 contains field 47B.
31 August 2007 29
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
• MT 700 does not contain fields 45A, 46A or 47A; the first MT 701 contains field 45B; the second MT 701
contains field 46B; the third MT 701 contains field 47B.
Some examples of invalid combinations:
• MT 700 contains field 45A; the first MT 701 contains fields 45B and 46B; the second MT 701 contains
field 47B (INVALID because there are two fields 45a).
• MT 700 contains field 45A; the first MT 701 contains field 45B; the second MT 701 contains fields 45B,
46B and 47B (INVALID because there are three fields 45a).
The specification of each new item should begin on a new line, preceded by the sign '+'.
PRESENCE
Optional
DEFINITION
This field contains a description of any documents required.
USAGE RULES
When the ultimate date of issue of a transport document is specified, it is to be specified with the relative
document in this field.
For credits subject to eUCP, the format in which electronic records are to be presented must be specified in this
field.
To cater for lengthy documentary credits, up to three MT 701s may be sent in addition to an MT 700.
However, field 46a may appear in only one message, ie, either in the MT 700 or in one MT 701.
This means that in any documentary credit, there is a limit of 100 lines of 65 characters to specify the
documents required.
Some examples of valid combinations:
• MT 700 contains field 45A; the subsequent MT 701 contains fields 46B and 47B.
• MT 700 contains field 46A; the subsequent MT 701 contains fields 45B and 47B.
• MT 700 contains field 46A; the first MT 701 contains field 45B; the second MT 701 contains field 47B.
• MT 700 does not contain fields 45A, 46A or 47A; the first MT 701 contains field 45B; the second MT 701
contains field 46B; the third MT 701 contains field 47B.
Some examples of invalid combinations:
• MT 700 contains field 46A; the first MT 701 contains fields 45B and 46B; the second MT 701 contains
field 47B (INVALID because there are two fields 46a).
• MT 700 contains field 46A; the first MT 701 contains field 46B; the second MT 701 contains fields 45B,
46B and 47B (INVALID because there are three fields 46a).
The specification of each new item should begin on a new line, preceded by the sign '+'.
PRESENCE
Optional
DEFINITION
This field contains a description of further conditions of the documentary credit.
USAGE RULES
In case the documentary credit is subject to any rules for which no code words are provided in field 40E of the
related MT 700, further details should be specified in this field.
To cater for lengthy documentary credits, up to three MT 701s may be sent in addition to an MT 700.
However, field 47a may appear in only one message, ie, either in the MT 700 or in one MT 701. This means
that in any documentary credit, there is a limit of 100 lines of 65 characters to specify the additional
conditions.
Some examples of valid combinations:
• MT 700 contains field 47A; the subsequent MT 701 contains fields 45B and 46B.
• MT 700 contains field 46A; the subsequent MT 701 contains fields 45B and 47B.
• MT 700 contains field 46A; the first MT 701 contains field 45B; the second MT 701 contains field 47B.
• MT 700 does not contain fields 45A, 46A or 47A; the first MT 701 contains field 45B; the second MT 701
contains field 46B; the third MT 701 contains field 47B.
Some examples of invalid combinations:
• MT 700 contains field 47A; the first MT 701 contains fields 45B and 46B; the second MT 701 contains
field 47B (INVALID because there are two fields 47a).
• MT 700 contains field 47A; the first MT 701 contains field 47B; the second MT 701 contains fields 45B,
46B and 47B (INVALID because there are three fields 47a).
Where applicable, for credits subject to eUCP:
• If presentation of both electronic records and paper documents is allowed, the place for presentation of the
electronic records (ie, the electronic address to which presentation must be made) as well as the place for
presentation of the paper documents must be specified in this field.
• If presentation of only electronic records is allowed, the place for presentation of the electronic records (ie,
the electronic address to which presentation must be made) must be specified in this field.
• If not already part of the original documentary credit, the advising bank, ie, the receiver of the message,
must provide the beneficiary or another advising bank with the electronic address of the issuing bank.
Furthermore, the advising bank must provide the beneficiary or another advising bank with the electronic
address where they wish the electronic records to be presented.
• In case the electronic address contains the "@" sign, the latter should be replaced by "(AT)".
In case the electronic address contains the "_", the latter should be replaced by "(UNDERSCORE)".
Examples:
- [email protected] should be shown as
EUCP(AT)DRESDNER-BANK.COM
- [email protected] should be shown as
EUCP(UNDERSCORE)RECS(AT)DRESDNER-BANK.COM
The specification of each new item should begin on a new line, preceded by the sign '+'.
EXAMPLE
:47B:+NOT SUBJECT TO ICC UCP500
31 August 2007 31
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
MT 701 Examples
There are no examples for this message type.
MT 705 Scope
This message is sent by the issuing bank to the advising bank.
It is a brief advice of a documentary credit, the full details of which will follow.
The pre-advice is not an operative credit instrument. Unless otherwise stated, the issuing bank must forward
the operative credit instrument, ie, MT 700 Issue of a Documentary credit, without delay.
M 50 Applicant 4*35x 4
M 59 Beneficiary [/34x] 5
4*35x
O 79 Narrative 35*50x 19
M = Mandatory, O = Optional
31 August 2007 33
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
PRESENCE
Mandatory
DEFINITION
This field specifies the type of credit.
CODES
One of the following codes must be used (Error code(s): T60):
PRESENCE
Mandatory
DEFINITION
This field specifies the documentary credit number which has been assigned by the Sender.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
PRESENCE
Mandatory
DEFINITION
This field specifies the latest date for presentation under the documentary credit and the place where
documents may be presented.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).
PRESENCE
Mandatory
DEFINITION
This field specifies the party on behalf of which the documentary credit is being issued.
PRESENCE
Mandatory
DEFINITION
This field specifies the party in favour of which the documentary credit is being issued.
PRESENCE
Mandatory
DEFINITION
This field contains the currency and amount of the documentary credit.
NETWORK VALIDATED RULES
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma ',' is mandatory and is
included in the maximum length. The number of digits following the comma must not exceed the maximum
number allowed for the specified currency (Error code(s): C03, T40, T43).
USAGE RULES
Special information relative to the amount of the credit must be specified in field 39A Percentage Credit
Amount Tolerance, field 39B Maximum Credit Amount or field 39C Additional Amounts Covered.
31 August 2007 35
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
PRESENCE
Conditional (see rule C1)
DEFINITION
This field specifies the tolerance relative to the documentary credit amount as a percentage plus and/or minus
that amount.
USAGE RULES
Tolerance 1 specifies a positive tolerance, Tolerance 2 specifies a negative tolerance.
PRESENCE
Conditional (see rule C1)
DEFINITION
This field further qualifies the documentary credit amount.
CODES
The following code must be used (Error code(s): T01):
PRESENCE
Optional
DEFINITION
This field specifies any additional amounts covered such as insurance, freight, interest, etc.
PRESENCE
Optional
DEFINITION
This field identifies the bank with which the credit is available (the place for presentation) and an indication of
how the credit is available.
CODES
In option A, or D, Code must contain one of the following codes (Error code(s): T68):
BY ACCEPTANCE
BY DEF PAYMENT
BY MIXED PYMT
BY NEGOTIATION
BY PAYMENT
PRESENCE
Optional
DEFINITION
This field specifies the place of taking in charge (in case of a multimodal transport document), the place of
receipt (in case of a road, rail or inland waterway transport document or a courier or expedited delivery service
document), the place of dispatch or the place of shipment to be indicated on the transport document.
PRESENCE
Optional
DEFINITION
This field specifies the port of loading or airport of departure to be indicated on the transport document.
31 August 2007 37
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
PRESENCE
Optional
DEFINITION
This field specifies the port of discharge or airport of destination to be indicated on the transport document.
PRESENCE
Optional
DEFINITION
This field specifies the final destination or place of delivery to be indicated on the transport document.
PRESENCE
Conditional (see rule C2)
DEFINITION
This field specifies the latest date for loading on board/dispatch/taking in charge.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).
PRESENCE
Conditional (see rule C2)
DEFINITION
This field specifies the period of time during which the goods are to be loaded on board/despatched/taken in
charge.
PRESENCE
Optional
DEFINITION
This field contains a description of the goods or services.
USAGE RULES
Terms such as FOB, CIF, etc. should be specified in this field.
The specification of each new item should begin on a new line, preceded by the sign '+'.
PRESENCE
Optional
DEFINITION
This field identifies the bank, if different from the Receiver, through which the pre-advice of a documentary
credit is to be advised to the beneficiary.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28,
T29, T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more
information about BEIs. This error code applies to all types of BICs referenced in a FIN message including
SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations
(Error code(s): C05).
PRESENCE
Optional
DEFINITION
This field specifies additional information concerning the documentary credit.
In addition to narrative text, structured text with the following line formats may be used:
31 August 2007 39
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
PRESENCE
Optional
DEFINITION
This field specifies additional information for the Receiver.
CODES
One or more of the following codes may be used:
USAGE RULES
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
MT 705 Examples
Narrative
Oesterreichische Laenderbank, Vienna, is going to issue its irrevocable documentary credit 12345, for Euro
100,000 on behalf of ABC Company, Kaerntnerstrasse 3, Vienna.
The credit is in favour of Amdam Company, PO Box 123, Amsterdam, covering 400,000 bottles of beer. It is
valid until 30 July 2003.
Amdam Company is to be advised through Bank Mees en Hope, Amsterdam.
Oesterreichische Laenderbank sends a pre-advice of the credit to the advising bank, Amsterdam-Rotterdam
Bank, Amsterdam.
(To review the issue of the documentary credit with all of the credit details, please see the Example Section of
the MT 700).
Information Flow
MT 705
Explanation Format
Sender OELBATWW
Receiver AMRONL2A
Message Text
31 August 2007 41
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
Explanation Format
MT 707 Scope
This message is sent by the issuing bank to the advising bank. It may also be sent by an advising bank to
another advising bank or by a transferring bank to an advising bank.
It is used to inform the Receiver about amendments to the terms and conditions of a documentary credit issued
by the Sender or by a third bank.
The amendment is to be considered as part of the documentary credit, unless the MT 707 is used to convey
only brief details of the amendment, details of which are to follow.
31 August 2007 43
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
O 79 Narrative 35*50x 22
M = Mandatory, O = Optional
PRESENCE
Mandatory
DEFINITION
This field specifies the reference assigned by the Sender to unambiguously identify the message.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
PRESENCE
Mandatory
DEFINITION
This field contains the reference number assigned to the documentary credit by the Receiver of the message.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
USAGE RULES
If the Receiver's reference is not known, NONREF must be used in this field.
PRESENCE
Optional
DEFINITION
This field specifies the documentary credit number of the issuing bank.
USAGE RULES
This field is used when the message is sent by a bank other than the issuing bank, ie, it is sent by an advising
bank.
31 August 2007 45
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
PRESENCE
Conditional (see rule C3)
DEFINITION
This field is used to identify the issuing bank, when different from the Sender of the message.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28,
T29, T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more
information about BEIs. This error code applies to all types of BICs referenced in a FIN message including
SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations
(Error code(s): C05).
USAGE RULES
When the MT 707 is used to advise a bank of amendments to a documentary credit by a third bank, this field
must specify the issuing bank.
PRESENCE
Optional
DEFINITION
This field specifies the date of the original issue of the documentary credit, ie, the date on which the issuing
bank considers the credit as being issued.
NETWORK VALIDATED RULES
Date must contain a valid date expressed as YYMMDD (Error code(s): T50).
PRESENCE
Optional
DEFINITION
This field specifies the date on which the issuing bank considers the credit as being amended.
NETWORK VALIDATED RULES
Date must contain a valid date expressed as YYMMDD (Error code(s): T50).
USAGE RULES
The absence of this field implies that the date of amendment of the documentary credit is the date on which
this MT 707 was sent.
PRESENCE
Optional
DEFINITION
This field specifies the number which identifies this amendment.
USAGE RULES
This number should be the latest in the series of all amendments made, regardless of the means by which
previous amendments were sent.
PRESENCE
Mandatory
DEFINITION
This field specifies the party in favour of which the documentary credit was issued, or transferred, prior to this
amendment.
USAGE RULES
It is used to assist the recipient in identifying the credit.
The presence of this field should not be interpreted to imply that the beneficiary is being changed.
If the name of the beneficiary is being amended by this message, this must be specified in field 79, along with
the relevant details, eg, the name and address of the new beneficiary.
PRESENCE
Conditional (see rule C6)
DEFINITION
This field specifies the new, ie, revised, expiry date for presentation under the documentary credit.
NETWORK VALIDATED RULES
Date must contain a valid date expressed as YYMMDD (Error code(s): T50).
31 August 2007 47
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
PRESENCE
Conditional (see rules C2 and C6)
DEFINITION
This field contains the currency and amount of an increase in the documentary credit amount.
NETWORK VALIDATED RULES
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma ',' is mandatory and is
included in the maximum length. The number of digits following the comma must not exceed the maximum
number allowed for the specified currency (Error code(s): C03, T40, T43).
Currency in fields 32B, 33B, and 34B must be the same (Error code(s): C02).
USAGE RULES
The currency of any increase in the credit amount must be in the same currency as that of the original credit
amount.
PRESENCE
Conditional (see rules C2 and C6)
DEFINITION
This field contains the currency code and amount of a decrease in the documentary credit amount.
NETWORK VALIDATED RULES
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma ',' is mandatory and is
included in the maximum length. The number of digits following the comma must not exceed the maximum
number allowed for the specified currency (Error code(s): C03, T40, T43).
Currency in fields 32B, 33B, and 34B must be the same (Error code(s): C02).
USAGE RULES
The currency of any decrease in the credit amount must be in the same currency as that of the original credit
amount.
PRESENCE
Conditional (see rules C1 and C6)
DEFINITION
This field contains the currency code and total amount of the documentary credit after the amendment,
disregarding any drawings.
NETWORK VALIDATED RULES
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma ',' is mandatory and is
included in the maximum length. The number of digits following the comma must not exceed the maximum
number allowed for the specified currency (Error code(s): C03, T40, T43).
Currency in fields 32B, 33B, and 34B must be the same (Error code(s): C02).
PRESENCE
Conditional (see rules C4 and C6)
DEFINITION
When the credit amount tolerance is being amended, this field specifies the new tolerance relative to the
documentary credit amount as a percentage plus and/or minus that amount.
USAGE RULES
Tolerance 1 specifies a positive tolerance, Tolerance 2 specifies a negative tolerance.
PRESENCE
Conditional (see rules C4 and C6)
DEFINITION
This field specifies the amended qualification of the documentary credit amount.
CODES
The following code must be used (Error code(s): T01):
PRESENCE
Conditional (see rule C6)
DEFINITION
This field specifies amendments to any additional amounts covered, such as insurance, freight, interest, etc.
31 August 2007 49
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
PRESENCE
Conditional (see rule C6)
DEFINITION
This field specifies amendments to the place of taking in charge (in case of a multimodal transport document),
the place of receipt (in case of a road, rail or inland waterway transport document or a courier or expedited
delivery service document), the place of dispatch or the place of shipment to be indicated on the transport
document.
PRESENCE
Conditional (see rule C6)
DEFINITION
This field specifies amendments to the port of loading or airport of departure to be indicated on the transport
document.
PRESENCE
Conditional (see rule C6)
DEFINITION
This field specifies amendments to the port of discharge or airport of destination to be indicated on the
transport document.
PRESENCE
Conditional (see rule C6)
DEFINITION
This field specifies amendments to the final destination or place of delivery to be indicated on the transport
document.
PRESENCE
Conditional (see rules C5 and C6)
DEFINITION
This field specifies amendments to the latest date for loading on board/dispatch/taking in charge.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).
PRESENCE
Conditional (see rules C5 and C6)
DEFINITION
This field specifies amendments to the period of time during which the goods are to be loaded on
board/despatched/taken in charge.
PRESENCE
Conditional (see rule C6)
DEFINITION
This field specifies amendments to the documentary credit for which there is no other specific field.
CODES
The following code may be used:
USAGE RULES
This field must be used when specifying changes in currency and/or increases or decreases in a currency
different from the basic currency.
When an MT 707 is used to convey only brief details which are not intended to form part of the operative
instrument, this field must contain the phrase DETAILS TO FOLLOW.
This field should also be used to indicate if pre-notification of a reimbursement claim or pre-debit notification
to the issuing bank is required. The number and type, ie, banking or calendar, of days within which the issuing
bank has to be notified is also to be indicated.
In case the name of the beneficiary is being amended by this message, the new name and address of the
beneficiary should be explicitly indicated in this field. The new name and address of the beneficiary applies
wherever the original name and address of the beneficiary appeared in the original credit.
31 August 2007 51
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
In addition to narrative text, structured text with the following line formats may be used:
PRESENCE
Conditional (see rule C6)
DEFINITION
This field specifies additional information for the Receiver.
CODES
One or more of the following codes may be used:
BENCON The Receiver is requested to advise the beneficiary's acceptance or non-acceptance of the
terms and conditions contained in the amendment.
PHONBEN Please advise/contact beneficiary by phone.
TELEBEN Please advise the beneficiary by the most efficient means of telecommunication.
USAGE RULES
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
MT 707 Examples
Narrative
Solvia AB. PO Box 123, Upsala, Sweden, imports computer and electrical parts from Proquinal S.A., 48 rue
de la Bourse, Brussels, under a documentary credit, issued on 17 May 2003.
The documentary credit is in US dollars.
Solvia AB banks with Skandinaviska Enskilda Banken, Stockholm.
Proquinal S.A. banks with Generale Bank, Brussels.
The following information comprises the documentary credit:
Shipment of:
1 2219 b-gr, 12" crt (64 x 16) u/l keyboard with single minidiskette with
controller
2 2291 w-2 gr, 120 char.sec. printer, 12 pitch 132 char per line
1 2229 b-cr 12" crt (64 x 16) u/l keyboard console with contr.
cif Stockholm
31 August 2007 53
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
Information Flow
Applicant Solvia AB
Upsala
50
Beneficiary Proquinal SA
Brussels
59
D0070003
SWIFT Message
Message A MT 700
Note: The number of characters in the following messages does not exceed the maximum input message
length. Three messages are used to illustrate the use of the fields of the MT 700/701.
Explanation Format
Sender ESSESESS
Receiver GEBABEBB
Message Text
Applicant :50:SOLVIA AB
PO BOX 123
UPSALA, SWEDEN
Curr/Amount :32B:USD31500,
Drawn on … :42A:GEBABEBB36A
Loading … :44A:ANTWERP
Transport … :44B:STOCKHOLM
31 August 2007 55
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
Explanation Format
Reimbursement :53A:MAHAUS33
Message B MT 701
Explanation Format
Sender ESSESESS
Receiver GEBABEBB
Message Text
Message C MT 701
Explanation Format
Sender ESSESESS
Receiver GEBABEBB
Message Text
Narrative
On 21 May 2003, Skandinaviska Enskilda Banken subsequently notifies Generale Bank of the following
changes to the terms and conditions of the documentary credit issued on 17 May 2003:
• The expiry date of the credit has been extended to 30 September 2003.
• The amount of the credit has been increased by USD 3,250 to USD 34,750.
31 August 2007 57
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
Information Flow
MT 707
Beneficiary Proquinal SA
Brussels
D0070004
59
SWIFT Message
Explanation Format
Sender ESSESESS
Receiver GEBABEBB
Message Text
Explanation Format
31 August 2007 59
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
MT 710 Scope
This message is sent by an advising bank, which has received a documentary credit from the issuing bank or
the non-bank issuer, to the bank advising the beneficiary or another advising bank.
It is used to advise the Receiver about the terms and conditions of a documentary credit.
M 50 Applicant 4*35x 12
M 59 Beneficiary [/34x] 13
4*35x
O 42a Drawee A or D 20
M = Mandatory, O = Optional
31 August 2007 61
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
• Unless otherwise specified, a documentary credit advised to the beneficiary or another advising bank based
on a SWIFT message constitutes an operative credit instrument.
• For freely negotiable documentary credits, if the Receiver does not further transmit the credit by another
MT 710, it must add sentences to the effect that:
- The advice to the beneficiary must be presented at each negotiation.
- The negotiating bank must note each negotiation on that advice.
• To avoid misunderstandings, where possible, banks are to use Bank Identifier Codes rather than
expressions such as ourselves, yourselves, us, or you.
• If this message is used to advise a non-bank issued documentary credit, field 50B must be present.
• The advising bank must advise a documentary credit, including all its details, in a way that is clear and
unambiguous to the beneficiary.
PRESENCE
Mandatory
DEFINITION
This field specifies the number of this message in the series of messages sent for a documentary credit, and the
total number of messages in the series.
PRESENCE
Mandatory
DEFINITION
This field specifies the type of credit and whether or not the Sender is adding its confirmation to the credit.
CODES
Type must contain one of the following codes (Error code(s): T64):
CODES
Code must contain one of the following codes (Error code(s): T66):
ADDING OUR CONFIRMATION The Sender is adding its confirmation to the credit.
WITHOUT OUR CONFIRMATION The Sender is not adding its confirmation to the credit.
USAGE RULES
Details of any special conditions applying to the transferability of the credit and/or the bank authorised to
transfer the credit in a freely negotiable credit should be included in field 47A Additional Conditions.
PRESENCE
Mandatory
DEFINITION
This field contains the reference number which the Sender has assigned to the documentary credit.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
PRESENCE
Mandatory
DEFINITION
This field specifies the documentary credit number which has been assigned by the issuing bank.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
PRESENCE
Optional
DEFINITION
This field specifies if the documentary credit has been pre-advised.
USAGE RULES
This field must contain the code PREADV followed by a slash '/' and a reference to the pre-advice, eg, by date.
31 August 2007 63
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
PRESENCE
Mandatory
DEFINITION
This field specifies the date on which the issuing bank considers the documentary credit as being issued.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).
USAGE RULES
If this field was not present in the MT 700/701 Issue of a Documentary Credit, the date of issue is the date on
which the MT 700/701 was sent.
PRESENCE
Mandatory
DEFINITION
This field specifies the rules the credit is subject to.
CODES
One of the following codes must be used (Error code(s): T59)
EUCP LATEST VERSION The credit is subject to the version of the Supplement of the ICC
Uniform Customs and Practice for Documentary Credits for
Electronic Presentations, International Chamber of Commerce, Paris,
France, which is in effect on the date of issue.
EUCPURR LATEST VERSION The credit is subject to the version of the Supplement of the ICC
Uniform Customs and Practice for Documentary Credits for
Electronic Presentations, International Chamber of Commerce, Paris,
France, which is in effect on the date of issue. The reimbursement is
subject to the version of the Uniform Rules for Bank-to-Bank
Reimbursements, International Chamber of Commerce, Paris, France,
which is in effect on the date of issue.
ISP LATEST VERSION The standby letter of credit is subject to the version of the ICC
International Standby Practices, International Chamber of Commerce,
Paris, France, which is in effect on the date of issue.
PRESENCE
Mandatory
DEFINITION
This field specifies the latest date for presentation under the documentary credit and the place where
documents may be presented.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).
PRESENCE
Conditional (see rule C5)
DEFINITION
This field specifies the issuing bank of the credit.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28,
T29, T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more
information about BEIs. This error code applies to all types of BICs referenced in a FIN message including
SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations
(Error code(s): C05).
31 August 2007 65
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
PRESENCE
Conditional (see rule C5)
DEFINITION
This field specifies the non-bank issuer of the credit.
PRESENCE
Optional
DEFINITION
This field specifies the bank of the applicant customer, if different from the issuing bank.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28,
T29, T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more
information about BEIs. This error code applies to all types of BICs referenced in a FIN message including
SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations
(Error code(s): C05).
PRESENCE
Mandatory
DEFINITION
This field specifies the party on behalf of which the documentary credit has been issued.
PRESENCE
Mandatory
DEFINITION
This field specifies the party in favour of which the documentary credit has been issued.
PRESENCE
Mandatory
DEFINITION
This field contains the currency code and amount of the documentary credit.
NETWORK VALIDATED RULES
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma ',' is mandatory and is
included in the maximum length. The number of digits following the comma must not exceed the maximum
number allowed for the specified currency (Error code(s): C03, T40, T43).
USAGE RULES
Special information relative to the amount of the credit must be specified in field 39B Maximum Credit
Amount.
PRESENCE
Conditional (see rule C1)
DEFINITION
This field specifies the tolerance relative to the documentary credit amount as a percentage plus and/or minus
that amount.
USAGE RULES
Tolerance 1 specifies a positive tolerance, Tolerance 2 specifies a negative tolerance.
PRESENCE
Conditional (see rule C1)
DEFINITION
This field further qualifies the documentary credit amount.
CODES
The following code must be used (Error code(s): T01):
31 August 2007 67
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
PRESENCE
Optional
DEFINITION
This field specifies any additional amounts covered such as insurance, freight, interest, etc.
PRESENCE
Mandatory
DEFINITION
This field identifies the bank with which the credit is available (the place for presentation) and an indication of
how the credit is available.
CODES
In option A, or D, Code must contain one of the following codes (Error code(s): T68):
BY ACCEPTANCE
BY DEF PAYMENT
BY MIXED PYMT
BY NEGOTIATION
BY PAYMENT
If the credit is to be freely negotiable by any bank, option D must be used with the phrase Any bank in … (city
or country).
If the credit is to be freely negotiable by any bank anywhere in the world, an indication of country is not
required.
When Code contains either BY DEF PAYMENT or BY MIXED PYMT, the specific details of the payment
terms must be specified in fields 42P and 42M respectively.
When Code contains BY PAYMENT, this should be understood to mean payment at sight.
PRESENCE
Conditional (see rules C2 and C3)
DEFINITION
This field specifies the tenor of drafts to be drawn under the documentary credit.
PRESENCE
Conditional (see rules C2 and C3)
DEFINITION
This field identifies the drawee of the drafts to be drawn under the documentary credit.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28,
T29, T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more
information about BEIs. This error code applies to all types of BICs referenced in a FIN message including
SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations
(Error code(s): C05).
USAGE RULES
The drawee must be a bank. If drafts on the applicant are required, they are to be listed as documents in field
46A.
The Party Identifier must not be present.
31 August 2007 69
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
PRESENCE
Conditional (see rule C3)
DEFINITION
This field specifies the payment dates, amounts and/or method for their determination in a documentary credit
which is available by mixed payment.
PRESENCE
Conditional (see rule C3)
DEFINITION
This field specifies the payment date or method for its determination in a documentary credit which is
available by deferred payment only.
PRESENCE
Optional
DEFINITION
This field specifies whether or not partial shipments are allowed under the documentary credit.
PRESENCE
Optional
DEFINITION
This field specifies whether or not transshipment is allowed under the documentary credit.
PRESENCE
Optional
DEFINITION
This field specifies the place of taking in charge (in case of a multimodal transport document), the place of
receipt (in case of a road, rail or inland waterway transport document or a courier or expedited delivery service
document), the place of dispatch or the place of shipment to be indicated on the transport document.
PRESENCE
Optional
DEFINITION
This field specifies the port of loading or airport of departure to be indicated on the transport document.
PRESENCE
Optional
DEFINITION
This field specifies the port of discharge or airport of destination to be indicated on the transport document.
PRESENCE
Optional
DEFINITION
This field specifies the final destination or place of delivery to be indicated on the transport document.
PRESENCE
Conditional (see rule C4)
DEFINITION
This field specifies the latest date for loading on board/dispatch/taking in charge.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).
PRESENCE
Conditional (see rule C4)
31 August 2007 71
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
DEFINITION
This field specifies the period of time during which the goods are to be loaded on board/despatched/taken in
charge.
PRESENCE
Optional
DEFINITION
This field contains a description of the goods and/or services.
USAGE RULES
Terms such as FOB, CIF, etc. should be specified in this field.
To cater for lengthy documentary credits, up to three MT 711s may be sent in addition to an MT 710.
However, field 45a may appear in only one message, ie, either in the MT 710 or in one MT 711.
This means that in any documentary credit, there is a limit of 100 lines of 65 characters to specify the
description of goods and/or services.
Some examples of valid combinations:
• MT 710 contains field 45A, 46A, and 47A.
• MT 710 contains field 45A; the subsequent MT 711 contains fields 46B and 47B.
• MT 710 contains field 46A; the subsequent MT 711 contains fields 45B and 47B.
• MT 710 contains field 46A; the first MT 711 contains field 45B; the second MT 711 contains field 47B.
• MT 710 does not contain fields 45A, 46A or 47A; the first MT 711 contains field 45B; the second MT 711
contains field 46B; the third MT 711 contains field 47B.
Some examples of invalid combinations:
• MT 710 contains field 45A; the first MT 711 contains fields 45B and 46B; the second MT 711 contains
field 47B (INVALID because there are two fields 45a).
• MT 710 contains field 45A; the first MT 711 contains field 45B; the second MT 711 contains fields 45B,
46B and 47B (INVALID because there are three fields 45a).
The specification of each new item should begin on a new line, preceded by the sign '+'.
PRESENCE
Optional
DEFINITION
This field contains a description of any documents required.
USAGE RULES
When the ultimate date of issue of a transport document is specified, it is to be specified with the relative
document in this field.
For credits subject to eUCP, the format in which electronic records are to be presented must be specified in this
field.
To cater for lengthy documentary credits, up to three MT 711s may be sent in addition to an MT 710.
However, field 46a may appear in only one message, ie, either in the MT 710 or in one MT 711.
This means that in any documentary credit, there is a limit of 100 lines of 65 characters to specify the
documents required.
Some examples of valid combinations:
• MT 710 contains field 45A, 46A, and 47A.
• MT 710 contains field 45A; the subsequent MT 711 contains fields 46B and 47B.
• MT 710 contains field 46A; the subsequent MT 711 contains fields 45B and 47B.
• MT 710 contains field 46A; the first MT 711 contains field 45B; the second MT 711 contains field 47B.
• MT 710 does not contain fields 45A, 46A or 47A; the first MT 711 contains field 45B; the second MT 711
contains field 46B; the third MT 711 contains field 47B.
Some examples of invalid combinations:
• MT 710 contains field 46A; the first MT 711 contains fields 45B and 46B; the second MT 711 contains
field 47B (INVALID because there are two fields 46a).
• MT 710 contains field 46A; the first MT 711 contains field 46B; the second MT 711 contains fields 45B,
46B and 47B (INVALID because there are three fields 46a).
The specification of each new item should begin on a new line, preceded by the sign '+'.
PRESENCE
Optional
DEFINITION
This field contains a description of further conditions of the documentary credit.
USAGE RULES
In case the documentary credit is subject to any rules for which no code words are provided in field 40E,
further details should be specified in this field.
To cater for lengthy documentary credits, up to three MT 711s may be sent in addition to an MT 710.
However, field 47a may appear in only one message, ie, either in the MT 710 or in one MT 711. This means
that in any documentary credit, there is a limit of 100 lines of 65 characters to specify the additional
conditions.
Some examples of valid combinations:
• MT 710 contains field 45A, 46A, and 47A.
• MT 710 contains field 47A; the subsequent MT 711 contains fields 45B and 46B.
• MT 710 contains field 46A; the subsequent MT 711 contains fields 45B and 47B.
31 August 2007 73
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
• MT 710 contains field 46A; the first MT 711 contains field 45B; the second MT 711 contains field 47B.
• MT 710 does not contain fields 45A, 46A or 47A; the first MT 711 contains field 45B; the second MT 711
contains field 46B; the third MT 711 contains field 47B.
Some examples of invalid combinations:
• MT 710 contains field 47A; the first MT 711 contains fields 45B and 46B; the second MT 711 contains
field 47B (INVALID because there are two fields 47a).
• MT 710 contains field 47A; the first MT 711 contains field 47B; the second MT 711 contains fields 45B,
46B and 47B (INVALID because there are three fields 47a).
Where applicable, for credits subject to eUCP:
• If presentation of both electronic records and paper documents is allowed, the place for presentation of the
electronic records (ie, the electronic address to which presentation must be made) as well as the place for
presentation of the paper documents must be specified in this field.
• If presentation of only electronic records is allowed, the place for presentation of the electronic records (ie,
the electronic address to which presentation must be made) must be specified in this field.
• If not already part of the original documentary credit, the advising bank, ie, the receiver of the message,
must provide the beneficiary or another advising bank with the electronic address of the issuing bank.
Furthermore, the advising bank must provide the beneficiary or another advising bank with the electronic
address where they wish the electronic records to be presented.
• In case the electronic address contains the "@" sign, the latter should be replaced by "(AT)".
In case the electronic address contains the "_", the latter should be replaced by "(UNDERSCORE)".
Examples:
- [email protected] should be shown as
EUCP(AT)DRESDNER-BANK.COM
- [email protected] should be shown as
EUCP(UNDERSCORE)RECS(AT)DRESDNER-BANK.COM
The specification of each new item should begin on a new line, preceded by the sign '+'.
EXAMPLE
:47A:+NOT SUBJECT TO ICC UCP500
:47A:+SUBJECT TO ICC EUCP VERSION 1.0
PRESENCE
Optional
DEFINITION
This field may be used only to specify charges to be borne by the beneficiary.
CODES
One or more of the following codes may be used, followed by the currency code and amount:
USAGE RULES
In the absence of this field, all charges, except negotiation and transfer charges, are to be borne by the
applicant.
Any code used in this field must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
PRESENCE
Optional
DEFINITION
This field specifies the period of time after the date of shipment within which the documents must be
presented for payment, acceptance or negotiation.
USAGE RULES
The period for presentation is expressed in number of days.
The absence of this field means that the presentation period is 21 days, where applicable.
PRESENCE
Mandatory
DEFINITION
This field contains confirmation instructions for the Receiver.
31 August 2007 75
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
CODES
One of the following codes must be used (Error code(s): T67):
PRESENCE
Optional
DEFINITION
This field specifies the name of the bank or branch of the Receiver which has been authorised by the issuing
bank to reimburse drawings under the documentary credit.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28,
T29, T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more
information about BEIs. This error code applies to all types of BICs referenced in a FIN message including
SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations
(Error code(s): C05).
USAGE RULES
The absence of this field does not imply authority to debit the Sender.
PRESENCE
Optional
DEFINITION
This field specifies instructions to the paying, accepting or negotiating bank. It may also indicate if pre-
notification of a reimbursement claim or pre-debit notification to the issuing bank is required.
USAGE RULES
When used to indicate pre-notification of a reimbursement claim or pre-debit notification to the issuing bank is
required, the number and type, ie, banking or calendar, of days within which the issuing bank has to be
notified should also be indicated.
PRESENCE
Optional
DEFINITION
This field identifies the bank, if different from the Receiver, through which the documentary credit is to be
advised/confirmed to the beneficiary.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28,
T29, T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more
information about BEIs. This error code applies to all types of BICs referenced in a FIN message including
SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations
(Error code(s): C05).
In addition to narrative text, structured text with the following line formats may be used:
Line 1 /8c/[additional information]
Lines 2-6 [//continuation of additional information]
or
[/8c/[additional information]]
PRESENCE
Optional
DEFINITION
This field specifies additional information for the Receiver.
CODES
One or more of the following codes may be used:
USAGE RULES
Any code must be between slashes and must appear at the beginning of a line.
31 August 2007 77
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
MT 710 Examples
Narrative
ABC Company in Austria imports beer from Amdam Company in the Netherlands under a documentary
credit.
ABC Co.'s bank is Oesterreichische Laenderbank, Vienna. Amdam Co.'s bank is Bank Mees en Hope,
Amsterdam.
Oesterreichische Laenderbank issues its documentary credit, number 12345, through its correspondent in
Amsterdam, Amsterdam-Rotterdam Bank. (To review the terms and conditions of the documentary credit, see
MT 700 Issue of a Documentary Credit.)
Amsterdam-Rotterdam Bank advises the credit (reference 606487) through Bank Mees en Hope, Amsterdam.
Information Flow
MT 710
SWIFT Message
Explanation Format
Sender AMRONL2A
Receiver MEESNL2A
Message Text
Transshipment :43T:ALLOWED
31 August 2007 79
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
Explanation Format
MT 711 Scope
This message is sent by an advising bank, which has received a documentary credit from the issuing bank or
the non-bank issuer, to the bank advising the beneficiary or another advising bank.
It is used to advise the Receiver about the terms and conditions of a documentary credit.
This message is sent in addition to an MT 710 Advice of a Third Bank's or a Non-Bank's Documentary Credit,
when the information in the documentary credit exceeds the maximum input message length of the MT 710.
M = Mandatory, O = Optional
31 August 2007 81
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
• The advising bank must advise a documentary credit, including all its details, in a way that is clear and
unambiguous to the beneficiary.
PRESENCE
Mandatory
DEFINITION
This field specifies the number of this message in the series of messages sent for a documentary credit, and the
total number of messages in the series.
PRESENCE
Mandatory
DEFINITION
This field contains the reference number which the Sender has assigned to the documentary credit.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
PRESENCE
Mandatory
DEFINITION
This field specifies the documentary credit number which has been assigned by the issuing bank.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
PRESENCE
Optional
DEFINITION
This field contains a description of the goods and/or services.
USAGE RULES
Terms such as FOB, CIF, etc. should be specified in this field.
To cater for lengthy documentary credits, up to three MT 711s may be sent in addition to an MT 710.
However, field 45a may appear in only one message, ie, either in the MT 710 or in one MT 711.
This means that in any documentary credit, there is a limit of 100 lines of 65 characters to specify the
description of goods and/or services.
Some examples of valid combinations:
• MT 710 contains field 45A; the subsequent MT 711 contains fields 46B and 47B.
• MT 710 contains field 46A; the subsequent MT 711 contains fields 45B and 47B.
• MT 710 contains field 46A; the first MT 711 contains field 45B; the second MT 711 contains field 47B.
• MT 710 does not contain fields 45A, 46A or 47A; the first MT 711 contains field 45B; the second MT 711
contains field 46B; the third MT 711 contains field 47B.
Some examples of invalid combinations:
• MT 710 contains field 45A; the first MT 711 contains fields 45B and 46B; the second MT 711 contains
field 47B (INVALID because there are two fields 45a).
• MT 710 contains field 45A; the first MT 711 contains field 45B; the second MT 711 contains fields 45B,
46B and 47B (INVALID because there are three fields 45a).
The specification of each new item should begin on a new line, preceded by the sign '+'.
PRESENCE
Optional
DEFINITION
This field contains a description of any documents required.
USAGE RULES
When the ultimate date of issue of a transport document is specified, it is to be specified with the relative
document in this field.
For credits subject to eUCP, the format in which electronic records are to be presented must be specified in this
field.
To cater for lengthy documentary credits, up to three MT 711s may be sent in addition to an MT 710.
However, field 46a may appear in only one message, ie, either in the MT 710 or in one MT 711.
This means that in any documentary credit, there is a limit of 100 lines of 65 characters to specify the
documents required.
Some examples of valid combinations:
31 August 2007 83
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
• MT 710 contains field 45A; the subsequent MT 711 contains fields 46B and 47B.
• MT 710 contains field 46A; the subsequent MT 711 contains fields 45B and 47B.
• MT 710 contains field 46A; the first MT 711 contains field 45B; the second MT 711 contains field 47B.
• MT 710 does not contain fields 45A, 46A or 47A; the first MT 711 contains field 45B; the second MT 711
contains field 46B; the third MT 711 contains field 47B.
Some examples of invalid combinations:
• MT 710 contains field 46A; the first MT 711 contains fields 45B and 46B; the second MT 711 contains
field 47B (INVALID because there are two fields 46a).
• MT 710 contains field 46A; the first MT 711 contains field 46B; the second MT 711 contains fields 45B,
46B and 47B (INVALID because there are three fields 46a).
The specification of each new item should begin on a new line, preceded by the sign '+'.
PRESENCE
Optional
DEFINITION
This field contains a description of further conditions of the documentary credit.
USAGE RULES
In case the documentary credit is subject to any rules for which no code words are provided in field 40E of the
related MT 710, further details should be specified in this field.
To cater for lengthy documentary credits, up to three MT 711s may be sent in addition to an MT 710.
However, field 47a may appear in only one message, ie, either in the MT 710 or in one MT 711. This means
that in any documentary credit, there is a limit of 100 lines of 65 characters to specify the additional
conditions.
Some examples of valid combinations:
• MT 710 contains field 47A; the subsequent MT 711 contains fields 45B and 46B.
• MT 710 contains field 46A; the subsequent MT 711 contains fields 45B and 47B.
• MT 710 contains field 46A; the first MT 711 contains field 45B; the second MT 711 contains field 47B.
• MT 710 does not contain fields 45A, 46A or 47A; the first MT 711 contains field 45B; the second MT 711
contains field 46B; the third MT 711 contains field 47B.
Some examples of invalid combinations:
• MT 710 contains field 47A; the first MT 711 contains fields 45B and 46B; the second MT 711 contains
field 47B (INVALID because there are two fields 47a).
• MT 710 contains field 47A; the first MT 711 contains field 47B; the second MT 711 contains fields 45B,
46B and 47B (INVALID because there are three fields 47a).
Where applicable, for credits subject to eUCP:
• If presentation of both electronic records and paper documents is allowed, the place for presentation of the
electronic records (ie, the electronic address to which presentation must be made) as well as the place for
presentation of the paper documents must be specified in this field.
• If presentation of only electronic records is allowed, the place for presentation of the electronic records (ie,
the electronic address to which presentation must be made) must be specified in this field.
• If not already part of the original documentary credit, the advising bank, ie, the receiver of the message,
must provide the beneficiary or another advising bank with the electronic address of the issuing bank.
Furthermore, the advising bank must provide the beneficiary or another advising bank with the electronic
address where they wish the electronic records to be presented.
• In case the electronic address contains the "@" sign, the latter should be replaced by "(AT)".
In case the electronic address contains the "_", the latter should be replaced by "(UNDERSCORE)".
Examples:
- [email protected] should be shown as
EUCP(AT)DRESDNER-BANK.COM
- [email protected] should be shown as
EUCP(UNDERSCORE)RECS(AT)DRESDNER-BANK.COM
The specification of each new item should begin on a new line, preceded by the sign '+'.
EXAMPLE
:47B:+NOT SUBJECT TO ICC UCP500
:47B:+SUBJECT TO ICC EUCP VERSION 1.0
31 August 2007 85
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
MT 720 Scope
When a beneficiary has requested the transfer of a documentary credit - originally issued by a bank or a non-
bank - to a second beneficiary, this message is sent by the bank authorised to advise the transfer of the
documentary credit, to the bank advising the second beneficiary.
It is used to advise the Receiver about the terms and conditions of the transferred documentary credit, or part
thereof.
O 42a Drawee A or D 18
M = Mandatory, O = Optional
31 August 2007 87
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
PRESENCE
Mandatory
DEFINITION
This field specifies the number of this message in the series of messages sent for a documentary credit, and the
total number of messages in the series.
PRESENCE
Mandatory
DEFINITION
This field specifies the type of credit and whether or not the Sender is adding its confirmation to the credit.
CODES
Type must contain one of the following codes (Error code(s): T64):
IRREVOC TRANS STANDBY The standby letter of credit is irrevocable and transferable.
IRREVOCABLE The documentary credit/standby letter of credit is irrevocable.
REVOCABLE The documentary credit/standby letter of credit is revocable.
CODES
Code must contain one of the following codes (Error code(s): T66):
ADDING OUR CONFIRMATION The Sender is adding its confirmation to the credit.
WITHOUT OUR CONFIRMATION The Sender is not adding its confirmation to the credit.
PRESENCE
Mandatory
DEFINITION
This field contains the reference number which the transferring bank (Sender) has assigned to the
documentary credit.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
PRESENCE
Mandatory
DEFINITION
This field specifies the documentary credit number which has been assigned by the issuing bank.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
PRESENCE
Optional
DEFINITION
This field specifies the date on which the issuing bank considers the documentary credit as being issued.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).
USAGE RULES
The absence of this field in an MT 700/701 Issue of a Documentary Credit implies that the date of issue of that
documentary credit is the date on which the MT 700/701 was sent.
It is strongly recommended that this field be included in the MT 720.
31 August 2007 89
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
PRESENCE
Mandatory
DEFINITION
This field specifies the rules the credit is subject to.
CODES
One of the following codes must be used (Error code(s): T59)
EUCP LATEST VERSION The credit is subject to the version of the Supplement of the ICC
Uniform Customs and Practice for Documentary Credits for
Electronic Presentations, International Chamber of Commerce, Paris,
France, which is in effect on the date of issue.
EUCPURR LATEST VERSION The credit is subject to the version of the Supplement of the ICC
Uniform Customs and Practice for Documentary Credits for
Electronic Presentations, International Chamber of Commerce, Paris,
France, which is in effect on the date of issue. The reimbursement is
subject to the version of the Uniform Rules for Bank-to-Bank
Reimbursements, International Chamber of Commerce, Paris, France,
which is in effect on the date of issue.
ISP LATEST VERSION The standby letter of credit is subject to the version of the ICC
International Standby Practices, International Chamber of Commerce,
Paris, France, which is in effect on the date of issue.
OTHR The credit is subject to any other rules.
UCP LATEST VERSION The credit is subject to the version of the ICC Uniform Customs and
Practice for Documentary Credits, International Chamber of
Commerce, Paris, France, which is in effect on the date of issue.
UCPURR LATEST VERSION The credit is subject to the version of the ICC Uniform Customs and
Practice for Documentary Credits, International Chamber of
Commerce, Paris, France, which is in effect on the date of issue. The
reimbursement is subject to the version of the Uniform Rules for
Bank-to-Bank Reimbursements under documentary credits,
International Chamber of Commerce, Paris, France, which is in effect
on the date of issue.
PRESENCE
Mandatory
DEFINITION
This field specifies the latest date for presentation under the documentary credit and the place where
documents may be presented.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).
PRESENCE
Conditional (see rule C5)
DEFINITION
This field specifies the issuing bank of the original documentary credit.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28,
T29, T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more
information about BEIs. This error code applies to all types of BICs referenced in a FIN message including
SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations
(Error code(s): C05).
USAGE RULES
In the absence of this field, the Sender of the message is the issuing bank of the original documentary credit.
PRESENCE
Conditional (see rule C5)
DEFINITION
This field specifies the non-bank issuer of the original documentary credit.
PRESENCE
Mandatory
DEFINITION
This field specifies the party on behalf of which the documentary credit has been issued/transferred.
31 August 2007 91
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
PRESENCE
Mandatory
DEFINITION
This field specifies the name of the beneficiary of the transferred credit, referred to in the UCP as the second
beneficiary.
PRESENCE
Mandatory
DEFINITION
This field contains the currency code and amount of the documentary credit.
NETWORK VALIDATED RULES
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma ',' is mandatory and is
included in the maximum length. The number of digits following the comma must not exceed the maximum
number allowed for the specified currency (Error code(s): C03, T40, T43).
USAGE RULES
Special information relative to the amount of the credit must be specified in field 39B Maximum Credit
Amount.
PRESENCE
Conditional (see rule C1)
DEFINITION
This field specifies the tolerance relative to the documentary credit amount as a percentage plus and/or minus
that amount.
USAGE RULES
Tolerance 1 specifies a positive tolerance, Tolerance 2 specifies a negative tolerance.
PRESENCE
Conditional (see rule C1)
DEFINITION
This field further qualifies the documentary credit amount.
CODES
The following code must be used (Error code(s): T01):
PRESENCE
Optional
DEFINITION
This field specifies any additional amounts covered such as insurance, freight, interest, etc.
PRESENCE
Mandatory
DEFINITION
This field identifies the bank with which the credit is available (the place for presentation) and an indication of
how the credit is available.
CODES
In option A, or D, Code must contain one of the following codes (Error code(s): T68):
BY ACCEPTANCE
BY DEF PAYMENT
BY MIXED PYMT
BY NEGOTIATION
BY PAYMENT
31 August 2007 93
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
• If presentation of both electronic records and paper documents is allowed, the place for presentation of the
electronic records (ie, the electronic address to which presentation must be made) as well as the place for
presentation of the paper documents must be specified in field 47A and not in this field.
• If presentation of only electronic records is allowed, the place for presentation of the electronic records (ie,
the electronic address to which presentation must be made) must be specified in field 47A and not in this
field.
If the credit is to be freely negotiable by any bank, option D must be used with the phrase Any bank in … (city
or country).
If the credit is to be freely negotiable by any bank anywhere in the world, an indication of country is not
required.
When Code contains either BY DEF PAYMENT or BY MIXED PYMT, the specific details of the payment
terms must be specified in field 42P and 42M.
When Code contains BY PAYMENT, this should be understood to mean payment at sight.
PRESENCE
Conditional (see rules C2 and C3)
DEFINITION
This field specifies the tenor of drafts to be drawn under the documentary credit.
PRESENCE
Conditional (see rules C2 and C3)
DEFINITION
This field identifies the drawee of the drafts to be drawn under the documentary credit.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28,
T29, T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more
information about BEIs. This error code applies to all types of BICs referenced in a FIN message including
SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations
(Error code(s): C05).
USAGE RULES
The drawee must be a bank. If drafts on the applicant are required, they are to be listed as documents in field
46A.
PRESENCE
Conditional (see rule C3)
DEFINITION
This field specifies the payment dates, amounts and/or method for their determination in a documentary credit
which is available by mixed payment.
PRESENCE
Conditional (see rule C3)
DEFINITION
This field specifies the payment date or method for its determination in a documentary credit which is
available by deferred payment only.
PRESENCE
Optional
DEFINITION
This field specifies whether or not partial shipments are allowed under the documentary credit.
PRESENCE
Optional
DEFINITION
This field specifies whether or not transshipment is allowed under the documentary credit.
31 August 2007 95
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
PRESENCE
Optional
DEFINITION
This field specifies the place of taking in charge (in case of a multimodal transport document), the place of
receipt (in case of a road, rail or inland waterway transport document or a courier or expedited delivery service
document), the place of dispatch or the place of shipment to be indicated on the transport document.
PRESENCE
Optional
DEFINITION
This field specifies the port of loading or airport of departure to be indicated on the transport document.
PRESENCE
Optional
DEFINITION
This field specifies the port of discharge or airport of destination to be indicated on the transport document.
PRESENCE
Optional
DEFINITION
This field specifies the final destination or place of delivery to be indicated on the transport document.
PRESENCE
Conditional (see rule C4)
DEFINITION
This field specifies the latest date for loading on board/dispatch/taking in charge.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).
PRESENCE
Conditional (see rule C4)
DEFINITION
This field specifies the period of time during which the goods are to be loaded on board/despatched/taken in
charge.
PRESENCE
Optional
DEFINITION
This field contains a description of the goods and/or services.
USAGE RULES
Terms such as FOB, CIF, etc. should be specified in this field.
To cater for lengthy documentary credits, up to three MT 721s may be sent in addition to an MT 720.
However, field 45a may appear in only one message, ie, either in the MT 720 or in one MT 721.
This means that in any documentary credit, there is a limit of 100 lines of 65 characters to specify the
description of goods and/or services.
Some examples of valid combinations:
• MT 720 contains field 45A, 46A, and 47A.
• MT 720 contains field 45A; the subsequent MT 721 contains fields 46B and 47B.
• MT 720 contains field 46A; the subsequent MT 721 contains fields 45B and 47B.
• MT 720 contains field 46A; the first MT 721 contains field 45B; the second MT 721 contains field 47B.
• MT 720 does not contain fields 45A, 46A or 47A; the first MT 721 contains field 45B; the second MT 721
contains field 46B; the third MT 721 contains field 47B.
Some examples of invalid combinations:
• MT 720 contains field 45A; the first MT 721 contains fields 45B and 46B; the second MT 721 contains
field 47B (INVALID because there are two fields 45a).
• MT 720 contains field 45A; the first MT 721 contains field 45B; the second MT 721 contains fields 45B,
46B and 47B (INVALID because there are three fields 45a).
The specification of each new item should begin on a new line, preceded by the sign '+'.
31 August 2007 97
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
PRESENCE
Optional
DEFINITION
This field contains a description of any documents required.
USAGE RULES
When the ultimate date of issue of a transport document is specified, it is to be specified with the relative
document in this field.
For credits subject to eUCP, the format in which electronic records are to be presented must be specified in this
field.
To cater for lengthy documentary credits, up to three MT 721s may be sent in addition to an MT 720.
However, field 46a may appear in only one message, ie, either in the MT 720 or in one MT 721.
This means that in any documentary credit, there is a limit of 100 lines of 65 characters to specify the
documents required.
Some examples of valid combinations:
• MT 720 contains field 45A, 46A, and 47A.
• MT 720 contains field 45A; the subsequent MT 721 contains fields 46B and 47B.
• MT 720 contains field 46A; the subsequent MT 721 contains fields 45B and 47B.
• MT 720 contains field 46A; the first MT 721 contains field 45B; the second MT 721 contains field 47B.
• MT 720 does not contain fields 45A, 46A or 47A; the first MT 721 contains field 45B; the second MT 721
contains field 46B; the third MT 721 contains field 47B.
Some examples of invalid combinations:
• MT 720 contains field 46A; the first MT 721 contains fields 45B and 46B; the second MT 721 contains
field 47B (INVALID because there are two fields 46a).
• MT 720 contains field 46A; the first MT 721 contains field 46B; the second MT 721 contains fields 45B,
46B and 47B (INVALID because there are three fields 46a).
The specification of each new item should begin on a new line, preceded by the sign '+'.
PRESENCE
Optional
DEFINITION
This field contains a description of further conditions of the documentary credit.
USAGE RULES
In case the documentary credit is subject to any rules for which no code words are provided in field 40E,
further details should be specified in this field.
To cater for lengthy documentary credits, up to three MT 721s may be sent in addition to an MT 720.
However, field 47a may appear in only one message, ie, either in the MT 720 or in one MT 721. This means
that in any documentary credit, there is a limit of 100 lines of 65 characters to specify the additional
conditions.
31 August 2007 99
Category 7 - Documentary Credits and Guarantees for SWIFTStandards MT October 2007
PRESENCE
Optional
DEFINITION
This field may be used only to specify charges to be borne by the beneficiary.
CODES
One or more of the following codes may be used, followed by the currency code and amount:
USAGE RULES
In the absence of this field, all charges, except negotiation and transfer charges, are to be borne by the
applicant.
Any code used in this field must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
PRESENCE
Optional
DEFINITION
This field specifies the period of time after the date of shipment within which the documents must be
presented for payment, acceptance or negotiation.
USAGE RULES
The period for presentation is expressed in number of days.
The absence of this field means that the presentation period is 21 days, where applicable.
PRESENCE
Mandatory
DEFINITION
This field contains confirmation instructions for the Receiver.
CODES
One of the following codes must be used (Error code(s): T67):
PRESENCE
Optional
DEFINITION
This field specifies instructions to the paying, accepting or negotiating bank. It may also indicate if pre-
notification of a reimbursement claim or pre-debit notification to the issuing bank is required.
USAGE RULES
When used to indicate pre-notification of a reimbursement claim or pre-debit notification to the issuing bank is
required, the number and type, ie, banking or calendar, of days within which the issuing bank has to be
notified should also be indicated.
PRESENCE
Optional
DEFINITION
This field identifies the bank, if different from the Receiver, through which the documentary credit is to be
advised/confirmed to the beneficiary.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28,
T29, T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more
information about BEIs. This error code applies to all types of BICs referenced in a FIN message including
SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations
(Error code(s): C05).
In addition to narrative text, structured text with the following line formats may be used:
PRESENCE
Optional
DEFINITION
This field specifies additional information for the Receiver.
CODES
One or more of the following codes may be used:
USAGE RULES
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
MT 720 Examples
Narrative
Motoimport, PO Box 9, Amsterdam, orders motor cycle and car parts from London Motospares Ltd., 12 Cycle
Square, London.
London Motospares Ltd. will obtain these parts from Cyclist Ltd., Singapore. It therefore requests a
transferable documentary credit in its own favour and transfers it in favour of Cyclist Ltd.
Motoimport banks with Nederlandsche Middenstandsbank, Amsterdam.
London Motospares Ltd. banks with Royal Bank of Scotland, London.
Cyclist Ltd. banks with the Hong Kong and Shanghai Banking Corporation, Singapore.
The documentary credit is comprised of the following:
Shipment:
400 Fuel tanks model 1320 AA cont, 10 gall.
120 clutches 4 gangs model A 154
800 cylinders 150 cc model C45-15
600 rear wheels complete 28" magnesium model MW 123-28
120 fuel-injection sets complete model A 156-F
FCA Singapore
Against presentation of the following documents:
• Signed Commercial Invoice in five-fold
• Combined transport documents (full set) evidencing taking in charge of the merchandise as a full
contained load for shipment by ocean vessel to Rotterdam issued to the order and blank endorsed dated not
later than 20 September 2003
• Packing list in five-fold
• Declaration issued by the company undersigning the CTD that the goods will be sent by vessel plying in
regular line-service
Special Conditions:
• Freight may be paid in excess of the credit amount against freight note in which case CTD to be stamped
freight prepaid
Documents are to be presented within 10 days after the date of issuance of the shipping documents.
The advising bank may add its confirmation to the credit.
Shipment will be from Singapore to Port of Rotterdam.
Transshipment is permitted.
Partial shipments are not permitted.
Information Flow
Applicant Motoimport
Amsterdam
50
Sender Nederlandsche
(Issuing Bank) Middenstandsbank
Amsterdam
MT 700
D0070006
SWIFT Message MT 700
Explanation Format
Sender NMBANL2A
Receiver RBOSGB2L
Message Text
Applicant :50:MOTOIMPORT
PO BOX 9
AMSTERDAM
Explanation Format
Curr/Amount :32B:GBP123675,
Transshipment :43T:ALLOWED
Transport … :44B:ROTTERDAM
Narrative
On the instructions of London Motospares Ltd., Royal Bank of Scotland transfers the documentary credit
(reference IMP124678) to Hong Kong and Shanghai Banking Corporation, Singapore, in favour of Cyclists
Ltd., 498 Wheeler St., Singapore.
The amount of the transferred credit is Pounds Sterling 100,000.
Information Flow
MT 720
59
Explanation Format
Sender RBOSGB2
Receiver HSBCSGSG
Message Text
Explanation Format
Currency/Amount :32B:GBP100000,
Transshipment :43T:ALLOWED
Transport … :44B:ROTTERDAM
Explanation Format
MT 721 Scope
When a beneficiary has requested the transfer of a documentary credit - originally issued by a bank or a non-
bank - to a second beneficiary, this message is sent by the bank authorised to advise the transfer of the
documentary credit, to the bank advising the second beneficiary.
It is used to advise the Receiver about the terms and conditions of the transferred documentary credit, or part
thereof.
This message is sent in addition to an MT 720 Transfer of a Documentary Credit, when the information in the
documentary credit exceeds the maximum input message length of the MT 720.
M = Mandatory, O = Optional
• The transferring bank must transfer the documentary credit, including all its details, in a way that is clear
and unambiguous to the beneficiary.
PRESENCE
Mandatory
DEFINITION
This field specifies the number of this message in the series of messages sent for a documentary credit, and the
total number of messages in the series.
PRESENCE
Mandatory
DEFINITION
This field contains the reference number which the transferring bank (Sender) has assigned to the
documentary credit.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
PRESENCE
Mandatory
DEFINITION
This field specifies the documentary credit number which has been assigned by the issuing bank.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
PRESENCE
Optional
DEFINITION
This field contains a description of the goods and/or services.
USAGE RULES
Terms such as FOB, CIF, etc. should be specified in this field.
To cater for lengthy documentary credits, up to three MT 721s may be sent in addition to an MT 720.
However, field 45a may appear in only one message, ie, either in the MT 720 or in one MT 721.
This means that in any documentary credit, there is a limit of 100 lines of 65 characters to specify the
description of goods and/or services.
Some examples of valid combinations:
• MT 720 contains field 45A; the subsequent MT 721 contains fields 46B and 47B.
• MT 720 contains field 46A; the subsequent MT 721 contains fields 45B and 47B.
• MT 720 contains field 46A; the first MT 721 contains field 45B; the second MT 721 contains field 47B.
• MT 720 does not contain fields 45A, 46A or 47A; the first MT 721 contains field 45B; the second MT 721
contains field 46B; the third MT 721 contains field 47B.
Some examples of invalid combinations:
• MT 720 contains field 45A; the first MT 721 contains fields 45B and 46B; the second MT 721 contains
field 47B (INVALID because there are two fields 45a).
• MT 720 contains field 45A; the first MT 721 contains field 45B; the second MT 721 contains fields 45B,
46B and 47B (INVALID because there are three fields 45a).
The specification of each new item should begin on a new line, preceded by the sign '+'.
PRESENCE
Optional
DEFINITION
This field contains a description of any documents required.
USAGE RULES
When the ultimate date of issue of a transport document is specified, it is to be specified with the relative
document in this field.
For credits subject to eUCP, the format in which electronic records are to be presented must be specified in this
field.
To cater for lengthy documentary credits, up to three MT 721s may be sent in addition to an MT 720.
However, field 46a may appear in only one message, ie, either in the MT 720 or in one MT 721.
This means that in any documentary credit, there is a limit of 100 lines of 65 characters to specify the
documents required.
Some examples of valid combinations:
• MT 720 contains field 45A; the subsequent MT 721 contains fields 46B and 47B.
• MT 720 contains field 46A; the subsequent MT 721 contains fields 45B and 47B.
• MT 720 contains field 46A; the first MT 721 contains field 45B; the second MT 721 contains field 47B.
• MT 720 does not contain fields 45A, 46A or 47A; the first MT 721 contains field 45B; the second MT 721
contains field 46B; the third MT 721 contains field 47B.
Some examples of invalid combinations:
• MT 720 contains field 46A; the first MT 721 contains fields 45B and 46B; the second MT 721 contains
field 47B (INVALID because there are two fields 46a).
• MT 720 contains field 46A; the first MT 721 contains field 46B; the second MT 721 contains fields 45B,
46B and 47B (INVALID because there are three fields 46a).
The specification of each new item should begin on a new line, preceded by the sign '+'.
PRESENCE
Optional
DEFINITION
This field contains a description of further conditions of the documentary credit.
USAGE RULES
In case the documentary credit is subject to any rules for which no code words are provided in field 40E of the
related MT 720, further details should be specified in this field.
To cater for lengthy documentary credits, up to three MT 721s may be sent in addition to an MT 720.
However, field 47a may appear in only one message, ie, either in the MT 720 or in one MT 721. This means
that in any documentary credit, there is a limit of 100 lines of 65 characters to specify the additional
conditions.
Some examples of valid combinations:
• MT 720 contains field 47A; the subsequent MT 721 contains fields 45B and 46B.
• MT 720 contains field 46A; the subsequent MT 721 contains fields 45B and 47B.
• MT 720 contains field 46A; the first MT 721 contains field 45B; the second MT 721 contains field 47B.
• MT 720 does not contain fields 45A, 46A or 47A; the first MT 721 contains field 45B; the second MT 721
contains field 46B; the third MT 721 contains field 47B.
Some examples of invalid combinations:
• MT 720 contains field 47A; the first MT 721 contains fields 45B and 46B; the second MT 721 contains
field 47B (INVALID because there are two fields 47a).
• MT 720 contains field 47A; the first MT 721 contains field 47B; the second MT 721 contains fields 45B,
46B and 47B (INVALID because there are three fields 47a).
Where applicable, for credits subject to eUCP:
• If presentation of both electronic records and paper documents is allowed, the place for presentation of the
electronic records (ie, the electronic address to which presentation must be made) as well as the place for
presentation of the paper documents must be specified in this field.
• If presentation of only electronic records is allowed, the place for presentation of the electronic records (ie,
the electronic address to which presentation must be made) must be specified in this field.
• If not already part of the original documentary credit, the advising bank, ie, the receiver of the message,
must provide the beneficiary or another advising bank with the electronic address of the issuing bank.
Furthermore, the advising bank must provide the beneficiary or another advising bank with the electronic
address where they wish the electronic records to be presented.
• In case the electronic address contains the "@" sign, the latter should be replaced by "(AT)".
In case the electronic address contains the "_", the latter should be replaced by "(UNDERSCORE)".
Examples:
- [email protected] should be shown as
EUCP(AT)DRESDNER-BANK.COM
- [email protected] should be shown as
EUCP(UNDERSCORE)RECS(AT)DRESDNER-BANK.COM
The specification of each new item should begin on a new line, preceded by the sign '+'.
EXAMPLE
:47B:+NOT SUBJECT TO ICC UCP500
:47B:+SUBJECT TO ICC EUCP VERSION 1.0
MT 721 Examples
There are no examples for this message type.
MT 730 Acknowledgement
MT 730 Scope
This message is used to acknowledge receipt of any documentary credit message. When applicable, it may
also explicitly indicate that the message has been forwarded according to instructions.
This message type may also be used:
• to account for bank charges
• to advise of acceptance or rejection of an amendment of a credit.
M = Mandatory, O = Optional
PRESENCE
Mandatory
DEFINITION
This field contains the reference assigned by the Sender to unambiguously identify the message.
PRESENCE
Mandatory
DEFINITION
This field contains the content of field 20 Transaction Reference Number of the message which this MT 730 is
acknowledging.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
USAGE RULES
If the related message was not sent via SWIFT, this field will contain a reference to that message which is
meaningful to the Receiver.
PRESENCE
Conditional (see rule C1)
DEFINITION
This field identifies the number of the account which has been used for the settlement of charges, on the books
of the Sender.
PRESENCE
Mandatory
DEFINITION
When this message is acknowledging an MT 700 Issue of a Documentary Credit, this field specifies the date
of issue.
In all other cases, this field specifies the date on which the message being acknowledged was sent.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).
PRESENCE
Optional
DEFINITION
This field contains the currency code and total amount of charges claimed by the Sender of the message.
NETWORK VALIDATED RULES
In option D, Date must be a valid date expressed as YYMMDD (Error code(s): T50).
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma ',' is mandatory and is
included in the maximum length. The number of digits following the comma must not exceed the maximum
number allowed for the specified currency (Error code(s): C03, T40, T43).
USAGE RULES
When the charges have been debited, option D must be used specifying the value date of the debit, in addition
to the currency code and amount.
When reimbursement for charges is requested, option B must be used.
PRESENCE
Conditional (see rules C1 and C2)
DEFINITION
This field identifies the bank to which the amount of charges is to be remitted in favour of the Sender.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28,
T29, T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more
information about BEIs. This error code applies to all types of BICs referenced in a FIN message including
SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations
(Error code(s): C05).
PRESENCE
Optional
DEFINITION
This field specifies the charges to be claimed.
CODES
One or more of the following codes may be used, followed by the currency code and amount:
USAGE RULES
Any code used in this field must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
In addition to narrative text, structured text with the following line formats may be used:
PRESENCE
Optional
DEFINITION
This field specifies additional information for the Receiver.
CODES
One or more of the following codes may be used:
USAGE RULES
When this message is used to advise of acceptance or rejection of an amendment of a credit, the confirmation
of the beneficiary must be indicated in this field.
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
MT 730 Examples
Narrative
Royal Bank of Scotland, London, receives documentary credit number DAE74568 from Nederlandsche
Middenstandsbank, Amsterdam, issued on 21 July 2003.
Royal Bank of Scotland acknowledges receipt of the credit with its reference IMP124678, indicating that it
has added its confirmation. Its charges are to be settled at a later date.
(To review the MT 700 which is being acknowledged see the Example section of the MT 700.)
Information Flow
(MT 700)
MT 730
Receiver Nederlandsche
(Issuing Bank) Middenstandbank
D0070008
Amsterdam
SWIFT Message
Explanation Format
Sender RBOSGB2L
Receiver NMBANL2A
Message Text
Explanation Format
Narrative
On 18 May 2002, Oesterreichische Laenderbank, Vienna, issues, and transmits via SWIFT, its documentary
credit number 12345. The applicant is Floral Encounters, Kruegerstrasse 12, Vienna; the beneficiary, Glory
Bulbs, Box 309, Lisse, The Netherlands. The amount of the credit is Euro 5,000. Amsterdam-Rotterdam Bank,
Amsterdam, is the advising and confirming bank for the credit.
The credit covers the purchase of 10,000 tulip bulbs, packed in cartons of 500 bulbs each, with each carton
being of one colour as per the purchase order. Partial shipments are not allowed. The following documents are
required:
• signed commercial invoice, in triplicate
• the forwarding agent's certificate, showing the goods addressed to the applicant.
Information Flow
MT 700
SWIFT Message
Explanation Format
Sender OELBATWW
Receiver AMRONL2A
Message Text
Example 2: Acknowledgement
Narrative
When it receives the documentary credit, Amsterdam-Rotterdam Bank sends the credit to the beneficiary,
including its confirmation. Amsterdam-Rotterdam Bank acknowledges receipt of the credit, with its reference
745322IMP, indicating that it has added its confirmation as requested. Charges are claimed in the amount of
EUR 300 for its confirmation and EUR 20 for cable costs.
Amsterdam-Rotterdam Bank requests Oesterreichische Laenderbank to pay total charges of EUR 320 to its
account number 75016375, at Creditanstalt Bankverein, Vienna.
Information Flow
(Charges)
D0070010
SWIFT Message
Explanation Format
Sender AMRONL2A
Receiver OELBATWW
Message Text
Charges :71B:/COMM/EUR300,
/CABLE/EUR20,
MT 732 Scope
This message is sent by the issuing bank to the paying/negotiating or accepting bank.
It may also be sent by the paying/accepting/negotiating bank to the bank from which it has received
documents.
It is used to advise the Receiver that the documents received with discrepancies have been taken up.
M = Mandatory, O = Optional
PRESENCE
Mandatory
DEFINITION
If the message is sent by the issuing bank, this field specifies the documentary credit number assigned by the
issuing bank.
If the message is sent by a bank other than the issuing bank, this field specifies either the documentary credit
number assigned by the issuing bank or another reference assigned by the Sender.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
PRESENCE
Mandatory
DEFINITION
This field specifies the reference which has been assigned by the presenting bank, ie, the Receiver of this
message.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
PRESENCE
Mandatory
DEFINITION
This field specifies the date of the covering letter under which the documents were sent.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).
PRESENCE
Mandatory
DEFINITION
This field contains the currency code and amount of the drawing, excluding any charges or deductions.
NETWORK VALIDATED RULES
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma ',' is mandatory and is
included in the maximum length. The number of digits following the comma must not exceed the maximum
number allowed for the specified currency (Error code(s): C03, T40, T43).
In addition to narrative text, structured text with the following line formats may be used:
PRESENCE
Optional
DEFINITION
This field specifies additional information for the Receiver.
USAGE RULES
The structured line format may be used for bilaterally agreed codes.
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
MT 732 Examples
Narrative
Oesterreichische Laenderbank issues its documentary credit number 12345 on behalf of ABC Company,
Vienna.
The advising bank for the credit is Amsterdam-Rotterdam Bank, Amsterdam; the beneficiary, Amdam
Company, Amsterdam, banks with Bank Mees en Hope, Amsterdam.
(To review the MT 700, 705 and 710 related to this documentary credit, please see the respective Example
sections.)
On July 26, 2003, Amsterdam-Rotterdam Bank, Amsterdam, advises Oesterreichische Laenderbank that
documents have been presented by Bank Mees en Hope, and that they have been paid subject to one minor
discrepancy (Oesterreichische Laenderbank shown as consignee).
Amsterdam-Rotterdam Bank has debited the account of Oesterreichische Laenderbank (number 311248123)
for Euro 100,383.75 (being EUR 100,000 plus charges totalling EUR 383.75) and requests its discharge.
The documents are sent to Vienna by mail.
Information Flow
MT 754
D0070011
SWIFT Message
Explanation Format
Sender AMRONL2A
Receiver OELBATWW
Message Text
Narrative
On receipt of the above message and the mailed documents, Oesterreichische Laenderbank advises
Amsterdam-Rotterdam Bank that the documents have been taken up and that Amsterdam-Rotterdam Bank is
now discharged.
Information Flow
MT 732
D0070012
SWIFT Message
Explanation Format
Sender OELBATWW
Receiver AMRONL2A
Message Text
MT 734 Scope
This message is sent by the issuing bank to the bank from which it has received documents related to a
documentary credit. It may also be sent by the bank nominated to pay/accept/negotiate/incur a deferred
payment undertaking to the bank from which it has received documents.
It is used to advise the Receiver that the Sender considers the documents, as they appear on their face, not to be
in accordance with the terms and conditions of the credit and that, consequently, it refuses them for the
discrepancies stated. The Sender also provides the Receiver with details regarding the disposal of the
documents.
This message type may also be used for claiming a refund.
M = Mandatory, O = Optional
PRESENCE
Mandatory
DEFINITION
If the message is sent by the issuing bank, this field specifies the documentary credit number assigned by the
issuing bank.
If the message is sent by a bank other than the issuing bank, this field specifies either the documentary credit
number assigned by the issuing bank or another reference assigned by the Sender.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
PRESENCE
Mandatory
DEFINITION
This field specifies the reference which has been assigned by the presenting bank from which the documents
have been received.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
PRESENCE
Mandatory
DEFINITION
This field specifies the date of the covering letter under which the documents were sent, followed by the
currency code and amount of the drawing.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma ',' is mandatory and is
included in the maximum length. The number of digits following the comma must not exceed the maximum
number allowed for the specified currency (Error code(s): C03, T40, T43).
Currency in fields 32A, and 33a must be the same (Error code(s): C02).
PRESENCE
Optional
DEFINITION
This field specifies the charges claimed by the Sender, if any.
USAGE RULES
The structured line format may be used for bilaterally agreed codes.
Any code used in this field must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
PRESENCE
Conditional (see rule C1)
DEFINITION
This field contains the currency code and amount claimed, including charges, by the Sender of the message.
NETWORK VALIDATED RULES
In option A, Date must be a valid date expressed as YYMMDD (Error code(s): T50).
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma ',' is mandatory and is
included in the maximum length. The number of digits following the comma must not exceed the maximum
number allowed for the specified currency (Error code(s): C03, T40, T43).
Currency in fields 32A, and 33a must be the same (Error code(s): C02).
USAGE RULES
When the amount claimed has been debited, option A must be used, specifying the value date of the debit.
When reimbursement of the amount claimed is requested, option B must be used.
PRESENCE
Optional
DEFINITION
This field specifies the financial institution at which the amount claimed is to be remitted in favour of the
Sender.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28,
T29, T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more
information about BEIs. This error code applies to all types of BICs referenced in a FIN message including
SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations
(Error code(s): C05).
USAGE RULES
Where the message also represents a claim for refund, the absence of this field implies that the account
relationship between the Sender and the Receiver is to be used.
In addition to narrative text, structured text with the following line formats may be used:
PRESENCE
Optional
DEFINITION
This field specifies additional information for the Receiver.
USAGE RULES
The structured line format may be used for bilaterally agreed codes.
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
PRESENCE
Mandatory
DEFINITION
This field specifies the reason(s) for refusal of the document(s), eg, discrepancies. It may contain any type of
instruction or information.
PRESENCE
Mandatory
DEFINITION
This field contains information regarding the disposal of the documents.
CODES
One of the following codes may be used:
USAGE RULES
Any code must be between slashes and must appear at the beginning of a line.
Any details regarding the disposal of documents for which the above codes cannot be used, must include a text
reflecting the following wording:
• The issuing bank is holding the documents until it receives a waiver from the applicant and agrees to
accept it, or receives further instructions from the presenter prior to agreeing to accept a waiver (for
example, NOTIFY).
• The bank is acting in accordance with instructions previously received from the presenter (for example,
PREVINST).
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
MT 734 Examples
Narrative
Royal Bank of Scotland, London, receives documentary credit number DAE74568 from Nederlandsche
Middenstandsbank, Amsterdam, issued on July 21, 2003.
Royal Bank of Scotland acknowledges the receipt of the credit with its reference IMP124678, indicating that it
has added its confirmation to the credit. Its charges are to be settled at a later date.
(To review the MTs 700, 730, 720 relating to this documentary credit, please see the respective Example
sections)
Royal Bank of Scotland negotiates the credit, determines the documents are in order and debits the account it
services for Nederlandsche Middenstandsbank.
Nederlandsche Middenstandsbank, Amsterdam disagrees and claims a refund. It advises Royal Bank of
Scotland (September 21, 2003, reference IMP124678) that the documents presented have been refused owing
to discrepancies:
1. Partial shipment was effected.
2. Declaration that vessel is running regular line service not presented.
The documents are being held by Nederlandsche Middenstandsbank pending further instructions. Charges and
drawings totalling GBP 123,798 (Drawings of 123,675 + Cable 10 + Royal Bank of Scotland charges 95 +
Interest 18) are to be credited to Nederlandsche Middenstandsbank's account value September 27, 2003.
Information Flow
Sender Nederlandsche
(Issuing Bank) Middenstandsbank
Amsterdam
MT 734
SWIFT Message
Explanation Format
Sender NMBANL2A
Receiver RBOSGB2L
Message Text
Explanation Format
(1) The date of the covering letter of the received documents and the amount of the drawing, excluding charges
or deductions.
MT 740 Scope
This message is sent by the issuing bank to the reimbursing bank.
It is used to request the Receiver to honour claims for reimbursement of payment(s) or negotiation(s) under a
documentary credit.
The MT 740 authorises the reimbursing bank to debit the account of the Sender, or one of the Sender's
branches if so indicated, for reimbursements effected in accordance with the instructions in the MT 740.
O 59 Beneficiary [/34x] 6
4*35x
O 42a Drawee A or D 13
M = Mandatory, O = Optional
C2 When used, fields 42C and 42a must both be present (Error code(s): C90).
C3 Either fields 42C and 42a together, or field 42M alone, or field 42P alone may be present. No other
combination of these fields is allowed (Error code(s): C90).
C4 Either field 58a or 59, but not both, may be present (Error code(s): D84).
PRESENCE
Mandatory
DEFINITION
This field specifies the documentary credit number which has been assigned by the Sender.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
PRESENCE
Optional
DEFINITION
This field identifies the account which is to be debited for reimbursements.
USAGE RULES
The account specified may also be that of a branch of the Sender.
PRESENCE
Mandatory
DEFINITION
This field specifies the rules the reimbursement is subject to.
CODES
One of the following codes must be used (Error code(s): T59).
NOTURR The reimbursement under the credit is not subject to the ICC Uniform
Rules for Bank-to-Bank Reimbursement.
URR LATEST VERSION The reimbursement under the credit is subject to the version of the
ICC Uniform Rules for Bank-to-Bank Reimbursement, which is in
effect on the date of issue.
PRESENCE
Optional
DEFINITION
This field specifies the latest date for presentation under the documentary credit and the place where
documents may be presented.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).
USAGE RULES
This field should not be used to specify the latest date for presentation of a reimbursement claim or an expiry
date for the reimbursement authorisation.
PRESENCE
Conditional (see rule C4)
DEFINITION
This field identifies the drawer of the drafts to be drawn on the reimbursing bank, when the drawer is the
negotiating bank.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28,
T29, T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more
information about BEIs. This error code applies to all types of BICs referenced in a FIN message including
SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations
(Error code(s): C05).
USAGE RULES
Option A is the preferred option. Option D is only allowed when it is necessary to indicate a name and address
or to indicate negotiating bank under freely negotiable credits.
PRESENCE
Conditional (see rule C4)
DEFINITION
This field identifies the drawer of the drafts to be drawn on the reimbursing bank, when the drawer is the
beneficiary.
USAGE RULES
Account must not be present.
The name of the drawer is mandatory but can also be indicated as beneficiary in case of a transferable credit.
The drawer's address is optional.
PRESENCE
Mandatory
DEFINITION
This field contains the currency code and amount of the documentary credit.
NETWORK VALIDATED RULES
Currency must be a valid ISO4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma ',' is mandatory and is
included in the maximum length. The number of digits following the comma must not exceed the maximum
number allowed for the specified currency (Error code(s): C03, T40, T43).
USAGE RULES
Special information relative to the amount of the credit must be specified in field 39A Percentage Credit
Amount Tolerance, field 39B Maximum Credit Amount or field 39C Additional Amounts Covered.
PRESENCE
Conditional (see rule C1)
DEFINITION
This field specifies the tolerance relative to the documentary credit amount as a percentage plus and/or minus
that amount.
USAGE RULES
Tolerance 1 specifies a positive tolerance, Tolerance 2 specifies a negative tolerance.
PRESENCE
Conditional (see rule C1)
DEFINITION
This field further qualifies the documentary credit amount.
CODES
The following code must be used (Error code(s): T01):
PRESENCE
Optional
DEFINITION
This field specifies any additional amounts covered such as insurance, freight, interest, etc.
PRESENCE
Mandatory
DEFINITION
This field identifies the bank(s) authorised to claim reimbursement. It is followed by how the credit is available
eg, by payment, by acceptance, etc.
CODES
One of the following codes must be used in subfield 2, ie, 14x (Error code(s): T68):
BY ACCEPTANCE
BY DEF PAYMENT
BY MIXED PYMT
BY NEGOTIATION
BY PAYMENT
PRESENCE
Conditional (see rules C2 and C3)
DEFINITION
This field specifies the tenor of drafts to be drawn under the documentary credit.
PRESENCE
Conditional (see rules C2 and C3)
DEFINITION
This field identifies the drawee of the drafts to be drawn under the documentary credit.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28,
T29, T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more
information about BEIs. This error code applies to all types of BICs referenced in a FIN message including
SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations
(Error code(s): C05).
USAGE RULES
Party Identifier must not be present.
PRESENCE
Conditional (see rule C3)
DEFINITION
This field specifies the payment dates, amounts and/or method for their determination in a documentary credit
which is available by mixed payment.
PRESENCE
Conditional (see rule C3)
DEFINITION
This field specifies the payment date or method for its determination in a documentary credit which is
available by deferred payment only.
PRESENCE
Optional
DEFINITION
This field specifies by which party the reimbursing bank's charges are to be borne.
CODES
One of the following codes may be used (Error code(s): T08):
CLM Charges are for the account of the bank claiming reimbursement.
OUR Charges are to be borne by the Sender.
USAGE RULES
The absence of this field implies that charges will be borne by the Sender of this message.
PRESENCE
Optional
DEFINITION
This field may only be used to indicate whether acceptance and/or discount charges are applicable and, if so,
by which party these charges are to be borne.
CODES
One or more of the following codes may be used, followed by the currency code and amount:
USAGE RULES
Any code used in this field must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
In addition to narrative text, structured text with the following line formats may be used:
PRESENCE
Optional
DEFINITION
This field contains any specific instructions for the reimbursing bank. It may also be used to indicate if pre-
debit notification from the reimbursing bank to the issuing bank is required.
USAGE RULES
Any latest date for a reimbursement claim or an expiry date for the reimbursement authorisation should be
indicated in this field and not in field 31D.
When this field is used to indicate if pre-debit notification from the reimbursing bank to the issuing bank is
required, the number and type, ie, banking or calendar, of days within which the issuing bank has to be
notified should also be indicated.
The absence of specific instructions in this field concerning the claiming bank's charges implies that the
reimbursing bank is authorised to pay those charges.
The structured line format may be used for bilaterally agreed codes.
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
MT 740 Examples
Narrative
Skandinaviska Enskilda Banken issues its documentary credit number DC.IMP 3410/3444, to Generale Bank,
Brussels, the advising bank, including the following details:
The credit is available with Generale Bank, Brussels, by acceptance, with all charges to be paid by the
claiming bank.
At maturity of the draft, reimbursement is to be claimed at Manufacturers Hanover Trust Company, New York.
(To review the MT 700/701 issuing this documentary credit see MT 700 and MT 701 Issue of a documentary
credit.)
At the time the MT 700 is issued, Skandinaviska sends an MT 740 Authorisation to Reimburse to
Manufacturers Hanover Trust Company, New York, indicating that authorisation to reimburse is restricted to
the credit amount and the claiming bank's acceptance commission.
Information Flow
New York
SWIFT Message
Explanation Format
Sender ESSESESS
Receiver MAHAUS33
Message Text
MT 742 Scope
This message is sent by the paying/negotiating bank to the bank authorised to reimburse the Sender for its
payments/negotiations.
It is used to claim reimbursement of payment(s) or negotiation(s) under a documentary credit, as relevant to
the reimbursing bank.
M = Mandatory, O = Optional
PRESENCE
Mandatory
DEFINITION
This field contains the reference which has been assigned to the transaction by the Sender.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
PRESENCE
Mandatory
DEFINITION
This field specifies the documentary credit number which has been assigned by the bank which issued the
authorisation to reimburse (issuing bank).
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
PRESENCE
Optional
DEFINITION
This field specifies the date on which the issuing bank considers the documentary credit as being issued.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).
PRESENCE
Mandatory
DEFINITION
This field identifies the bank which has given the authorisation to reimburse.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28,
T29, T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more
information about BEIs. This error code applies to all types of BICs referenced in a FIN message including
SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations
(Error code(s): C05).
PRESENCE
Mandatory
DEFINITION
This field contains the currency code and amount of principal claimed by the Sender of the message. It is the
amount which is to be deducted from the outstanding balance of the documentary credit.
NETWORK VALIDATED RULES
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma ',' is mandatory and is
included in the maximum length. The number of digits following the comma must not exceed the maximum
number allowed for the specified currency (Error code(s): C03, T40, T43).
USAGE RULES
If the amount claimed is in a currency other than the currency of the credit, this field must indicate the
currency of the amount claimed. Details of the conversion and the amount deducted from the outstanding
balance of the documentary credit must be given in field 72.
6. Field 33B: Additional Amount Claimed as Allowed for in Excess of Principal Amount
FORMAT
Option B 3!a15d (Currency)(Amount)
PRESENCE
Optional
DEFINITION
This field specifies any additional amount(s) paid/negotiated on the strength of special authorisation, such as
specifications provided in field 39C of the MT 700.
NETWORK VALIDATED RULES
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma ',' is mandatory and is
included in the maximum length. The number of digits following the comma must not exceed the maximum
number allowed for the specified currency (Error code(s): C03, T40, T43).
USAGE RULES
If the amount claimed is in a currency other than the currency of the credit, then this field must indicate the
currency of the amount claimed.
Details of the conversion and the amount deducted from the outstanding balance of the documentary credit
must be given in field 72.
PRESENCE
Optional
DEFINITION
This field is used to identify charges which have been added or deducted by the Sender.
CODES
One or more of the following codes may be used, followed by the currency code and amount:
USAGE RULES
Any code used in this field must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
PRESENCE
Mandatory
DEFINITION
This field specifies the currency code and total amount claimed from the reimbursing bank.
NETWORK VALIDATED RULES
In option A, Date must be a valid date expressed as YYMMDD (Error code(s): T50).
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma ',' is mandatory and is
included in the maximum length. The number of digits following the comma must not exceed the maximum
number allowed for the specified currency (Error code(s): C03, T40, T43).
USAGE RULES
This field is the total of the amounts in fields 32B and 33B, and any charges specified in field 71B.
PRESENCE
Optional
DEFINITION
This field identifies the bank, if different from the Receiver, at which the Receiver is requested to remit the
total amount claimed, in favour of the Sender of this message, or its branch or affiliate bank, as specified in
field 58a.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28,
T29, T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more
information about BEIs. This error code applies to all types of BICs referenced in a FIN message including
SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations
(Error code(s): C05).
PRESENCE
Optional
DEFINITION
This field identifies the branch or affiliate bank of the Sender, in favour of which the total amount claimed is to
be transferred.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28,
T29, T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more
information about BEIs. This error code applies to all types of BICs referenced in a FIN message including
SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations
(Error code(s): C05).
USAGE RULES
If the account of a branch or an affiliate of the Sender is to be credited by the Receiver, this field will be used
to identify that branch or affiliate and its account serviced by the Receiver. In this case, field 57a should not be
present.
Additionally, where there are multiple account relationships between the Sender and the Receiver or the
account with bank, this field shall specify the Sender's SWIFT address, ie, option A, and in the account
number line, the specific account to be credited.
In addition to narrative text, structured text with the following line formats may be used:
PRESENCE
Optional
DEFINITION
This field contains instructions or additional information for the Receiver.
CODES
The following code may be used:
USAGE RULES
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
MT 742 Examples
Narrative
On 7 June 2003, Chemical Bank, New York, issues its documentary credit number IMP 693/70224 to
Deutsche Bank AG, Munich.
This credit is issued on behalf of Macy's, 724 Seventh Avenue, New York, in the amount of Euro 95,000. The
credit is in favour of Deutsche Steins AG, Muenchering, Munich, covering 10,000 beer mugs:
5,000 of model B337
5,000 of model B324
The credit expires on 7 September 2003.
The following documents are required:
Signed commercial invoice in quintuplicate
Forwarding Agent's Certificate of Receipt, showing goods addressed to Macy's
Reimbursement will be provided through Chemical Bank, Frankfurt.
Information Flow
Applicant Macy's
New York
50
SWIFT Messages
Explanation Format
Sender CHEMUS33
Receiver DEUTDEMM
Message Text
Explanation Format
Applicant :50:MACY'S
724 SEVENTH AVENUE
NEW YORK
Explanation Format
Sender CHEMUS33
Receiver CHEMDEFF
Message Text
Narrative
On 23 August 2003, Deutsche Bank, Munich, requests reimbursement from Chemical Bank, Frankfurt, asking
that it pay Deutsche Bank, Munich's account number 700-373473 at Deutsche Bank, Frankfurt.
The amount claimed includes the total credit amount of EUR 95,000 and EUR 200 charges for commission.
Information Flow
(MT 700)
(MT 740)
MT 742
Explanation Format
Sender DEUTDEMMA
Receiver CHEMDEFF
Message Text
Explanation Format
Charges :71B:/COMM/EUR200,
MT 747 Scope
This message is sent by the bank which has issued an authorisation to reimburse (issuing bank) to the
reimbursing bank.
It is used to inform the Receiver about amendments to the terms and conditions of the credit relevant to the
authorisation to reimburse.
The amendment is to be considered as part of the authorisation to reimburse.
M = Mandatory, O = Optional
PRESENCE
Mandatory
DEFINITION
This field contains the documentary credit number which has been assigned by the issuing bank.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
PRESENCE
Optional
DEFINITION
This field contains the reference number, assigned by the Receiver of the message.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
PRESENCE
Mandatory
DEFINITION
This field specifies the date on which the original authorisation to reimburse was sent.
PRESENCE
Conditional (see rule C1)
DEFINITION
This field specifies the new, ie, revised, expiry date for presentation under the documentary credit.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).
USAGE RULES
This field should not be used to specify a new latest date for presentation of a reimbursement claim or a new
expiry date for the reimbursement authorisation.
PRESENCE
Conditional (see rules C1, C3, and C5)
DEFINITION
This field contains the currency code and amount by which the documentary credit amount has been increased.
NETWORK VALIDATED RULES
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma ',' is mandatory and is
included in the maximum length. The number of digits following the comma must not exceed the maximum
number allowed for the specified currency (Error code(s): C03, T40, T43).
Currency in fields 32B, 33B and 34B must be the same (Error code(s): C02).
USAGE RULES
Currency of any increase in the credit must be in the same currency as that of the original credit.
PRESENCE
Conditional (see rules C1, C3, and C5)
DEFINITION
This field contains the currency code and amount by which the documentary credit amount has been
decreased.
PRESENCE
Conditional (see rules C1, C2, and C5)
DEFINITION
This field contains the currency code and total amount of the documentary credit after the amendment,
disregarding any drawings on the credit.
NETWORK VALIDATED RULES
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma ',' is mandatory and is
included in the maximum length. The number of digits following the comma must not exceed the maximum
number allowed for the specified currency (Error code(s): C03, T40, T43).
Currency in fields 32B, 33B and 34B must be the same (Error code(s): C02).
USAGE RULES
Currency of the new documentary credit must be in the same currency as that of the original credit.
PRESENCE
Conditional (see rules C1 and C4)
DEFINITION
Where the credit amount tolerance is being amended, this field specifies the new tolerance relative to the
documentary credit amount as a percentage plus and/or minus that amount.
USAGE RULES
Tolerance 1 specifies a positive tolerance, Tolerance 2 specifies a negative tolerance.
PRESENCE
Conditional (see rules C1 and C4)
DEFINITION
This field further qualifies the documentary credit amount.
CODES
The following code must be used (Error code(s): T01):
PRESENCE
Conditional (see rule C1)
DEFINITION
This field specifies amendments to any additional amounts covered such as insurance, freight, interest, etc.
In addition to narrative text, structured text with the following line formats may be used:
PRESENCE
Conditional (see rule C1)
DEFINITION
This field contains instructions or additional information for the Receiver.
CODES
The following code may be used:
CANC The reimbursement authorisation is cancelled for the unutilised portion of the credit to which it refers.
USAGE RULES
Any new latest date for a reimbursement claim or a new expiry date for the reimbursement authorisation
should be indicated in this field and not in field 31E.
When this field is used to indicate if pre-debit notification from the reimbursing bank to the issuing bank is
required, the number and type, ie, banking or calendar, of days within which the issuing bank must be notified
should also be indicated.
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
PRESENCE
Conditional (see rule C1)
DEFINITION
This field specifies amendments for which no other specific field has been included in the message.
MT 747 Examples
Narrative
On 17 May 2003, Skandinaviska Enskilda Banken issues its documentary credit number DC.IMP 3410/3444,
to Generale Bank, Brussels, the advising bank, and its authorisation to reimburse to Manufacturers Hanover
Trust Company, New York.
(To review the MT 700/701 issuing this documentary credit and the MT 740 authorising reimbursement,
please see the respective Example sections.)
On 21 May 2003, Skandinaviska Enskilda Banken notifies Manufacturers Hanover Trust Company, New York
of the following changes to the terms and conditions of the documentary credit:
• The expiry date of the credit has been extended to 30 September 2003.
• The amount of the credit has been increased by USD 3,250 to USD 34,750.
Information Flow
MT 747
New York
SWIFT Message
Explanation Format
Sender ESSESESS
Receiver MAHAUS33
Message Text
MT 750 Scope
This message is sent by the bank to which documents have been presented, to the issuing bank. It may also be
sent to a bank nominated to pay/accept/negotiate/incur a deferred payment undertaking.
It is used to advise the Receiver that documents which have been presented are not in accordance with the
terms and conditions of the credit.
The MT 750 is a request for authorisation to take up documents. Authorisation may be provided using an
MT 752 Authorisation to Pay, Accept or Negotiate; a negative reply to the request may be provided using an
MT 796 Answers.
M = Mandatory, O = Optional
PRESENCE
Mandatory
DEFINITION
This field contains the reference number which has been assigned by the Sender.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
PRESENCE
Mandatory
DEFINITION
If the message is sent to the issuing bank, this field contains the documentary credit number assigned by the
issuing bank.
If the message is sent to a bank other than the issuing bank, this field contains either the documentary credit
number assigned by the issuing bank, or another reference meaningful to the Receiver.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
PRESENCE
Mandatory
DEFINITION
This field contains the currency code and amount to be deducted from the outstanding balance of the
documentary credit.
NETWORK VALIDATED RULES
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma ',' is mandatory and is
included in the maximum length. The number of digits following the comma must not exceed the maximum
number allowed for the specified currency (Error code(s): C03).
Currency in fields 32B and 34B must be the same (Error code(s): C02).
PRESENCE
Optional
DEFINITION
This field specifies any additional amount(s) as allowed for in the credit, eg, insurance.
NETWORK VALIDATED RULES
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma ',' is mandatory and is
included in the maximum length. The number of digits following the comma must not exceed the maximum
number allowed for the specified currency (Error code(s): C03, T40, T43).
USAGE RULES
Currency may be different from the currency in field 32B. In this event, an explanation of any currency
conversion(s) must be specified in field 72.
PRESENCE
Optional
DEFINITION
This field specifies charges which have been deducted from the amount of the drawing.
CODES
One or more of the following codes may be used, followed by the currency code and amount:
USAGE RULES
Any code used in this field must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
PRESENCE
Optional
DEFINITION
This field specifies the charges which have been added to the amount of the drawing.
USAGE RULES
The structured format may be used with bilaterally agreed codes.
Any code used in this field must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
PRESENCE
Conditional (see rule C1)
DEFINITION
This field contains the currency code and total amount to be remitted to the Sender of the message.
NETWORK VALIDATED RULES
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma ',' is mandatory and is
included in the maximum length. The number of digits following the comma must not exceed the maximum
number allowed for the specified currency (Error code(s): C03, T40, T43).
Currency in fields 32B and 34B must be the same (Error code(s): C02).
PRESENCE
Optional
DEFINITION
This field identifies the bank at which any amounts due are to be remitted in favour of the Sender.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28,
T29, T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more
information about BEIs. This error code applies to all types of BICs referenced in a FIN message including
SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations
(Error code(s): C05).
USAGE RULES
If there is a direct account relationship in the currency of the claim between the Sender and the Receiver, the
absence of field 57a implies that this account relationship will be used in settlement of the amount to be
remitted to the Sender.
In addition to narrative text, structured text with the following line formats may be used:
PRESENCE
Optional
DEFINITION
This field contains instructions or additional information for the Receiver.
USAGE RULES
The structured line format may be used for bilaterally agreed codes.
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
PRESENCE
Mandatory
DEFINITION
This field specifies the discrepancy(ies) of the document(s).
USAGE RULES
The structured line format may be used for bilaterally agreed codes.
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
MT 750 Examples
Narrative
On 17 May 2003, Skandinaviska Enskilda Banken issues its documentary credit number DC.IMP 3410/3444,
to Generale Bank, Brussels, the advising bank, and its authorisation to reimburse to Manufacturers Hanover
Trust Company, New York.
On 21 May 2003, Skandinaviska Enskilda Banken notifies Generale Bank that the expiry date of the credit has
been extended to 30 September 2003 and the amount has been increased to USD 34,750.
(To review the MT 700/701 issuing this documentary credit and the MT 707 amending it see the respective
Example sections.)
On 23 August 2003, Generale Bank advises Skandinaviska Enskilda Banken that the documents have been
presented with the following discrepancies:
• Copy of consular invoice was not presented
• Copy letter from beneficiary's does not show original consular invoice airmailed to applicant.
Generale Bank requests authorisation (reference EXP98734) to accept a draft for the full credit amount due 18
September 2003.
Information Flow
MT 750
D0070018
SWIFT Message
Explanation Format
Sender GEBABEBB
Receiver ESSESESS
Message Text
MT 752 Scope
This message is sent by the issuing bank, or the nominated bank if so authorised by the issuing bank, to a
paying/accepting/negotiating bank in response to a request for authorisation to pay/accept/negotiate/incur a
deferred payment undertaking previously requested via an MT 750 Advice of Discrepancy or otherwise.
It is used to advise the Receiver that documents may be taken up, notwithstanding the discrepancies, provided
they are otherwise in order.
M = Mandatory, O = Optional
PRESENCE
Mandatory
DEFINITION
This field specifies the documentary credit number which has been assigned by the issuing bank.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
PRESENCE
Mandatory
DEFINITION
This field contains the reference number which has been assigned by the presenting bank (Receiver).
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
PRESENCE
Mandatory
DEFINITION
This field further identifies the purpose of the message.
CODES
One of the following codes must be used:
USAGE RULES
When code is REMITTED, field 33A must be present, specifying the value date of the remittance and the
amount.
PRESENCE
Mandatory
DEFINITION
This field specifies the date on which the advice of discrepancy was sent, either electronically or by mail.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).
PRESENCE
Optional
DEFINITION
This field contains the currency code and total amount advised by the presenting bank, eg, field 34B from the
MT 750.
NETWORK VALIDATED RULES
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma ',' is mandatory and is
included in the maximum length. The number of digits following the comma must not exceed the maximum
number allowed for the specified currency (Error code(s): C03, T40, T43).
Currency in fields 32B and 33a must be the same (Error code(s): C02).
PRESENCE
Optional
DEFINITION
This field is used to specify the charges which have been deducted, by the Sender of the message, from the
total amount advised.
CODES
One or more of the following codes may be used, followed by the currency code and amount:
USAGE RULES
Any code used in this field must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
PRESENCE
Conditional (see rule C1)
DEFINITION
This field specifies the currency code and net amount that was or will be remitted or is to be claimed, and
possibly a value date.
NETWORK VALIDATED RULES
In option A, Date must be a valid date expressed as YYMMDD (Error code(s): T50).
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma ',' is mandatory and is
included in the maximum length. The number of digits following the comma must not exceed the maximum
number allowed for the specified currency (Error code(s): C03, T40, T43).
Currency in fields 32B and 33a must be the same (Error code(s): C02).
USAGE RULES
When REMITTED is specified in field 23, option A must be used, specifying the value date on which the net
amount was or will be remitted.
When DEBIT is specified in field 23, option A must be used, specifying the value date on which the account
of the issuing bank is to be debited with the net amount.
PRESENCE
Optional
DEFINITION
Where required, this field specifies the account or branch of the Sender or another bank through which the
Sender will reimburse the Receiver.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28,
T29, T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more
information about BEIs. This error code applies to all types of BICs referenced in a FIN message including
SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations
(Error code(s): C05).
PRESENCE
Optional
DEFINITION
Where required, this field specifies the branch of the Receiver or another financial institution at which the
funds will be made available to the Receiver.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28,
T29, T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more
information about BEIs. This error code applies to all types of BICs referenced in a FIN message including
SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations
(Error code(s): C05).
USAGE RULES
In those cases where funds will be made available to the Receiver at its branch or another bank, through a
financial institution other than the one indicated in field 53a, this financial institution, ie, the intermediary
institution, should be specified in field 54a. Field 72 must in this case contain the code RCB (Receiver's
Correspondent Bank), followed by the BIC of the Receiver's branch or other bank.
In addition to narrative text, structured text with the following line formats may be used:
Line 1 /8c/[additional information]
Lines 2-6 [//continuation of additional information]
or
[/8c/[additional information]]
PRESENCE
Optional
DEFINITION
This field contains instructions or additional information for the Receiver.
CODES
The following code may be used:
USAGE RULES
The structured line format may also be used for bilaterally agreed codes.
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
When there is an intermediary bank between the Sender's and Receiver's correspondent, this field should
contain the code RCB, followed by the BIC code (or narrative name and address) of the Receiver's
correspondent. Remark that the code RCB may only be used if both fields 53a and 54a are present.
This field may include ERI, as specified in the chapter entitled "Euro - Impact on SWIFT Message Standards".
MT 752 Examples
Narrative
On 7 June 2003, Chemical Bank, New York issues its documentary credit number IMP 693/70224 to Deutsche
Bank, Munich.
(To review the details of this credit, see the Example section of MT 742.)
The mugs were delivered to the forwarding agent and a sight draft was presented to Deutsche Bank, Munich.
On 15 August 2003, after examining the documents, Deutsche Bank sends an MT 750 Advice of Discrepancy
to Chemical Bank, New York, advising that the documents have been presented with the following
discrepancy:
• Three (3) versus five (5) commercial invoices were presented.
Deutsche Bank, Munich, requests authorisation (Reference DIS93708) to pay the draft for the full credit
amount.
Information Flow
MT 750
D0070019
SWIFT Message
Explanation Format
Sender DEUTDEMM
Receiver CHEMUS33
Message Text
Narrative
On 16 August 2003, Chemical Bank, New York, sends Deutsche Bank, Munich an MT 752 Authorisation to
Pay, Accept or Negotiate, advising it to pay and accept the draft.
Information Flow
(MT 750)
MT 752
D0070020
SWIFT Message
Explanation Format
Sender CHEMUS33
Receiver DEUTDEMM
Message Text
Narrative
On 17 May 2002, Skandinaviska Enskilda Banken issues its documentary credit number DC.IMP 3410/3444
to Generale Bank, Brussels.
On 23 August 2003, Generale Bank request authorisation to accept the draft for the full credit amount.
(To review the MT 700, 701, 707 and 750 relating to this documentary credit, see the respective Example
sections.)
On 25 August 2003, Skandinaviska Enskilda Banken authorises Generale Bank to accept the draft.
Information Flow
(MT 750)
MT 752
D007D021
SWIFT Message
Explanation Format
Sender ESSESESS
Receiver GEBABEBB
Message Text
Narrative
On the maturity date of the draft, Generale Bank requests Manufacturers Hanover Trust Company to credit its
account in reimbursement.
Commission charges of USD 36 have been added to the total amount of the credit.
Information Flow
(MT 700)
MT 742
D0070022
New York
SWIFT Message
Explanation Format
Sender GEBABEBB
Receiver MAHAUS33
Message Text
Charges :71B:/COMM/USD36,
MT 754 Scope
This message is sent by the paying, accepting or negotiating bank, or the bank incurring a deferred payment
undertaking, to the issuing bank. It may also be sent by the bank to which documents have been presented to a
bank that has been nominated to pay/accept.
It is used to advise the Receiver that documents were presented in accordance with the credit terms and are
being forwarded as instructed.
The MT 754 may also be used:
• for the settlement of the payment/negotiation
• as a pre-notification of a reimbursement claim from the claiming bank to the issuing bank
• as a pre-debit notification from the claiming bank to the issuing bank.
Note:Where a pre-debit notification from the reimbursing bank to the issuing bank is required, banks
should use the MT 799 Free Format message, specifying the future date of debit.
M = Mandatory, O = Optional
PRESENCE
Mandatory
DEFINITION
This field contains the reference number which has been assigned by the Sender.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
PRESENCE
Mandatory
DEFINITION
If the MT 754 is sent to the Issuing Bank, this field contains the documentary credit number assigned by the
issuing bank.
If the message is sent to a bank other than the issuing bank, this field contains either the documentary credit
number assigned by the issuing bank, or another reference meaningful to the Receiver.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
PRESENCE
Mandatory
DEFINITION
This field contains the currency code and amount which has been paid, accepted or negotiated by the Sender.
NETWORK VALIDATED RULES
In option A, Date must be a valid date expressed as YYMMDD (Error code(s): T50).
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma ',' is mandatory and is
included in the maximum length. The number of digits following the comma must not exceed the maximum
number allowed for the specified currency (Error code(s): C03, T40, T43).
Currency in fields 32a and 34a must be the same (Error code(s): C02).
USAGE RULES
The amount will be deducted from the outstanding balance of the documentary credit.
PRESENCE
Optional
DEFINITION
This field specifies the currency code and amount of any additional amounts allowed for in the credit, such as
insurance.
NETWORK VALIDATED RULES
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma ',' is mandatory and is
included in the maximum length. The number of digits following the comma must not exceed the maximum
number allowed for the specified currency (Error code(s): C03, T40, T43).
USAGE RULES
Currency may be different from that in field 32a. When this is the case, an explanation of any currency
conversion(s) must be provided in field 72 (or field 77A).
PRESENCE
Optional
DEFINITION
This field is used to specify the charges which have been deducted from the amount paid/accepted/negotiated.
CODES
One or more of the following codes may be used, followed by the currency code and amount:
USAGE RULES
Any code used in this field must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
PRESENCE
Optional
DEFINITION
This field is used to specify any charges which have been added to the amount paid/accepted/negotiated.
CODES
One or more of the following codes may be used:
USAGE RULES
Any code used in this field must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
PRESENCE
Optional
DEFINITION
This field specifies the currency code and total amount claimed or to be remitted, and possibly a value date.
NETWORK VALIDATED RULES
In option A, Date must be a valid date, expressed as YYMMDD (Error code(s): T50).
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma ',' is mandatory and is
included in the maximum length. The number of digits following the comma must not exceed the maximum
number allowed for the specified currency (Error code(s): C03, T40, T43).
Currency in fields 32a and 34a must be the same (Error code(s): C02).
USAGE RULES
Depending on how the MT 754 is used, the following table provides additional information about the use of
this field:
PRESENCE
Conditional (see rule C2)
DEFINITION
This field specifies the bank from which the Sender has claimed reimbursement, in accordance with the terms
of the documentary credit. This may be a branch of the Sender or the Receiver or an entirely different bank.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28,
T29, T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more
information about BEIs. This error code applies to all types of BICs referenced in a FIN message including
SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations
(Error code(s): C05).
PRESENCE
Conditional (see rule C2)
DEFINITION
This field identifies the bank at which the Receiver is requested to remit the total amount claimed in favour of
the Sender of this message, or its branch or affiliate bank as specified in field 58a.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28,
T29, T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more
information about BEIs. This error code applies to all types of BICs referenced in a FIN message including
SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations
(Error code(s): C05).
PRESENCE
Optional
DEFINITION
This field identifies the branch or affiliate bank of the Sender, in favour of which the total amount claimed is to
be transferred.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28,
T29, T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more
information about BEIs. This error code applies to all types of BICs referenced in a FIN message including
SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations
(Error code(s): C05).
USAGE RULES
If the account of a branch or an affiliate of the Sender is to be credited by the Receiver, this field will be used
to identify that branch or affiliate and its account serviced by the Receiver. In this case, field 57a should not be
present.
Additionally, in those cases where there are multiple account relationships between the Sender and the
Receiver or the account with bank, this field shall specify the Sender's SWIFT BIC, ie, option A, and, in the
account number line, the specific account to be credited.
In addition to narrative text, structured text with the following line formats may be used:
Line 1 /8c/[additional information]
Lines 2-6 [//continuation of additional information]
or
[/8c/[additional information]]
PRESENCE
Conditional (see rule C1)
DEFINITION
This field contains additional information for the Receiver or account with bank.
CODES
One or more of the following codes may be used:
USAGE RULES
This field may include ERI, as specified in the chapter entitled "Euro - Impact on SWIFT Message Standards".
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
PRESENCE
Conditional (see rule C1)
DEFINITION
This field contains additional information for which no other field has been defined within the message.
USAGE RULES
This field is to be used instead of field 72, only when that field is not sufficient.
The structured line format may be used for bilaterally agreed codes.
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
MT 754 Examples
Narrative
On 17 August 2003, Deutsche Bank, Munich, pays Deutsche Steins EUR 95,000 provided under the terms of
documentary credit number IMP 693/70224 issued by Chemical Bank, New York.
(To review the details of this credit, see the Example sections of the MTs 742 and 752.)
On the same day, Deutsche Bank advises Chemical Bank, New York of the payment and forwarding of
documents, indicating it has claimed reimbursement for the credit amount and its commission of EUR 200.
Deutsche Bank, Munich, sends an MT 754 Advice of Payment/Acceptance/Negotiation (reference
CL934372).
Information Flow
(MT 740)
Receiver Chemical Bank
(Issuing Bank) New York
D0070023
SWIFT Message
Explanation Format
Sender DEUTDEMM
Receiver CHEMUS33
Message Text
MT 756 Scope
This message is sent by the issuing bank to the bank from which it has received documents or by the
reimbursing bank to the bank from which it has received a reimbursement claim. It may also be sent by the
bank nominated to pay/accept/negotiate/incur a deferred payment undertaking to the bank from which it has
received documents.
It is used to advise the Receiver about reimbursement or payment, to that bank, for a drawing under a
documentary credit for which no specific reimbursement instructions or payment provisions were provided.
The account relationship between the Sender and the Receiver is used unless otherwise expressly stated in the
message.
M = Mandatory, O = Optional
PRESENCE
Mandatory
DEFINITION
When this message is sent by the Issuing Bank, or the bank nominated to pay/accept/negotiate, this field
specifies the documentary credit number which has been assigned by the issuing bank.
In all other cases this field contains a reference meaningful to the Sender.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
PRESENCE
Mandatory
DEFINITION
This field contains the reference number which has been assigned by the presenting bank.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
USAGE RULES
When the MT 756 is being sent to the presenting bank by the reimbursing bank, this field should contain the
contents of field 20 Claiming Bank's Reference of the MT 742 Reimbursement Claim or an equivalent
reference.
PRESENCE
Mandatory
DEFINITION
This field contains the currency code and total amount claimed by the bank from which documents have been
received.
NETWORK VALIDATED RULES
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma ',' is mandatory and is
included in the maximum length. The number of digits following the comma must not exceed the maximum
number allowed for the specified currency (Error code(s): C03, T40, T43).
Currency in fields 32B and 33A must be the same (Error code(s): C02).
PRESENCE
Mandatory
DEFINITION
This field specifies the value date, currency code and net amount to be reimbursed or paid.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma ',' is mandatory and is
included in the maximum length. The number of digits following the comma must not exceed the maximum
number allowed for the specified currency (Error code(s): C03, T40, T43).
Currency in fields 32B and 33A must be the same (Error code(s): C02).
USAGE RULES
If there is a difference between this amount and the amount specified in field 32B, this must be explained in
field 72.
PRESENCE
Optional
DEFINITION
Where required, this field specifies the account or branch of the Sender or another financial institution through
which the Sender will reimburse the Receiver.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28,
T29, T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more
information about BEIs. This error code applies to all types of BICs referenced in a FIN message including
SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations
(Error code(s): C05).
USAGE RULES
The absence of fields 53a and/or 54a implies that the single direct account relationship between the Sender
and Receiver, in the currency of the credit, will be used.
PRESENCE
Optional
DEFINITION
Where required, this field specifies the branch of the Receiver or another financial institution at which the
funds will be made available to the Receiver.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28,
T29, T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more
information about BEIs. This error code applies to all types of BICs referenced in a FIN message including
SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations
(Error code(s): C05).
USAGE RULES
The absence of fields 53a and/or 54a implies that the single direct account relationship between the Sender
and Receiver, in the currency of the credit, will be used.
In those cases where funds will be made available to the Receiver at its branch or another bank, through a
financial institution other than the one indicated in field 53a, this financial institution, ie, the intermediary
institution, should be specified in field 54a. Field 72 must in this case contain the code RCB (Receiver's
Correspondent Bank), followed by the BIC of the Receiver's branch or other bank.
In addition to narrative text, structured text with the following line formats may be used:
PRESENCE
Optional
DEFINITION
This field contains additional information for the Receiver.
CODES
The following code may be used:
USAGE RULES
The structured line format may also be used for bilaterally agreed codes.
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
When there is an intermediary bank between the Sender's and Receiver's correspondent, this field should
contain the code RCB, followed by the BIC code (or narrative name and address) of the Receiver's
correspondent. Note that, the code RCB may only be used if both fields 53a and 54a are present.
This field may include ERI, as specified in the chapter entitled "Euro - Impact on SWIFT Message Standards".
MT 756 Examples
Narrative
On 23 September 2003, Midland Bank, London, issues its documentary credit number DC86411891 to The
Fuji Bank, Osaka.
This credit is issued on behalf of Harrod's, Knightsbridge, London, in the amount of Pounds Sterling 38,000.
The credit is in favour of Tsashubi, 11-4 Kyodan-ku, Osaka covering 250 hand-painted bamboo screens:
100 3H number 6481
150 Single number 2219
The credit expires on 23 December 2003.
The following documents are required:
Signed commercial invoice in quadruplicate
Forwarding Agent's Certificate of Receipt, showing goods addressed to Harrod's
Information Flow
Applicant Harrod's
London
50
MT 700
Beneficiary Tsashubi
Osaka
59
D0070024
SWIFT Message (MT 700)
Explanation Format
Sender MIDLGB22
Receiver FUJIJPJS
Message Text
Applicant :50:HARROD'S
KNIGHTSBRIDGE
LONDON
Beneficiary :59:TSASHUBI
11-4 KYODAN-KU
OSAKA
Explanation Format
Narrative
On 6 November 2003, Midland Bank, London, advises The Fuji Bank, Osaka, that full reimbursement will be
credited to them, for payment of the documentary credit plus charges, at the Fuji Bank Limited's London
branch.
Information Flow
SWIFT Message
Explanation Format
Sender MIDLGB22
Receiver FUJIJPJS
Message Text
Narrative
Midland Bank, London sends a payment request to Fuji Bank Limited, London, in cover of the documentary
credit.
Information Flow
MT 202
SWIFT Message
Explanation Format
Sender MIDLGB22
Receiver FUJIGB2L
Message Text
The following table lists all Guarantee message types defined in Category 7.
For each message type, there is a short description, an indicator whether the message type requires
authentication (Y or N), the maximum message length for input (2,000 or 10,000 characters) and whether the
use of the message requires registration with SWIFT for use in a message user group (Y or N).
769 Advice of Reduction or Advises that a bank has been released Y 2,000 N
Release of its liability for a specified amount
under its guarantee
Note: A Message User Group (MUG), for the purposes of this book, is a group of users who have voluntarily
agreed to support the specified message type and have registered with SWIFT to send or receive the
specified message type. These messages are indicated in the preceding table in the column MUG.
Registration is free of charge. To register to use one or more message types, submit a registration request
(Register to a Message User Group) through www.swift.com. To withdraw from a MUG, use the
Deregister from a Message User Group request.
These forms are available on www.swift.com > Ordering & Support > Ordering.
To get the list of other members of a particular MUG, send an MT 999 to the Customer Implementation
team (SWHQBEBBCOS).
MT 760 Guarantee
MT 760 Scope
This message is sent between banks involved in the issuance of a guarantee.
It is used to issue a guarantee or to request the Receiver to issue a guarantee.
O 30 Date 6!n 4
M = Mandatory, O = Optional
PRESENCE
Mandatory
DEFINITION
This field specifies the number of this message in the series of messages sent for a guarantee, and the total
number of messages in the series.
PRESENCE
Mandatory
DEFINITION
When the message is sent to issue a guarantee, this field must specify the guarantee number.
When the message is sent to request the Receiver to issue a guarantee, this field must contain the reference of
the request, as assigned by the Sender.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
PRESENCE
Mandatory
DEFINITION
This field further identifies the purpose of the message.
CODES
One of the following codes must be used:
PRESENCE
Optional
DEFINITION
When the message is sent to issue a guarantee, this field specifies the issue date of the guarantee.
When the message is sent to request the Receiver to issue a guarantee, this field specifies the date of the
request.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).
USAGE RULES
In the absence of this field, the issue date or request date is the date on which the message was sent.
PRESENCE
Mandatory
DEFINITION
This field specifies the rules the guarantee is subject to.
CODES
Type must contain one of the following codes (Error code(s): T60):
PRESENCE
Mandatory
DEFINITION
This field contains all terms, conditions and details of the guarantee.
In addition to narrative text, structured text with the following line formats may be used:
Line 1 /8c/[additional information]
Lines 2-6 [//continuation of additional information]
or
[/8c/[additional information]]
PRESENCE
Optional
DEFINITION
This field contains additional information for the Receiver.
CODES
One or more of the following codes may be used:
BENCON The Receiver is requested to advise the beneficiary's acceptance or non-acceptance of the
terms and conditions contained in the guarantee.
PHONBEN Please advise/contact the beneficiary by phone.
TELEBEN Please advise/contact the beneficiary by the most efficient means of telecommunication.
USAGE RULES
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
MT 760 Examples
Narrative
Video, Inc, San Francisco, has signed a contract with Sound and Image Productions, London, regarding the
production of the film The Video Story.
The contract is in US Dollars.
Video, Inc. banks with Swiss Bank Corporation, San Francisco.
Sound and Image Productions banks with National Westminster Bank Plc., London.
On 1 May 2002, National Westminster Bank Plc, London, issues a guarantee in favour of Video, Inc., and
advises Swiss Bank Corporation, San Francisco.
The content of the guarantee is as follows:
Issue of Performance Guarantee no. PG8761234
We, National Westminster Bank, London, hereby undertake to pay to you any sum or sums not exceeding an
aggregate of USD 27,240 (United States Dollars twenty seven thousand two hundred and forty), representing
5% of the total order/contract price on receipt by us at this office of your first demand on us in writing,
complying with all the requirements hereof, quoting our reference overseas division guarantee No.
PG8761234. The signatures appearing thereon to be duly confirmed by your bankers, stating the amount
payable and that Sound and Image have failed to perform the terms of the order/contract No. S556VSF for the
supply of a film The Video Story.
Always provided that
1. This undertaking is personal to you and is not assignable.
2. Our liability hereunder shall be limited to a sum or sums not exceeding in aggregate USD 27,240 (United
States Dollars twenty seven thousand two hundred and forty).
3. Our liability is valid as at 1 June 2002 and shall expire on 31 May 2003 except in respect of any written
demands for payment complying with all the requirements hereof received by us at this office on or before
31 May 2003, after which date this undertaking shall become null and void whether returned to us or not.
4. Our liability under this undertaking shall be reduced by any amounts demanded in accordance with the
terms hereof.
5. This undertaking shall be governed by and construed according to the Laws of England, the Courts of
which country shall have sole jurisdiction to adjudicate on any and all claims directly or indirectly relating
hereto and your acceptance of our undertaking shall be your confirmation that you submit to the
jurisdiction of the Courts of England in this regard.
Information Flow
MT 760
Video, Inc.
San Francisco
D0070027
SWIFT Message
* Format
1 NWBKGB2L
2 760
3 SBCOUS66
Message Text
4 :27:1/1
5 :20:PG8761234
6 :23:ISSUE
7 :30:020501
8 :40C:NONE
*
1. Sender of the message
2. Message type
3. Receiver of the message
MT 767 Scope
This message is sent by a bank which has issued a guarantee to the bank to which the guarantee was issued. It
may also be sent by a bank which has requested the issuance of a guarantee to the bank to which the request
for a guarantee was sent.
It is used to amend or request the amendment of the guarantee.
O 30 Date 6!n 5
M = Mandatory, O = Optional
PRESENCE
Mandatory
DEFINITION
This field specifies the number of this message in the series of messages sent for a guarantee, and the total
number of messages in the series.
PRESENCE
Mandatory
DEFINITION
This field contains a reference assigned by the Sender to unambiguously identify the message.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
PRESENCE
Mandatory
DEFINITION
If the Receiver of this message has previously sent an MT 768 Acknowledgement of a Guarantee Message or
its equivalent, this field contains the contents of field 20 Transaction Reference Number of the
acknowledgement.
If no acknowledgement has been previously received, this field will contain a reference which is meaningful to
the Receiver, eg, the guarantee number.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
USAGE RULES
If no meaningful reference is available, the code NONREF must be used.
PRESENCE
Mandatory
DEFINITION
This field further identifies the purpose of the message.
CODES
One of the following codes must be used:
ISSUE The message is an amendment to a guarantee which the Sender previously issued.
REQUEST The message is requesting the amendment to a guarantee which the Sender previously
requested to be issued.
PRESENCE
Optional
DEFINITION
When the message is sent to amend a guarantee, this field specifies the date of the amendment.
When the message is sent to request the Receiver to amend a guarantee, this field specifies the date of the
request for the amendment.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).
USAGE RULES
In the absence of this field, the amendment date or request for amendment date of the guarantee is the date on
which this MT 767 was sent.
PRESENCE
Optional
DEFINITION
This field specifies the number which identifies this amendment.
USAGE RULES
This number should be the latest in the series of all amendments made, regardless of the means by which
previous amendments were sent.
PRESENCE
Mandatory
DEFINITION
When the message is sent to amend a guarantee, this field must specify the original issue date of the guarantee.
When the message is sent to request the Receiver to amend a guarantee, this field must specify the original
date of the request to issue the guarantee.
NETWORK VALIDATED RULES
Date must be a valid date expressed as YYMMDD (Error code(s): T50).
PRESENCE
Mandatory
DEFINITION
This field specifies all amended terms, conditions and details of the guarantee.
CODES
The following code may be used:
USAGE RULES
The terms and conditions of the original guarantee which are not mentioned in this field, remain the same.
In addition to narrative text, structured text with the following line formats may be used:
PRESENCE
Optional
DEFINITION
This field contains additional information for the Receiver.
CODES
One or more of the following codes may be used:
BENCON The Receiver is requested to advise the beneficiary's acceptance or non-acceptance of the
terms and conditions contained in the guarantee.
PHONBEN Please advise/contact the beneficiary by phone.
TELEBEN Please advise/contact the beneficiary by the most efficient means of telecommunication.
USAGE RULES
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
MT 767 Examples
Narrative
On 15 May 2002, National Westminster Bank, London, sends Swiss Bank Corporation, San Francisco, an
amendment (reference AG5559823) to its issue of Performance Guarantee No. PG8761234.
(To review the guarantee, see the Example section of the MT 760.)
The amendment states:
"We hereby advise you of the amendments made to the referenced performance guarantee.
Our liability is valid as at 1 July 2002 and shall expire on 30 June 2003.
All other terms and conditions remain unchanged as agreed upon in the initial issue of this guarantee.
Please confirm the beneficiary's acceptance of this amendment."
Information Flow
(MT 760)
MT 767
Video, Inc.
San Francisco
D0070028
SWIFT Message
Explanation Format
Sender NWBKGB2L
Receiver SBCOUS66
Message Text
TRN :20:AG5559823
Explanation Format
(1) The reference meaningful to the Receiver, which is the reference initially assigned to the issue of the
guarantee.
(2) Further identification of the purpose of the message - this message is an amendment to a guarantee
originally issued by the Sender.
(3) The Sender is requesting that the beneficiary confirm acceptance of the terms of the amendment.
MT 768 Scope
This message type is sent by a bank which has received a guarantee to the bank which issued the guarantee or
an amendment thereto. It may also be sent by a bank which has been requested to issue a guarantee to the bank
which requested the guarantee or an amendment thereto.
It is used to acknowledge receipt of any message relating to a guarantee and, where applicable, to indicate that
action has been taken according to the instructions.
The Sender's charges may also be accounted for in this message.
M = Mandatory, O = Optional
PRESENCE
Mandatory
DEFINITION
This field specifies the reference assigned by the Sender to unambiguously identify the message.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
PRESENCE
Mandatory
DEFINITION
This field contains the reference of the message which is being acknowledged.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
USAGE RULES
If the related message was not sent via SWIFT, this field contains a reference which is meaningful to the
Receiver.
If no such reference is available, this field must contain the code NONREF.
PRESENCE
Conditional (see rule C1)
DEFINITION
This field identifies, where necessary, the account which is used for settlement of charges.
USAGE RULES
The absence of fields 25 and 57a means that the account relationship between the Sender and the Receiver in
the currency of the charges is to be used for settlement.
PRESENCE
Mandatory
DEFINITION
This field specifies the date on which the message being acknowledged was sent.
PRESENCE
Conditional (see rule C3)
DEFINITION
This field specifies the currency code and total amount of charges claimed by the Sender of the message.
NETWORK VALIDATED RULES
In option D, Date must be a valid date expressed as YYMMDD (Error code(s): T50).
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma ',' is mandatory and is
included in the maximum length. The number of digits following the comma must not exceed the maximum
number allowed for the specified currency (Error code(s): C03, T40, T43).
USAGE RULES
If the Sender services an account for the Receiver in the currency of the charges, and this account has been
debited in reimbursement, Option D must be used, specifying the value date of the debit.
In all other cases, Option B must be used.
PRESENCE
Conditional (see rules C1 and C2)
DEFINITION
This field specifies the bank at which the Sender wishes to receive credit for charges claimed in field 32a.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28,
T29, T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more
information about BEIs. This error code applies to all types of BICs referenced in a FIN message including
SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations
(Error code(s): C05).
PRESENCE
Optional
DEFINITION
This field contains the specific details of commission and charges claimed by the Sender in field 32a.
CODES
One or more of the following codes may be used, followed by the currency code and amount:
USAGE RULES
Any code used in this field must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
In addition to narrative text, structured text with the following line formats may be used:
PRESENCE
Optional
DEFINITION
This field contains additional information for the Receiver.
CODES
One of the following codes may be used.
USAGE RULES
This field may be used to advise the beneficiary's acceptance or non-acceptance of the terms and conditions of
a guarantee or an amendment thereof.
This field may include ERI, as specified in the chapter entitled "Euro - Impact on SWIFT Message Standards".
The structured line format may be used for bilaterally agreed codes.
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
MT 768 Examples
Narrative
On 20 May 2002, Swiss Bank Corporation, San Francisco, acknowledges to National Westminster Bank Plc,
London (reference 1PG8761234), receipt of the amendment to the issue of Performance Guarantee No.
PG8761234, as well as the beneficiary's acceptance of the amendment.
(To review the guarantee amendment for this example, see the Example section of the MT 767.)
Information Flow
Video, Inc.
San Francisco
MT 768
D0070029
SWIFT Message
Explanation Format
Sender SBCOUS66
Receiver NWBKGB2L
Message Text
TRN :20:1PG8761234
Example 2: Guarantee
Narrative
Shining Star Jewellers, New York, has signed a contract with Fine Gems Company, Antwerp, covering the
purchase of 1,000 carats of quality diamonds.
The contract is in Belgian Francs.
Shining Star Jewellers banks with Bank Leumi Trust Co. of New York.
Fine Gems Company banks with Kredietbank, N.V., Antwerp.
On 10 February 2003, Bank Leumi Trust Co. of New York issues a guarantee in favour of Fine Gems
Company, and advises Kredietbank, N.V., Antwerp.
The content of the guarantee is as follows:
Issue of Performance Guarantee No. PG378556
We, Bank Leumi Trust Company of NY, New York, hereby undertake to pay to Fine Gems Company,
Antwerp, any sum or sums not exceeding an aggregate of EUR 20,000,000 (Euro twenty million),
representing the purchase of 1000 VVVF diamonds, on receipt by us at this office of your first demand on us
in writing, complying with all the requirements hereof, quoting our reference Performance Guarantee No.
PG378556. The signatures appearing thereon to be duly confirmed by your bankers.
Always provided that:
• This undertaking is personal to you and is not assignable.
• Our liability hereunder shall be limited to a sum or sums not exceeding in aggregate EUR 20,000,000
(Euro twenty million)
• Our liability is valid as at 10 February 2003 and shall expire on 10 April 2003 after which date this
undertaking shall become null and void.
• This undertaking shall be governed by and construed according to the Laws of the State of New York,
U.S.A., which shall have sole jurisdiction to adjudicate on any and all claims directly or indirectly relating
hereto and your acceptance of our undertaking shall be your confirmation that you submit to the
jurisdiction of the Courts of the State of New York.
Information Flow
MT 760
Receiver Kredietbank
Antwerp
D0070030
SWIFT Message MT 760
* Format
1 LUMIUS3N
2 760
3 KREDBE22
4 :27:1/1
Message Text
5 :20:PG378556
6 :23:ISSUE
7 :30:030210
* Format
8 :77C:WE, BANK LEUMI TRUST COMPANY OF NY, NEW YORK, HEREBY UNDERTAKE
TO PAY TO FINE GEMS COMPANY, ANTWERP, ANY SUM OR SUMS NOT EXCEEDING
AN AGGREGATE OF EUR 20,000,000 (EURO TWENTY MILLION), REPRESENTING
THE PURCHASE OF 1000 VVVF DIAMONDS, ON RECEIPT BY US AT THIS OFFICE
OF YOUR FIRST DEMAND ON US IN WRITING, COMPLYING WITH ALL THE
REQUIREMENTS HEREOF, QUOTING OUR REFERENCE PERFORMANCE GUARANTEE
NO. PG378556. THE SIGNATURES APPEARING THEREON TO BE DULY CONFIRMED
BY YOUR BANKERS.
ALWAYS PROVIDED THAT:
1. THIS UNDERTAKING IS PERSONAL TO YOU AND IS NOT ASSIGNABLE.
2. OUR LIABILITY HEREUNDER SHALL BE LIMITED TO A SUM OR SUMS NOT
EXCEEDING IN AGGREGATE EUR 20,000,000 (EURO TWENTY MILLION).
3. OUR LIABILITY IS VALID AS AT 10 FEBRUARY 2003 AND SHALL EXPIRE
ON 10 APRIL 2003 AFTER WHICH DATE THIS UNDERTAKING SHALL BECOME
NULL AND VOID.
4. THIS UNDERTAKING SHALL BE GOVERNED BY AND CONSTRUED.
5. ACCORDING TO THE LAWS OF THE STATE OF NEW YORK, USA, WHICH SHALL
HAVE SOLE JURISDICTION TO ADJUDICATE ON ANY AND ALL CLAIMS
DIRECTLY OR INDIRECTLY RELATING HERETO AND YOUR ACCEPTANCE OF
OUR UNDERTAKING SHALL BE YOUR CONFIRMATION THAT YOU SUBMIT TO
THE JURISDICTION OF THE COURTS OF THE STATE OF NEW YORK.
Narrative
On 11 February 2003, Kredietbank forwards the guarantee to its customer, Fine Gems Company. On
acceptance of the terms of the guarantee by Fine Gems, Kredietbank acknowledges to Bank Leumi and
requests that its advising commission of EUR 4,000 be paid to its account at Kredietbank's main office in
Brussels.
Information Flow
Sender Kredietbank
Antwerp
MT 768
D0070031
Kredietbank
Brussels
SWIFT Message
Explanation Format
Sender KREDBE22
Receiver LUMIUS3N
Message Text
TRN :20:GA7326
(3) Sender to receiver information, indicating beneficiary acceptance of the terms and conditions of the
guarantee.
MT 769 Scope
This message is sent by a bank which has received a guarantee to the bank which has issued the guarantee. It
may also be sent by a bank which has been requested to issue a guarantee to the bank which requested the
issuance of the guarantee.
It is used to advise the Receiver that it has been released of all liability for the amount specified in field 33B or
field 39C.
The Sender's charges may also be accounted for in this message.
M = Mandatory, O = Optional
PRESENCE
Mandatory
DEFINITION
This field contains the reference assigned by the Sender to unambiguously identify the message.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
PRESENCE
Mandatory
DEFINITION
This field contains the reference number of the guarantee or request for the issuance of a guarantee to which
this message is related.
NETWORK VALIDATED RULES
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//' (Error code(s):
T26).
USAGE RULES
If the related message was not sent via SWIFT, this field contains a reference which is meaningful to the
Receiver.
PRESENCE
Conditional (see rule C1)
DEFINITION
When the Sender has debited the account of the Receiver for its charges, ie, field 32D is used, this field
identifies the number of the account which has been debited.
PRESENCE
Optional
DEFINITION
This field specifies the date as of which the bank which has issued or requested the issuance of the guarantee,
ie, the Receiver, is released of all its liability under the specified guarantee for the amount specified in field
33B or 39C.
NETWORK VALIDATED RULES
Date must contain a valid date expressed as YYMMDD (Error code(s): T50).
USAGE RULES
The absence of this field implies that the bank which has issued or requested the issuance of the guarantee is
released of all its liability as of the date the message was sent.
PRESENCE
Conditional (see rule C4)
DEFINITION
This field specifies the currency code and total amount of charges claimed by the Sender of the message.
NETWORK VALIDATED RULES
In option D, Date must be a valid date expressed as YYMMDD (Error code(s): T50).
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma ',' is mandatory and is
included in the maximum length. The number of digits following the comma must not exceed the maximum
number allowed for the specified currency (Error code(s): C03, T40, T43).
USAGE RULES
If the Sender services an account for the Receiver in the currency of the charges, and this account has been
debited in reimbursement, Option D must be used, specifying the value date of the debit.
In all other cases, Option B must be used.
PRESENCE
Conditional (see rule C2)
DEFINITION
This field specifies the currency code and amount for which the bank which has issued or requested the
issuance of the guarantee is released of all its liability under the specified guarantee.
NETWORK VALIDATED RULES
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma ',' is mandatory and is
included in the maximum length. The number of digits following the comma must not exceed the maximum
number allowed for the specified currency (Error code(s): C03, T40, T43).
Currency in fields 33B and 34B must be the same (Error code(s): C02).
USAGE RULES
Where the amount of the guarantee and, consequently, the amount released, cannot be expressed in terms of a
specific amount, field 39C must be used instead of field 33B.
PRESENCE
Optional
DEFINITION
When the liability under the specified guarantee is not to be released in its entirety, this field specifies the
currency code and amount outstanding.
NETWORK VALIDATED RULES
Currency must be a valid ISO 4217 currency code (Error code(s): T52).
The integer part of Amount must contain at least one digit. The decimal comma ',' is mandatory and is
included in the maximum length. The number of digits following the comma must not exceed the maximum
number allowed for the specified currency (Error code(s): C03, T40, T43).
Currency in fields 33B and 34B must be the same (Error code(s): C02).
PRESENCE
Conditional (see rule C2)
DEFINITION
This field contains a description of the amount for which the bank which has issued or requested the issuance
of the guarantee is released of all its liability under the specified guarantee.
USAGE RULES
This field must be used in those instances where the amount of the guarantee and, consequently, the amount
released, cannot be expressed in terms of a specific amount.
PRESENCE
Conditional (see rules C1 and C3)
DEFINITION
This field specifies the bank at which the Sender wishes to receive credit for charges claimed in field 32a.
NETWORK VALIDATED RULES
The BIC must be a SWIFT registered address, either connected or non-connected (Error code(s): T27, T28,
T29, T45).
The BIC must not be a BEI. Please refer to the latest version of the BIC Directory - Corporations for more
information about BEIs. This error code applies to all types of BICs referenced in a FIN message including
SWIFT BICs, non-SWIFT BICs, Masters, Synonyms, Live destinations and Test & Training destinations
(Error code(s): C05).
PRESENCE
Optional
DEFINITION
This field contains the specific details of commission and charges claimed by the Sender in field 32a.
CODES
One or more of the following codes may be used, followed by the currency code and amount:
USAGE RULES
Any code used in this field must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
In addition to narrative text, structured text with the following line formats may be used:
PRESENCE
Optional
DEFINITION
This field contains additional information for the Receiver.
USAGE RULES
This field may include ERI, as specified in the chapter entitled "Euro - Impact on SWIFT Message Standards"
The structured line format may be used for bilaterally agreed codes.
Any code must be between slashes and must appear at the beginning of a line.
Narrative text must not begin with a slash and, if used, must begin on a new line and be the last information in
the field.
MT 769 Examples
Narrative
On 12 January 2003, Swiss Bank Corporation, San Francisco, advises National Westminster Bank Plc,
London (reference 2PG8761234), that it has been released of all liability for an amount of US Dollars 14,000.
The outstanding obligation under the guarantee is US Dollars 13,240.
Swiss Bank Corporation would like to receive payment of its charges of US Dollars 35 (being cable costs of
USD 21 and commission charges of USD 14) at its account at Bank of New York, New York.
(To review the guarantee for this example, see the Example section of the MT 760.)
Information Flow
MT 760
MT 769
D0070032
57a New York
SWIFT Message
Explanation Format
Sender SBCOUS66
Receiver NWBKGB2L
Message Text
The following table lists all Common Group message types defined in Category 7.
For each message type, there is a short description, an indicator whether the message type requires
authentication (Y or N), the maximum message length for input (2,000 or 10,000 characters) and whether the
use of the message requires registration with SWIFT for use in a message user group (Y or N).
Note: A Message User Group (MUG), for the purposes of this book, is a group of users who have voluntarily
agreed to support the specified message type and have registered with SWIFT to send or receive the
specified message type. These messages are indicated in the preceding table in the column MUG.
Registration is free of charge. To register to use one or more message types, submit a registration request
(Register to a Message User Group) through www.swift.com. To withdraw from a MUG, use the
Deregister from a Message User Group request.
These forms are available on www.swift.com > Ordering & Support > Ordering.
To get the list of other members of a particular MUG, send an MT 999 to the Customer Implementation
team (SWHQBEBBCOS).
Please refer to Category n - Common Group Messages, Chapter n90 Advice of Charges, Interest and Other
Adjustments for details concerning this message type.
Please refer to Category n - Common Group Messages, Chapter n91 Request for Payment of Charges, Interest
or Other Expenses for details concerning this message type.
Please refer to Category n - Common Group Messages, Chapter n92 Request for Cancellation for details
concerning this message type.
MT 795 Queries
Please refer to Category n - Common Group Messages, Chapter n95 Queries for details concerning this
message type.
MT 796 Answers
Please refer to Category n - Common Group Messages, Chapter n96 Answers for details concerning this
message type.
Please refer to Category n - Common Group Messages, Chapter n98 Proprietary Message for details
concerning this message type.
Please refer to Category n - Common Group Messages, Chapter n99 Free Format Message for details
concerning this message type.
Glossary of Terms
In addition to the definitions which appear in the Glossary of Terms in SWIFTStandards MT General
Information, the following terms apply to category 7 message types.
For any additional definitions or details, please refer to the Uniform Rules for Bank-to-Bank Reimbursements
under documentary credits (URR) and the Uniform Customs and Practice for documentary credits (UCP),
International Chamber of Commerce, Paris, France.
Advising Bank
The bank requested to advise the documentary credit.
Advising Instruction
An instruction to the Advising Bank regarding confirmation of the documentary credit.
Amendment Date
The date on which an amendment was issued.
Amendment Statement
A standard phrase linking the amendment to the original documentary credit.
Amount Claimed
The total claimed for reimbursement in a documentary credit, optionally followed by the date on which
the Claiming Bank requests the amount to be placed at its disposal.
Applicant
The party at whose request a transaction or service is to be undertaken.
Charges Authorisation
Issuing Bank's approval to the Reimbursement Bank to honour charges.
Charges Claimed
The charges and commissions in addition to a principal amount claimed under a documentary credit.
Claiming Bank's Reference Number
The reference assigned by the Claiming Bank which unambiguously identifies a particular transaction.
Credit Available by
The method by which a documentary credit will be made available.
Credit Available With
The identification of the nominated bank at which the credit is available.
Draft Details
Information pertaining to the draft(s) required under a documentary credit.
Endorsement of Drawings
A record of a specific drawing on a documentary credit.
Expiry Date and Place
The latest date and place for presentation of documents for payment, acceptance, or negotiation.
Issue Date and Place
The date of issue of a documentary credit.
Partial Shipments
An incomplete shipment of goods.
Place for presentation
Under a credit subject to UCP, this means an address where the paper documents should be presented.
Under a credit subject to eUCP, this means an electronic address where the electronic records should be
presented.
Presentation Period
The period of time after the date of the issuance of the transport document within which documents
must be presented for action.
Shipping
Information as to where the goods must be shipped/loaded on board/dispatched/taken in charge and to
which destination they must be transported.
Transshipment
The shipment of goods between two points other than the original point of shipment.
Transport Details
The method whereby the goods were loaded on board, dispatch and taken in charge, and to which
destination they have been transported.