Customer Statement - MT940 with Structured Information To Account Owner



Similar documents
Format Description SWIFT MT940 Structured

Format Description MT940. Rabo Cash Management

Deutsche Bank Deutsche Bank MT940/942 format specifications

MT104 Direct Debit and Request for Debit Transfer Message.

Format Description. SWIFT MT103 Single Customer Credit Transfer

SEPA Direct Debit Implementation Guide. Version 1.7

OUTGOING PAYMENTS ISO APPLICATION GUIDELINE

Format description XML SEPA Credit Transfer. Format Description

SWIFT MT940 MT942 formats for exporting data from OfficeNet Direct

F o r e i g n p a y m e n t i n P o l a n d Page 1 of 6 B u s i n e s s O n l i n e

XML message for Payment Initiation Implementation Guideline. Version 1.02

HANDBOOK FOR THE STANDARDISATION AND APPLICATION OF

Online Banking Record Descriptions

Direct Exchange Notes on the Electronic Interface Technical Documentation

SEPA CREDIT TRANSFER SCHEME INTER-BANK IMPLEMENTATION GUIDELINES

User's manual for OTPdirekt Internet Banking. v.1.0

ELECTRONIC BANKING. RFT MT101 File Format Description Ver

More information on completing payment details

SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES

ISO PAYMENT GUIDE. Messages: Pain Pain

ELECTRONIC BANKING. SWIFT MT 940 Customer Statement Message and SWIFT MT 942 Interim Transaction Report Ver

Format Description. SWIFT MT202: General Financial Institution Transfer

Bankline internet banking import file layout user guide

SEPA DATA MODEL. Reason for Issue Approved by the EPC Plenary on 13 December 2006

Format Differences SWIFT FIN MT940 MT942

INTERNATIONAL BANK ACCOUNT NUMBER (IBAN) AND BANK IDENTIFIER CODE (BIC) IN PAYMENTS

NAB Connect Consolidated File Format Specifications

SEPA Direct Debit Unpaid Report File Format

HSBC Your Guide to SEPA. Capitalising on the opportunities

ANZ TRANSACTIVE FILE FORMATS WEB ONLY Page 1 of 118

FILES FORMATS USED IN ING ONLINE

Terms and Conditions applicable to Correspondent Banks 1 st November 2015

FILE FORMAT OF PAYMENT ORDERS ACCEPTED BY CITIBANK EUROPE PLC FOR CITIBUSINESS DIRECT INTERNET BANKING

Spanish legacy branch code 4 numbers. Spanish legacy bank code 4 numbers

SEPA. Frequently Asked Questions

ERP SEPA readiness checklist

SEPA Credit Transfer. Readiness Checklist

ISO ACCOUNT STATEMENT GUIDE. v 1.3

1.1. Overview Direct credits Direct debits Nab direct credits... 12

PAIN.002. Format description Functional

Creating international money transfers

Implementing SEPA in Belgiu m

Hal E-Bank Foreign payments (Format of export/import files)

Standards MX Message Implementation Guide and Rule Book

SEPA - Frequently Asked Questions

Entering payment order abroad and payment order in a foreign currency in the Czech Republic via electronic banking service ČSOB InternetBanking 24

SEPA DIRECT DEBIT SCHEME IMPLEMENTATION GUIDELINES

BEST client format supported by KB (valid from 28th November 2015)

Background. IBAN Overview

Single Euro Payments Area

in Fr a nce Introduction

Coded statement of account (CODA)

Guide. 1 Dec Introduction of the global Structured Creditor Reference in Finnish companies. 1 December 2010

DESCRIPTION OF SEPA XML FORMAT FOR ING BUSINESSONLINE IMPORT AND EXPORT TEMPLATES

SEPA Direct Debit Creditor Guide

EBS204 Version 1 Published November EBS204 Version 2 Published July EBS204 Version 3 Published February 2001

International ACH Transactions (IAT) File Format Guide

Terms and conditions Cross-border trading

Foreign payment orders

STANDARD 48 FORMAT OF THE IBAN ISSUED IN THE UK (International Bank Account Number) June 2007

FAQ on the UAE Funds Transfer System (FTS)

SEPA in Netherlands. Quick facts. International Bank Account Number (IBAN) IBAN structure. 66 SEPA Country Sheets - Netherlands

1. VERSIONSHISTORY MERCHANT TRANSACTION RECONCILIATION FILE GENERAL STRUCTURE FILE DETAILED FILE DESCRIPTION...

Format description of MT103 (Multicash PLA) foreign payment file.

pg. 2 pg. 6 pg.8 pg. 20

Format Reference Guide

OUTGOING PAYMENTS ISO APPLICATION GUIDELINE

Fee schedule and cut-off times applying to International Payments. Sampo Bank Plc, Finland. A fully owned subsidiary of Danske Bank A/S

Guidance on reason codes for SDD R-transactions

Intra-day payment Frequently asked questions

Nordea Bank AB Lithuania branch Price List for corporate customers Valid from 1 st of September, Contents

MT 103+ Single Customer Credit Transfer

File format DETAILS RECORD TYPES ABBREVIATIONS (LEGEND) GENERAL REMARKS. Welcome to

Electronic foreign currency payments, LUM2

Format Description SWIFT FIN MT101. Rabobank

XML ACCOUNT STATEMENT. Service Description

International Products & Services. Fees, charges and services explained.

Terms and conditions - Cross-border payments

SEPA Direct Debit Initiation Customer-to-Bank Implementation Guidelines for the Netherlands

for CONSUMERS Information on the SINGLE EURO PAYMENTS AREA

International transfers are not always easy to understand.

INTERNATIONAL BANK ACCOUNT NUMBER (IBAN)

User Manual Internet Banking Enter and Send Orders

FAQ on the International Bank Account Number (IBAN) 2. Question: Can you explain briefly the IBAN for Bahrain?

SEPA Country Guide Italy. Introduction

INTERNATIONAL BANK ACCOUNT NUMBER (IBAN) AND BANK IDENTIFIER CODE (BIC) IN PAYMENTS

SEPA Creditors Guide. SEPA Direct Debit Core Scheme. Version 1.3 Final Page 1 of 38

International payments Tariff for corporate customers effective from 1 January 2015

State Bank of Pakistan. Guidelines: IBAN Implementation in Pakistan

Minimum / Maximum charge

Minimum / Maximum charge. Quarterly, on the daily balance of the unutilised balance of the loan.

Nordea Account structure. Corporate egateway

Business On Line. The complete online package for your business

SEPA CORE DIRECT DEBIT SCHEME INTER-BANK IMPLEMENTATION GUIDELINES

SEPA Country-Specific Information Hungary

Fee schedule and cut-off times applying to International Payments & Trade Finance. Denmark

Functional specification for Payments Corporate egateway

Form Payments statistics (formerly form-9006)

Transcription:

General Information The MT940 customer statement message is an electronic message containing financial statement information for customers concerning their accounts. Danske Bank can send a MT940 either produced by the bank itself or received from another bank. The format of the message is a SWIFT compliant standard format and is sent via the SWIFT network or through the Business Online file handling system as well as via direct communication channels. MT940 stands for Message Type 940. The content can be adjusted according to the individual descriptions below. Block Information A MT940 message is divided into three blocks of information each consisting of a number of fields. Some of these fields are mandatory while others are optional. Each field must abide by the rules specified in its format to ensure the standardisation of the message. There is always one and only one Header and one End Block in a MT940 message, and there can be several Transaction Blocks or none. Blocks Header Block Transaction Blocks End Block Fields 20: Transaction reference number 25: Account Identification by IBAN or BBAN account number The account number will be preceded by BIC code if delivered in Business Online or via direct communication channels other than SWIFT NET FIN 28C: Sequential number of the statement and sequence 60F: Opening Balance 86: In case of cash pool account, a text regarding the cash pool will be written if delivered through Business Online or via direct communication channels other than SWIFT NET FIN 61: Details of the transaction 86: Additional information 86: In case of cash pool account, a text regarding the cash pool will be written if delivered through the SWIFT NET FIN network 62M/62F: Intermediate closing balance / Final closing balance 64: Value balance Example of Blocks in a MT940 message: Header :20:3996-3001123456 :25:DABADKKK/1122334 :28C:00084/001 :60F:C031002DKK40435,15 Page 1 of 13

Transaction :61:1206150615DK4000,15NMSCTransaction Details :86:Additional Information concerning the transaction is presented here. A maximum of 6 lines with 65 characters each may be used to present this information, each line consisting of a set number of characters. Transaction Transaction End :61:1206190619DK300,15NTRFTransfer :86:/REMI/Loan payment :61:1206270627DK150,NTRFArbi/deposit//1323333800 :86: Arbi/deposit 1323333800 :62F:C1206300630DKK44885,45 :64: C1206300630DKK44885,45 Field Information Fields may be mandatory or optional. Some fields are divided into subfields. Information in all fields must abide by the formatting rules described below. For example, a field may require that a date be specified in the format YYMMDD (e.g. 120126 = January 26 th 2012). This field s format will be denoted as 6!N meaning always 6 digits Formatting detailed Format Description Occurrence (e.g. The number of occurrences 8)! Meaning always (if missing, read Up to ) [] The brackets contain optional logical expressions N Digits only D Numbers with comma (,) used to precede any decimals C Alphabetic letters (all cases) and digits only (alphanumeric) X Any character permitted within the EBCDIC code A Uppercase alphabet letters only Special Characters which must be present characters e.g. //. Examples: 1. 10n = Up to 10 digits 2. 6!n[4!n]2a[1!a] = Always 6 digits (followed be an optional always 4 digits) followed by 2 uppercase alphabet letters (followed by an optional always 1 uppercase alphabet letter) 3. 15d1!a3!c16x[//16x][34x] = Up to 15 numbers which may include a comma followed by always 1 uppercase letter followed by always 3 alphanumeric characters, followed by up to 16 EBCDIC characters (followed be an optional two slashes (//) and 16 EBCDIC characters) (followed by an optional up to 34 EBCDIC characters) Page 2 of 13

Details of each Field Field 20: Transaction Reference Number Presence: Mandatory Field: Contains the transaction reference number 16x :20:3996-3258112345 Field 25: Presence: Account Identification Mandatory 35X Examples with IBAN account numbers: :25: DE03203205004989012345 :25: DK0230003617012345 :25: FI0281199710012345 :25: GB02DABA30128122012345 :25: IE02DABA95182390012345 :25: NO0281013312345 :25: PL02236000050000004550212345 :25: SE031200000001220012345 :25: FI0734499400012345 Examples with BBAN account numbers: :25: 4989012345 (DE) :25: 3617012345 (DK) :25: 81199710012345 (FI) :25: 22012345 (GB) :25: 90012345 (IE) :25: 8101.33.12345 (NO) :25: 4550212345 (PO) :25: 1220-01-12345 (SE) :25: 344994-00012345 (FI) For unformatted the following BBAN account numbers are valid: :25: 30128122012345 (GB) 25: 95182390012345 (IE) Page 3 of 13

If the MT940 is received via other channels than SWIFT NET FIN, the Bank Identification Code and a slash will precede the actual account number. It s possible to choose IBAN in all countries regardless of channel. Please contact customer support if the Bank Identification Code should be removed or if you require IBAN instead of BBAN in field 25. Examples: :25: DABADKKK/DE03203205004989012345 :25: DABADKKK/DK0230003617012345 :25: DABADKKK/FI0281199710012345 :25: DABADKKK/GB02DABA30128122012345 :25: DABADKKK/IE02DABA95182390012345 :25: DABADKKK/NO0281013312345 :25: DABADKKK/PL02236000050000004550212345 :25: DABADKKK/SE0312000000012200112345 If you have questions then please contact EDI Support- on Integration Services Homepage: Field 28C: Statement Number/Sequence Number Presence: Mandatory Field: Contains the statement number followed by an optional sequence number 5n[/5n] :28C: 00532/001 (First message of statement 532) :28C: 00532/002 (Second message of statement 532) Field 60F/M: Opening Balance (60F for first opening balance and 60M for interim opening balance) Presence: Mandatory 1!a6!n3!a15d Subfield 1: Debit/Credit mark 1!a C for credit D for debit Subfield 2: Date 6!n YYMMDD Page 4 of 13

Subfield 3: Currency 3!a Valid ISO 4217 code Subfield 4: Example Amount 15d maximum 15 numeric characters, decimal format is comma :60F:C020306DKK985623,04 Page 5 of 13

Field 61: Presence: Subfield 1: Subfield 2: Subfield 3: Subfield 4: Subfield 5: Subfield 6: Subfield 7: Note! Subfield 8: Statement Line Optional 6!n[4!n]2a[1!a]15d1!a3!c16x[//16x][34x] Value date 6!n (YYMMDD) Entry date [4!n] (optional MMDD) Debit/Credit Mark 2a C for Credit D for Debit RC for Reversal of credit (debit entry), RD for Reversal of debit (credit entry) Funds Code (Third character of currency code) [1!a] Amount 15d Transaction Type Identification Code 1!a3!c (where 1!a is within the character set { S, N, F }) Reference for the Account Owner 16x If reference exceeds 16 characters, the extra characters (in a readable form) will be delivered in the next subfield! Account Servicing Institution s Reference [//16x] Subfield 9: Supplementary Details [34X] /OCMT/FIM128945,05/ :61:0203010228CK366336,2NTRFArbi/deposit//1323333800 Page 6 of 13

Transaction Type Identification Code Every transaction is identified by a transaction code. The code is a 4 letter code where the first letter is always determined by the following rule set: For entries related to SWIFT transfer instructions and subsequent charge messages, the format of the identification code is always: S3!n The last three characters will indicate the message type of the SWIFT message, causing the entry (for debit entries) or the message type of the SWIFT message used to advise the account owner (for credit entries). Examples: S103, S202 For entries related to payment and transfer instructions, including related charge messages not sent through SWIFT, format is N3!c. Examples: NMSC, NCHG For entries being first advised by the statement (items originated by the account servicing institution), format is always: F3!c Examples: FINT, FCHG The last 3 letters of the transaction type identification code are determined by the transaction type. See the table below: List of transaction types and their transaction type codes: Payment and transfer BOE (Bill of exchange) instructions including CLR (Cash letters / Cheques Remittance) related charge messages CHG (Charges and other expenses) not sent through SWIFT. CMS (Cash Management Item Sweeping) N + CMZ (Cash Management Item - Zero Balancing) CHK (Cheques) COL (Collections) COM (Commissions) DDT (Direct Debit Item) DIV (Dividends-Warrants) DCR (Documentary credit) ECK (Euro cheques) EQA (Equivalent amount) FEX (Foreign exchange) INT (Interest) LDP (Loan deposit) MSC (Miscellaneous) RTI (Returned item) SEC (Securities) STO (Standing order) TCK (Travellers cheques) TRF (Transfer) CMT (Topping) Page 7 of 13

For entries being first advised by the statement (items originated by the account servicing institution) F + For entries related to SWIFT transfer instructions and subsequent charge messages S + CHG (Charges and other expenses) CMS (Cash Management Item Sweeping) CMZ (Cash Management Item - Zero Balancing) CHK (Cheques) INT (Interest) RTI (Returned item) 101 (SWIFT message 101) 103 (SWIFT message 103) 190 (SWIFT message 190) 191 (SWIFT message 191) 200 (SWIFT message 200) 201 (SWIFT message 201) 202 (SWIFT message 202) 203 (SWIFT message 203) 205 (SWIFT message 205) 300 (SWIFT message 300) 320 (SWIFT message 320) 400 (SWIFT message 400) 554 (SWIFT message 554) 556 (SWIFT message 556) Page 8 of 13

Field 86: Presence: Note: Information to Account Owner Optional maximum 6 x 65x (up to 6 lines consisting of up to 65 EBCDIC code characters) :86:/RREF/3825-0031367289 /EREF/1309101116-0000001 /ORDP//NAME/AB AG /REMI/Inv. 1000217666-22.724,00, Inv. 1000217693-68.130,00,in v. 1000217801-16.470,00 /RCMT/EUR 100.000,00 /CHRG/DKK 4,00 As a starting point, field 86 is used to supply extra information related to the preceding statement line in file 61. However, a separate field 86 can also be supplied. If other channels than SWIFT NET FIN are used as receiving channel - the first instance of field 86 may contain general information about the account being part of a Group Cash Pool arrangement. This instance is not related to a statement line. If SWIFT NET FIN is used as receiving channel, the same information may be given as a last Instance of field 86, which is not related to a statement line. :86:This account is part of a Group Cash Pool arrangement. Credit respectively debit balances based on the sum of entries represent intra-group outstanding only, and do not reflect outstanding issues with Danske Bank. The information will be structured with some of the following labels dependant of transaction types: Tag Description /IREF/ Instruction ID / Transaction ID /SVCL/ Identification code of the Scheme /ORDT/ /RREF/ Original due date of the collection Danske Bank reference of the transfer from abroad /EREF/ Creditors End to end reference from the original payment. If not present, the value will be 'Not Provided' /FREF/ Filing Code (accounts in Finland only) /ORDP//NAME/ Organisation name of payment initiator from the original payment /ID/ Organisation ID of payment initiator from the original payment. If no name exists, the ID will have SWIFT code /ORDP//ID/ /REMI/ The remittance information from the original payment /CDTRREFTP//CD/ Remittance information, Structured part, Reference Type e.g. 'SCOR'. Only present if payment initiator have used the Structured advice part of the ISO 20022 XML customer credit transfer message /ISSR/ Remittance information, Structured part, Issuer. Only present if payment initiator have used the Structured advice part of the ISO 20022 XML customer credit transfer message /CDTRREF/ Remittance information, Structured part, Reference. Only present if payment initiator have used the Structured advice part of the ISO 20022 XML customer credit transfer message /ULTD//NAME/ Name of Ultimate Debtor from the original payment /ID/ Organisation ID of Ultimate Debtor from the original payment If no name exists, the Org ID will have SWIFT code /ULTD//ID/ /ULTB//NAME/ Name of Ultimate creditor from the original payment /RTRN/ Return reason code if the payment is returned /RCMT/ = Received Amount - preceded by currency code /CHRG/ Danske Bank total charges amount related to the specific transaction Page 9 of 13

/XCRT/ /BENM/ preceded by currency code Exchange rate preceded by currency codes involved in the exchange. The codes are separated by a dash between "From currency " and "To currency" e.g. DKK-EUR 7.451286 Beneficiary In connection with this the following codes can appear: /NAME/ = Name of beneficiary /ADDR/ = Address of beneficiary /IBAN/ = International bank account number /BBAN/ = Base bank account number /BIC/ = Bank identifier code /CHGS/ /MCID/ /ORDP/ /ORID/ /RCMT/ /RCTS/ /REMI/ /ULTB/ /ULTD/ Charges Merchant Id Ordering party - In connection with this the following codes can appear: /NAME/ = Name of beneficiary /ADDR/ = Address of beneficiary /IBAN/ = International bank account number /BBAN/ = Base bank account number /ID/ = Organization Id (Business number) Ordering Id Received amount Received timestamp Remittance information - In connection with this the following codes can appear: /CDTRREFTP//CD/ = Creditor reference type /ISSR/ = Issuer /CDTRREF/ = Creditor reference Ultimate creditor - In connection with this the following codes can appear: /NAME/ = Name /ID/ = Id Ultimate debtor - In connection with this the following codes can appear: NAME/ = Name /ID/ = Id SEPA Direct Debit Transactions Information for account owner on SEPA related transactions item may contain the following labels per transaction type: Incoming SEPA Direct Debit: Tag /IREF/ Description Instruction ID Page 10 of 13

/ID/ /SVCL/ /ORDT/ /REMI/ /EREF/ Transaction ID Identification code of the Scheme Original due date of the collection The remittance information Creditor s reference Outgoing SEPA Direct Debit Initiation: Tag /EREF/ /IREF/ /PREF/ /SVCL/ /MARF/ /CSID/ /ORDP//NAME/ Description Creditor s reference Instruction ID / Transaction ID Payment Information ID Identification code of the Scheme Mandate reference Identifier of the creditor The name of the debtor Incoming SEPA Direct Debit Return (after settlement date): Tag /EREF/ /IREF/ /SVCL/ /MARF/ /CSID/ /RTRN/ /MISC/ /OTHR/ /ORDP//NAME/ Description Creditor s reference Instruction ID / Transaction ID Identification code of the Scheme Mandate reference Identifier of the creditor Reason code for non-acceptance (Reject, Return or Refund) Original amount Interest Compensation to Debtor Bank The name of the debtor Field 62F/M: Closing Balance (F for the final balance and M for interim balance) Presence: Mandatory 1!a6!n3!a15d (D/C Mark)(Date)(Currency)(Amount) Subfield 1: D/C Mark 1!a C for credit D for debit Subfield 2: Date 6!n YYMMDD Page 11 of 13

Subfield 3: Currency 3!a Valid ISO 4217 code Subfield 4: Amount 15d :62F:C020228DKK12724930,14 :62M:C020228DKK12724930,14 Field 64: Presence: Closing Available Balance (always Value date balance) mandatory 1!a6!n3!a15d (D/C Mark)(Date)(Currency)(Amount) Subfield 1: D/C Mark 1!a C for credit D for debit Subfield 2: Date 6!n YYMMDD Subfield 2: Currency 3!a Valid ISO 4217 code Subfield 3: Amount 15d :64:C020228DKK6698733,27 Page 12 of 13

Change log Version Date Change 1.0 2014-12-09 Document created Page 13 of 13