Top Banner
MultiCash PRO STA file format description ELECTRONIC BANKING
12
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Mt940 Format Details

MultiCash PRO STA file format description

ELECTRONIC BANKING

Page 2: Mt940 Format Details

SPIS TREŚCI

1. Format description of MultiCash STA file 3 1.1 General information about STA file 3

1.1.1 What is STA file? 3 1.1.2 What is the difference between statements

(MT940) and intraday information (MT942)? 3

1.1.3 How does the Structure of STA file look like? 3

1.1.4 How are transaction details presented (fields :61: i :86:)? 4

1.1.5 What types of codes are availiable in MultiCash? 5

1.2 Format description 5 1.2.1 Key to columns in the description of the

records 5 1.2.2 Description of MT 940 Statement block

format 6 1.2.2.1 Header 6 1.2.2.2 Transaction block 6 1.2.2.3 Transaction details structure

(field :86:) 7 1.2.2.4 Closing block 8

1.2.3 Description of MT 942 intraday information block 9

1.2.3.1 Header 9 1.2.3.2 Transaction block 9

1.2.4 Examples 10 1.2.4.1 Example of STA file 10 1.2.4.2 Transaction codes (SWIFT and

GVC) 11 2 Further information 12

- 2 -

Page 3: Mt940 Format Details

1. Format description of MultiCash STA file

1.1 GENERAL INFORMATION ABOUT STA FILE

This document explains format of STA files in MultiCash system and is intended as reference for creators of interfaces between ERP system and MultiCash. STA file, which is delivered by MultiCash BPHPBK contains MT940 statements and MT942 interim transaction reports.

1.1.1 WHAT IS STA FILE?

MultiCash system uses STA files as source of data in account history. STA files are downloaded from bank server and after communication are imported to MultiCash databases. Downloaded STA files are stored in …\MCCWIN directory. Because of exact specification of contents of these files, they can be imported to any ERP system, enabling automated entry of transactions.

STA is structured text file, containing statements blocks (based on SWIFT MT940) and intraday information blocks (based on MT942).

1.1.2 WHAT IS THE DIFFERENCE BETWEEN STATEMENTS (MT940) AND INTRADAY INFORMATION (MT942)?

Statements block (MT940), next to transaction information, contains opening balance, closing balance and statement number. Only MT940 data can should be used for ERP automated booking. MT942 blocks are for information purposes only and main task of these is fast informing of customer about movements on accounts. If there is movement on account MT942 block is appended immediately to STA file.

It is essential, that STA file parser distinguishes MT940 block from MT942 block, otherwise the same transaction will be booked twic . MT942 can be easily distinguished from statement by STARTDISP keyword in field :20:

1.1.3 HOW DOES THE STRUCT:20:statement date :25:account number :28C:statement number :60F:opening balance :61:transaction 1 :86:transaction 1 details :61:transaction 2 :86:transaction 2 details :61:transaction 3 :86:transaction 3 details

e

URE OF STA FILE LOOK LIKE?

Statement block (MT940).

Contains full transaction information for day 1along with opening balance, closing balance,statement number

- 3 -

Page 4: Mt940 Format Details

:62F:closing balance :64:available balance - :20:STARTDISP :25:account number :13:timestamp for message generation :61:transaction 4 :86:transaction 4 details - :20:STARTDISP :25:account number :13:timestamp for message generation :61:transaction 5 :86:transaction 5 details - :20:statement date :25:account number :28C:statement number :60F:opening balance :61:transaction 4 :86:transaction 4 details :61:transaction 5 :86:transaction 5 details :62F:closing balance :64: available balance

1.1.4 HOW ARE TRANSACTION DETAILS PRESENTED (FIELDS :61: I :86:)?

Transaction details are presented in lines :61: and :86: Line :61: contains value date , entry date, amount and currency of transaction, line :86: presents payment details, beneficiary details and transaction codes. :61:0203260326DN5312,00NTRF :86:020<00Wyplata-(dysp/przel)<10transaction number <20 1st Payment details line<21 2nd Payment details line <22 3rd Payment details line<23 4th Payment details line <24 5th Payment details line<25 6th Payment details line <26 7th Payment details line <27 Ord.Party/Beneficiary NAME1 <28 Ord.Party/Beneficiary NAME2 <29 Ord.Party/Beneficiary NAME3 (STREET) <30 Ord.Party/Beneficiary bank<31Ord.Party/Beneficiary Account number <32 Ord.Party/Beneficiary short1<33 Ord.Party/Beneficiary short2 <34 ind. code<38 Ord.Party/Beneficiar IBAN <60 Ord.Party/Beneficiary NAME4 (TOWN <61 Reconciliation code 1 (transactio<62 Reconciliation code 2 (beneficiar<63 REF5898327000090031789 <64 original amount, charges <66 booking code from host system Pro

Two transactions (4 and 5) were bookedduring the day 2. Information (MT942s)was generated as soon as possible andappended to STA file

Contains list of all transactions from day 2 along with opening balance, closing balance and statement number

Statement MT940 for day 2

Intraday block MT942.

y)

n id in ERP) y id in ERP)

file

- 4 -

Page 5: Mt940 Format Details

1.1.5 WHAT TYPES OF CODES ARE AVAILIABLE IN MULTICASH?

Transaction details contain 2 types of codes:

Transaction codes: depending on type of transaction, different codes according to SWIFT and GVC (Geschäftsvorfallcodes) standards are given to each transaction. For example standard domestic payment is given SWIFT code TRF and GVC code 020. Transaction codes give ERP system differentiation, whether booked amount is payment order or interest cost.

Reconciliation codes: each outgoing order can be marked with number or code, that

will be returned in exactly specified place on electronic statement. This enables automatic recognition whether order derives from ERP system and which customer (according to ERP database) it concerns. It is also possible to give unique number (string) to every outgoing order. When this number (string) shows on statement it means, that order was sussessfully processed and marked in ERP system as “done”.

1.2 FORMAT DESCRIPTION

Each STA file may contain one or more MT940 statements and intraday reports MT942. Number of statements in STA file depends on frequency with which STA file is downloaded from bank server;

Each statement (MT940) / intraday report (MT942) consist of header, transaction block and footer (closing block);

Code page for Polish characters is cp852; Before every line the characters <CR><LF> (ASCII 13 + 10) are used; Information blocks (statements, intraday information) are separated with dash „-” Total length of row in STA text file cannot be longer that 65 characters.

1.2.1 KEY TO COLUMNS IN THE DESCRIPTION OF THE RECORDS

Status M- Mandatory, O - Optional Format n Digits only a Alphabetic letters, upper case only c Alphabetic letters (upper case) and digits only x Any character d Amount with comma (,) as decimal separator

Example 2n - up to 2 digits 3!a - always 3 letters 4*35x - up to 4 lines of up to 35 characters each

- 5 -

Pawel Domanski
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 0 1 2 3 4 5 6 7 8 9 / - ? : ( ) . , ' + { } CR LF Space
Page 6: Mt940 Format Details

1.2.2 DESCRIPTION OF MT 940 STATEMENT BLOCK FORMAT

1.2.2.1 HEADER

Field number Status Format Description :20: Reference

M 6!n Reference number - statement date in format YYMMDD. :20:030226

:25: Account identification (IBAN)

M 2!a26!n Account identification IBAN (International Bank Account Number) whereIBAN = PLSSBBBBBBBBRRRRRRRRRRRRRRRR PL = Country code 2!a SS= Control digits 2!nBBBBBBBB = Bank Sorting Code [BSC] 8!nRRRRRRRRRRRR= Account number [AccNr] 16!n :25:PL79106000760000320000752973

:28C: Statement number

M 5!n/2!n Statement number/page Eg. :28C:00057/01

:60F: Opening balance

M 1!a Field specifies for the opening balance, whether it is a debit or credit balance, the date, the currency and the amount of the balance. F = Opening Balance

Debit/Credit indicator

M 1!a C = Credit D = Debit

Date M 6!n Date YYMMDD Currency M 3!a Currency code ISO Amount M 15d Amount Example for complete line :60F: :60F:C020326PLN134526,16

1.2.2.2 TRANSACTION BLOCK

Field number

Status Format Description

:61: Transaction line

M

Value date M 6!n Value date YYMMDD

Entry date M 4!n Entry date MMDD

Debit/credit indicator

M 2a C = Credit D = Debit RC = Reversal of credit (debit entry) RD = Reversal of debit (credit entry)

Funds code M 1!a Funds Code (3rd character of the currency code) Eg. N for PLN

Amount M 15d Amount

Transaction type

M N3!c Transaction code (type) according to SWIFT specification Eg. TRF

Account owner reference

M 16x Customer reference: For outgoing payments: PLI – first line of customer-bank information (first 16 char. from 35) PLA – field :20: (customer reference –16 znaków) INT- fiels :20: (customer reference – 16 znaków)

- 6 -

Page 7: Mt940 Format Details

For incoming orders: Reference: under condition they are received from ordering party bank If there are no references NONREF is used.

Bank reference

M (//)16x Bank reference Last 16 digits of transaction reference number in Profile (host system) Eg. 8327000090031789

Bank reference

M 34x Second line of bank reference (after <CR><LF>). Description of type of transaction Eg. Oplata za wydanie/wznowienie karty

:86: Transaction details

M See below

Transaction details. Special formatting applies (see below).

1.2.2.3 TRANSACTION DETAILS STRUCTURE (FIELD :86:)

General rules for field :86:

Subfield separator is < Empty subfields are not presented. For example, if 6th and 7th payment details line is

empty, subfields marks <25 and <26 do not exist; Subfields from <20 to <26 are reserved for payment details; Subfields from <27 to <60 are reserved for ord. Party/beneficiary details (name and

account); Subfields <61, <62 are reserved for reconciliation codes.

Subfield number

Status Format Description

Beginning of field

M 3!n Transaction code (type) according to GVC specification Eg. 020

<00 M 27a Booking text - text description of Transaction code from Profile that is also printed on paper statement Eg. Wypl/dys. przelew

<10 M 10n Batch number Sequential number of transaction on account Eg. 24755

<20 M 27x 1st Payment details line

<21 O 27x 2nd Payment details line

<22 O 27x 3rd Payment details line <23 O 27x 4th Payment details line <24 O 27x 5th Payment details line <25 O 27x 6th Payment details line <26 O 27x 7th Payment details line <27 M 35x Ord. Party/Beneficiary Name 1 (full 35 characters) <28 O 35x Ord. Party/Beneficiary Name 2 (full 35 characters) <29 O 35x Ord. Party/Beneficiary Name 3 (street) (full 35 characters) <30 M 10x Ord.Party/Beneficiary bank identification:

Bank Sorting Code (for domestic payments) or BIC (in case of SWIFT payments) In case of Polish domestic payments, when account is in form of NRB, characters 2 –10 are presented here

- 7 -

Page 8: Mt940 Format Details

<31 M 24x Ord.Party/Beneficiary account identification: In case of Polish domestic payments, when account is in form of NRB, characters 11 –26 are presented here

<32 M 27x Shortened Ord. Party/Beneficiary Name 1 (name is shortened to 27 characters.) NOTE: Filed is for MultiCash screen presentation purposes only and should not be used by ERP as source of Ord. Party/beneficiary data. For ERP subfields <27, <28, <29< <60 should be used.

<33 O 35x Shortened Ord. Party/Beneficiary Name 2 (for MultiCash screen presentation purposes only )

<34 O 3!x Individual transaction codes, according to agreement with customer. <38 O 34x Ord.Party/Beneficiary IBAN

For Polish domestic payments NRB number is placed here (NRB is IBAN without PL)

<60 O 35x Ord. Party/Beneficiary Name 3 (town) (full 35 characters) <61 O 35x Reconciliation code 1 (only for outgoing payments)

May be used as unique transaction id in ERP system. Second line of customer-bank information from PLI, PLA and INT files.

<62 O 35x Reconciliation code 2 (only for outgoing payments) May be used for customer id in ERP system. Third line of customer-bank information from PLI, PLA and INT files.

<63 M 35x Transaction reference number from Profile (bank host system) with keyword REF Eg. REF 5898327000090031789

<64 O 35x Original amount and charges (for SWIFT/non-domestic payments) With code words /OCMT/ oraz /CHGS/ Eg. <64/OCMT/USD10000,00//CHGS/EUR01,00/

<66 M 35x Booking code from host system Profile

1.2.2.4 CLOSING BLOCK

Field number Status Format Description :62F: Closing balance

M Closing balance

Debit/Credit indicator

M 1!a C = Credit D = Debit

Date M 4!n Date MMDD Currency M 3!a Currency ISO Amount M 15d Amount Example for complete line :62F: :62F:C020628PLN3481,35 :64: Available balance

M Available balance

Debit/Credit indicator

M 1!a C = Credit D = Debit

Date M 4!n Entry date MMDD Currency M 3!a Currency ISO Amount M 15d Amount Example for complete line :64: :64:C020628PLN3481,35 :86: Additional information from statement

O 6*65x MultiCash 3.0 can display 6 lines 65 characters each of additional information from statement if it is put here. Currently this filed is not used. Note: this line :86: appears after line :64:, concerning whole statement and should not be mistaken with line :86: after line :61: (particular

- 8 -

Page 9: Mt940 Format Details

transaction details) :OS: O No

restrictions

x

(Optional – very rarely!) It can happen that text file or other small file is appended to the STA file. When MultiCash processes STA file and finds :OS: record, displays text information in info-log manager or places the file (patch) to one of MCC directories. Such appended file always begins with :OS: and name of the file. This part of STA should not be processed by ERP system. Eg. :OS:0400003163DMIMCPRO.txt Dear Customers, we would like to inform...

1.2.3 DESCRIPTION OF MT 942 INTRADAY INFORMATION BLOCK

1.2.3.1 HEADER

Field number Status Format Description :20: Reference - MT942 indicator

M 9!a Reference: MT942 indicator: Always STARTDISP :20:STARTDISP

:25: Account identification (IBAN)

M 2!a26!n Account identification IBAN (International Bank Account Number) whereIBAN = PLSSBBBBBBBBRRRRRRRRRRRRRRRR PL = Country code 2!a SS= Control digits 2!nBBBBBBBB = Bank Sorting Code [BSC] 8!nRRRRRRRRRRRR= Account number [AccNr] 16!n :25:PL79106000760000320000752973

:13: Timestamp for message generation

M 10!n Timestamp for message generation in format RRMMDDGGMM. E.g. :13:0308272359

1.2.3.2 TRANSACTION BLOCK

:61: Transaction line

M patrz opis

:61: Transaction line. Identical like described above in MT940

:86: Szczegóły operacji

M patrz opis

Transaction details line. Identical to those described above in MT940

MT942 does not have closing block.

- 9 -

Page 10: Mt940 Format Details

1.2.4 EXAMPLES

1.2.4.1 EXAMPLE OF STA FILE :20:030825 :25:PL72106000760000320000546101 :28C:00237 :60F:C030825PLN0,00 :61:0308250825CN142680,00NTRFNONREF//8327000090031789 Przelew przychodzący wewnętrzny :86:051<00Wpłata na rach.<101000000001 <20F-RA 4762/2003 ZAPŁATA ZA<21DOSTAWĘ KINESKOPÓW <22LIPIEC 2003<2622106000760000320000584734 <27BLACKTRONIX FABRYKA TELEWIZORÓW <29GŁOGOWSKA 248 <3010600076<310000320000584734 <32BLACKTRONIX FABRYKA TELEWIZ<33ORÓW <34051<3822106000760000320000584734 <6060-010 POZNAŃ <63REF5983270000900317897 <66DD :61:0308250825CN20000,00NTRFSENDERS REF//8327000090031790 Przelew przychodzący wewnętrzny :86:051<00Wpłata na rach.<101000000002 <20FAKTURA 7/2003<21DOSTAWA KINESKOPÓW <22BLACK 17' 25 SZT.<23BLACK 21' 30 SZT <2667106000760000300000374405 <27MATRIX WYTWÓRNIA SPRZĘTU TV I AGD <29PUŁAWSKA 65 <3010600076<310000300000374405 <32MATRIX WYTWÓRNIA SPRZĘTU TV<33 I AGD <34051<3867106000760000300000374405 <6000-950 WARSZAWA <63REF598327000090031790 <66DD :61:0308250825DN8566,27NTRFREFERENCJE//8327000090031791 Przelew wychodzący zewnętrzny :86:020<00Wyplata-(dysp/przel)<101000000003 <20FRA 7611/2003 TERMIN 030826<21ZA REMONT ZAKŁADOWYCH <22POMIESZCZEŃ MAGAZYNOWYCH<2602105014451000002252037854 <27USŁUGI REMONTOWE SP. Z O.O. <28JAN KOWALSKI <29STRĄKOWA 3A <3010501445<311000002252037854 <32USŁUGI REMONTOWE SP. Z O.O.<33 <34020<3802105014451000002252037854 <6031-345 KRAKÓW <61TRANS65348259 <62USLREMONT <63REF598327000090031791 <66DWP :61:0308250825DN19587,57NTRFREFERENCJE //8327000090031792 Przelew wychodzący wewnętrzny :86:020<00Wyplata-(dysp/przel)<101000000004 <20FRA 324-2342-234/2003<21ZA PREFABRYKATY DO TUB <22PRÓŻNIOWYCH <2661106000760000320000119499 <27HUTA SZKŁA TOPIK <29PRZEMYSŁOWA 67 <30110600076<310000320000119499 <32HUTA SZKŁA TOPIK<33 <34020<3861106000760000320000119499 <6050-505 WROCŁAW <61TRANS65348260 <62HUTASZKLA

- 10 -

Page 11: Mt940 Format Details

<63REF598327000090031792 <66DWP :62F:C030825PLN134526,16 :64:C030825PLN134526,16 -

1.2.4.2 TRANSACTION CODES (SWIFT AND GVC)

Transaction codes list is in separate document.

- 11 -

Page 12: Mt940 Format Details

2. Further information

If you have any questions about formats of MultiCash payment files please contact Hotline MultiCash: Hotline MultiCash Banku BPH Tel. 0801 362274 (0801 3mcash) Tel. +48 12 6186688 Fax: +48 12 6186686 e-mail: [email protected] Internet:www.bph.pl/multicash

- 12 -