45
PKO Webconnect – Context CZ - Data Import Formats. March 2017

PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

  • Upload
    others

  • View
    16

  • Download
    0

Embed Size (px)

Citation preview

Page 1: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

PKO Webconnect – Context CZ - Data Import Formats. March 2017

Page 2: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

2

TABLE OF CONTENTS

ORDER IMPORT FORMAT TYPES IN CZ CONTEXT ............................................................................................................................. 3

ABO FORMAT DESCRIPTION AND STRUCTURE .................................................................................................................................. 3

Example 1( CCT domestic transfer): .......................................................................................................................................................... 5

Example 2 (CDD Direct Debit): .................................................................................................................................................................... 5

XML FORMAT ...................................................................................................................................................................................................... 6

SEPA Credit Transfer (pain.001.001.03.xml) ......................................................................................................................................... 6

Examples: .............................................................................................................................................................................................................. 9

ISO20022-COMPLIANT ORDER IMPORT FORMAT (PAIN.001.001.07) ................................................................................. 13

SEPA Credit Transfer Order ....................................................................................................................................................................... 13

Example .............................................................................................................................................................................................................. 17

ELIXIR OR SORBNET TRANSFER TO POLISH ACCOUNT IN PLN (TRANSFERS TO POLAND) ..................................... 20

Example .............................................................................................................................................................................................................. 21

CROSS-BORDER TRANSFER (SWIFT) .................................................................................................................................................... 24

Example .............................................................................................................................................................................................................. 26

RFT/MT101 FX ORDER ................................................................................................................................................................................. 30

Example .............................................................................................................................................................................................................. 32

IMPORT OF CDD DIRECT DEBITS (PAIN.008.001.02) .................................................................................................................... 33

Example .............................................................................................................................................................................................................. 38

MT103 /MT101(RFT) IMPORTS ................................................................................................................................................................ 41

Overall structure of the transfer import file ....................................................................................................................................... 42

Example .............................................................................................................................................................................................................. 43

ELIXIR FORMAT ............................................................................................................................................................................................... 44

Example of one line from the transfer import file: ........................................................................................................................... 44

Examples ............................................................................................................................................................................................................ 45

Page 3: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

3

Order Import Format Types in CZ Context

ABO Format Description and Structure

It is a local format for the import of Domestic Transfers and Direct Debits - the standard prevailing on the

Czech market.

Both types of orders can be imported from a single file.

Note: the character set supported by the ABO standard is LATIN in code page 1250.

1. Overview of header

Position in character string

Value Description

1 - 4 UHL label content, non-standard label

5 - 10 date in DDMMYY format

11 - 30 short name of organization - 20 alphanumerical characters

31 - 40 originator bank basic number

41 - 43 serial number assigned by accounting (001)

44 - 46 file clearing number (999)

47 - 48 CR and LF line break character

2. Overview of accounting header

Position in character string

Value Description

1 1 header file type – fixed value (1)

2 space separator

3 - 6 1501 or 1502 Order data type: 1501 – CCT-type orders (domestic transfer) 1502 – CDD-type orders (Direct Debits)

7 space separator

8 - 10 SSS – accounting file number from range 001-999

11 -13 PPB – filled

14 space separator

15 - 18 3060 bank branch code

19 - 20 CR and LF line break character

3. Order group header

Position in character string

Value Description

1 2 Header file type – fixed value (2)

1 space separator

17 PPPPPP-UUUUUUUUUU Account number (optional) „PPPPPP” account prefix –„UUUUUUUUUU” = account number, must be stated once only in group if visible in header, (may be completed with

Page 4: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

4

zeros)

1 space separator

15 total amount of transfers / Direct Debits

1 space separator

6 execution date in DDMMYY format

1 CR and LF line break character

4. Order data

Position in character string

Value Description

17 PPPPPP-UUUUUUUUUU account number (optional) „PPPPPP” account prefix „UUUUUUUUUU”= account number . Account number may be stated once only if present in header.

1 space

17 PPPPPP-UUUUUUUUUU beneficiary account number

1 space separator

15 transfer amount in cents (haléře) / debit

1 space separator

10 variable symbol (VS)

1 space separator

4 Bank branch

4 Fixed symbol (KS)

1 space separator

10 specific symbol (SS) – (optional) if waived, replace with space)

1 space separator

3 + (4 times 35) AV: AV: = mandatory text field

2 CR and LF line break character

5. Order group header

Position in character string

value description

1 3 header footer variable value

2 space separator

3 + Header end character

4 - 5 CR and LF line break character

1 5 + End of whole order

Page 5: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

5

File structure:

UHL 1…….. Header 1 1501….(CCT payment) 1 1502….(CDD collection) Payment type 2…. 000… 000… end of group 1 000… 000… 3+ 2… 000… 000… end of group 2 000… 000… 3+ 2… 000… 000… 000… end of group 3…n 000… 3+ 5+ end of whole order

Example 1( CCT domestic transfer):

UHL1010212PRVNÍ ÚČETNÍ S.R.O. 1234567890001999111111222222 1 1501 100068 3060 2 00000003206 210217 200000435 107-1143211109 3206 1 0067001109 3 + 2 200000435 00000003006 210217 107-1143211109 1001 1 0067000558 2 AV:ABC test for electricity for the month of January.|Invoice - 1 107-1143211109 1002 1 0067000558 2 AV:ABC test for electricity for the month of January.|Invoice - 2 107-1143211109 1003 1 0067000558 2 AV:ABC test for electricity for the month of January.|Invoice - 3 3 + 5 +

Example 2 (CDD Direct Debit): UHL1010212PRVNÍ ÚČETNÍ S.R.O. 1234567890001999111111222222 1 1502 100068 3060 2 00000003206 210217 200000435 107-1143211109 3206 1 0067001109 3 + 2 200000435 00000003003 210217 107-1143211109 1501 1 0067000558 2 AV:RS test for electricity for the month of January.|Invoice - 1 107-1143211109 1502 1 0067000558 2 AV:Rs test for electricity for the month of January.|Invoice - 2 3 + 5 +

Page 6: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

6

XML Format SEPA Credit Transfer (pain.001.001.03.xml)

File format for importing SEPA Credit Transfer orders.

Notation used

Field format:

n = only numerals (0-9) allowed

a = only capitals (A-Z) allowed

x = any character

c = only capitals and numerals allowed

d = decimal number

! = fixed length

[ ] = optional value

ISODate = YYYY-MM-DD

Field status:

M = Mandatory

O = Optional

C = Conditional

- = Prohibited

the XML file should be saved in the UTF-8 code

the XML file should begin in the following declaration:

<?xml version=”1.0” encoding=”UTF-8”?>

xml document name space: urn:sepa:xsd:pain.001.001.03

#. Field name XML tag Height Description

1. Payment title CstmrCdtTrfInitn +PmtInf ++PmtId +++EndToEndId

M 35x

End-to-End ID If data unavailable, value NOTPROVIDED is expected

2. Order type category code

CstmrCdtTrfInitn +PmtInf ++PmtTpInf +++CtgyPurp ++++Cd

OC 4!a

Alternates with „Order type category ID” 4-letter code, not validated by application

3. Order type category ID

CstmrCdtTrfInitn +PmtInf ++PmtTpInf +++CtgyPurp ++++Prtry

OC 35x

Alternates with „Order type category code”

4. Order value date CstmrCdtTrfInitn +PmtInf ++ReqdExctnDt

M Converted into current date if past date.

5. Originator data CstmrCdtTrfInitn +PmtInf ++Dbtr

O Originator name, address and ID. In this case ID only may be specified. If no name and address is supplied – fields will be populated from database. Field not editable in application.

6. Originator account number

CstmrCdtTrfInitn +PmtInf ++DbtrAcct +++Id

M Originator account number in IBAN format

Page 7: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

7

++++IBAN

7. Payment title CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++PmtId ++++ EndToEndId

O 35x

End-to-End ID If data unavailable, value NOTPROVIDED is acceptable. Value preferred over CstmrCdtTrfInitn/PmtInf/PmtId/EndToEndId

8. Order type category code

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++CtgyPurp ++++Cd

OC 4!a

Alternates with „Order type category ID” 4-letter code, not validated by application. Value preferred over CstmrCdtTrfInitn/PmtInf/PmtTpInf/ CtgyPurp/Cd

9. Order type category ID

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++CtgyPurp ++++Prtry

OC 35x

Alternates with „Order type category code” Value preferred over CstmrCdtTrfInitn/PmtInf/PmtTpInf/ CtgyPurp/Prtry

10. Transfer amount CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++Amt ++++InstdAmt

M 18d

Transfer amount in EUR. Point to be used as decimal separator. Ccy attribute must have fixed value of EUR Ccy="EUR"

11. Original Originator

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++UltmtDbtr

O Original Originator name, address and ID.

12. Beneficiary bank BIC

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++ CdtrAgt ++++FinInstnId +++++BIC

O

„Creditor Agent” Beneficiary bank BIC. 4!a2!a2!c[3!c]

13. Beneficiary data CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++Cdtr

M Beneficiary name, address and ID

14. Beneficiary account number

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++CdtrAcct ++++Id +++++IBAN

M Beneficiary account number in IBAN format

15. Ultimate Beneficiary

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++UltmtCdtr

O Ultimate Beneficiary name, address and ID

16. Order purpose code

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++Purp ++++Cd

O 4!a

4-letter code, not validated by application

17. Ustrd Remittance Information

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++RmtInf ++++Ustrd

OC 140x

„Unstructured Remittance Information” Additional information (unstructured).

Maximum length of 140 characters

If present, field „Structured Remittance Information” cannot be present +++RmtInf ++++Ustrd

Strd Remittance Information

CstmrCdtTrfInitn +PmtInf

OC 140x

“Structured Remittance Information” Additional information (structured)

Page 8: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

8

++CdtTrfTxInf +++RmtInf ++++UStrd

Use of field not recommended

Field cannot be edited in application

Maximum length of 140 characters including tags except for Strd tag.

If present, field “Unstructured Remittance Information” cannot be present +++RmtInf ++++Ustrd

CstmrCdtTrfInitn/PmtInf nodes are present for every source account or for every order in the file.

CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf are present for every order in the file. Structure of Originator, Beneficiary, Original Originator and Ultimate Beneficiary data:

#. Field name XML tag Height Description

1. Name Nm M Name

2. Address PstlAdr +AdrLine

M Address. Maximum 2 instances of AdrLine

3. Country code PstlAdr +Ctry

M 2!a

Country code

4. ID Id O Private or organization ID

Private ID

#. Field name XML tag Height Description

1. Date and place of birth

PrvtId +DtAndPlcOfBirth

C Alternates with „Other ID” <DtAndPlcOfBirth> <BirthDt>1980-04-01</BirthDt> <CityOfBirth>Radom</CityOfBirth> <CtryOfBirth>PL</CtryOfBirth> </DtAndPlcOfBirth>

2. Other ID PrvtId +Othr

C Alternates with „Date and place of birth” <Othr> <Id>ID</Id> <Issr>Issuer</Issr> </Othr>

Organization ID

#. Field name XML tag Height Description

1. BIC or BEI ID OrgId +BICOrBEI

C Alternates with „Other ID”

2. Other ID OrgId +Othr

C Alternates with „BIC or BEI ID” <Othr> <Id>ID</Id> <Issr>Issuer</Issr> </Othr>

UStrd field

#. Field name XML tag Height Description

1. Beneficiary reference type code

CdtrRefInf +Tp ++CdOrPrtry +++Cd

M 4!a

Calculated value. Currently only SCOR available.

2. Issuer CdtrRefInf +Tp ++Issr

O Issuer ID

3. Beneficiary transaction references

CdtrRefInf +Ref

M References

Page 9: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

9

Examples: <?xml version="1.0" encoding="UTF-8"?> <Document xmlns="urn:sepa:xsd:pain.001.001.03"> <CstmrCdtTrfInitn> <PmtInf> <!-- originator account 1 --> <PmtId> <EndToEndId>NOTPROVIDED</EndToEndId> </PmtId> <ReqdExctnDt>2012-01-02</ReqdExctnDt> <DbtrAcct> <Id> <IBAN>PL38144011560000000000071013</IBAN> </Id> </DbtrAcct> <CdtTrfTxInf> <!-- transfer 1 from account 1 --> <PmtId> <EndToEndId>end2end ref</EndToEndId> </PmtId> <PmtTpInf> <CtgyPurp> <Cd>CASH</Cd> </CtgyPurp> </PmtTpInf> <Amt> <InstdAmt Ccy="EUR">123.99</InstdAmt> </Amt> <CdtrAgt> <FinInstnId> <BIC>AAABITM0XXX</BIC> </FinInstnId> </CdtrAgt> <Cdtr> <Nm>Beneficiary name</Nm> <PstlAdr> <AdrLine>Beneficiary address 1</AdrLine> <AdrLine>Beneficiary address 1</AdrLine> <Ctry>PL</Ctry> </PstlAdr> </Cdtr> <CdtrAcct> <Id> <IBAN>PL67101011400149482222000000</IBAN> </Id> </CdtrAcct> <Purp> <Cd>KODC</Cd> </Purp> <RmtInf> <Ustrd> FA/111/2011 </Ustrd> </RmtInf> </CdtTrfTxInf> <CdtTrfTxInf> <!-- transfer 2 from account 1 --> <PmtId> <EndToEndId>end2end ref </EndToEndId>

Page 10: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

10

</PmtId> <Amt> <InstdAmt Ccy="EUR">333.23</InstdAmt> </Amt> <CdtrAgt> <FinInstnId> <BIC>AAABITM0XXX</BIC> </FinInstnId> </CdtrAgt> <Cdtr> <Nm>Beneficiary name 2</Nm> <PstlAdr> <AdrLine>Beneficiary address 1</AdrLine> <AdrLine>Beneficiary address 2</AdrLine> <Ctry>PL</Ctry> </PstlAdr> <Id> <PrvtId> <DtAndPlcOfBirth> <BirthDt>2000-01-01</BirthDt> <CityOfBirth>Warszawa</CityOfBirth> <CtryOfBirth>PL</CtryOfBirth> </DtAndPlcOfBirth> </PrvtId> </Id> <CtryOfRes>PL</CtryOfRes> </Cdtr> <CdtrAcct> <Id> <IBAN>PL67101011400149482222000000</IBAN> </Id> </CdtrAcct> <RmtInf> <Ustrd>Remittance information</Ustrd> </RmtInf> </CdtTrfTxInf> </PmtInf> <PmtInf> <!-- Originator account 2 --> <PmtId> <EndToEndId>1234567890</EndToEndId> </PmtId> <ReqdExctnDt>2012-01-09</ReqdExctnDt> <Dbtr> <Id> <OrgId> <Othr> <Id>1234567890</Id> <SchmeNm> <Cd>TXID</Cd> </SchmeNm> <Issr>Issuer1234</Issr> </Othr> </OrgId> </Id> </Dbtr> <DbtrAcct> <Id> <IBAN>PL70144011560000000000088188</IBAN> </Id>

Page 11: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

11

</DbtrAcct> <CdtTrfTxInf> <!-- transfer 1 from account 2 --> <PmtTpInf> <CtgyPurp> <Prtry>ABCDEFGHIJKLMNOPQRST</Prtry> </CtgyPurp> </PmtTpInf> <Amt> <InstdAmt Ccy="EUR">123.99</InstdAmt> </Amt> <UltmtDbtr> <Nm>Jan Kowalski</Nm> <PstlAdr> <AdrLine>03-580 Warszawa</AdrLine> <AdrLine>Askenazego 43</AdrLine> <Ctry>PL</Ctry> </PstlAdr> <Id> <OrgId> <BICOrBEI>NDEAPLXXXXX</BICOrBEI> </OrgId> </Id> </UltmtDbtr> <CdtrAgt> <FinInstnId> <BIC>AAABITM0XXX</BIC> </FinInstnId> </CdtrAgt> <Cdtr> <Nm>Creditor name</Nm> <PstlAdr> <AdrLine>Creditor address line 1</AdrLine> <AdrLine>Creditor address line 2</AdrLine> <Ctry>PL</Ctry> </PstlAdr> <Id> <OrgId> <BICOrBEI>NDEAPLBB</BICOrBEI> </OrgId> </Id> <CtryOfRes>PL</CtryOfRes> </Cdtr> <CdtrAcct> <Id> <IBAN>PL67101011400149482222000000</IBAN> </Id> </CdtrAcct> <UltmtCdtr> <Nm>Jan Nowak</Nm> <PstlAdr> <AdrLine>Puławska 101</AdrLine> <AdrLine>00-000 Warszawa</AdrLine> <Ctry></Ctry> </PstlAdr> <Id> <OrgId> <BICOrBEI>NDEAPLAA</BICOrBEI> </OrgId> </Id>

Page 12: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

12

</UltmtCdtr> <Purp> <Cd>TEST</Cd> </Purp> <RmtInf> <Strd> <CdtrRefInf> <Tp> <CdOrPrtry> <Cd>SCOR</Cd> </CdOrPrtry> </Tp> <Ref>RefNo:1234567890</Ref> </CdtrRefInf> </UStrd> </RmtInf> </CdtTrfTxInf> </PmtInf> </CstmrCdtTrfInitn>

</Document>

Page 13: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

13

ISO20022-compliant order import format (pain.001.001.07) Notation used

Field format:

n = only numerals (0-9) allowed

a = only capitals (A-Z) allowed

x = any character

c = only capitals and numerals allowed

d = decimal number

! = fixed length

[ ] = optional value

ISODate = YYYY-MM-DD

ISODateTime = YYYY-MM-DDThh:mm:ss

Field status:

M = Mandatory

O = Optional

C = Conditional

- = Prohibited

the XML file should be saved in the UTF-8 code

the XML file should begin in the following declaration:

<?xml version=”1.0” encoding=”UTF-8”?>

the xml document name space urn:iso:std:iso:20022:tech:xsd:pain.001.001.07

CstmrCdtTrfInitn/PmtInf/DbtrAcct/Id/Othr/Id

<DbtrAcct>

<Id>

<Othr>

<Id>38144011560000000000071013</Id>

</Othr>

<!--<IBAN>PL38144011560000000000071013</IBAN>-->

</Id>

</DbtrAcct>

It is permitted to use the NRB account format instead of IBAN also in the “Beneficiary account number” field

in domestic transfers in PLN as well as intra-bank transfers, but then the country must be identified in one of

the fields with specified values

CdtrAgt/FinInstnId/ClrSysMmbIdClrSysId/Cd=PLKNR

CdtrAgt/FinInstnId/PstlAdr/Ctry=PL

SEPA Credit Transfer Order

#. Field name XML tag Height Description

1. Message ID CstmrCdtTrfInitn +GrpHdr ++MsgId

M 35x

Value ignored

2. Message creation time

CstmrCdtTrfInitn +GrpHdr ++CreDtTm

M ISODateTime

Value ignored

3. Number of CstmrCdtTrfInitn M Number of transactions in message

Page 14: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

14

transactions +GrpHdr ++NbOfTxs

15n Field verified

4. Sum-total of transaction amounts

CstmrCdtTrfInitn +GrpHdr ++CtrlSum

O 18d

Sum-total of transaction amounts disregarding currency Field verified if present

5. Originator data

CstmrCdtTrfInitn +GrpHdr ++InitgPty

M Value ignored

6. Payment ID CstmrCdtTrfInitn +PmtInf ++PmtInfId

M 35x

Value ignored

7. Payment method

CstmrCdtTrfInitn +PmtInf ++PmtMtd

M 3!a

Field should have value TRF

8. Order type category code

CstmrCdtTrfInitn +PmtInf ++PmtTpInf +++CtgyPurp

++++Cd

OC 4!a

Alternates with „Order type category ID” 4-letter code

9. Order type category ID

CstmrCdtTrfInitn +PmtInf ++PmtTpInf +++CtgyPurp

++++Prtry

OC 35x

Alternates with „Order type category code”

10. Order value date

CstmrCdtTrfInitn +PmtInf ++ReqdExctnDt

M ISODate

Converted into current date if past date.

11. Originator data

CstmrCdtTrfInitn +PmtInf

++Dbtr

O Originator name, address and ID. In this case just ID may be specified. If no name and address is supplied – fields will be populated from database. Field not editable in application.

12. Originator account number

CstmrCdtTrfInitn +PmtInf

++DbtrAcct

+++Id

++++IBAN

M Originator account number in IBAN format

13. Originator bank ID

CstmrCdtTrfInitn +PmtInf ++DbtrAgt +++FinInstnId

M

Value ignored

14. Commission account

CstmrCdtTrfInitn +PmtInf ++ChrgsAcct +++Id ++++IBAN

O

Commission account

15. Payment title CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++PmtId ++++ EndToEndId

O 35x

End-to-End ID

If data unavailable, value NOTPROVIDED is

acceptable.

16. Payment type code

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++PmtTpInf ++++SvcLvl +++++Cd

M Value SEPA for SCT

17. Order type CstmrCdtTrfInitn OC Alternates with „Order type category ID”

Page 15: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

15

category code

+PmtInf ++CdtTrfTxInf +++PmtTpInf ++++CtgyPurp +++++Cd

4!a 4-letter code

Value preferred over CstmrCdtTrfInitn/PmtInf/PmtTpInf/ CtgyPurp/Cd

18. Order type category ID

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++PmtTpInf ++++CtgyPurp +++++Prtry

OC 35x

Alternates with „Order type category code”

Value preferred over CstmrCdtTrfInitn/PmtInf/PmtTpInf/

CtgyPurp/Prtry

19. Transfer amount

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++Amt ++++InstdAmt

M 18d

Transfer amount in EUR. Point to be used

as decimal separator.

Ccy attribute must have fixed value of EUR Ccy="EUR"

20. Original Originator

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++UltmtDbtr

O Original Originator name, address and ID.

21. Beneficiary bank BIC

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++ CdtrAgt ++++FinInstnId +++++BICFI

O

Value ignored Beneficiary bank BIC. 4!a2!a2!c[3!c]

22. Beneficiary data

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++Cdtr

M Beneficiary name, address and ID

23. Beneficiary account number

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++CdtrAcct ++++Id +++++IBAN

M Beneficiary account number in IBAN format

24. Ultimate Beneficiary

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++UltmtCdtr

O Ultimate Beneficiary name, address and ID

25. Order purpose code

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++Purp ++++Cd

O 4!a

4-letter code, not validated by application

26. Ustrd Remittance Information

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++RmtInf ++++Ustrd

OC 140x

„Unstructured Remittance Information”

Additional information (unstructured).

Maximum one instance

Maximum length of 140 characters

If present, field „Structured Remittance Information” cannot be present

+++RmtInf

++++Ustrd

27. Strd Remittance Information

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++RmtInf

++++Ustrd

OC 140x

“Structured Remittance Information”

Additional information (structured)

Maximum one instance

Use of field not recommended

Field cannot be edited in application

Page 16: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

16

Maximum length of 140 characters including tags except for Strd tag.

If present, field “Unstructured Remittance Information” cannot be present

+++RmtInf

++++Ustrd

PmtTpInf nodes are present for every source account in CstmrCdtTrfInitn/PmtInf, or for every order in

CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf

Structure of Originator, Beneficiary, Original Originator and Ultimate Beneficiary data:

#. Field name XML tag Height Description

1. Name Nm M Name

2. Country code PstlAdr +Ctry

M 2!a

Country code

3. Address PstlAdr +AdrLine

M Address. Maximum 2 instances of AdrLine

4. ID Id O Private or organization ID

Private ID

#. Field name XML tag Height Description

1. Date and place of birth

PrvtId +DtAndPlcOfBirth

C Alternates with „Other ID” <DtAndPlcOfBirth> <BirthDt>1980-04-01</BirthDt> <CityOfBirth>Radom</CityOfBirth> <CtryOfBirth>PL</CtryOfBirth> </DtAndPlcOfBirth>

2. Other ID PrvtId +Othr

C Alternates with „Date and place of birth” <Othr> <Id>ID</Id> <Issr>Issuer</Issr> </Othr>

Organization ID

#. Field name XML tag Height Description

1. BIC or BEI ID OrgId +AnyBIC

C Alternates with „Other ID”

2. Other ID OrgId +Othr

C Alternates with „BIC or BEI ID” <Othr> <Id>ID</Id> <Issr>Issuer</Issr> </Othr>

UStrd field

#. Field name XML tag Height Description

1. Beneficiary reference type code

CdtrRefInf +Tp ++CdOrPrtry +++Cd

M 4!a

Calculated value. Currently only SCOR available.

2. Issuer CdtrRefInf +Tp ++Issr

O Issuer ID

3. Beneficiary CdtrRefInf M References

Page 17: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

17

transaction references

+Ref

Example

File with 3 transfers.

<?xml version="1.0" encoding="UTF-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.07"> <CstmrCdtTrfInitn> <GrpHdr> <MsgId>xx</MsgId> <CreDtTm>2017-03-21T10:10:11</CreDtTm> <NbOfTxs>3</NbOfTxs> <CtrlSum>581.21</CtrlSum> <InitgPty/> </GrpHdr> <PmtInf> <!-- Originator account 1 --> <PmtInfId>P1</PmtInfId> <PmtMtd>TRF</PmtMtd> <ReqdExctnDt>2017-01-02</ReqdExctnDt> <Dbtr/> <DbtrAcct> <Id> <IBAN> CZ4230600000000200000418</IBAN> </Id> </DbtrAcct> <DbtrAgt> <FinInstnId/> </DbtrAgt> <CdtTrfTxInf> <!-- transfer 1 from account 1 --> <PmtId> <EndToEndId>NOTPROVIDED</EndToEndId> </PmtId> <Amt> <InstdAmt Ccy="EUR">123.99</InstdAmt> </Amt> <Cdtr> <Nm>Beneficiary name</Nm> <PstlAdr> <Ctry>PL</Ctry> <AdrLine>Beneficiary address 1</AdrLine> <AdrLine>Beneficiary address 2</AdrLine> </PstlAdr> </Cdtr> <CdtrAcct> <Id> <IBAN>PL67101011400149482222000000</IBAN> </Id> </CdtrAcct> <RmtInf> <Ustrd> FA/111/2011 </Ustrd> </RmtInf> </CdtTrfTxInf> <CdtTrfTxInf> <!-- transfer 2 from account 1 -->

Page 18: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

18

<PmtId> <EndToEndId>end2end ref </EndToEndId> </PmtId> <Amt> <InstdAmt Ccy="EUR">333.23</InstdAmt> </Amt> <Cdtr> <Nm>Beneficiary name 2</Nm> <PstlAdr> <Ctry>PL</Ctry> <AdrLine>Beneficiary address 1</AdrLine> <AdrLine>Beneficiary address 2</AdrLine> </PstlAdr> <Id> <PrvtId> <DtAndPlcOfBirth> <BirthDt>2000-01-01</BirthDt> <CityOfBirth>Warszawa</CityOfBirth> <CtryOfBirth>PL</CtryOfBirth> </DtAndPlcOfBirth> </PrvtId> </Id> <CtryOfRes>PL</CtryOfRes> </Cdtr> <CdtrAcct> <Id> <IBAN>PL67101011400149482222000000</IBAN> </Id> </CdtrAcct> <RmtInf> <Ustrd>Payment title</Ustrd> </RmtInf> </CdtTrfTxInf> </PmtInf> <PmtInf> <!-- Originator account 2 --> <PmtInfId>P2</PmtInfId> <PmtMtd>TRF</PmtMtd> <ReqdExctnDt>2017-01-09</ReqdExctnDt> <Dbtr> <Id> <OrgId> <Othr> <Id>1234567890</Id> <SchmeNm> <Cd>TXID</Cd> </SchmeNm> <Issr>Issuer1234</Issr> </Othr> </OrgId> </Id> </Dbtr> <DbtrAcct> <Id> <IBAN> CZ4230600000000200000418</IBAN> </Id> </DbtrAcct> <DbtrAgt> <FinInstnId/> </DbtrAgt>

Page 19: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

19

<CdtTrfTxInf> <!-- transfer 1 from account 2 --> <PmtId> <EndToEndId>NOTPROVIDED</EndToEndId> </PmtId> <PmtTpInf> <CtgyPurp> <Prtry>ABCDEFGHIJKLMNOPQRST</Prtry> </CtgyPurp> </PmtTpInf> <Amt> <InstdAmt Ccy="EUR">123.99</InstdAmt> </Amt> <UltmtDbtr> <Nm>Jan Kowalski</Nm> <PstlAdr> <Ctry>PL</Ctry> <AdrLine>03-580 Warszawa</AdrLine> <AdrLine>Askenazego 43</AdrLine> </PstlAdr> <Id> <OrgId> <AnyBIC>NDEAPLXXXXX</AnyBIC> </OrgId> </Id> </UltmtDbtr> <Cdtr> <Nm>Creditor name</Nm> <PstlAdr> <Ctry>PL</Ctry> <AdrLine>Creditor address line 1</AdrLine> <AdrLine>Creditor address line 2</AdrLine> </PstlAdr> <Id> <OrgId> <AnyBIC>XXXXPLBB</AnyBIC> </OrgId> </Id> <CtryOfRes>PL</CtryOfRes> </Cdtr> <CdtrAcct> <Id> <IBAN>PL67101011400149482222000000</IBAN> </Id> </CdtrAcct> <UltmtCdtr> <Nm>Jan Nowak</Nm> <PstlAdr> <Ctry>PL</Ctry> <AdrLine>Puławska 101</AdrLine> <AdrLine>00-000 Warszawa</AdrLine> </PstlAdr> <Id> <OrgId> <AnyBIC>BPKOPLAA</AnyBIC> </OrgId> </Id> </UltmtCdtr> <Purp> <Cd>TEST</Cd>

Page 20: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

20

</Purp> <RmtInf> <UStrd> <CdtrRefInf> <Tp> <CdOrPrtry> <Cd>SCOR</Cd> </CdOrPrtry> </Tp> <Ref>RefNo:1234567890</Ref> </CdtrRefInf> </UStrd> </RmtInf> </CdtTrfTxInf> </PmtInf> </CstmrCdtTrfInitn>

</Document>

Elixir or Sorbnet transfer to Polish account in PLN (Transfers to Poland)

# Field name XML tag Height Description

1. Message ID CstmrCdtTrfInitn +GrpHdr ++MsgId

M 35x

Value ignored

2. Message creation time

CstmrCdtTrfInitn +GrpHdr ++CreDtTm

M ISODateTime

Value ignored

3. Number of transactions

CstmrCdtTrfInitn +GrpHdr ++NbOfTxs

M 15n

Number of transactions in message Field verified

4. Sum-total of transaction amounts

CstmrCdtTrfInitn +GrpHdr ++CtrlSum

O 18d

Sum-total of transaction amounts disregarding currency Field verified if present

5. Originator data

CstmrCdtTrfInitn +GrpHdr ++InitgPty

M Value ignored

6. Payment ID CstmrCdtTrfInitn +PmtInf ++PmtInfId

M 35x

Value ignored

7. Payment method

CstmrCdtTrfInitn +PmtInf ++PmtMtd

M 3!a

Field should have value TRF

8. Order value date

CstmrCdtTrfInitn +PmtInf ++ReqdExctnDt

M ISODate

Converted into current date if past date.

9. Originator data

CstmrCdtTrfInitn +PmtInf ++Dbtr

O Value ignored.

10. Originator account number

CstmrCdtTrfInitn +PmtInf ++DbtrAcct +++Id ++++IBAN

M Originator account number in IBAN format

11. Originator bank ID

CstmrCdtTrfInitn +PmtInf

M

Value ignored

Page 21: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

21

++DbtrAgt +++FinInstnId

12. Payment title CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++PmtId ++++ EndToEndId

M 35x

Value ignored.

13. Payment type code

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++PmtTpInf ++++SvcLvl +++++Cd

RTGS value for SORBNET transfers Ignored if Beneficiary banks with same bank.

14. Transfer amount

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++Amt ++++InstdAmt

M 18d

Transfer amount in PLN or, if Beneficiary banks with PKO BP, other currencies may be used (verified against Beneficiary account). Point to be used as decimal separator. Ccy="PLN"

15. Beneficiary data

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++Cdtr

M Name and address

16. Beneficiary account number

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++CdtrAcct ++++Id +++++IBAN

M Beneficiary account number in IBAN format

17. Ustrd Remittance Information

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++RmtInf ++++Ustrd

OC 140x

„Unstructured Remittance Information” Additional information (unstructured).

PmtTpInf nodes are present for every source account in CstmrCdtTrfInitn/PmtInf, or for every order in

CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf

Structure of Beneficiary data:

#. Field name XML tag Height Description

1. Name Nm M 70x

Name

2. Address PstlAdr +AdrLine

M 1x70x or 2x35x

Address. Maximum 2 instances of AdrLine

Example

<?xml version="1.0" encoding="UTF-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.07"> <CstmrCdtTrfInitn> <GrpHdr> <MsgId>xx</MsgId> <CreDtTm>2016-09-26T10:10:11</CreDtTm> <NbOfTxs>3</NbOfTxs> <CtrlSum>125.99</CtrlSum> <InitgPty/> </GrpHdr> <!--domestic transfer-->

Page 22: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

22

<PmtInf> <PmtInfId>1</PmtInfId> <PmtMtd>TRF</PmtMtd> <ReqdExctnDt>2012-01-02</ReqdExctnDt> <Dbtr/> <DbtrAcct> <Id> <Othr> <!-- NRB Format--> <Id>38144011560000000000071013</Id> </Othr> <!--<IBAN>PL38144011560000000000071013</IBAN>--> </Id> </DbtrAcct> <DbtrAgt> <FinInstnId/> </DbtrAgt> <CdtTrfTxInf> <!-- payment 1--> <PmtId> <EndToEndId>NOTPROVIDED</EndToEndId> </PmtId> <Amt> <InstdAmt Ccy="PLN">123.99</InstdAmt> </Amt> <Cdtr> <Nm>Domestic beneficiary name</Nm> <PstlAdr> <AdrLine>Warszawa</AdrLine> </PstlAdr> </Cdtr> <CdtrAcct> <Id> <IBAN>PL17101010100164212223000000</IBAN> </Id> </CdtrAcct> <RmtInf> <Ustrd>Title 123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890</Ustrd> </RmtInf> </CdtTrfTxInf> </PmtInf> <!--domestic transfer SORBNET--> <PmtInf> <PmtInfId>1</PmtInfId> <PmtMtd>TRF</PmtMtd> <ReqdExctnDt>2012-01-02</ReqdExctnDt> <Dbtr/> <DbtrAcct> <Id> <IBAN>PL38144011560000000000071013</IBAN> </Id> </DbtrAcct> <DbtrAgt> <FinInstnId/> </DbtrAgt> <CdtTrfTxInf> <!-- payment 1--> <PmtId>

Page 23: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

23

<EndToEndId>NOTPROVIDED</EndToEndId> </PmtId> <PmtTpInf> <SvcLvl> <Cd>RTGS</Cd> </SvcLvl> </PmtTpInf> <Amt> <InstdAmt Ccy="PLN">1.00</InstdAmt> </Amt> <Cdtr> <Nm>Domestic beneficiary name</Nm> <PstlAdr> <AdrLine>Warszawa</AdrLine> </PstlAdr> </Cdtr> <CdtrAcct> <Id> <IBAN>PL17101010100164212223000000</IBAN> </Id> </CdtrAcct> <RmtInf> <Ustrd>SORBNET Title 1234567</Ustrd> <Ustrd>title line 2</Ustrd> <Ustrd>title line 3</Ustrd> <Ustrd>title line 4</Ustrd> </RmtInf> </CdtTrfTxInf> </PmtInf> <!-- Intra-bank FX transfer--> <PmtInf> <PmtInfId>1</PmtInfId> <PmtMtd>TRF</PmtMtd> <ReqdExctnDt>2012-01-02</ReqdExctnDt> <Dbtr/> <DbtrAcct> <Id> <IBAN>PL38144011560000000000071013</IBAN> </Id> </DbtrAcct> <DbtrAgt> <FinInstnId/> </DbtrAgt> <CdtTrfTxInf> <PmtId> <EndToEndId>NOTPROVIDED</EndToEndId> </PmtId> <Amt> <InstdAmt Ccy="USD">1.00</InstdAmt> </Amt> <Cdtr> <Nm>Klient PKOBP</Nm> <PstlAdr> <AdrLine>Warszawa</AdrLine> </PstlAdr> </Cdtr> <CdtrAcct> <Id> <IBAN>PL31102023130000330203878022</IBAN>

Page 24: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

24

</Id> </CdtrAcct> <RmtInf> <Ustrd>Remittance title 123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890</Ustrd> </RmtInf> </CdtTrfTxInf> </PmtInf> </CstmrCdtTrfInitn>

</Document>

Cross-border transfer (SWIFT) If the beneficiary account is identified as held with PKO BP, the transfer will be reclassified as an intra-bank

transfer. Individual exchange rates cannot be applied in intra-bank transfers.

#. Field name XML tag Height Description

1.

Message ID CstmrCdtTrfInitn +GrpHdr ++MsgId

M 35x

Value ignored

2.

Message creation time

CstmrCdtTrfInitn +GrpHdr ++CreDtTm

M ISODateTime

Value ignored

3.

Number of transactions

CstmrCdtTrfInitn +GrpHdr ++NbOfTxs

M 15n

Number of transactions in message Field verified

4.

Sum-total of transaction amounts

CstmrCdtTrfInitn +GrpHdr ++CtrlSum

O 18d

Sum-total of transaction amounts disregarding currency Field verified if present

5.

Originator data

CstmrCdtTrfInitn +GrpHdr ++InitgPty

M Value ignored

6.

Payment ID CstmrCdtTrfInitn +PmtInf ++PmtInfId

M 35x

Value ignored

7.

Payment method

CstmrCdtTrfInitn +PmtInf ++PmtMtd

M 3!a

Field should have value TRF

8.

Order value date

CstmrCdtTrfInitn +PmtInf ++ReqdExctnDt

M ISODate

Converted into current date if past date.

9.

Originator data

CstmrCdtTrfInitn +PmtInf ++Dbtr

O Value ignored.

10.

Originator account number

CstmrCdtTrfInitn +PmtInf ++DbtrAcct +++Id ++++IBAN

M Originator account number in IBAN format

11.

Originator bank ID

CstmrCdtTrfInitn +PmtInf ++DbtrAgt +++FinInstnId

M

Value ignored

12. Commission account

CstmrCdtTrfInitn +PmtInf ++ChrgsAcct

O

Commission account

Page 25: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

25

+++Id ++++IBAN

13.

Payment title CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++PmtId ++++ EndToEndId

O 35x

End-to-End ID Value ignored

14. Priority CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++PmtTpInf ++++InstrPrty

O NORM – default value +2 HIGH – Urgent +1 If HIGH and SvcLvl=SDVA – Urgent +0

15.

Payment type code

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++PmtTpInf ++++SvcLvl +++++Cd

O 4!a

If InstrPrty=HIGH and SvcLvl =SDVA, then Priority = Urgent +0

16.

Order type category code

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++PmtTpInf ++++CtgyPurp +++++Cd

OC 4!a

If INTC value, no individual exchange rate and Beneficiary BIC consistent with bank requirements, then transfer qualified as PKO Intracompany Payment Value preferred over CstmrCdtTrfInitn/PmtInf/PmtTpInf/ CtgyPurp/Cd

17.

Transfer amount

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++Amt ++++InstdAmt

M 18d

Transfer amount in currency handled by bank, except for PLN for beneficiary in Polish bank. Point to be used as decimal separator.

18. Individual rate

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++XchgRateInf ++++CtrctId

O Contract ID as KFX prefix followed by 6 to 9 numerals

19. Cost CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++ChrgBr

O SHAR – shared – default value DEBT – originator CRED – beneficiary (prohibited for PSD countries)

20.

Beneficiary bank BIC

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++ CdtrAgt ++++FinInstnId +++++BICFI

C

Beneficiary bank BIC. 4!a2!a2!c[3!c] Required except USA

21. Beneficiary bank other ID

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++ CdtrAgt ++++FinInstnId +++++ClrSysMmbId

C Mandatory if BIC not available ID Fedwire (ClrSysId/Cd=USABA) and beneficiary bank name and address, and country code: <FinInstnId> <ClrSysMmbId> <ClrSysId> <Cd>USABA</Cd> </ClrSysId> <MmbId>251480563</MmbId> </ClrSysMmbId> <Nm>1ST ADVANTAGE FCU</Nm> <PstlAdr> <Ctry>US</Ctry>

Page 26: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

26

<AdrLine>GLOUCESTER</AdrLine> <AdrLine>VA</AdrLine> </PstlAdr> </FinInstnId>

22.

Beneficiary data

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++Cdtr

M Beneficiary name, address and ID

23.

Beneficiary account number - IBAN

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++CdtrAcct ++++Id +++++IBAN

C 35x

Beneficiary account number in IBAN format. Mandatory for PSD countries

24. Beneficiary account number - Other

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++CdtrAcct ++++Id +++++Othr ++++++Id

C 35x

Beneficiary account number in other format than IBAN

25.

Order purpose code

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++Purp ++++Prtry

C 4!a

FRGN value

FRGN value required if SWIFT payment

deliberately in EUR to SEPA country. If not present, classification as SEPA CT payment possible .

26.

Payment details

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++RmtInf ++++Ustrd

OC 140x

PmtTpInf nodes are present for every source account in CstmrCdtTrfInitn/PmtInf, or for every order in

CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf

Structure of Beneficiary data:

#. Field name XML tag Height description

1. Name Nm M Name

2. Address PstlAdr +AdrLine

M 70x or 2x35x

Address. Maximum 2 instances of AdrLine

Example

<?xml version="1.0" encoding="UTF-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.07"> <CstmrCdtTrfInitn> <GrpHdr> <MsgId>xx</MsgId> <CreDtTm>2017-03-21T10:10:11</CreDtTm> <NbOfTxs>4</NbOfTxs> <CtrlSum>4.00</CtrlSum> <InitgPty/> </GrpHdr> <PmtInf> <!-- Originator account 1 -->

Page 27: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

27

<PmtInfId>1</PmtInfId> <PmtMtd>TRF</PmtMtd> <ReqdExctnDt>2017-01-02</ReqdExctnDt> <Dbtr/> <DbtrAcct> <Id> <IBAN>PL38144011560000000000071013</IBAN> </Id> </DbtrAcct> <DbtrAgt> <FinInstnId/> </DbtrAgt> <!--Commission account--> <ChrgsAcct> <Id> <IBAN>PL55102055610000320200118109</IBAN> </Id> </ChrgsAcct> <!--transfer SWIFT priority +1--> <CdtTrfTxInf> <!-- payment 1 from account 1 --> <PmtId> <!--Ignored in SWIFT transfers--> <EndToEndId>NOTPROVIDED</EndToEndId> </PmtId> <PmtTpInf> <!--Priority +1--> <InstrPrty>HIGH</InstrPrty> </PmtTpInf> <Amt> <InstdAmt Ccy="USD">1.00</InstdAmt> </Amt> <XchgRateInf> <!--Individual rate--> <CtrctId>KFX123456789</CtrctId> </XchgRateInf> <CdtrAgt> <FinInstnId> <BICFI>NBP##WXXX</BICFI> </FinInstnId> </CdtrAgt> <Cdtr> <Nm>Creditor name</Nm> <PstlAdr> <Ctry>PL</Ctry> <AdrLine>Creditor address line 1</AdrLine> <AdrLine>Creditor address line 2</AdrLine> </PstlAdr> </Cdtr> <CdtrAcct> <Id> <IBAN>PL67101011400149482222000000</IBAN> </Id> </CdtrAcct> <Purp> <!--Optional for currency other than EUR. SWIFT by default instead of SCT--> <Prtry>FRGN</Prtry> </Purp> <RmtInf> <Ustrd>

Page 28: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

28

FA/111/2016 </Ustrd> </RmtInf> </CdtTrfTxInf> <!--transfer SWIFT priority +0--> <CdtTrfTxInf> <PmtId> <EndToEndId>NOTPROVIDED</EndToEndId> </PmtId> <PmtTpInf> <InstrPrty>HIGH</InstrPrty> <SvcLvl> <!--Priority +0 if <InstrPrty>HIGH</InstrPrty>--> <Cd>SDVA</Cd> </SvcLvl> </PmtTpInf> <Amt> <InstdAmt Ccy="GBP">1.00</InstdAmt> </Amt> <XchgRateInf> <CtrctId>KFX123456789</CtrctId> </XchgRateInf> <!--Cost charged to originator--> <ChrgBr>DEBT</ChrgBr> <CdtrAgt> <FinInstnId> <BICFI>AGRIFRPP802</BICFI> </FinInstnId> </CdtrAgt> <Cdtr> <Nm>FR1</Nm> <PstlAdr> <AdrLine>Creditor address line 1</AdrLine> <AdrLine>Creditor address line 2</AdrLine> </PstlAdr> </Cdtr> <CdtrAcct> <Id> <IBAN>FR7610206000829837034948618</IBAN> </Id> </CdtrAcct> <RmtInf> <Ustrd> FA/111/2016 </Ustrd> </RmtInf> </CdtTrfTxInf> <!-- Simplest domestic SWIFT in EUR--> </PmtInf> <!-- SWIFT transfer in EUR to Poland--> <PmtInf> <PmtInfId>1</PmtInfId> <PmtMtd>TRF</PmtMtd> <ReqdExctnDt>2017-01-02</ReqdExctnDt> <Dbtr/> <DbtrAcct> <Id> <IBAN>PL38144011560000000000071013</IBAN> </Id>

Page 29: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

29

</DbtrAcct> <DbtrAgt> <FinInstnId/> </DbtrAgt> <CdtTrfTxInf> <PmtId> <EndToEndId>NOTPROVIDED</EndToEndId> </PmtId> <Amt> <InstdAmt Ccy="EUR">1.00</InstdAmt> </Amt> <CdtrAgt> <FinInstnId> <BICFI>NBP##WXXX</BICFI> </FinInstnId> </CdtrAgt> <Cdtr> <Nm>Creditor name</Nm> <PstlAdr> <AdrLine>Creditor address line 1</AdrLine> </PstlAdr> </Cdtr> <CdtrAcct> <Id> <IBAN>PL67101011400149482222000000</IBAN> </Id> </CdtrAcct> <Purp> <!--Forcing of SWIFT for EUR --> <Prtry>FRGN</Prtry> </Purp> <RmtInf> <Ustrd> FA/111/2011 </Ustrd> </RmtInf> </CdtTrfTxInf> </PmtInf> <!-- transfer to USA with Fedwire--> <PmtInf> <PmtInfId>1</PmtInfId> <PmtMtd>TRF</PmtMtd> <ReqdExctnDt>2012-01-02</ReqdExctnDt> <Dbtr/> <DbtrAcct> <Id> <IBAN>PL38144011560000000000071013</IBAN> </Id> </DbtrAcct> <DbtrAgt> <FinInstnId/> </DbtrAgt> <CdtTrfTxInf> <PmtId> <EndToEndId>NOTPROVIDED</EndToEndId> </PmtId> <Amt> <InstdAmt Ccy="USD">1.00</InstdAmt> </Amt> <CdtrAgt>

Page 30: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

30

<FinInstnId> <ClrSysMmbId> <ClrSysId> <Cd>USABA</Cd> </ClrSysId> <MmbId>251480563</MmbId> </ClrSysMmbId> <Nm>1ST ADVANTAGE FCU</Nm> <PstlAdr> <Ctry>US</Ctry> <AdrLine>GLOUCESTER</AdrLine> <AdrLine>VA</AdrLine> </PstlAdr> </FinInstnId> </CdtrAgt> <Cdtr> <Nm>Creditor name</Nm> <PstlAdr> <AdrLine>Creditor address line 1</AdrLine> </PstlAdr> </Cdtr> <CdtrAcct> <Id> <Othr> <Id>1234567890</Id> </Othr> </Id> </CdtrAcct> <Purp> <!--Forcing of SWIFT for EUR--> <Cd>FRGN</Cd> </Purp> <RmtInf> <Ustrd> FA/111/2011 </Ustrd> </RmtInf> </CdtTrfTxInf> </PmtInf> </CstmrCdtTrfInitn>

</Document>

RfT/MT101 FX order

# Field name XML tag Height Description

1. Message ID CstmrCdtTrfInitn +GrpHdr ++MsgId

M 35x

Value ignored

2.

Message creation time

CstmrCdtTrfInitn +GrpHdr ++CreDtTm

M ISODateTime

Value ignored

3.

Number of transactions

CstmrCdtTrfInitn +GrpHdr ++NbOfTxs

M 15n

Number of transactions in message Field verified

4.

Sum-total of transaction

CstmrCdtTrfInitn +GrpHdr

O 18d

Sum-total of transaction amounts disregarding currency

Page 31: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

31

amounts ++CtrlSum Field verified if present

5.

Originator data

CstmrCdtTrfInitn +GrpHdr ++InitgPty

M Value ignored

6.

Payment ID CstmrCdtTrfInitn +PmtInf ++PmtInfId

M 35x

Value ignored

7.

Payment method

CstmrCdtTrfInitn +PmtInf ++PmtMtd

M 3!a

Field should have value TRF

8.

Order value date

CstmrCdtTrfInitn +PmtInf ++ReqdExctnDt

M ISODate

Converted into current date if past date.

9.

Originator data

CstmrCdtTrfInitn +PmtInf ++Dbtr

O Value ignored.

10.

Originator account number

CstmrCdtTrfInitn +PmtInf ++DbtrAcct +++Id ++++IBAN

C Originator account number in IBAN format

11. Originator account number

CstmrCdtTrfInitn +PmtInf ++DbtrAcct +++Id ++++Other +++++Id

C Originator account number in other format than IBAN

12.

Originator bank ID

CstmrCdtTrfInitn +PmtInf ++DbtrAgt +++FinInstnId ++++BICFI

M

Account-operating bank BIC

13.

References

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++PmtId ++++ EndToEndId

O 16x

References

14.

Transfer amount

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++Amt ++++InstdAmt

M 18d

Transfer amount in currency handled by bank, except for PLN for beneficiary in Polish bank. Point to be used as decimal separator.

15. Cost CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++ChrgBr

O SHAR – shared – default value DEBT – originator CRED – beneficiary (prohibited for PSD countries)

16.

Beneficiary bank BIC

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++ CdtrAgt ++++FinInstnId +++++BICFI

M

Beneficiary bank BIC. 4!a2!a2!c[3!c]

17.

Beneficiary data

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++Cdtr

M Beneficiary name, address and ID

18.

Beneficiary account number -

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf

C Beneficiary account number in IBAN format. Mandatory for PSD countries

Page 32: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

32

IBAN +++CdtrAcct ++++Id +++++IBAN

19. Beneficiary account number - Other

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++CdtrAcct ++++Id +++++Othr ++++++Id

C Beneficiary account number in other format than IBAN

20. Transfer type CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++InstrForCdtrAgt ++++InstrInf

O Order type in account operating bank. Permitted value from closed list dependent on account-operating bank BIC.

21.

Payment details

CstmrCdtTrfInitn +PmtInf ++CdtTrfTxInf +++RmtInf ++++Ustrd

M 140x

PmtTpInf nodes are present for every source account in CstmrCdtTrfInitn/PmtInf, or for every order in

CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf

Structure of Beneficiary data:

#. Field name XML tag Height Description

1. Name Nm M Name

2. Address PstlAdr +AdrLine

M 70x or 2x35x

Address. Maximum 2 instances of AdrLine

Example

<?xml version="1.0" encoding="UTF-8"?> <Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.07"> <CstmrCdtTrfInitn> <GrpHdr> <MsgId>xx</MsgId> <CreDtTm>2016-09-26T10:10:11</CreDtTm> <NbOfTxs>1</NbOfTxs> <CtrlSum>1.00</CtrlSum> <InitgPty/> </GrpHdr> <!-- RFT/MT101 1 from foreign account--> <PmtInf> <PmtInfId>1</PmtInfId> <PmtMtd>TRF</PmtMtd> <ReqdExctnDt>2012-01-02</ReqdExctnDt> <Dbtr/> <DbtrAcct> <Id> <IBAN>IT72O0560839920000000004187</IBAN> </Id> </DbtrAcct> <DbtrAgt> <FinInstnId> <BICFI>SANTITNN</BICFI>

Page 33: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

33

</FinInstnId> </DbtrAgt> <CdtTrfTxInf> <PmtId> <EndToEndId>References 16zn</EndToEndId> </PmtId> <Amt> <InstdAmt Ccy="EUR">1.00</InstdAmt> </Amt> <CdtrAgt> <FinInstnId> <BICFI>NBP##WXXX</BICFI> </FinInstnId> </CdtrAgt> <Cdtr> <Nm>Creditor name</Nm> <PstlAdr> <AdrLine>Creditor address line 1</AdrLine> </PstlAdr> </Cdtr> <CdtrAcct> <Id> <IBAN>PL67101011400149482222000000</IBAN> </Id> </CdtrAcct> <InstrForCdtrAgt> <InstrInf>INTC</InstrInf> </InstrForCdtrAgt> <RmtInf> <Ustrd> FA/111/2011 </Ustrd> <Ustrd>aaa</Ustrd> </RmtInf> </CdtTrfTxInf> </PmtInf> </CstmrCdtTrfInitn>

</Document>

Import of CDD Direct Debits (pain.008.001.02)

Direct Debit, also within the Czech Branch.

Notation used

Field format:

n = only numerals (0-9) allowed

a = only capitals (A-Z) allowed

x = any character

c = only capitals and numerals allowed

d = decimal number

! = fixed length

[ ] = optional value

ISODate = YYYY-MM-DD

ISODateTime = YYYY-MM-DDThh:mm:ss

Page 34: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

34

Field status:

M = Mandatory

O = Optional

C = Conditional

- = Prohibited

the XML file should be saved in the UTF-8 code

the XML file should begin in the following declaration:

<?xml version=”1.0” encoding=”UTF-8”?>

the xml document name space urn:iso:std:iso:20022:tech:xsd:pain.008.001.02

#. Field name XML tag Height Description

1 Message ID <CstmrDrctDbtInitn> + <GrpHdr> ++ <MsgId>

M 35x File ID / name

Message creation time

<CstmrDrctDbtInitn> + <GrpHdr> ++ <CreDtTm>

M ISODateTime

file creation date and time

2 Number of transactions

<CstmrDrctDbtInitn> + <GrpHdr> ++ <NbOfTxs>

M 15n

number of transactions (Direct Debits in file)

3 Sum-total of transaction amounts

<CstmrDrctDbtInitn> + <GrpHdr> ++ <CtrlSum>

O 18d

transaction amounts checksum disregarding currency. Field verified if present.

4 Originator data <CstmrDrctDbtInitn> + <GrpHdr> ++ <InitgPty> +++ <Nm>

M Originator data

5 Originator country

<CstmrDrctDbtInitn> + <GrpHdr> ++ <InitgPty> +++ <Nm> ++++ <PstlAdr> +++++ <Ctry>

M 2!a

Originator country (country code )

6 Originator address

<CstmrDrctDbtInitn> + <GrpHdr> ++ <InitgPty> +++ <Nm> ++++ <PstlAdr> +++++ <AdrLine>

M More than one line !!! originator address

7 Bundle ID <CstmrDrctDbtInitn> + <PmtInf> ++ <PmtInfId>

M 35x

„Bundle” identification (Bundle ID 1 Direct Debit in CZK with message for payer and all symbols)

8 Payment method <CstmrDrctDbtInitn> + <PmtInf> ++ <PmtMtd>

M 2!a

payment method indicates it is Direct Debit (DD), rather than transfer

9 Counting indicator

<CstmrDrctDbtInitn> + <PmtInf> ++ <BtchBookg>

M True – bundle processing mark (identifies input entry for sum-total of all transactions in message; it is mandatory.) False – if single transaction processing is used

10 Number of transactions

<CstmrDrctDbtInitn> + <PmtInf> ++ <NbOfTxs>

M15!n Number of transactions (Number of individual transactions included in message.)

11 Checksum <CstmrDrctDbtInitn> M18d Checksum (per bundle)

Page 35: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

35

+ <PmtInf> ++ <CtrlSum>

12 Payment date <CstmrDrctDbtInitn> + <PmtInf> ++ <ReqdColltnDt>

ISODate Payment date of Direct Debit required

13 Beneficiary name <CstmrDrctDbtInitn> + <PmtInf> ++ <Cdtr> +++ <Nm>

M 140x

Beneficiary name

14 Beneficiary country

<CstmrDrctDbtInitn> + <PmtInf> ++ <Cdtr> +++ <PstlAdr> ++++ <Ctry>

M 2!a

Beneficiary country (country code)

15 Originator address

<CstmrDrctDbtInitn> + <PmtInf> ++ <Cdtr> +++ <PstlAdr> ++++ <AdrLine>

70x More than one line !!! Originator address

16 Beneficiary account number

<CstmrDrctDbtInitn> + <PmtInf> ++ <CdtrAcct> +++ <Id> ++++ <IBAN>

M Beneficiary account number (if stated in IBAN format, bank code (sort code) in BIC / SWIFT format must be specified. Beneficiary bank code (sort code) cannot be stated in domestic format))

17 Beneficiary account currency

<CstmrDrctDbtInitn> + <PmtInf> ++ <CdtrAcct> +++ <Id> ++++ <Ccy>

M3!a Beneficiary account currency (ID of currency in which account is maintained, e.g. CZK.)

18 Beneficiary bank code

<CstmrDrctDbtInitn> + <PmtInf> ++ <CdtrAgt> +++ <FinInstnId> ++++ <BIC>

MC Beneficiary bank code (because Beneficiary account number is stated in IBAN format, Beneficiary bank code (sort code) must be stated in BIC/SWIFT format. (It cannot be specified in domestic bank code format))

Number of account for charges

<CstmrDrctDbtInitn> + <PmtInf> ++ <ChrgsAcct> +++ <Id> ++++ <IBAN>

O Number of account for charges (either in IBAN format or in local BBAN (i.e. Basic Bank Account Number) format; it is recommended to state account number in same format as beneficiary account number was stated)

19 Beneficiary unique code

<CstmrDrctDbtInitn> + <PmtInf> ++ <CdtrSchmeId> +++ <Id> ++++ <PrvtId> +++++ <Othr> ++++++ <Id>

O 35x Beneficiary ID code (Unique and unequivocal identification of person)

20 Direct Debit ID <CstmrDrctDbtInitn> + <PmtInf> ++ <DrctDbtTxInf> +++ <PmtId> ++++ <InstrId>

OC 35x Direct Debit ID (Unique identification by sender, unequivocally identifies group payment information in message)

21 Reference <CstmrDrctDbtInitn> + <PmtInf> ++ <DrctDbtTxInf> +++ <PmtId> ++++ <EndToEndId>

OC 35x Reference / ID (ID is passed on unaltered throughout end chain)

Page 36: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

36

22 Direct Debit amount

<CstmrDrctDbtInitn> + <PmtInf> ++ <DrctDbtTxInf> +++ <InstdAmt @Ccy=”CZK”>

M Part of Direct Debits (individual payment amount in currency)

23 <CstmrDrctDbtInitn> + <PmtInf> ++ <DrctDbtTxInf> +++ <DbtrAgt> ++++ <FinInstnId> +++++ <BIC>

MC Payer bank code (if stated in BIC/SWIFT code format, then payer account must be stated in IBAN format (payer account number cannot be stated in domestic BBAN (i.e. Basic Bank Account Number) format)

24 Payer data <CstmrDrctDbtInitn> + <PmtInf> ++ <DrctDbtTxInf> +++ <Dbtr> ++++ <Nm>

M 140x

Payer name

25 Payer country code

<CstmrDrctDbtInitn> + <PmtInf> ++ <DrctDbtTxInf> +++ <Dbtr> ++++ <PstlAdr> +++++ <Ctry>

M 2!a

Payer country (country code)

26 Payer account number

<CstmrDrctDbtInitn> + <PmtInf> ++ <DrctDbtTxInf> +++ <DbtrAcct> ++++ <Id> +++++ <IBAN>

MC Payer account number (because Payer account number is stated in BIC/SWIFT code format, account number must be specified in IBAN format, (It cannot be specified in domestic BBAN (i.e. Basic Bank Account Number) format)

27 Payment details. <CstmrDrctDbtInitn> + <PmtInf> ++ <DrctDbtTxInf> +++ <RmtInf> ++++ <Ustrd>

OC 140x

„Unstructured Remittance Information„

Additional information (unstructured).

Maximum one instance

Maximum length of 140 characters

If present, field „Structured Remittance Information” cannot be present

+++RmtInf

++++Ustrd

28 Variable symbol value

<CstmrDrctDbtInitn> + <PmtInf> ++ <DrctDbtTxInf> +++ <RmtInf> ++++ <Strd> +++++ <CdtrRefInf> ++++++ <Ref>

OC 35x Variable symbol (VS) value

29. Specific symbol value

<CstmrDrctDbtInitn> + <PmtInf> ++ <DrctDbtTxInf> +++ <RmtInf> ++++ <Strd> +++++ <CdtrRefInf> ++++++ <Ref>

OC 35x Specific symbol (SS) value

30 Fixed symbol value

<CstmrDrctDbtInitn> + <PmtInf> ++ <DrctDbtTxInf> +++ <RmtInf> ++++ <Strd> +++++ <CdtrRefInf> ++++++ <Ref>

OC 35x Fixed symbol (KS) value

Page 37: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

37

31 Direct Debit ID <CstmrDrctDbtInitn> + <PmtInf> ++ <DrctDbtTxInf> +++ <PmtId> ++++ <InstrId>

M35x Direct Debit ID

32 Reference <CstmrDrctDbtInitn> + <PmtInf> ++ <DrctDbtTxInf> +++ <PmtId> ++++ <EndToEndId>

O 35x Reference / ID (ID is passed on unaltered throughout end chain)

33 Direct Debit amount

<CstmrDrctDbtInitn> + <PmtInf> ++ <DrctDbtTxInf> +++ <InstdAmt @Ccy=”CZK”>

M 35x Direct Debit amount in stated currency.

34 Payer bank code <CstmrDrctDbtInitn> + <PmtInf> ++ <DrctDbtTxInf> +++ <DbtrAgt> ++++ <FinInstnId> +++++ <BIC>

MC Payer bank code (if stated in BIC/SWIFT code format, payer account number should be stated in in IBAN format (account number cannot be stated in domestic BBAN (i.e. Basic Bank Account Number) format)

35 Payer data <CstmrDrctDbtInitn> + <PmtInf> ++ <DrctDbtTxInf> +++ <Dbtr> ++++ <Nm>

M 140x

Payer name

36 Payer street <CstmrDrctDbtInitn> + <PmtInf> ++ <DrctDbtTxInf> +++ <Dbtr> ++++ <PstlAdr> +++++ <StrtNm>

OC 70x

Payer street

37 Payer building number

<CstmrDrctDbtInitn> + <PmtInf> ++ <DrctDbtTxInf> +++ <Dbtr> ++++ <PstlAdr> +++++ <BldgNb>

OC 16x

Payer building number

38 Payer post code <CstmrDrctDbtInitn> + <PmtInf> ++ <DrctDbtTxInf> +++ <Dbtr> ++++ <PstlAdr> +++++ <PstCd>

OC 16x

Payer post code

39 Payer town <CstmrDrctDbtInitn> + <PmtInf> ++ <DrctDbtTxInf> +++ <Dbtr> ++++ <PstlAdr> +++++ <TwnNm>

OC 35x

Payer town

40 Payer country code

<CstmrDrctDbtInitn> + <PmtInf> ++ <DrctDbtTxInf> +++ <Dbtr> ++++ <PstlAdr> +++++ <Ctry>

M 2!a Payer country code e.g. „CZ”

41 Originator account number

<CstmrDrctDbtInitn> + <PmtInf>

MC Originator account number (because originator bank code is stated in

Page 38: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

38

++ <DrctDbtTxInf> +++ <DbtrAcct> ++++ <Id> +++++ <IBAN>

BIC/SWIFT code format, account number must be stated in IBAN format, it cannot be stated in domestic BBAN (i.e. Basic Bank Account Number) format)

42 <CstmrDrctDbtInitn> + <PmtInf> ++ <DrctDbtTxInf> +++ <RmtInf> ++++ <Ustrd>

OC 140x

„Unstructured Remittance Information”

Additional information (unstructured).

Maximum one instance

Maximum length of 140 characters

If present, field „Structured Remittance Information” cannot be present

+++RmtInf

++++Ustrd

43 Variable symbol value

<CstmrDrctDbtInitn> + <PmtInf> ++ <DrctDbtTxInf> +++ <RmtInf> ++++ <Strd> +++++ <CdtrRefInf> ++++++ <Ref>

OC 35x

Variable symbol (VS) value

44 Specific symbol value

<CstmrDrctDbtInitn> + <PmtInf> ++ <DrctDbtTxInf> +++ <RmtInf> ++++ <Strd> +++++ <CdtrRefInf> ++++++ <Ref>

OC 35x

Specific symbol (SS) value

45 Fixed symbol value

<CstmrDrctDbtInitn> + <PmtInf> ++ <DrctDbtTxInf> +++ <RmtInf> ++++ <Strd> +++++ <CdtrRefInf> ++++++ <Ref>

OC 35x

Fixed symbol (KS) value

Example Import of CDD orders in XML pain.008.001.002 format

<?xml version="1.0" encoding="UTF-8"?>

<!-- description: Created with Liquid XML Studio Developer Edition 9.0.11.3078 (http://www.liquid-

technologies.com) -->

<Document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xmlns="urn:iso:std:iso:20022:tech:xsd:pain.008.001.02">

<CstmrDrctDbtInitn><GrpHdr><MsgId>9573D5R35</MsgId>

<!-- description: file ID / name -->

<CreDtTm>2015-09-23T16:48:30.29</CreDtTm>

<!-- description: file creation date and time-->

<NbOfTxs>2</NbOfTxs>

<!-- description: Number of transactions (Direct Debits in file)-->

<CtrlSum>1090.00</CtrlSum>

<!-- description: Checksum (per file)-->

<InitgPty><Nm>PKO BP CZ </Nm>

<!-- description: Originator name-->

<PstlAdr><Ctry>CZ</Ctry>

Page 39: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

39

<!-- description: Originator country-->

<AdrLine>JUNGMANNOVA 1</AdrLine>

<!-- description: Originator address -->

<AdrLine>PRAHA 1, 110 00</AdrLine>

<!-- description: Originator address -->

</PstlAdr></InitgPty></GrpHdr><PmtInf><PmtInfId>35330</PmtInfId>

<!-- description: “bundle” ID (Bundle ID 1 Direct Debit in CZK communicated to payer and all symbols)-->

<PmtMtd>DD</PmtMtd>

<!-- description: payment method determines it is CDD Direct Debit rather than transfer -->

<BtchBookg>true</BtchBookg>

bundle processing mark , „False” , if transactions processed one by one-->

<NbOfTxs>2</NbOfTxs>

<!-- description: Number of transactions-->

<CtrlSum>1090.00</CtrlSum>

<!-- description: Checksum without currency (per bundle)-->

<ReqdColltnDt>2017-01-29</ReqdColltnDt>

<!—description: Direct Debit payment date required -->

<Cdtr><Nm>PKO BP CZ</Nm>

<!-- description: Beneficiary name-->

<PstlAdr><Ctry>CZ</Ctry>

<!-- description: Beneficiary country-->

<AdrLine>JUNGMANNOVA 1</AdrLine>

<!-- description: Beneficiary address-->

<AdrLine>PRAHA 1, 110 00</AdrLine>

<!-- description: Beneficiary address-->

</PstlAdr></Cdtr><CdtrAcct><Id><IBAN>CZ9530600000000200000435</IBAN>

<!-- description: Beneficiary account number (if stated in IBAN format, bank code (sort code) must be stated

in BIC / SWIFT format. Beneficiary bank code (sort code) cannot be stated in domestic format))-->

<!--<Othr>-->

<!--<Id>35</Id>-->

<!--</Othr>-->

</Id><Ccy>CZK</Ccy>

<!-- description: Beneficiary account currency-->

</CdtrAcct><CdtrAgt><FinInstnId><BIC>BPKOCZPP</BIC>

<!-- description: Beneficiary bank code entered (because Beneficiary account number is stated in IBAN

format, Beneficiary bank code (sort code) must be stated in BIC/SWIFT format. (It cannot be stated in

domestic bank code format))-->

<!--<Othr>-->

<!--<Id>3060</Id> -->

<!-- description: fixed PKO BP bank branch code for beneficiary – originator account-->

<!--</Othr>-->

</FinInstnId></CdtrAgt><ChrgsAcct><Id><IBAN>CZ9530600000000200000435</IBAN>

<!-- description: Number of account for charges (either in IBAN format or in local BBAN (i.e. Basic Bank

Account Number) format, it is required to state account number in format in which Beneficiary account

number was stated)-->

</Id></ChrgsAcct><CdtrSchmeId><Id><PrvtId><Othr><Id>CZ28ZZZ10036</Id>

<!-- description: Beneficiary ID code-->

</Othr></PrvtId></Id></CdtrSchmeId><DrctDbtTxInf><PmtId><InstrId>97539</InstrId>

<!-- description: Direct Debit ID-->

<EndToEndId>38R240</EndToEndId>

<!-- description: Reference / ID-->

Page 40: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

40

</PmtId><InstdAmt Ccy="CZK">1000.00</InstdAmt>

<!-- description: part of Direct Debit-->

<DbtrAgt><FinInstnId><BIC>BPKOCZPP</BIC>

<!-- description: Payer bank code (if stated in BIC/SWIFT code format, then payer account number must be

stated in IBAN format (payer account number cannot be stated in domestic BBAN (i.e. Basic Bank Account

Number) format)-->

</FinInstnId></DbtrAgt><Dbtr><Nm>PAVEL KARTA</Nm>

<!-- description: Payer surname and name / trading name-->

<PstlAdr><Ctry>CZ</Ctry>

<!-- description: kraj płatnika-->

</PstlAdr></Dbtr><DbtrAcct><Id><IBAN>CZ2530600000000200000822</IBAN>

<!-- description: payer account number (because Payer bank code stated in BIC/SWIFT code format, account

number must be stated in IBAN format, it cannot be stated in domestic BBAN (i.e. Basic Bank Account

Number) format)-->

</Id></DbtrAcct><RmtInf><Ustrd>INKASO ZA MOBILNI SLUZBY</Ustrd>

<!-- description: Direct Debit for GSM operator services, message for payer-->

<Strd><CdtrRefInf><Ref>VS:42040777</Ref>

<!-- description: Variable symbol value-->

</CdtrRefInf></Strd><Strd><CdtrRefInf><Ref>SS:3507</Ref>

<!-- description: Specific symbol value-->

</CdtrRefInf></Strd><Strd><CdtrRefInf><Ref>KS:0308</Ref>

<!-- description: Fixed symbol value-->

</CdtrRefInf></Strd></RmtInf></DrctDbtTxInf><DrctDbtTxInf><PmtId><InstrId>97540</InstrId>

<!-- description: Direct Debit ID-->

<EndToEndId>38R241</EndToEndId>

<!-- description: Reference / ID-->

</PmtId><InstdAmt Ccy="CZK">90.00</InstdAmt>

<!-- description: Direct Debit amount-->

<DbtrAgt><FinInstnId><BIC>BPKOCZPP</BIC>

<!-- description: Payer bank code (if stated in BIC/SWIFT code format, payer account number should be

stated in IBAN format (account number cannot be stated in domestic BBAN (i.e. Basic Bank Account Number)

format)-->

<!--<Othr>-->

<!--<Id>3060</Id>-->

<!-- description: Payer bank code (because payer account number stated in domestic BBAN (i.e. Basic Bank

Account Number) format, Payer bank code must be stated in domestic bank account format (it cannot be

stated in BIC / SWIFT code format))-->

<!--</Othr>-->

</FinInstnId></DbtrAgt><Dbtr><Nm>PETR BALIK</Nm>

<!-- description: Payer name-->

<PstlAdr><StrtNm>ZKUSEBNIi</StrtNm>

<!-- description: Payer street-->

<BldgNb>12</BldgNb>

<!-- description: Payer building number-->

<PstCd>11000</PstCd>

<!-- description: Payer post code-->

<TwnNm>PRAHA 1</TwnNm>

<!-- description: Payer town-->

<Ctry>CZ</Ctry></PstlAdr></Dbtr><DbtrAcct><Id><IBAN>CZ7630600000000200000777</IBAN>

Page 41: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

41

<!-- description: Originator account number (because originator bank code stated in BIC/SWIFT code format,

account number must be stated in IBAN format, it cannot be stated in domestic BBAN (i.e. Basic Bank

Account Number) format)-->

<!--<Othr>-->

<!--<Id>3060</Id>-->

<!-- description: Originator account number (if account number stated in domestic BBAN (i.e. Basic Bank

Account Number) format, Originator bank code must be stated in domestic format (Originator bank code

cannot be stated in BIC/SWIFT code format ))-->

<!--</Othr> -->

</Id></DbtrAcct><RmtInf><Ustrd>INKASO ZA MOBILNI SLUZBY</Ustrd>

<!-- description: Direct Debit for GSM operator services, message for originator-->

<Strd><CdtrRefInf><Ref>VS:42040347</Ref>

<!-- description: Variable symbol value-->

</CdtrRefInf></Strd><Strd><CdtrRefInf><Ref>SS:35057</Ref>

<!-- description: Specific symbol value-->

</CdtrRefInf></Strd><Strd><CdtrRefInf><Ref>KS:0308</Ref>

<!-- description: Fixed symbol value-->

</CdtrRefInf></Strd></RmtInf></DrctDbtTxInf></PmtInf></CstmrDrctDbtInitn></Document>

MT103 /MT101(RFT) Imports Import of orders in MT103 / MT101 format is possible for the following types: 1. Domestic transfers in PLN and intra-bank transfers 2. FX transfers 3. MT101 Requests for Transfers, SWIFT only he MT103 format is recognised by the brace “{“ or colon “:” as the first character. Comment 1

File size limit to 50 Mb or to 50 000 orders

Header blocks are ignored

A new record where the field number is lower than the preceding one Comment 2 The file to be imported must satisfy the following criteria:

The line break symbol (<CR><LF>(HEX 0D 0A)) is the field separator.

The first line in the file must begin in “:” or “{“.

The file does not have a header or footer. It is comprised of blocks of orders. The required file code page is Windows 1250

Which fields are mandatory depends on the order type.

Which characters are permitted depends on the order type.

The type of the imported order will be determined on the basis of line 4 of field 72: or, if blank, on the basis of the review of the contents of other completed fields according to a special formula. In both cases, after the type is recognised, the order will be reviewed for completeness and correctness of the content according to the recognised type. Conspicuous specification of the type is important so as not to distort the Importer’s intention concerning the type of order.

Field ID numbers must be defined in an ascending order within an order. Where an ID number is followed by a lower ID number, it means that the definition of a new order has commenced.

If the type is not conspicuously specified, the procedure is as follows: conditions a. to f. are checked one by one. If the first is satisfied, the related type is set: a) The originator account and the beneficiary account are with PKO Bank Polski (NRB with the branch

number commencing in 1020 or 1440), and Domestic/Intra-bank transfer - PRZ/WEW

Page 42: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

42

b) The originator account with PKO Bank Polski and the beneficiary account in the NRB or IBAN format with the PL country code, the currency code being PLN:

domestic transfer - PRZ/KRA c) The originator account with PKO Bank Polski and the beneficiary account in the NRB or IBAN format

with the PL country code, the currency being other than PLN, and domestic FX transfer – PZA/PKW d) The originator account with another bank (information stored in the system) and MT101 Request for

Transfer - RfT e) Beneficiary bank code :57A: beginning in NDEA, and international transfer / PKO Payment - PZA/NP. f) Orders not matching the earlier criteria are recognised as international transfers – type PZA/ZAG.

Overall structure of the transfer import file

Field code/Tag

Field name Status Data Format Comments

:20: Sender's Reference

O 16x Customer order reference. Only used in MT101

:23E: Instruction Code O 4!c[/30x] Permitted values depend on account-operating bank. Only used in MT101

:32A: M 6!n3!a15d Field consists of three components

Value Date M 6!n Transfer execution date in yymmdd format. Date converted to current if past.

Currency M 3!a Transfer currency ISO code limited to currencies supported by PKO Bank Polski

Interbank Settled Amount

M 15d Transfer amount. Comma as decimal separator

:52D: Originator account Line 1

M 26!n/34x Originator account

Commission account Line 2

O 26!n Account for charging commission. Only for international transfers

Line 3

O 3!a15x or blank At least empty line required. Content ignored

Line 4 O 15x2!a<space> 2!a 15 characters ignored, Counterparty country ISO code space Counterparty bank country ISO code If none, counterparty bank country code determined on basis of IBAN or BIC/SWIFT code

Bank clearing number

O 34x Country-specific bank clearing number e.g. FW123456789 or SC123456

:57A: Beneficiary bank BIC/SWIFT code

M or option :57D:

11c Beneficiary bank BIC/SWIFT code. Must be specified or option :57D: Not applicable to domestic transfers.

:57D: Beneficiary bank name and address Line 1-4

O 4*35x Beneficiary name in first two lines, followed by two lines of beneficiary address: If 57A: stated, field :57A: is binding

:59: Beneficiary account Line 1

M /34x Beneficiary account number after „/” without BIC code

Counterparty name and address Line 2-5

M 4*35x Counterparty name in first two lines, followed by two lines of counterparty address. At least one line each of name and address mandatory

Page 43: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

43

:70:

Payment details Line 1-4

M 4x35 Payment title. At least one line. Tax transfer to conform with Elixir/MultiCash format

:71A: Foreign bank costs

M 3!c Permitted values: BN1 or SHA – Cost shared – Originator bank’s cost to be covered by originator, Beneficiary bank’s cost to be covered by beneficiary OUR – all costs to be covered by originator BN2 or BEN – all costs to be covered by beneficiary Not applicable to domestic transfers.

:72: Additional information Line 1-2

O First two lines ignored

Line 3 O for RfT and ZAG orders

5!x Order priority – permitted values: /STD/ - Standard – default value /URG/ - Urgent(+1) executed next day /EXP/ - Urgent(+0) executed on order date

Line 4 O 7x Order type. Permitted values „PRZ/WEW”, „PRZ/KRA”, „ZUS”,„POD”, “RfT” “PZA/ZAG”, “PZA/NP” ,“PZA/NIP”

Following the import, if there is an erroneous order, an error message will be displayed next to the import summary, specifying the line number where the erroneous order begins and the error identification message.

Example

:32A:000000CHF20,00

:52D: CZ9530600000000200000436

35116022020000000087654321

FR FR

:57A:AGRIFRPP833

:59:/FR9213306000140111122223333

first beneficiary name line FR,

second beneficiary name line

rue de Paris,

11-222 France

:70:Transfter title line_1

Transfer title line_22222222222END

:71A:BN1

:72:

/EXP/

:32A:091112EUR10,00

:52D: CZ9530600000000200000436

23144022020000000087654321

EE EE

:57A:NDEAEE2XAXXX

Page 44: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

44

:59:/EE92141011560000000000071013

first beneficiary name line,

second beneficiary name line

beneficiary address (e.g. street),

beneficiary address (e.g. post code and town)

:70:Transfer title line_1

Transfer title line_22222222222END

Transfer title line_33333333333END

Transfer title line_44444444444END

:71A:BN1

:72:

/EXP/

ELIXIR Format General comments:

One file may contain orders of different types.

Code page – 1250.

The file header is optional.

Each payment is presented in a separate line.

All the fields are mandatory.

Individual payments (lines) must be separated with the line break sign <CR><LF> (Hex 0D 0A).

The fields within a record are separated with a comma (,) .

Inverted commas (“) serve as a text qualifier.

Fields are divided into subfields with the vertical bar “|”.

A PKO WebConnect report on the imported transfers specifies the amount of the FX transfers expressed in the account currency.

Example of one line from the transfer import file: (For the sake of clarity, each field is presented in a separate line while in actual fact all the lines are presented as shown in the example below).

Example of subfield Comments

410, or 110, or 411, - number 410 means that the transfer in the line is an international transfers, numbers (110 and 411)

1

20170323, - payment date in YYYYMMDD format – current or future

100000, - transfer amount (multiplied by 100 – in this example the actual amount is 1000 e.g. CZK)

, blank field– space

0, - unused field – value always 0

" CZ9530600000000200000436 ", or "200000400/3060",

- originator account number in IBAN format with prefix (CZ) or optionally in short form

2

e.g." CZ9530600000000200000436" (IBAN account with ISO country prefix) or „DE37643500700000705555” (foreign account),

- beneficiary account number in IBAN format, or optionally, for intra-bank formats, it may be in short form

3

"OwnNameP1|OwnNameP2|OwnAddressP3|OwnAddressP4",

- originator’s (customer’s) own name and address 4

"BeneficiaryNameP1|BeneficiaryNameP2|BeneficiaryAddressP3|BeneficiaryAddressP4",

- beneficiary’s name and address 5

Page 45: PKO Webconnect Context CZ - Data Import Formats. March 2017 · 3 Order Import Format Types in CZ Context ABO Format Description and Structure It is a local format for the import of

45

0, - unused field – value always 0

0, - technical field for international payments – value always 0

6

"PaymentTitleP1|P2|P3|P4”, - payment details / title 7

"", - unused field - always blank

"", - unused field - always blank

"51", - technical field – value always 51

REF:|WAL:CZK|CZ/ALBPP#WXXX|BeneficiaryBankDataP4|BeneficiaryBankDataP5|BeneficiaryBankDataP6"

- detailed description of payment below 8

Examples Example 1: 410,20170324,10000,30600000,0,"CZ9530600000000200000436","DE37643500700000705555","OwnNameP1|OwnNameP2|OwnAddressP3|OwnAddressP4","BeneficiaryNameP1|BeneficiaryNameP2|BeneficiaryAddressP3|BeneficiaryAddressP4",0,0,"PaymentTitleP1|P2|P3|P4","","","51","REF:|WAL:CZK|CZ/ALBPP#WXXX|BeneficiaryBankDataP4|BeneficiaryBankDataP5|BeneficiaryBankDataP6" Example 2: 411,20170320,11155,30600000,0,"CZ7330600000000200000446","PL10102055610000370203387778"," OwnNameP1|OwnNameP2|OwnAddressP3|OwnAddressP4","BeneficiaryNameP1|BeneficiaryNameP2|BeneficiaryAddressP3|BeneficiaryAddressP4",0,0,"PaymentTitleP1|P2|P3|P4","","","51","REF:|WAL:CZK|CZ/KOMBCZPPXXX|BeneficiaryBankDataP4|BeneficiaryBankDataP5|BeneficiaryBankDataP6" Example 3: 110,20170327,63500,30600000,0,"200000400/3060","PL37249000050000400023316151","OwnNameP1|OwnNameP2|OwnAddressP3|OwnAddressP4","BeneficiaryNameP1|BeneficiaryNameP2|BeneficiaryAddressP3|BeneficiaryAddressP4",0,0,"PaymentTitleP1|P2|P3|P4","","","51","REF:|WAL:CZK|CZ/ALBPP#WXXX|BeneficiaryBankDataP4|BeneficiaryBankDataP5|BeneficiaryBankDataP6” 1 Number 410 means that the line in question will be imported as an international transfer. For domestic transfers, use number 110 (standard outbound domestic transfer, for intra-bank transfers, originator’s own account and beneficiary account may be stated in short form) or 411 (intra-bank transfer, i.e. between a customer’s own accounts with PKO BP, executed in the source account currency and to the Bank on the territory of Czechia) – domestic and international transfers can be imported in one file. To differentiate domestic transfers from international ones, check the transfer currency and the beneficiary bank. International transfers are to be interpreted as all foreign currency transfers (regardless of the location of the beneficiary bank) and CZK-denominated transfers to a foreign bank. 2 This account number is an example in the IBAN format or, optionally, in the short format for intra-bank transfers. 3 As regards the beneficiary account, the IBAN format, or – with intra-bank transfers – the short format may be used. 4 The fields is comprised of 4 subfields (P1,2,3,4), each of maximum 35 characters in length. Each of the fields is separated with the „|” (Hex 7C) symbol. Please, note that the field may be left blank unless you intend to change your name or address. Then the order will be populated with data ascribed by default to the originator’s account. If your name and address do not require four subfields, you can leave them blank. 5 This field is also comprised of 4 subfields (P1,2,3,4), each of maximum 35 characters in length, separated with the “|” symbol (Hex 7C). Depending on the length of the beneficiary name and address, some of the subfields may be left blank. Please, note that the first two subfields are related to the name and the two last ones to the address of the beneficiary and both these pieces of information are required. This means you have to fill in at least the first field of beneficiary name and the first field of beneficiary address. Thus the first and the third subfields must always be filled (the second and the fourth may be left blank). 6 For an international transfer, this field always assumes the value of 0. 7 This field also comprises 4 subfields (P1,2,3,4), each of maximum 35 characters in length, separated with the “|” symbol (Hex 7C). 8 This fields comprises 6 subfields, subfields (P1,2,3,) each of maximum 35 characters in length, separated with the “|” symbol (Hex 7C): The first subfield contains an additional payment reference – field length max. 10 characters. The AddRef subfield need not be filled. The second subfield contains the currency code of WAL<three-letter currency code>, e.g. WAL:USD. The third subfield contains the beneficiary country code and, following the mandatory “/S” parameter, the beneficiary bank SWIFT

code. The SWIFT code is made up of 8 or 11 characters.

Subfields four, five and six contain the beneficiary bank name and address.