Structure of output messages for MultiCash v.

Structure and Contents of Outgoing Messages for MultiCash

SOB
Version 8

Page 1 /

Structure of output messages for MultiCash v. 8

CONTENTS
1 MESSAGES OF MT940 TYPE ...................................................................................................... 3 1.1 ACCOUNT STATEMENT STRUCTURE .......................................................................................... 3 1.2 USE OF SUBFIELDS OF FIELD 86 FOR ACCOUNT STATEMENTS .................................................... 6 1.2.1 Domestic Payments (TPS) ................................................................................................ 6 1.2.2 Foreign Payments (ZPS) ................................................................................................... 6 1.2.3 Other Transactions ............................................................................................................ 7

Page 2 /

Structure of output messages for MultiCash v. 8

1 Messages of MT940 Type

A format of the file for Account Statements is based on the format of SWIFT MT940 message. The file has no heading and contains one or more statements. Any logical Account Statement may have one or more pages (sheets). Every page of the Account Statement consists of a Heading, a Text Block, and trailer characters. Before the Heading, characters X01 should be entered. The trailer characters include }, X03 and <CR><LF> (X7D030D0A). Heading and Text block items are assigned flags. The sequence of Headings and flags described in the tables below is binding. The tables below describe structures of the Heading and the Text Block of each Statement. They also include descriptions of subfields and their characteristics.
The Statement file may also contain a free text, which will not be described here. Such free text is designated for the MultiCash application, and it is not important for loading into the accounting system. Structure of the Statement Heading is the following: {1:F01xxxxxxxxxxxxbbbbtttttt}{2:I940ccccccccccccpmyyy}{4: Where 1:F01 xxxxxxxxxxxx bbbb tttttt 2:I940 cccccccccccc p m yyy 4: Fix basic block of the Heading Payer's bank identification number Status (session number) (program generated; 0 - 9999) Transaction number (numbering is a data record inside the file; 0 - 999999) Fix application block of the Heading Beneficiary's number Priority (character being used is N for a standard transmission) Monitoring of delivery (not used enter a space) Ageing period (used 020) Fix Text Block

Conversion: 1st part of the Heading {1:F01xxxxxxxxxxxbbbbtttttt}{ 2nd part of the Heading 2:I940ccccccccccccpmyyy}{4:

into the format {1:F01xxxxxxxxxxx0000000000}{ into the format 2:I940ccccccccccccN 020}{4:

Account Statement inside the file has the following structure of the Text Block: M/O D/F = = field relevancy M = mandatory field O = optional field field length and format n = numeric (0-9) a = alphabetic P = fixed length V = variable length

Page 3 /

Structure of output messages for MultiCash v. 8

Description <CR><LF>:20: Reference Internal structure used: date in ddmmmrr format, and frequency (DAILY,. <CR><LF>:21: Other reference Not used. <CR><LF>:25: Account description bank number / account number Always BBBB/PPPPPPUUUUUUUUUU where BBBB is the bank code leading zeroes PPPPPP pre-number without leading zeroes UUUUUUUUUU account number leading zeroes, if there is any pre-number Examples 0300/190012345671 0300/123 0300/80109999999999 <CR><LF>:28: Statement number Statement number / page number (statement number leading zeroes; page number without leading zeroes) <CR><LF>:60x: where x = balance type x = F for opening balance, x = M for subtotals (if the statement has more pages) Subfield 1 : Balance sign, C = Credit, D = Debit Subfield 2 : Balance date in RRMMDD format Subfield 3 : ISO code of balance currency Subfield 4 : Balance amount <CR><LF>:61: Transaction line Subfield 1 : Booking date in RRMMDD format Subfield 2 : Date of the entry into the system in MMDD format Subfield 3 : Booking type C=Credit, D=Debit, RC=Reverse Credit, RD=Reverse Debit Subfield 4 : Currency type Subfield 5 : Transaction amount (no leading zeroes, with decimal point) Subfield 6 : Text key FMSC for clearing transactions, NMSC for other transact. Subfield 7 : Client reference If none, then give NONREF or a space

M/O M M

D/F 4aP 16 a V

O O M M

4aP 16 a V 4aP 35 a V

M M

4aP 5nP / 2nV 5aP

M M M M O M O M

1aP 6nP 3aP 15 n V 4aP 6nP 4nP 2aV

O M M

1aV 15 n V 4aP

16 a V

Page 4 /

Structure of output messages for MultiCash v. 8

Subfield 8 : //Bank reference (transaction number) <CRLF>Subfield 9 : /Additional information for transactions from another financial institution within domestic payment system; position 29-34 Date of deduction from the counteraccount in RRMMDD format or /OCMT/XXXNNNNNNNN,NN Where /OCMT/ key word, XXX ISO code of payment currency NNNNNNNN,NN original amount with 2 decimal places <CR><LF>:86: Field of additional information The field may contain up to 6 subfields separated by CRLF Description of the field content is in a separate table. <CR><LF>:62x: Where x = balance type x = F for closing (final, carried fwd.) balance, x = M for subtotal (if the Statement has more pages) Subfield 1 : Balance sign C = Credit, D = Debit Conversion: for closing (carried fwd.) balance balance_end For subtotal according to the balance sign Subfield 2 : Balance date in RRMMDD format Subfield 3 : ISO code of the balance currency Subfield 4 : Balance amount <CR><LF>:64: Current balance according to the Value Date Subfield 1 : Balance sign C = Credit, D = Debit Subfield 2 : Balance date in RRMMDD format Subfield 3 : ISO code of the balance currency Subfield 4 : Current balance amount <CR><LF>:65: Future balance according to the Value Date Subfield 1 : Balance sign C = Credit, D = Debit Subfield 2 : Balance date in RRMMDD format Subfield 3 : ISO code of balance currency Subfield 4 : Future balance amount <CR><LF>End of MT940 Statement

O O

16 a V 34 a V

6 x 65 a V

5aP

1aP

M M M O M M M M O M M M M M

6nP 3aP 15 n V 4aP 1aP 6nP 3aP 15 n V 4aP 1aP 6nP 3aP 15 n V 1aP

Notes: Amounts are entered with two decimal places with a decimal point without leading zeroes. For round amounts, the decimal part after the decimal point (all zeroes) is unnecessary.

Page 5 /

Structure of output messages for MultiCash v. 8

Any SWIFT message may contain 2000 characters as a maximum. In the case of a higher number of transactions (:61:,:86:), more Statement pages should be used, i.e., one separate Statement for each

page (the first page :60F:, :62M:; the second page :60M:, :62F: or :62M:; etc.). In SOB, fields 64 and 65 are not used.

1.2

Use of Subfields of Field 86 for Account Statements

A question mark ? is used as a separator. Using of subfields differs for domestic (clearing) payment transactions (in Czech TPS), foreign payment transactions (in Czech ZPS), and other transactions (cash withdrawals, fees, interest, card operations, and the like).

1.2.1

Domestic Payments (TPS)

Subfield Description 111 Code of the business event ?00 Text for the counteraccount ?20 Counteraccount no. (prenumber-acc./bank) <crlf >?21 Variable Symbol ?22 Specific Symbol ?23 Constant Symbol <crlf > ?24 Message to beneficiary, part 1 ?25 Message to beneficiary, part 2 <crlf >?26 Message to beneficiary, part 3 ?27 Message to beneficiary, part 4 <crlf >?28 Variable Symbol of the counterparty ?29 Specific Symbol of the counterparty

1.2.2

Foreign Payments (ZPS)

Subfield Description 030 Code of business event ?00 Rate:xxxxxx,yyyyyy *) ?20 Name of the counterparty ?21 FOREIGN PAYMENT <crlf > ?22 Payment purpose ?23 Payment purpose <crlf > ?24 Payment purpose ?25 Payment purpose <crlf > ?26 Payment purpose ?27 FOREIGN FEE:XXXNNNNNNNNNN.NN where XXX is currency code, NNN fee amount ?30 Payer's/Beneficiary's Bank ID <crlf > ?31 Payer's/Beneficiary's account number ?32 Name of the counterparty <crlf > ?33 Name of the counterparty //CHGS/ Fee amount (XXXnnnnnnnn,nn), where XXX is ISO code of the fee currency and Nnnnnnnn,nn is the fee amount.

*) Without leading zeroes; fixed number of decimal places. If the fee information (e.g., Resend) is unknown upon the Statement generation, it will not be given.

Page 6 /

Structure of output messages for MultiCash v. 8

1.2.3

Other Transactions
Format 27aV VS:10nP (leading 0) 27aV 27aV 27aV 27aV SS:10nP (leading 0) KS:4nP (leading 0)

Subfield Description 040 Code of the business event ?00 Operation text or counteraccount name ?20 Variable Symbol ?21 Message to Beneficiary, part 1 <crlf >?22 Message to Beneficiary, part 2 ?23 Message to Beneficiary, part 3 <crlf >?24 Message to Beneficiary, part 4 ?25 Specific Symbol ?26 Constant Symbol

If the field in the banking system is blank, the subfield should be filled in with a dot .

Page 7 /