where:
Optional
This field contains the details of each transaction.
Subfield 3, Debit/Credit Mark, must contain one of the following codes (Error code(s): T51):
Subfield 6, Transaction Type Identification Code, may be completed in one of three ways (Error code(s): T53):
When formats (2) or (3) are used, the last three characters, ie, 3!c, may contain one of the following codes:
Subfield 1, Value Date, must be a valid date expressed as YYMMDD (Error code(s): T50).
The SWIFT System validates subfield 2, Entry Date (Date in reduced ISO form), using current System Year (Error code(s): T50).
The integer part of Amount must contain at least one digit. The decimal comma ',' is mandatory and is included in the maximum length (Error code(s): T40, T43).
When the first character of subfield 6, Transaction Type Identification Code, is an 'S', the remaining characters must be in the range 100-999 (Error code(s): T18).
This field may be repeated within the constraints of the maximum input message length.
'Original' advices for charges, ie, the first time the account owner is informed of a charge, must be identified in subfield 6, Transaction Type Identification Code, with the transaction type code 'FCHG'.
The following rules apply to subfield 7, Reference for the Account Owner:
At least one valid character other than a blank must be present.
For debit entries, the purpose of this subfield is to identify, to the account owner, the instruction which caused the debit. Therefore, the content of this subfield is the field 20 Sender's Transaction Reference Number (or its equivalent) of the original instruction.
Credit entries may be the result of one of the following situations:
The account servicing institution is identifying, to the account owner the receipt of funds for its account as a result of a related transaction. In this case, the content of subfield 7, Reference for the Account Owner is the reference for the beneficiary (eg, field 21 Related Reference) of the related transaction.
The account servicing institution has issued a payment instruction to the account owner and the credit identified in this subfield is for that payment. The content of subfield 7, Reference for the Account Owner is the field 20 Transaction Reference Number (or its equivalent) of the payment instruction issued by the account servicing institution.
If no reference is available for subfield 7, Reference for the Account Owner, the code NONREF shall be used. The account servicing institution must then supply, in subfield 9, Supplementary Details, what it considers to be the best alternative information.
This reference must be quoted in all cases when available. In cases where a transaction passes through several financial institutions, the original reference must always be forwarded.
This reference must always be quoted against any charges or fees debited by the account servicing institution.
Debits against standing instructions must show the reference of the standing instruction.
In cases where a mutually agreed alternative reference exists (eg, in foreign exchange or money market transactions), this reference should then be used.
If the statement entry concerns a cheque, the cheque number should be indicated in this subfield.
The following rules apply to subfield 8, Account Servicing Institution's Reference:
The content of this subfield is the account servicing institution's own reference for the transaction.
When the transaction has been initiated by the account servicing institution, this reference may be identical to subfield 7, Reference for the Account Owner. If this is the case, Account Servicing Institution's Reference, subfield 8 may be omitted.
The following rules apply to subfield 9, Supplementary Details:
When no reference for the account owner is available, ie, subfield 7, Reference for the Account Owner contains NONREF, the account servicing institution should provide the best available alternative information in this subfield.
Supplementary details may be provided when an advice has not been sent for a transaction, or to provide additional information to facilitate reconciliation.
This field may include ERI, as specified in the chapter entitled "Euro - Impact on SWIFT Message Standards.
This field may contain ERI to transport dual currencies, as explained in the chapter 'Euro - Impact on Category 9 Message Standards'.
In order to comply with the EC-directive on cross border credit transfers, the optional code word EXCH may be used to transport an exchange rate. In line with ERI, the code word EXCH is placed between slashes, followed by the exchange rate, format 12d, and terminated with another slash.