Scribd Logo
Upload

Welcome to Scribd!

  • 573 views

    14 Multicash Format

    Uploaded by

    Pavan Kumar
    This document provides a technical description of the file format structure for importing domestic payment orders in Czech currency (CZK) into an internet banking system. It outlines the basic rules of the file format, including that each file can contain a maximum of 100 payment orders separated by carriage return line feed sequences. It then describes each field and subfield in the file structure, providing the name, whether it is mandatory or optional, and the length and format of the data. An example payment order is provided to illustrate the file structure.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    14 Multicash Format

    Uploaded by

    Pavan Kumar
    573 views4 pages
    This document provides a technical description of the file format structure for importing domestic payment orders in Czech currency (CZK) into an internet banking system. It outlines the basic rules of the file format, including that each file can contain a maximum of 100 payment orders separated by carriage return line feed sequences. It then describes each field and subfield in the file structure, providing the name, whether it is mandatory or optional, and the length and format of the data. An example payment order is provided to illustrate the file structure.

    Original Description:

    14 multicash format

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document provides a technical description of the file format structure for importing domestic payment orders in Czech currency (CZK) into an internet banking system. It outlines the basic rules of the file format, including that each file can contain a maximum of 100 payment orders separated by carriage return line feed sequences. It then describes each field and subfield in the file structure, providing the name, whether it is mandatory or optional, and the length and format of the data. An example payment order is provided to illustrate the file structure.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    573 views4 pages

    14 Multicash Format

    Uploaded by

    Pavan Kumar
    This document provides a technical description of the file format structure for importing domestic payment orders in Czech currency (CZK) into an internet banking system. It outlines the basic rules of the file format, including that each file can contain a maximum of 100 payment orders separated by carriage return line feed sequences. It then describes each field and subfield in the file structure, providing the name, whether it is mandatory or optional, and the length and format of the data. An example payment order is provided to illustrate the file structure.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 4

    Stránka 1 z 4

    MULTICASH format

    Technical description of file format structure for import of domestic payment orders in CZK to internet
    banking. The extension of the file is always *.CFD

    Basic rules:
     payment file begins without header
     every file can contains maximum number of 100 payment orders
     Every payment order begins with the field code "HD:"
     Code page of payment file is CP 852 (Latin2)
     File must contain only upper case characters
     File must not contain empty row (Empty row is several spaces too).
     <CR> <LF> sequence separates payment orders within a payment file from each other.
     File format is divided to field and subfields
     some of the subfields are optional
     Empty subfields inside a field can be represented by a space. Exceptions of this rule are the fields
    "DI:", "KI:" and "AV:". <CR> <LF> separates optional subfields of these fields
     Subfields are separated from each other by space character (ASCII 32)

    If a payment order is Credit transfer, fields "UD:" contains information about Ordering party account and "DI:"
    contains information about Ordering party Name. Filed "UK:" contains information about Partner account and
    filed "KI: " contains information about Partner Name.

    Note:
    Partner = Beneficiary

    Additional information for fields ZK, AK, EC.


    Leading zeros are not removed from these fields, i.e. what is entered to the application will also be contained
    in output file.

    Example:
    Client enters or imports ZK:00123
    On the screen and in an output file will be ZK:00123

    If client doesn’t enter or import any value into this field, ZK will be filled with one zero.
    Example: Client enters or imports no number. In format will be ZK:0

    Column description:

    Field = serial number of data field


    M/O = completion of the field
    M = mandatory
    O = optional

    L/F = length and format of the data field


    N = numeric 0 – 9, leading zeros are allowed but not compulsory
    A = alphanumeric
    F = fixed field length
    V = variable length
    Stránka 2 z 4

    Structure of the file

    Content M/O L/F


    HD: M 3AF
    Subfield 1 :
    Payment type: M 2NF
    11 : Money transfer (*.cfd)
    Subfield 2 :
    Date of order M 6NF
    Format : YYMMDD
    Subfield 3 :
    M 7AV
    Bank code of payer
    Subfield 4 :
    Serial number (1 - 999999) M 6NV
    (generated by the program)
    Subfield 5 :
    M 7AV
    Bank code of beneficiary
    <CR><LF>KC: M 3AF
    Subfield 1 :
    M 15 N V
    Amount (with 2 decimals – decimals are not separated)
    Subfield 2 :
    M 6NF
    Null field (000000)
    Subfield 3 :
    M 3AF
    Currency code (ISO) – always filled „CZK“
    <CR><LF>UD: M 3AF
    Subfield 1 :
    Prefix of payer account
    M 6NV
    Checked by modulo-11. If the prefix is missing, field will contain one space
    without subfields separator.
    Subfield 2 :
    Account number of payer M 10 N V
    Checked by modulo-11
    Subfield 3 :
    O 20 A V
    Short description of payer account
    <CR><LF>DI: M 3AF
    Subfield 1 :
    M 35 A V
    Payer description 1
    <CR><LF> Subfield 2 : (row must start with 3 spaces)
    O 35 A V
    Payer description 2
    <CR><LF> Subfield 3 : (row must start with 3 spaces)
    O 35 A V
    Payer description 3
    <CR><LF> Subfield 4 : (row must start with 3 spaces)
    O 35 A V
    Payer description 4
    <CR><LF>UK: M 3AF
    Stránka 3 z 4

    Subfield 1 :
    Prefix of beneficiary account
    M 6NV
    Checked by modulo-11. If the prefix is missing, field will contain one space
    without subfields separator.
    Subfield 2 :
    M 10 N V
    Account number of beneficiary
    Subfield 3 :
    O 20 A V
    Short description of payer account
    <CR><LF>AK: M 3AF
    Specific symbol
    O 10 N V
    If the S-symbols is not present, field will be filled with one zero.
    <CR><LF>KI: M 3AF
    Subfield 1 :
    M 35 A V
    Beneficiary description 1
    <CR><LF> Subfield 2 : (row must start with 3 spaces)
    O 35 A V
    Beneficiary description 2
    <CR><LF> Subfield 3 : (row must start with 3 spaces)
    O 35 A V
    Beneficiary description 3
    <CR><LF> Subfield 4 : (row must start with 3 spaces)
    O 35 A V
    Beneficiary description 4
    <CR><LF>EC: M 3AF
    Constant symbol
    (following C-symbols are not permitted from CNB side: 0002, 0005, 0006,
    0051, 0498, 0598, 0898, 1178, 2178, 3178, 4444) O 4NV
    If the C-symbol is not present, field will be filled with one zero. List of valid C-
    symbols is shown at CNB web pages.
    <CR><LF>ZK: M 3AF
    Subfield 1 :
    Variable symbol O 10 N V
    If the V-symbol is not present, field will be filled with one zero.
    <CR><LF>AV: M 3AF
    Subfield 1 :
    O 35 A V
    Supplementary information 1
    <CR><LF> Subfield 2 : (row must start with 3 spaces)
    O 35 A V
    Supplementary information 2
    <CR><LF> Subfield 3 : (row must start with 3 spaces)
    O 35 A V
    Supplementary information 3
    <CR><LF> Subfield 4 : (row must start with 3 spaces)
    O 35 A V
    Supplementary information 4
    <CR><LF>S1: M 3AF
    Subfield 1:
    Number of transfers in the file M 9NF
    Supplemented with leading zeros

    Subfield 2:
    Total amount of transfers M 15 N V
    If not filled, field will contains 3 zeros
    Stránka 4 z 4

    <CR><LF>S3: M 3AF
    Subfield 1:
    Number of direct debits in the file
    M 9NF
    Supplemented with leading zeros

    Subfield 2:
    M 15 N V
    Total amount of direct debits
    If not filled, field will contains 3 zeros

    Example of transfer:
    HD:11|090131|6100|1|0300
    KC:4005006000|000000|CZK
    UD:100001|0000014277|ACCOUNT1
    DI:PAYER|DESCRIPTION|1
    |||PAYER|DESCRIPTION|2
    |||PAYER|DESCRIPTION|3
    |||PAYER|DESCRIPTION|4
    UK:|7777777777|ACCOUNT2
    AK:0
    KI:BENEFICIARY|DESCRIPTION|1
    |||BENEFICIARY|DESCRIPTION|2
    |||BENEFICIARY|DESCRIPTION|3
    |||BENEFICIARY|DESCRIPTION|4
    EC:0
    ZK:1122334455
    AV:INFO1
    |||INFO2
    |||INFO3
    |||INFO4
    S1:000000001|4005006000
    S3:000000000|000

    Transmigration between 2 transfers:


    AV:INFO1
    HD:11|080131|6100|1|0300
    KC:4005006000|000000|CZK
    UD:100001|0000014277|ACCOUNT1
    DI:PAYER|DESCRIPTION|1
    |||PAYER|DESCRIPTION|2
    Example for the field UD with prefix:
    UD:100001|2222222222|ACCOUNT1
    Example for the field UK with prefix:
    UK:19|7777777777|ACCOUNT1
    Example for the field UD without prefix:
    UD:|2222222222|ACCOUNT1

    Example for the field UD without prefix:


    UK:|7777777777|ACCOUNT1

    You might also like