EUR MT103 Customer Transfer Guide / STP Quick Guide

[M = mandatory field O = optional field C = conditional field]
SWIFT Field and Name Description and Format
20 Sender's Reference M Sending bank’s reference, named as Transaction Reference Number in the MT103. Also referred to as TRN.
23B Bank Operation Code M This field identifies the type of operation.

LHB Bank accepts the code word CRED.

23E Instruction Code O/C This field specifies an instruction.

See Swift Standard Code Words.

26T Transaction Type Code O This field identifies the nature of, purpose of, and/or reason for the individual transaction.

Not relevant to EUR transactions sent to LHB Bank

32A Value Date, Currency, Interbank Settled Amount M Follows standard SWIFT formats. Named as Value Date, Currency Code, Amount in the MT103.
33B Currency/ Instructed Amount O/C This field specifies the currency and amount of the instruction.

This amount is provided for information when a currency conversion or an exchange has been performed on the Sender's side

36 Exchange Rate O/C Specifies the exchange rate used to convert the instructed amount specified in field 33B.

This field must be present when a currency conversion or an exchange has been performed on the Sender's side.

50 Ordering Customer M Identifies the originating customer.

Two options can be used, Option A or K. For Option A, the account number is first, followed by the BEI or the Business Entity Identifier, which is a corporate BIC. Option K, which is more common, is to give the account number followed by the name and address.

51 Sending Institution O Identifies the Sender of the message.

Not relevant to EUR transactions sent to LHB Bank

52 Ordering Bank O Identifies the bank that is ordering the transaction, when different from the sending bank.

If Field 52 is present, Option A must be used for STP-reasons.

53 Sender’s Correspondent Bank O/C Identifies the debit account, when different from the sending bank.

If the Sender has no direct relationship with LHB Bank, use the SWIFT BIC of a Branch that does have a direct account (Option A). If the Sender has another account directly with LHB Bank, state the account number preceded by a single / (Option B).
Option D should not be used for STP-reasons.

54 Receiver’s Correspondent Bank O/C Identifies the Bank that will be sending cover funds through the local clearing to reimburse the Receiving Bank of this MT103.

If Field 54 is present, Option A must be used for STP-reasons.

55 Third Reimbursement Bank O/C Specifies the Receiver's branch, when the funds are made available to this branch through a financial institution other than that indicated in field 53a.

If Field 55 is present, Option A must be used for STP-reasons.

56 Intermediary Bank O/C Identifies the bank through which funds must pass if the Account With Bank (57) or the Beneficiary (59) do not maintain a direct account relationship with LHB Bank.

If Field 56 is present, Option A must be used for STP-reasons.

57 Beneficiary Bank O/C Identifies the bank where the beneficiary has an account. Also referred to as BBK or Beneficiary Bank. Field 57 is mandatory if different from receiver, even if field 59 contains an IBAN.

If Field 57 is present, the below options must be used for STP-reasons.

OPTION A: SWIFT BIC (8-11 alpha-numeric characters)
OPTION D: //BL (8 digit German Clearing Code). For example //BL50030800 or other national clearing system identifier and codes in accordance with SWIFT standard field definitions.
 

59 Beneficiary Customer M Identifies the ultimate beneficiary.
70 Remittance Information O/C Specifies details of the individual transaction or a reference to another message containing the details. Named as Details of Payment in the MT103. The information contained in this field is passed to the beneficiary of the payment.
71A Details of Charges M Specifies which party will bear the charges for the transaction.

Use either of the following SWIFT Code words:

  • BEN - charges are to be covered by the beneficiary through a deduction from the amount paid.
  • OUR - charges are to be covered by the originator
  • SHA - charges on the Sender's side are to be borne by the ordering customer, transaction charges on the Receiver's side are to be borne by the beneficiary customer through a deduction from the amount paid.
71F Sender's Charges O/C Specifies the currency and amount of the transaction charges deducted by the Sender and by previous banks in the transaction chain.

Currency in Field 71F must be the same as the currency in Field 32A

71G Receiver's Charges O/C Specifies the currency and amount of the transaction charges due to the Receiver.

Where field 71A indicates OUR payments, this field identifies the charges agreed with LHB Bank, which have been prepaid and included in the interbank settlement amount. Currency in Field 71F must be the same as the currency in Field 32A

72 Bank to Bank Information O Specifies additional information for the Receiver or other party specified. Code words within single slashes must precede the information in this field. Double slashes are required to indicate the continuation on a new line.

Field 72 should not be used for STP reasons. See Swift Standard Code Words for a list of most frequently used code words and explanation if they cause a repair item or not.

77B Regulatory Reporting O Specifies the code(s) for the statutory and/or regulatory information required by the authorities in the country of Receiver or Sender.

Not yet relevant for EUR payments

 

Information on Conditional Fields

Under specific circumstances, optional fields become conditional fields. This means that the fields must or must not be used, depending on other fields. Examples:

  • If field 55a is present, then both fields 53a and 54a must also be present

  • If Field 56 is present, Field 57 must also be present.

  • If Field 23E contains the code CHQB, subfield 1 (Account) in Field 59a is not allowed.

  • If Field 71A contains OUR, then Field 71F is not allowed and Field 71G is optional.

For further details on conditional fields please refer to the SWIFT Standards, Network Validated Rules.