ISO 7746:1998
(Main)Banking — Telex formats for inter-bank messages
Banking — Telex formats for inter-bank messages
Banque — Formats télex pour messages interbancaires
General Information
Relations
Standards Content (Sample)
IS0
INTERNATIONAL
7746
STANDARD
Second edition
1998-03- 15
Telex formats for inter-bank
Banking -
messages
Banque - Formats tdex pour messages interbancaires
Reference number
IS0 7746: 1998(E)
---------------------- Page: 1 ----------------------
IS0 7746: 1998(E)
Contents
. . .
III
Foreword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1
1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1
. . . . . . . . . . . . . . . . . . .*.
2 Normative references
1
Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .-.
3
4 Technical features of a telex format conforming with this International Standard . . . . . . . . . . . . . . . . . 2
9
5 Message Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Annexes
27
A Samples formats
..*.................................................................,..............................................
B
Diagrammatic representation of bank/customer identification fields, showing their
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
relationships with one another
0 IS0 1998
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced
or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm, without permission in writing from the publisher.
International Organization for Standardization
Case postale 56 l CH-1211 Geneve 20 l Switzerland
Internet central @ iso.ch
x.400 c=ch; a=400net; p=iso; o=isocs; s=central
Printed in Switzerland
ii
---------------------- Page: 2 ----------------------
@ IS0 IS0 7746: 1998(E)
Foreword
IS0 (the International Organization for Standardization) is a
worldwide federation of national standards bodies (IS0 member
bodies). The work of preparing International Standards is normally
carried out through IS0 technical committees. Each member body
interested in a subject for which a technical committee has been
established has the right to be represented on that committee.
International organizations, governmental and non-governmental, in
liaison with ISO, also take part in the work. IS0 collaborates closely
with the International Electrotechnical Commission (IEC) on all
matters of electrotechnical standardization.
Draft International Standards adopted by the technical committees
are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the
member bodies casting a vote.
International Standard IS0 7746 was prepared by Technical
Committee ISOTTC 68, Banking and related financial sewices.
This second edition cancels and replaces the first edition
(IS0 7746:1988), of which it constitutes a technical revision.
Annexes A and B of this International Standard are for information
only.
---------------------- Page: 3 ----------------------
IS0 7746: 1998(E) @ IS0
Introduction
Standard telex formats for inter-bank payment and other financial messages are
required in order to
prevent misinterpretation by the receiver of the sender’s instructions; “clean
a)
payment” message types have been specifically designed to be
understandable to a receiver who is not aware of the existence of this
International Standard;
provide format specifications which are suitable for the automaiic (machine)
W
handling of telex messages.
Examples of messages using the non-standard (traditional) format, each followed by the
format specified in this International Standard are shown in annex A.
The formats specified in this International Standard have been aligned, GS far as it is
possible to do so, with those formats specified by S.W.I.F.T. The IS0 formats tend to be
simpler and arise from the need to design a format readily understandabis by a user
holding neither a copy of this International Standard nor of the S.W.I.F.T. manuals. This
International Standard is not intended to dissuade users from using S.W.I.F.T. formats
where it is appropriate to do so. Such users would need to agree their own start of
transmission code (as explained in 4.6.1) for the use of strict S.W.I.F.T. format to be
clearly understood by both parties.
---------------------- Page: 4 ----------------------
-----
INTERNATIONAL STANDARD @ IS0
IS0 7746:1998(E)
Banking - Telex formats for inter-bank messages
1 Scope
This International Standard specifies the format to be used for telex messages relating to
the transfer of funds and other financial messages, which are exchanged between
banks. It does not address the division of responsibility between sender and receiver.
2 Normative references
The following standards contain provisions which, through reference in this text,
constitute provisions of this International Standard. At the time of publication, the
editions indicated were valid. All standards are subject to revision, and parties to
agreements based on this International Standard are encouraged to investigate the
possibility of applying the most recent editions of the standards indicated below.
Members of IEC and IS0 maintain registers of currently valid International Standards.
IS0 4217: 1995, Codes for the representation of currencies and funds.
IS0 7982: 1987, Bank telecommunication - Funds transfer messages - Part 1: Vocabulary
and data elements.
IS0 8601: 1988, Data elements and interchange formats - Information interchange -
Representation of dates and times.
International Chamber of Commerce, Paris :
Uniform Customs and Practice for Documentary Credits. (Version in force at the time of
the issue of the credit.)
Uniform Rules for Collections. (Version in force at the time the collection is sent out.)
3 Definitions
For the purpose of this International Standard, the following definitions apply.
31 claiming bank: Bank claiming reimbursement for payment(s) or negotiation(s)
under a documentary credit.
32 collecting bank: Correspondent commissioned by the remitting bank to see to
the acceptance and/or payment of financial or commercial documents.
33 funds transfer (abbreviated in this International Standard to “transfer”):
Complete movement of funds between the originator and the beneficiary. A funds
transfer may consist of one or more funds transfer transactions.
---------------------- Page: 5 ----------------------
@ IS0
IS0 7746:1998(E)
funds transfer transaction (abbreviated in this International Standard to
34
“;ransaction”): Movement of funds directly between two parties, involving no
intermediaries other than a payment or communication service.
issuing bank: Bank issuing the documentary credit.
35 .
message: A communication containing one or more transactions or related
36
information.
37 multiple message: One message containing more than one transaction or
related information.
reimbursing bank: Bank authorized by the issuing bank to honour claims for
38
reimbursement of payment(s) or negotiation(s) under a documentary credit.
39 transmission : A data sequence (answerbacks and messages) transmitted
between two parties; and operating from the time of the establishment of a connection,
to its termination.
Technical features of a telex format conforming with this
4
International Standard
41 . Message categories
The message type is indicated by a three-digit number. The first digit shall indicate the
category as follows:
1 - Customer Transfers
2 - Bank Transfers
3 - Foreign Exchange and (Loan/Deposit Transactions)
4 - Collections
5 - (Securities)
6 - (Reserved for future assignment)
7 - Documentary Credits
8 - (Special Messages)
9 - Confirmations and Statements
NOTE - Items in parentheses are not defined in this International Standard.
The second and third digits of the message type shall indicate the specific purpose of
the message within its general category.
Where a message type is applicable to all categories, the first digit is shown in this
International Standard as n. Thus, n92 shall be taken to represent nine possible
message types with n = 1 to n = 9.
42 . Structuring of a transmission
One transmission may contain several messages. Each message in a single
transmission should contain its own header and trailer; and should be separated by the
code QQ.
---------------------- Page: 6 ----------------------
IS0 7746: 1998(E)
@ IS0
A multiple message shall contain several transactions. No more than 10 transactions
shall be incorporated in a single multiple message.
3
---------------------- Page: 7 ----------------------
@ IS0
IS0 7746: 1998(E)
Identification of message types
43 .
Message types, as described in table 1, shall be identified by the number and name
shown.
Table 1 - Identification of message types
Number and name Description
A payment order in which either the
100 Customer Transfer
originator and/or the beneficiary are
non-banks
Bank Transfer for Sender’s Own A payment order in which the sender
200
Account orders the transfer of funds from its
account serviced by the receiver to its
account serviced by another bank.
201 Multiple Bank Transfer for A multiple payment order in which the
Sender’s Own Account sender orders the transfer of funds
from its account serviced by the
receiver to its accounts serviced by
other banks.
A payment order where the sender
202 Bank Transfer in favour of a third
bank and the beneficiary are banks but not
the same bank. Such a transfer is
always in relation to some other
transaction.
203 Multiple Transfer in favour of a A multiple payment order where the
third bank sender and beneficiary(ies) are banks
but not the same bank. Such transfers
are always in relation to other
transactions.
210 Notice to Receive An advance notice to an account
servicing bank that it will receive funds
to be credited to the account of the
bank sending the notice.
300 Foreign Exchange Confirmation A message exchanged between
banks to confirm a foreign exchange
deal or an amendment to or
cancellation of such a deal. This
message may also be used to correct
or complete a previously exchanged
confirmation.
400 Collection. Advice of Payment A message from the collecting bank to
the remitting bank accounting for a
collection or part thereof. The
message type also handles the
settlement of proceeds.
4
---------------------- Page: 8 ----------------------
IS0 7746: 1998(E)
@ IS0
Authorization to Reimburse A message sent by an issuing bank
740
relating to a documentary credit. It
contains a request (and authorization)
to honour claims for reimbursement
under the identified documentary
credit.
Claim for reimbursement under a
742 Reimbursement Claim
documentary credit.
Amends a previously sent
747 Amendment to an Authorization to
authorization to reimburse.
Reimburse
Advice by the account servicing bank
900 Confirmation of Debit
of a debit to the account of the
receiving (account owner) bank.
Advice by the account sewicing bank
910 Confirmation of Credit
of a credit to the account of the
receiving (account owner) bank. This
message shall not be used to transmit
payment instructions.
A message requesting the receiving
n92 Request for Cancellation
bank to cancel the message identified
in the request
Narrative request for instructions or
Queries
n95
for information.
Response to Queries (n95) or
n96 Answers
Request for Cancellation (n92).
---------------------- Page: 9 ----------------------
@ IS0
IS0 7746:1998(E)
Line length
44 .
A line may consist of a field identifying code (field tag), a field descriptor and field
content. A maximum line length is specified for the content of each field. It is permissible
for the first line of the field content to appear on the same line as its field tag and
descriptor (see 5.3.2).
This line limit shall not apply to the collation line in the trailer (see 5.6).
NOTE - These requirements allow compatibility with commercial international
communication systems already operational.
. Message structure rules
45
4.51 All lines shall be justified to the left, unless otherwise specified in this
International Standard.
4.52 Every message shall contain:
header (see 5.1);
a)
instruction (or information) to the receiver (see 5.2);
b)
message text consisting of : field identifying codes (for field tags see 5.4); field
C)
descriptors (unless omitted, see 4.5.4); and field content;
a trailer (see 5.6).
d)
An index of message components is included in annex A.
4.5.3 Fields in a message shall be in the specified sequence for that message type. In
a multiple message, field content common to all transactions shall appear first, in
numerical order (for instance 15 TEST KEY; 19 SUM OF AMOUNTS; 30 VALUE DATE;
and 53 REIMBURSEMENT in Example 2B in annex A), followed by five blank lines and
the fields relating to the individual transactions.
4.5.4 Field descriptors (see 5.3.1) may be omitted when it is known that omission is
acceptable to the receiver.
. Separation indicators
46
4.6.1 Start of transmission: The code YZYZ shall be used to indicate that the
transmission is in the format prescribed by this International Standard. This start of
transmission code shall be separated from the next message element (header) by one
blank line.
4.6.2 Separation of messages in a single transmission: The code QQ shall be used to
indicate the end of one message in a transmission which includes several messages.
Ten blank lines shall be used to separate the QQ from the beginning of the next
message.
4.6.3 Separation of transactions in a multiple message: Five blank I ines shall be used
to separate the transactions in a multiple message.
4.6.4 End of transmission: The code NNNN shall be used.
---------------------- Page: 10 ----------------------
@ IS0 IS0 7746: 1998(E)
47 .
Opening, closing and answerbacks
An exchange of answerbacks shall be initiated by the sender at the opening and closing
of a transmission. The answerbacks may be followed by any miscellaneous control
information (several lines) required by the transmission service. The start of transmission
code (YZYZ) shall be separated from previous information (answerbacks and/or
miscellaneous control information) by at least one blank line. The closing answerbacks
and any miscellaneous control information shall be followed by several blank lines
immediately before the end of transmission code (NNNN).
.
48 Cable references
If required, these should appear under any miscellaneous control information and before
the start of transmission code (YZYZ).
49 . Possible duplicate
To indicate a message that possibly duplicates an earlier message, the start of
transmission separator cc
de (YZYZ) shall be immediately followed by
Blank line
PD:POSSIBLE DUPL
I CATE (written as literal narrative text)
Blank line
This should be followed b
‘I
narrative identifying the possible duplicate and the possible cause of
a)
duplication, and
the text of the message structured in accordance with this International
b)
Standard and which the sender believes to be a possible duplicate of a
previous message. For example
12345 LONCOM G
54332 BANFIC CH
YZYZ
PD:POSSIBLE DUPLICATE
PAYMENT INSTRUCTIONS DOUBTFULLY SENT 801130
REF 100/32AB201
FROM :BANQUE FICTITIOUS, GENEVA
TO :LONDON COMMERCIAL BANK,
BIRMINGHAM
DATE :801201
Message Text
4.10 Expression of names and addresses
The name (bank or customer) shall be separated from the address by a comma. It is
preferred that the city name (with postal code) should start the last line of the address.
7
---------------------- Page: 11 ----------------------
IS0 7746:1998(E) @ IS0
4.11 Account identification
Where an account identification is specified, the party specified shall be the account
owner. It shall be up to 34 characters in length and preceded by a slash (the account
number identification symbol).
8
---------------------- Page: 12 ----------------------
IS0 7746:1998(E)
@ is0
5 Message structure
This clause specifies the method of use (where not apparent from the definition) of each
of the message types specified in 4.3. Individual fields are given an identification (field
tag) and a structure. Each message type is specified by means of fields which shall
always be present for the proper handling of the message; and further fields which are
additionally available where appropriate in particular messages, such fields being shown
in parentheses in 5.5.
51 . Header
The header of the message shall contain field descriptors FROM, TO and DATE each
followed by a colon in the fifth character position. The variable information associated
with each field shall be on one or more lines each justified to the left and beginning in the
sixth character position. For examples see annex A.
FROM: Name and place of sender, with name followed by a comma.
TO : Name and place of receiver, with name followed by a comma.
DATE : YYMMDD (see IS0 2014) optionally followed by an alternative form where the
month is written in alphanumeric characters. The date shall be followed by
one blank line.
Message types shall be identified according to table 1 (see 4.3), preceded by a double
colon. For example
::lOO CUSTOMER TRANSFER
followed by one blank line.
Examples of headers drawn up in accordance with this International Standard are given
in annex A.
52 . Instruction (or information) to the receiver
An instruction (or information) to the receiver shall follow the blank line after the header
(message type and description). The instruction (or information) to the receiver shall be
followed by one blank line. For example
::lOO CUSTOMER TRANSFER
PLEASE PAY
. Field identifiers (tags and descriptors)‘) and field contents
53
53.1 General
The text of the message shall consist of a set of fields (see 5.5), each comprising an
2 [field tag followed by field descriptor, unless omitted (see
identifier selected from table
4.5.4)], followed by its field content. The last line of the text shall be separated from the
trailer by at least one blank line.
1)
Descriptors have been selected for their suitability as an aid to the vocabulary of funds transfer terms as given in
IS0 7982. However, where variations arise, cross referencing to the preferred term will be given in the vocabulary
mentioned above.
9
---------------------- Page: 13 ----------------------
IS0 7746:1998(E) @ IS0
As an aid to automating these messages, the following rules shall be observed
no line shall start with a colon, other than as a field tag identifier;
a)
the text of a single message shall contain no blank line(s) between the blank
b)
line following the instruction (or information) to the receiver and the blank line
preceding the trailer. In the case of a multiple message, five blank lines shall
separate the individual transactions (see 4.6.3).
10
---------------------- Page: 14 ----------------------
@ IS0 IS0 7746: 1998(E)
Table 2 - Field identifiers
Field Field descriptor
tag
French
English
Security
TEST KEY CODE AUTHENTIF
15
SUM OF AMOUNTS SOMME MONTANTS
19
References
20 SENDERS REF RCF EXPCNDITEUR
RCF POUR BCNEF
21 RELATED REF
a
REF COMMUNE
22 COMMON REF
COMPTE
25 ACCOUNT ID
Dates and Values
DATE DU CONTRAT
30 CONTRACT DATE
I I I
,
130~~~~ , ~~~~~~---~_~~~_~_~ , DATE DE “ALEUR
VALUE DATE
DATE DE PREMIERE
30 DATE OF ORIGINAL
AUTHORISATION DE
ATHORIZATION TO
REMBOURSER
REIMBURSE
DATE D’EMISSION
I31C 1 ISSUE DATE
I I
31D EXPIRY DATE DATE D’EXPIRATION
1
NOUVELLE DATE DE
31E NEW DATE OF EXPIRY
FIN DE VALIDITE
AMOUNT MONTANT
32
DATE ~CHEANCE
32K MATURITY DATE/
MONTANT ENCAISSE
AMOUNT COLLECTED
DATE DE VALEURI
32R VALUE DATE/
AMOUNT BOUGHT MONTANT ACHAT
VALUE DATE/ DATE DE VALEUR/
33A
PROCEEDS REMITTED MONTANT VS REVENANT
I I
( 33B 1 ADDITIONAL AMOUNTS AUTRES MONTANTS
I
DATE DE VALEURI
33P VALUE DATE/ AMOUNT
MONTANT VENTE
SOLD
MONTANT DEMANDC
34 AMOUNT CLAIMED
TAUX DE CHANGE
36 EXCHANGE RATE
I
I I
DCTAILS MONTANT
AMOUNT DETAILS
39
I I I
11
---------------------- Page: 15 ----------------------
@ IS0
IS0 7746:1998(E)
Documentary Credit Details
AVAILABLE WITH. BY.
41 UTILISABLE AVEC. PAR.
42 DRAFT DETAILS DiTAILS EFFETS
Banks and Customers
ORIGINATOR DONNEUR D’ORDRE
50
ISSUING BANK BANQUE ~METTRICE
52
ORIGINATORS BANK BQDUDONNEUR
52
D’ORDRE
REIMBURSEMENT
53 REMBOURSEMENT
INTERMEDIARY BANK
56 BQ INTERMiDlAlRE
PAY THRU BQ DU BENCF
57
59 BENEFICIARY B~N~FICIAIRE
Information and Instructions
BENEF INFO INFO Bl?N~FICIAIRE
70
71 CHARGES FRAIS
71B CHARGES CLAIMED FRAIS DEMANDtS
71B DEDUCTIONS DiDUCTlONS
72 SENDER TO RECEIVER INFO DE L’EXPEDITEUR
INFO AU DESTINATAIRE
73 AMOUNTS ADDED MONTANTS EN SUS
75 QUERIES DEMANDES
D’INFORMAilON
77A NARRATIVE INFORMATIONS POUR LE
DESTINATAIRE
82 PAY THRU INFO INFO BQ DU BCNCF
53.2 Field structure
The structure of each field shall be as follows:
First line : colon field tag [one space field descriptor] colon field content
Items in brackets may be omitted (see 4.5.4)
Second line : field content
Additional lines : optionally available where permitted. These lines contain continuation
of field content. Where a maximum number of lines is specified, it is desirable that this
number shall not normally be exceeded. Receivers are warned, however that truncation
.
of such fields is not a recommended procedure.
12
---------------------- Page: 16 ----------------------
IS0 7746:1998(E)
@ IS0
54 . Specifications of individual fields
NOTE - Annex B gives a diagrammatic representation of bank/customer identification
fields (50 to 59) showing their relationship to one another.
5.4.1 Field 15 TEST KEY
A code used to validate the source; it may validate certain other elements of a message
text such as amount, date and sequence.
Format : Up to 16 characters followed by a maximum of two text lines of up to 35
characters each to inform the receiver which test key was used.
5.4.2 Field 19 SUM OF AMOUNTS
The sum of the transaction amounts in a multiple message.
Format : Numeric only, up to 35 characters (including punctuation and decimal sign).
5.4.3 Field 20 SENDERS REF
The reference assigned by the sending bank, which unambiguously identifies the
transaction.
Format : Up to 16 characters.
5.4.4 Field 21 RELATED REF
The reference for the beneficiary which enables the beneficiary to identify the transfer.
Where no reference is available, the expression NONREF may be used. In the case of
message type 300, when used to confirm a new foreign exchange transaction, the word
NEW shall be used.
Format : Up to 16 characters.
5.4.5 Field 22 COMMON REF
A description of the nature of the confirmation followed by a reference to a particular
foreign exchange deal. The content and structure shall be as agreed between dealing
banks.
Format : One of the descriptions specified below (up to eight alpha characters) followed
by slash, followed by up to 16 characters.
Descriptions: NEW NOUVEAU
AMEND MODIF
CANCEL ANNUL
CORRECT ERREUR
COMPLETE INF-COMP
5.4.6 Field 25 ACCOUNT ID
Identifies a specific account.
13
---------------------- Page: 17 ----------------------
@ IS0
IS0 7746:1998(E)
Format : Up to 35 characters.
5.4.7 Field 30 VALUE DATE
Date on which the funds are to be at the disposal of the receiving bank.
or Field 30 CONTRACT DATE (MT 300 only, see 5.5.7)
Date on which the contract was agreed between the dealers.
or Field 30 DATE OF ORIGINAL AUTHORIZATION TO REIMBURSE (MT 747 only,
see 5.5.11)
Date on which the original authorization to reimburse was sent.
Format : One line of up to 35 characters; six digits YYMMDD (two digits each to specify
year, month and day: see IS0 2014).
NOTE - As an aid to the introduction of this International Standard, it is alternatively
permitted to express the date in a non-standard form, with the month in alpha
characters. Alternative all-digit modes are not permitted.
5.4.8 Field 31C ISSUE DATE
Date of issue of documentary credit.
Format : One line of up to 35 characters. See 5.4.7.
5.4.9 Field 31 D EXPIRY DATE
Date (and, optionally, place) of expity of a documentary credit.
Format: One or two lines of up to 35 characters each.
date : See 5.4.7 followed optionally on a second line by
a)
specification of place of expiry.
b)
5.4.10 Field 31 E NEW DATE OF EXPIRY
The new (i.e., revised) expiry date (and, optionally, place) for presentation under a
documentary credit.
Format: One or two lines of up to 35 characters each.
date: See 5.4.7 followed optionally on a second line by
a)
specification of place of expiry.
b)
5.4.11 Field 32 AMOUNT
The amount of the transaction.
Format : One line of up to 35 characters including triad separators and decimal sign. The
IS0 alpha beta currency code (see IS0 4217) shall be followed immediately, i.e. without
any spaces, by the amount, in numeric form only.
14
---------------------- Page: 18 ----------------------
IS0 7746: 1998(E)
@ IS0
5.412 Field 32K MATURITY DATE/AMOUNT COLLECTED
The maturity date of the collection and the amount paid by the drawee.
Format : Up to two lines of up to 35 characters each.
date as specified in 5.4.7 on first line, followed on the second line by
4
amount as specified in 5.4.11.
W
NOTE - An alternative non-calendar date form in the first line (for example 10 days
after sight) is also allowed.
5.4.13 Field 32R VALUE DATE/AMOUNT BOUGHT
The value/maturity date of the foreign exchange deal and the amount the sender is
buying.
Format : Up to two lines of up to 35 characters each.
date as specified in 5.4.7 on first line, followed on the second line by
a)
amount as specified in 5.4.11.
W
5.4.14 Field 33A VALUE DATE/PROCEEDS REMllTED
Specifies the value date and amount remitted by the sending bank to the receiving bank
for a collection or part thereof. [The amount in this field will normally be equal to the
amount specified in field 32K (see 5.4.12) plus any amount(s) listed in field 73 (see
5.4.32), less any charge(s) specified in field 71 B (see 5.4.30).]
Format: Up to two lines of up to 35 characters each.
date as specified in 5.4.7 on first line, followed on the second line by
a)
amount as specified in 5.4.11.
b)
5.415 Field 338 ADDITIONAL AMOUNTS
Specifies any additional amount claimed for reimbursement in a documentary credit.
Format: One line of up to 35 characters as specified in 5.4.11.
5.4.16 Field 33P VALUE DATE/AMOUNT SOLD
The value/maturity date of the foreign exchange deal and the amount the sender is
selling.
Format: Up to two lines of 35 characters each.
date as specified in 5.4.7 on first line, followed on the second line by
4
amount as specified in 5.4.11.
b)
5.4.17 Field 34 AMOUNT CLAIMED
Total amount claimed for reimbursement in a documentary credit, optionally followed by
the date on which the claiming bank requests the amount to be at its disposal.
15
---------------------- Page: 19 ----------------------
@ IS0
IS0 7746:1998(E)
Format : Up to two lines of 35 characters each.
amount as specified in 54.11 on first line, fol lowed on the second line by
a)
date as specified in 5.4.7.
W
5.4.18 Field 36 EXCHANGE RATE
The exchange rate between currencies appearing in the message, expressed in decimal
form.
Format : Up to 12 digits, including a decimal sign which must be preceded by at least
one integer figure.
5.4.19 Field 39 AMOUNT DETAILS
Detailed amount specifications of the documentary credit (e.g. insurance to be paid
additionally).
Format : Up to four lines of up to 35 characters each.
5.4.20 Field 41 AVAILABLE WITH. BY.
Indicates the bank(s) authorized to claim reimbursement. In the case of a freely
negotiable documentary credit, the phrase “ANY BANK” should appear in this field.
Format : Up to four lines of up to 35 characters each.
5.4.21 Field 42 DRAFT DETAILS
Field available for use when the documentary credit requires drafts. To avoid
misunderstandings, the wording used should always be “DRAFTS AT.” and, on a new
line, “DRAWN ON.“.
Format : Up to four lines of up to 35 characters each.
5.4.22 Field 50 ORIGINATOR
Identifies the initiator of the transfer instructions.
Format : Up to four lines of up to 35 characters each.
5.4.23 Field 52 ORIGINATORS BANK
Identifies the bank acting for the originator of the transfer.
or Field 52 ISSUING BANK
Identifies the bank issuing the documentary credit.
Format : Up to four lines of up to 35 characters each.
5.4.24 Field 53 REIMBURSEMENT
Instructions and/or any other information concerning reimbursement of tt;e transaction.
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.