Format Description MT940S - Rabobank - Particulieren
Format descriptionMT940 Structuredversion 1.5.3Rabo Direct Connect,SWIFT FileAct andRabo Internetbanking(Professional)August 2019
Contents1.RabobankMT940 CUSTOMER STATEMENT MESSAGE31.1General information31.2Format structure41.3Schematic representation42.TECHNICAL DESCRIPTION63.FIELD 86: DESCRIPTION173.1Considerations173.2Field 86: SEPA Credit Transfer and non-SEPA transfer scenarios193.3Field 86: SEPA Direct Debit and non-SEPA collection scenarios20APPENDIX 1: TRANSACTION TYPE CODES21APPENDIX 2: REASON RETURN CODES22APPENDIX 3: EXPECTED CHANGES23CHANGE LOG24Format description MT940 StructuredAugust 2019 Version 1.5.32
1. MT940 Customer Statement Message1.1General informationThe official name for this export format is “MT940 Customer Statement Message”, an internationalformat that is used as the digital equivalent of the official paper statements. On the statement theopening balance and closing balance listed on the entry date as well as specific data of all bookingson the account.The MT940 Structured as supplied by Rabobank is not fully compliant with SWIFT. For example, themessage starts with the tag :940: and the message size is not limited to the prescribed 2.000 charactersof the SWIFT MT940 base message.The statement does not contain transaction lines (field 61 and 86) if there are no transactions for thespecific entry date. The message supplied by Rabobank is always closed with field 62F, 64 or 65.The following table describes the characteristics of the MT940S per channel:RIB (Pro)RDC/SWIFT FileActLayout file name- Actual dowload: MT940S Date Time ContractIdMT940S O download dateStatementTransportAgreement.zip time.swi- Selection/calender:MT940S A download datetime.swiNumber of accounts in 1 file.1 or more accounts- 1 or more Rabobank accounts(customer’s choice).- only 1 Multibank or 1 RNB accountper file (.zip).Sequence accounts in 1 file.In accordance to theIn accordance to the sequence ofsequence in RIB (Pro)IBANNumber of statements in 1 file 1 or more statements1 or more statementsSelection period statements in 1 or more bookdates1 bookdate1 fileSelection period transactions in 1 bookdate1 bookdate1 statementIf applicable transactions are shown not-cumulated in the MT940 Structured. This applies to accountsheld at local branches of Rabobank and to Corporate accounts which are held at WRR (formerRabobank International).The MT940 Structured is available for Rabobank ‘s current accounts, savings accounts, Multibankaccounts (non-Rabobank accounts) and Rabo Network Banking (RNB) accounts (accounts held at ourRabobank branches in Germany, Belgium and the United Kingdom).Rabobank’s current accounts are accounts held at local branches of Rabobank or Corporate accountsheld at WRR former Rabobank International.For Multibank and RNB accounts, no statement is provided by Rabobank when the Rabobank has notreceived an incoming SWIFT MT940 for that particular date.This format description of MT940 Structured only applies to exports of Rabo Internetbanking (Professional), Rabo Direct Connect and SWIFT FileAct.This document is not applicable for the MT940 Structured of RIB Online accounting.RabobankFormat description MT940 StructuredAugust 2019 Version 1.5.33
1.2 Format structureEach SWIFT MT940-message starts with a fixed header-record (:940:) followed by record 20, 25, 28C, 60F,61 (0-n). Each record 61 contains record 86 (0-6), 62F and (optional) record 64 and 65.MT940 Structured provides an opening and closing balance and the associated intermediate bookings.For this format exporting book balances is required which means that only complete book days can beexported. Each block of information in a customer statement message is preceded by a field (label, tag).The contents of the field may consist of different elements. The file begins with a fixed value of “940”.Each statement in the file begins with field-20 and ends with the following field-20 or when the end offile is reached. The sequence of fields within a single message is described in Chapter 2. Within onestatement a group consisting of field-61 and field-86 can occur multiple times. Code words within field86 are separated by a slash (/). These codes are used to create structure in field 86 to separate the different information.1.3Schematic representationThe image in this paragraph shows the file structure of the MT940:RabobankFormat description MT940 StructuredAugust 2019 Version 1.5.34
RabobankFormat description MT940 StructuredAugust 2019 Version 1.5.35
2. Technical descriptionLength[ ] optionald numeric with decimalsn numericx alphanumeric! fixed lengtha textc values code listField/SubfieldMandatory Description // Optional Fieldname940MFile header20MTransaction reference number5!xRecordcode4!xReference16x21ORelated reference25MIdentification of accountRecord code4!xAccount number35xContentRabobank account: descriptionMultibank/RNB account: description:940:Not SWIFT-compliant.Not SWIFT-compliant.:20:Is used.Is used.Is filled with value 940 S followedby the bookdate of the statement innotation YYMMDD .Example “940S190624”.Is not used.Is filled with the content of field-20 fromthe incoming SWIFT MT940.Is used.Is used.:25:Is not used. IBAN space Currency This field is filled with the accountIf available account number is shown in number (IBAN / BBAN) as registered atIBAN including the currency of the acRabobank and will be enriched with thecount.currency code from mid October 2019.The notation of this field will be: IBAN/BBAN space currency code For example:DE89370400440532013000 EURFR1420041010050500013M02606 GBPRabobankFormat description MT940 StructuredAugust 2019 Version 1.5.36
LengthField/SubfieldMandatory Description // Optional Fieldname[ ] optionald numeric with decimalsn numericx alphanumeric! fixed lengtha textc values code listContentRabobank account: descriptionMultibank/RNB account: description021000021 USDNote: when the accountnumber has alength of 35 positions, only the first 34positions of the accountnumber arereported.28CMStatement / Sequence numberRecord code5!xStatement number5n:28C:Is used.Is used.The statement number is filled with year year bookdate number year year wil be changed annuallywith “ 1”and the bookdate number is resetted every year and starts with‘001’.The statement number is filled with thecontent from field-28C of the incomingSWIFT MT940.For example:1 January 2019: ‘19001’1 January 2020: ‘20001’60FRabobankMSeparation[/]Is not used.Is not used.Sequence number[2!n]Is not used.Is not used.Opening balanceRecord code5!x:60F:Is used.Is used.Debit / Credit1!aValue D and CIs used.This is filled with the debet/credit indicator from field-60F of the incomingSWIFT MT940.Format description MT940 StructuredAugust 2019 Version 1.5.37
LengthField/SubfieldMandatory Description // Optional Fieldname[ ] optionald numeric with decimalsn numericx alphanumeric! fixed lengtha textc values code listDate6!nCurrency code3!xAmount15!dContentRabobank account: descriptionMultibank/RNB account: description YYMMDD The date is equal to the bookdate of the This is filled with the date from field- 60Fclosing balance of the previous stateof the incoming SWIFT MT940.ment.ISO currency codeCurrency of the account.This is filled with the currency codefrom field- 60F of the incoming SWIFTMT940.The number of decimals is Is used.Is used.in accordance to ISO4217.The decimal separator, acomma, is included in thefixed length of 15. Theamount will be filled withleading zeros.For example:(EUR) 000000000032,00(KWD) 00000000001,000(JPY) 00000123456789,61O [0-n]Statement lineRecord code4!x:61:Is used.Is used.Sub 1 MValue date6!n YYMMDD Value date of the transaction.Sub 2 OEntry date[4!n] MMDD Is not used.This subfield is filled with the value datefrom field-61 sub-1 of the incomingSWIFT MT940.The entry date is filled with the datefrom field-61 sub-2 of the incomingSWIFT MT940.When the entry date is not available, theRabobankFormat description MT940 StructuredAugust 2019 Version 1.5.38
LengthField/SubfieldMandatory Description // Optional Fieldname[ ] optionald numeric with decimalsn numericx alphanumeric! fixed lengtha textc values code listSub 3 MDebit / Credit2aSub 4 OFunds code[1!a]Sub 5 MAmount15!dContentValue D, C, RD and RCRabobank account: descriptionValue D and C.Is not used.The number of decimals is Is used.in accordance to ISO4217.The decimal separator, acomma, is included in thefixed length of 15. Theamount will be filled withleading zeros.Multibank/RNB account: descriptionentry date is filled with the date fromfield-62F.Value D, C, RD and RC.This subfield is filled with the contentfrom field-61 sub-3 of the incomingSWIFT MT940.The funds code is filled if available infield-61 sub-4 of the incoming SWIFTMT940.Is used.For example:(EUR) 000000000032,00(KWD) 00000000001,000(JPY) 00000123456789,Sub 6 MRabobankTransaction typeIdentification code1!a3!cThis subfield is filled with N transaction type code .The code may be incomplete. For thecorrect code, refer to codeword 'TRCD'in field 86.More information about transactiontype codes of Rabobank, see Appendix1.Format description MT940 StructuredThis subfield is filled with the contentfrom field-61 sub-6 of the incomingSWIFT MT940.August 2019 Version 1.5.39
LengthField/SubfieldMandatory Description // Optional FieldnameSub 7 MReference for theaccount owner[ ] optionald numeric with decimalsn numericx alphanumeric! fixed lengtha textc values code list16xContentRabobank account: descriptionMultibank/RNB account: descriptionIn case of non-SEPA transactions thissubfield is filled with the transactionreference.This subfield is filled with thecontent from field-61 sub-7 of the incoming SWIFT MT940.In case of a SEPA transaction, fhis fieldspecifies the reference which is availablein field 86 on the first position.Used values:‘EREF’: end-to-end reference‘MARF’: mandate reference‘PREF’: batch reference‘NONREF’: non-SEPA transactionSub 8 OReference of the accountservicing institution[//16x]Sub 9 OAdditional information[34x]Note: When MARF is present, EREFmay also be available in field 86.This subfield is filled with a uniqueRabobank reference number.This subfield is filled if available with thecontent from field-61 sub-8 of the incoming SWIFT MT940.This subfield contains the counterparty This subfield is filled if available with theaccount number. This can also be acontent from field-61 sub-9 of the insavings account.coming SWIFT MT940.It is filled in the following order: IBAN or NON-IBAN or If there is no counterparty account number available then it isfilled with 10 zeros.RabobankFormat description MT940 StructuredAugust 2019 Version 1.5.310
LengthField/Subfield86Mandatory Description // Optional FieldnameO [0-6]ContentRabobank account: descriptionMultibank/RNB account: descriptionSub 9 starts on a new line according toSWIFT.Rabobank uses code words tostructure the provided informationto the account owner.Information to accountowner6*65xRecordcode4!x:86:Mandate reference35x/MARF/End-to-End reference35x/EREF/Batch reference35x/PREF/Return reason4!c/RTRN/CounterpartyRabobank[ ] optionald numeric with decimalsn numericx alphanumeric! fixed lengtha textc values code listThis field is filled with the content fromfield-86 of the incoming SWIFT MT940.Code words used by Rabobank do notapply for Multibank accounts.Remittance information provided by the Usage and meaning of code wordscustomer will not be supplemented by used by non-Rabobank are unknown forRabobank with (SEPA) information.Rabobank.(SEPA) information can be derived fromthe code words in field 86Is used.Is used./BENM/ or /ORDP/The mandate reference is preceded by/MARF/.The End-to-End Id is preceded by/EREF/.The batch reference of a SEPA batch ispreceded by /PREF/.-Return reason code, please refer toAppendix 2 for the most relevant codesand their description.Code preceding counterparty data.-Format description MT940 StructuredAugust 2019 Version 1.5.311
LengthField/SubfieldMandatory Description // Optional Fieldname[ ] optionald numeric with decimalsn numericx alphanumeric! fixed lengtha textc values code listContentRabobank account: descriptionMultibank/RNB account: description-Name70x/NAME/1Counterparty name.Id35x/ID/Counterparty Id, unless the Id is theCreditor Id. Creditor Id may be availableafter code /CSID/.Remittance information can bepresent in a structured and/orunstructured form.If unstructured the value is beplaced after /REMI/.If structured, it is followed by thefour codes below.Remittance informationStructured remittanceinformation390x/REMI/1Remittance information provided by thecustomer will not be supplemented byRabobank with (SEPA) information.(SEPA) information can be derived fromthe code words in field 86CDTRREFTP//CD/SCOR/Structured payment referenceISSR/CUR/CDTRREF/ pay ( betalingskenmerk).ment reference CD if present, this is filled with ‘SCOR’.ISSR if present, it can be filled with:CDTRREFTP//CD/SCOR/- ‘CUR’ issuer NL- payment reference;CDTRREF/ payment ref- - ‘ISO’ issuer international paymenterence reference;- ‘BBA’ issuer Belgian payment referCDTRREFTP//ISSR/CUR/ence;1Only applicable for MT940S of savings accounts: in case of a non-SEPA savings transaction, the name of the counterparty is not preceded with /ORDP//NAME/ or /BENM//NAME/ but with code word /REMI/. For example:/REMI/ Bouwbedrijf H. JanssenAanvullen saldo spaarrekeningRabobankFormat description MT940 StructuredAugust 2019 Version 1.5.312
LengthField/SubfieldMandatory Description // Optional FieldnameCreditor ID[ ] optionald numeric with decimalsn numericx alphanumeric! fixed lengtha textc values code list35xUltimate counterpartyRabobank account: descriptionCDTRREF/ payment reference - own issuer of own payment reference.CDTRREFTP//CDTRREF/ payment reference /CSID/Creditor Identifier./ULTD/ of /ULTB/Multibank/RNB account: description-Name70x/NAME/Name of the ultimate counterparty.-Id35x/ID/ID of the ultimate counterparty.-Purpose of the transaction.-Purpose code.The purpose code is incorrectly filledwith the category purpose code.Unknown when this will be filled withthe purpose code.The 3- and 4- numerical transactiontype code will be shown. More information about transaction type codes ofRabobank, see Appendix 1.Notation: CCYY-MM-DD.For example: ‘2018-04-09’The instructed amount and currencywill be shown if the booked amountdiffers from the instructed amount.For example: e code4!c/CD/Transaction type code4c/TRCD/Interbank settlement date10/ISDT/Instructed amount3!a15d/OCMT/Format description MT940 Structured--August 2019 Version 1.5.313
LengthField/SubfieldMandatory Description // Optional Fieldname[ ] optionald numeric with decimalsn numericx alphanumeric! fixed lengtha textc values code listRabobankThe exchange rate of the incoming and outgoing transaction will be shown.The rate is displayed as "1 currency unitof the account currency in relation tothe currency of the instructed amount.The deducted charges which arecharged by the (foreign) banks.The order in which codewords areshown is the same as the processing ofthe transaction by the banks.For example: 3//CHGS4//CHGS5/NameMRabobank account: descriptionEchange rateInitiating party62FContent/INIT/Multibank/RNB account: description-70x/NAME/The name of the initiating part y whohas initiated the payment.-Field code5!x:62F:Is used.Is used.Debit / Credit1!aValue D and CIs used.Date6!n YYMMDD Is used.Currency code3!aISO currency codeCurrency of the account.This is filled with the debet/creditindicator from field-62F of theincoming SWIFT MT940.This is filled with the date fromfield-62F of the incoming SWIFT MT940.Currency of the account.Amount15!dThe number of decimals is Is used.in accordance to ISO4217.The decimal separator, aClosing BalanceFormat description MT940 StructuredIs used.August 2019 Version 1.5.314
LengthField/SubfieldMandatory Description // Optional Fieldname[ ] optionald numeric with decimalsn numericx alphanumeric! fixed lengtha textc values code listContentRabobank account: descriptionMultibank/RNB account: descriptioncomma, is included in thefixed length of 15. Theamount will be filled withleading zeros.For example:(EUR) 000000000032,00(KWD) 00000000001,000(JPY) 00000123456789,64OClosing (available) value balanceIs used.Is used.Field code4!x:64:Is used.Is used.Debit / Credit1!aValue D and CIs used.Date6!n YYMMDD Currency code3!aISO currency codeIs equal to the bookdate of the statement.Currency of the account.This is filled with the debet/creditindicator from field-64 of theincoming SWIFT MT940.This is filled with the date fromfield-64 of the incoming SWIFT MT940.Currency of the account.Amount15!dThe number of decimals is Is used.in accordance to ISO4217.The decimal separator, acomma, is included in thefixed length of 15. Theamount will be filled withleading zeros.Is used.For example:(EUR) 000000000032,00RabobankFormat description MT940 StructuredAugust 2019 Version 1.5.315
LengthField/SubfieldMandatory Description // Optional Fieldname[ ] optionald numeric with decimalsn numericx alphanumeric! fixed lengtha textc values code listContentRabobank account: descriptionMultibank/RNB account: description(KWD) 00000000001,000(JPY) 00000123456789,65O [0-4]Forward (available) value balance(total 4 days in the future)Field code4!xIs used.Is used.:65:Is used.Is used.Debit / Credit1!aValue D and CIs used.Date6!n YYMMDD Is used.Currency code3!aISO currency codeCurrency of the account.This is filled with the debet/creditindicator from field-65 of theincoming SWIFT MT940.This is filled with the date fromfield-65 of the incoming SWIFT MT940.Currency of the account.Amount15!dThe number of decimals is Is used.in accordance to ISO4217.The decimal separator, acomma, is included in thefixed length of 15. Theamount will be filled withleading zeros.Is used.For example:(EUR) 000000000032,00(KWD) 00000000001,000(JPY) 00000123456789,86RabobankOInformation to AccountOwner6*65Is not used.Format description MT940 StructuredIs not used.August 2019 Version 1.5.316
3. Field 86: DescriptionInformation described in this chapter is only applicable for Rabobank (savings) accounts.3.1 ConsiderationsCodes and descriptions are only reported if the information is present in the transaction.Descriptions and code words are separated with slashes.For example: /MARF/12345678/EREF/2456425/.Information in field 86 is filled continuously in 6 strings of 65 positions.For EREF/ABCDEFGHIJKLMNOPQ CDEFGHIABCDEFGHIJKLMNOPQRSTU BCDEFGHIJKLMNOP BCDEFGHIField 86 is built up to 6 x 65 positions. In case there is more information available than field’smaximum, the order of feedback is according to the order in which they are listed in thetables, see chapter 3.2 and 3.3.Unstructured Remittance Information ( URI) and Structured Remittance Information ( SRI)can occur both in field 86.For example:/REMI/ Unstructured Remittance Information /CDTRREFTP//CD/SCOR/ISSR2/CUR/CDTRREF/ Structured Remittance Information In case of structured remittance information the following presentation are possible, dependenton the provided information at RREF/ payment reference /REMI//CDTRREFTP//CD/SCOR/CDTRREF/ payment reference /REMI//CDTRREFTP//ISSR2/CUR/CDTRREF/ payment reference /REMI//CDTRREFTP//CDTRREF/ payment reference Spaces at the end of each description line (provided by the customer) may be omitted.SDD-in
Rabobank Format description MT940 Structured August 2019 Version 1.5. 3 1. MT940 Customer Statement Message 1.1 General information The official name for this export format is “MT940 Customer Statement Message”, an international format that is used as the digital equivalent of the official paper statements. On the statement the
Diemer Salome is Global Head of Non-Financial Risk for Rabobank. Previously he was Head of Global Risk Advisory and Project Manager for Basel III at Rabobank. He has been Director of The Risk Management Centre and was an advisor to the Board at Bank BGZ (Poland). He was also the Head of Credit Policies & Procedures in the Netherlands for Basel II.
3.3 BTL’91 Field description 20 3.4 BTL’91 Appendix 29 4 Rabo MT940 Extended 35 4.1 General information. 35 4.2 SWIFT MT940 Specifics 35 4.3 SWIFT MT940 file structure 37 4.4 SWIFT MT940 File layout 37 4.5 Extended options 39 Examples: 41 5 SWIFT MT940 standard 42 5.1 General information. 42 5.2 Format structure 42 5.3 Content description 44
i) Format - 1 Khelo India sports Accreditation form 14 ii) Format - 2 About the Academy 15 iii) Format - 3 Facilities available in the Academy 17 iv) Format - 4 Sports science support 20 v) Format - 5 Residential facilities 21 vi) Format - 6 Educational facilities 22 vii) Format - 7 Coaching and Staff 23
Each SWIFT MT942-message starts with a fixed header-record (:942:) followed by record 20, 25, 28C, 34F (twice), 13D, 61 (0-n), 86 (0-6), 90D and 90C. The file begins with a fixed value of “942”. Each report in the file begins with field 20 and ends with the
1. Cutting audit format 2. Cutting pattern check format. 3. Sewing in-line inspection format 4. Sewing end-line inspection format 5. Sewing cause & effect analysis format. 6. Finishing initial inspection format Identification of various options at the check points to capture defects Selection of various tools to
SWF file format specification The SWF file format (pronounced "swiff") delivers vector graphics, text, video, and sound over the Internet and is supported by Adobe Flash Player software. The SWF file format is designed to be an efficient delivery format, not a format for exchanging graphics between graphics editors.
Creating a SWIFT Format A SWIFT message format can be created in the designer either from Existing SWIFT message format, or Empty message format When using an existing format, the same set of sequences and fields are available for the newly created format. Though the mandatory elements cannot be changed,
THE AMERICAN REVOLUTION AND CONFEDERATION, 1774-1787 87 . Thomas Paine, a recent English imntigrant to the colonies, argued strongly for what until then had been considered a radical idea. Entitled Common Sense, Paine's essay argued in clear and forceful language for the colonies becoming independent states and breaking all political ties with the British monarchy. Paine argued that it was .
