mbank CompanyNet, BRESOK

Transcription

1 mbank CompanyNet, BRESOK Structure of import export data files in elixir format Electronic banking for corporate clients and SMEs Version 1.05, 20 November 2017 mbank S.A., ul. Senatorska 18, Warszawa, entered in the commercial register of the National Court Register kept by the District Court for the Capital City of Warsaw, 12th Commercial Division, under KRS , Tax Identification Number (NIP): , with its fully paid-up share capital amounting to PLN as at 1 January 2017.

2 Table of contents: 1. General Requirements for and format of the columns in the file structure description File structure Structure of the field "Payment details" for Tax Payments Structure of the field "Payment details" for direct debit List of characters allowed in foreign transactions and EuroEkspres List of validation error codes for collective direct debits List of transaction codes, transaction classification Structure of the field "Beneficiary's identification code

3 Structure of files used in the import - export of transactions, auxiliary databases and export of the validation report for collective direct debit validation (EILIXIR-O compliant comma and inverted comma format) 1. General The file contains no header. In the case of the mbank CompanyNet, one file can contain multiple payment transactions of various types. For the BRESOK system, one file should contain multiple payment transactions of one type. Each transaction begins with a symbol of the transaction type (e.g. 110 = money transfer, 210 = direct debit). The instructions are separated by the end-of-line symbol <CR><LF> (Hex0D 0A). Text fields are always inserted in inverted commas (" "). Individual fields in the instruction and separated by a comma (,). If a field contains more than one line, the lines are separated by the character " " (Hex 7C). The character is treated as the control character and is not transferred to the transaction format fields and counterparties databases. For all types of transactions except for postal order the fields must not include the following characters: : * ;! +? #. In the case of the postal order the fields must not contain the character: ;. In addition, the field of details of direct debit must not contain the character /. The field counterparty's account number for domestic orders and direct debit must not contain the characters: / and,. The field counterparty's account number must not begin with the character for all types of transactions. Allowed Polish characters encoding: ISO , Windows-1250, CP852 IBMLatin2. 2. Requirements for and format of the columns in the file structure description E / W = Occurrence of fields: W = Required has to be filled with content. E = Possible may occur as 0 (zero number) or empty inverted commas without content. Subfields may be possibly skipped. FORMAT = Length and field type: n = numerical 0 9 leading zeros are acceptable, although they are not obligatory, a = alphanumerical, written in inverted commas " " (Hex 22). Individual lines are separated by the character " " (Hex 7C), d = date field, format: YYYYMMDD F = fixed, V = variable. 3

4 3. File structure No. Description of the field Format 1. Transaction type (transfer or base code). 3 n F Allowed field values for transfers: Field code value Transfer type Domestic money transfer, including Express Elixir and BlueCash instant transfer (available only in mbank CompanyNet) and collective direct debit Taxes Direct debit Domestic FX transfer FX internal order executed instantly FX order, foreign order Postal order EuroEkspres transfer Allowed filed values for other bases: Field code value Database type Database of domestic beneficiaries Database of FX beneficiaries Database of postal order beneficiaries Database of SEPA beneficiaries Database of EuroEkspres beneficiaries Debtors 2. Payment date 8 d F 310, 320, 410, 510, 710 Transaction date in the YYYYMMDD format. 4

5 3. Amount to be paid 15 n V base code 310, 320, 410, 510, 710 Amount to be paid, without separators, multiplied by 100 (the value 100 = 1.00). 4. Settlement number of the ordering party bank 8 n F base code 310, 320, 410, 510, digit settlement number of the ordering party bank (numbers from 3 to 10 from account number in NRB format). 5. Payment execution procedure 8 n V 0 ordinary transfer Express Elixir instant transfer 2 BlueCash instant transfer 5 Sorbnet transfer 190, 210, 320, 710, 011, 014, 015, 016, 017, Standard 410, Urgent 2 Express or 510 against confirmation of receipt 511 Poste restante 6. Account number of ordering party 34 a V 310, 320, 410, 510, 710 Account number of the ordering party in the NRB format (written without spaces). Shortened name, max. 20 characters. 5

6 7. Counterparty's account number 34 a V , , 014, , 017 Counterparty's account number in the NRB format (written without spaces). For orders outside of the mbank: Account number in the IBAN format (written without spaces). For orders within the mbank: account number in the NRB format (written without spaces). Counterparty's account number or an empty field in the case of payment by check (CHQB). Counterparty's account number in the IBAN format, Counterparty's account number in the NRB format (written without spaces). Counterparty's account number in the IBAN format (written without spaces). 8. Name and address of the ordering party 3*35 av 110, 210, 310, 320, 410, 510, Individual lines are separated by the symbol " ". Name and address of the ordering party. Individual lines are separated by the symbol " ". Name of the payer or person making the payment. 9. Name and address of the counterparty 4*35 av 110, 310, 320, 410, 011, Individual lines are separated by the symbol " ". In the first two lines the Beneficiary's Name, in the remaining lines Beneficiary's Address. The first line must be completed. Individual lines are separated by the symbol " ". In the first two lines the name of the Tax Office, in the third line the city of the Tax Office. If tax is to be paid to a tax authority other than the Tax Office, three lines should be used to provide the name and address of the authority. The first and third line are required. The fourth line should remain empty. The data contained therein will not be in the transaction. For: 016 2*35 av + 2*70 av For: 710 and 017 2*35 av + 2*35 av 6

7 210, , , 016, 017 Individual lines are separated by the symbol " ". In the first line the Debtor's Name. In the second and the third the Debtor's Address. In the fourth line one character of the status: F natural person, P legal person. Individual lines are separated by the symbol " ". In the first line the Beneficiary's Name, in the second line the address, in the third line: NNNNN:PPPPPP where: NNNNN post code (five characters disallowed code number: 00000), PPPPP post office name (26 characters as the first character may only be a letter; other characters may include: letters, digits, full stops, commas, hyphens, slashes). In the fourth line: DDDDDDD (7 characters) :MMMMMMM (7 characters), where: DDDDDDD building number, MMMMMM flat number. Individual lines are separated by the symbol " ". In the first two lines the Beneficiary's Name, in the remaining lines the Beneficiary's Address. 10. Fees and commissions 8 n V 320, , costs of the foreign banks are covered by the ordering party, 2 costs of the foreign bank are covered by the beneficiary, 3 costs of mbank are covered by the ordering party, 4 costs of mbank are covered by the beneficiary, Exemplary value: 23. The value 14 is not allowed. For transfer type 310 in BRESOK system allowed only or Settlement number of the counterparty's bank 8 digits 8 n V 310, 320, 011, , 510, 710, 014, 015, 016, 017 Settlement number of the counterparty's bank (numbers from 3 to 10 from account number in NRB format). 7

8 12. Payment details 4*35 an 110, 310, 320, 410, 510 (sent by CompanyNet), (sent by BRESOK) Individual lines are separated by the symbol " ". Payment title, 4*35 characters. Detailed description of the structure in point 4. Detailed description of the structure in point 5. 1*35 characters. 13. Empty field 0 a F 310, 320, 410, 510, 710, 011, 014, 015, 016, 017, Empty field 310, 320, 410, 510, 710, 011, 014, 015, 017, Identification code of the beneficiary (description of fields in point 9). 0 a F For: 016 1*520 a V If the empty field is left, the identification code of the beneficiary will not be supplemented. 15. Instruction classification 2 a F , 320, 410, 510, 710 Fixed value "51". Fixed value "71" or "74". Fixed value "01". Detailed description of allowed values of the field in point 6. 8

9 16. Information Client -Bank 6*35 an Individual lines are separated from one another by the character " " , The first line of the field may include the transaction reference symbol in the following format (max. 16 characters + 3 REF characters): REF:xxxxxxxx. The first line of the field may include the transaction reference symbol in the following format (max. 16 characters + 3 REF characters): REF:xxxxxxxx. In the second line the transaction currency: WAL:USD; The first line of the field may include the transaction reference symbol in the following format (max. 16 characters + 3 REF characters): REF:xxxxxxxx. In the second line: the transaction currency, name of the beneficiary's bank country in the form: WAL:EUR; country name (max. 14 characters). Then, two special characters /S and the abbreviation of the SWIFT of a foreign bank (8 or 11 characters). The field transaction currency is obligatory. Other fields from the list above are optional e.g.: /Poland/SBX5TPLTTY or Poland. 710 Optionally, if there is no abbreviation of SWIFT, in the fourth line the name of the beneficiary's bank (maximum 22 characters), in the fifth and sixth line the address of the beneficiary's bank (maximum 2*35 characters). The first line of the field may contain a transaction reference symbol in the following format (max. 16 characters + 3 characters for REF): REF:xxxxxxxx. In the second line the transaction currency, information on exchange rate, name of the beneficiary's bank country in the form: WAL:EUR; Country name (max. 14 characters). In the third line: first 2-character beneficiary s country code as per ISO , then, two special characters /S and abbreviation of SWIFT of the foreign bank (8 or 11 characters) e.g.: PL/SBX5TPLTTY. 011, 015, The first line is empty. In the second line the name of the beneficiary's bank country (maximum 14 characters). In the third line two special characters /S and the abbreviation of the SWIFT of a foreign bank (8 or 11 characters). All the above fields are optional e.g.: 9

10 Poland /SBX5TPLTTY or Poland. 016 Optionally, if there is no abbreviation of SWIFT in the fourth line in the fourth line the name of the beneficiary's bank (maximum 22 characters), in the fifth and sixth line the address of the beneficiary's bank (maximum 2*35 characters). The first two lines are empty. In the third line 2-character beneficiary s country code as per ISO (mandatory field if the field counterparty address was filled in). Then, two special characters /S and abbreviation of SWIFT of the foreign bank (8 or 11 characters) e.g.: PL/SBX5TPLTTY. 017 The first two lines are empty. In the third line 2-character beneficiary s country code as per ISO Then, two special characters /S and abbreviation of SWIFT of the foreign bank (8 or 11 characters) e.g.: PL/SBX5TPLTTY. 17. Validation error code for collective direct debit 140 an Notice! The field appears only in the validation report for transactions sent as collective direct debit (collective direct debit), Mass Payment (Mass transfer) and Mass Payment Plus (Plus Mass Transfer). For collective direct debit the field can contain one of the error codes described in point 7. For mass transfers the field can contain a detailed description of a reason for transfer rejection. 18. End of instruction <CR><LF> 4. Structure of the field "Payment details" for Tax Payments In addition, the field of details of Tax Payment cannot contain the characters \ and _. Some fields are preceded by code words containing several characters and put between two slashes ( / ) (the character / may only be used in code words). The length of the first line depends on the selected parameters (Identifier type, Period, Form symbol). Code words may not be divided into several lines, the second line always begins before the code word /TXT/. Field E / W Format Subfield content Line number Identifier type W 1 a F /TI/ identifier type 1 can have one of the following values: N NIP [tax identification number], P PESEL [population register number], 10

11 R REGON [enterprise statistical number], 1 ID card, 2 passport number, 3 another identity document. id content W 14 a V Identifier content. 1 Period W 7 a V /OKR/ period for which payment is made. 1 Form symbol W 7 a V /SFP/ form symbol or payment title. 1 Free text E 40 a V /TXT/ free text. 2 Number of the line indicates in which logical line of payment details a given subfield should be inserted The Period field has the following structure: Period the first part of the field contains the two characters for the year. The second part contains one of the following characters from the list (Period type): M month, P semi-annual, R year, K quarter, D decade, J - day. The third part contains the period number: a. When Period Type is R, the field contains no period number, b. When Period Type is P, it requires two-character space to be filled in with the value 01 or 02, c. When Period Type is K, it requires the two-character space to be filled in with the value 01, 02, 03 or 04, d. When Period Type is M it is requires the two-character space to be filled in with the value from 01-12, e. When Period Type is D it requires two-character space to be filled in with the value 01, 02 or 03, and then two-character space with the value from range, f. When Period Type is J, it requires the two-character space to be filled in with the value from range, corresponding to a given day, and then two-character space with the value from range, corresponding to a given month. 5. Structure of the field "Payment details" for direct debit Key word E / W Format Subfield content /NIP/ W 10 n F Ordering party's (creditor's) NIP (tax identification number). /IDP/ W 20 a V Payment identifier To be filled in also in the Debtor's database. /TYT/ E To the end of the field "Payment details" Free text. It may be used instead of the two-digit /TYT/ field. Max. 2*35 characters. Fields /OD/ and /DO/ are only used in conjunction with the two-digit /TYT/ field. There may be only one field /TYT/ - a two-digit field or a free text field. No separators (including spaces) may be used between the subfield key word and the subfield content or between the subfield content and the key word of the following subfield. 6. List of characters allowed in foreign transactions and EuroEkspres List of allowed characters to be used in the fields of foreign transactions and EuroEkspres transfers a b c d e f g h i j k l m n o p q r s t u v w x y z A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

12 / - ( )., + Space 7. List of validation error codes for collective direct debits Error code Error description Creditor's account incorrect (1). Debtor's bank does not process in direct debits (2). Payment amount limit exceeded (3) does not apply since 24 December Creditor s NIP (tax identification number) incorrect (4). Account does not have direct debit activated (6). Debtor does not have direct debit activated (7). Debtor's bank number incorrect (9). Wrong file structure (20). Wrong transaction type (21). Wrong payment date (22). Wrong transaction amount (23). Creditor's bank number incorrect (24). Wrong number of debtor's account (25). Wrong name and address of the creditor (26) does not apply since 24 December Wrong name and address of the debtor (27) does not apply since 24 December Wrong debtor type (legal/natural person within the meaning of the Civil Code) (28). Wrong transaction code (29). Wrong Creditor- Bank information field (30). Transaction description too long (31). Wrong IDP (32). Incorrect data following /TYT/ code word (33). Disallowed special characters (34). Transaction account number incompliant with the account given in the batch (35). Payment details field incorrect (36). 8. List of transaction codes, transaction classification 12

13 in file used to import transactions Code Description in Polish Description in English Transfer code 51 N/A N/A N/A 110, 310, 320, 410, 510, or N/A N/A N/A 210 N/A N/A N/A 190 INTC Płatność wew. Grupy Kapitałowej Intra-company Payment 310, 410, 710 CHQB Płatność czekiem Pay by cheque 310, Structure of the field "Beneficiary's identification code Key word E / W Group Format Subfield content \TYP\ W A 1 a F The first line. Type of the ordering party: P legal person, F natural person, The field is mandatory if any of the following groups is filled in. For legal persons, i.e. where \TYP\ has value P, one of the following groups can be filled in (fields in the natural person section are not provided). In particular none of the groups may be filled in. The completed fields are to follow one another without any separation tags. \BIC\ E B 11 a V BICORBEI. \BEI\ E C 11 a V BICORBEI. \BICORBEI\ E D 11 a V BICORBEI. \DUNS\ \BKPTYID\ \TAXIDNB\ \CUST\ \EMPL\ \GS1G\ \IDTP\ E E 35 n V DUNS. Bank's Party Identifier Tax Identification Number. Customer number Employer's Identification Number. GS1G. Proper name of identifier. Subfield group: Other identifier one value of the code words field is permitted interchangeably. Subfield allowed only when \ID\ filed is used. \ID\ E 35 a V Field group: Another identifier. 13

14 Party identifier \ISSR\ E 35 a V Field group: Identifier Issuer For natural persons i.e. where \TYP\ has value F one of the following groups from B to K and/or group L can be filled in (fields in the legal person section are not provided). In particular, none of the groups may be filled in. The completed fields are to follow one another without any separation tags. \BRITHDT\ E F 8 d F Field group: Date and place of birth. \PRVCOFBRITH\ \CITYOFBIRTH\ \CTRYOFBIRTH\ \ID\ Subfield: Date of birth YYYYMMDD format - subfield allowed only when \PRVCOFBRITH\, \CITYOFBIRTH\, \CTRYOFBIRTH\ fields are used. E 35 a V Field group: Date and place of birth. Subfield: Province subfield allowed only when \BRITHDT\, \CITYOFBIRTH\, \CTRYOFBIRTH\ fields are used. E 35 a V Field group: Date and place of birth. Subfield: City of birth subfield allowed only when \BRITHDT\, \PRVCOFBRITH\, \CTRYOFBIRTH\ fields are used. E 2 a F Fields group: Date and place of birth. Subfield: Country of birth subfield allowed only when \BRITHDT\, \PRVCOFBRITH\, \CITYOFBIRTH\ fields are used. Country code as per ISO3166, Alpha-2 code. E G 35 a V Field group: Another identifier. Additional identifier. \DRVRSLICNB\ \CSTMRNB\ \SCLSCTYNB\ \ALNREGNNB\ \PSPTNB\ \TAXIDNB\ \IDNTYCARDNB\ \MPLYRIDNB\ \IDTP\ E 35 a V Driving license number. Customer number. Social Security number. Foreigner identification number. Passport number. Tax Identification Number. Identity card number. Employer's Identification Number. Proper name of identifier. Field group: Additional identifier one value of the code words field is permitted interchangeably. Subfield allowed only when \ID\ field is used. 14

15 \ISSR\ E 35 a V Issuer mbank S.A. reserves the right to introduce amendments or changes to data structure, specified herein, at any time without notice. 15