Import & Export BiznesPl@net

Import & Export BiznesPl@net Bank BGŻ BNP Paribas Spółka Akcyjna with its seat in Warsaw at Kasprzaka 10/16, 01-211 Warsaw, registered in the Register of Entrepreneurs of the National Court Register by the District Court for the capital city of Warsaw in Warsaw, XII Business Division of the National Court Register under the number KRS 0000011571, with tax identification number (NIP): 526-10-08-546 and share capital of PLN 84,238,318 fully paid up

1. Defining/odifying Import Template New Template Defining Import template Company: Template type: Domestic Transfer After selecting the New Import template function, a form is displayed enabling to define/modify an import template. Import template definition consists in the following: Specifying the company type (in the case of a Holding), Specifying a template type only after selecting a template, further portion of the format (on change) will be displayed, Specifying a template name obligatory field, Choosing a separator character, Choosing a code page (code pages available are the following: Windows1250, ISO88592, CP 852, ANSI without Polish characters, UTF8) Specifying the choice and sequence of fields from a defined list specific to given dictionary (import template type) Choosing a date format from a defined list; formats available are the following: yy-mm-dd, ddmm-yy, mm-dd-yy, yyyymmdd. Taking into account the Text fields in quotation marks option.

Option to choose date separator any character Option to choose a decimal separator dot or comma. When defining a new Import template, you will see two lists displayed next to each other. The list on the left contains field names available for a given template type. The list on the right contains field names that have been added to the template; their sequence on the list is the same as the sequence in the file line. Fields available for a given template type are similar to the field specification in the Transfers module for: Domestic transfers, Cross-border transfers, Tax transfers, ZUS Transfers, Direct debit, T101 Transfers, Domestic contractors (beneficiaries) defined in the Dictionaries, Foreign contractors (beneficiaries) defined in the Dictionaries, Debtors in direct debit as defined in the Dictionaries. Default fields displayed on the list on the right are required in the import template for a given dictionary. Users cannot remove any required fields from the list on the right. If a Domestic Transfer Import template is defined, the list on the right of the format shows the following default fields: Amount (incl. currency), Contractor s short name, Contractor s account number, Principal s account number and Payment title. The list on the left of the format features the remaining fields (optional) according to the specification of fields in the Domestic transfer format. If a Foreign Transfer Import template is defined, the list on the right shows the following default fields: Contractor s name, Contractor s country, Amount (incl. currency), Contractor's account number, SWIFT code, Name and country of the Contractor s bank, Principal s account number, Payment details, cost sharing manner. The list on the left of the format features the remaining fields according to the specification of fields in the Cross-border transfer format. If a ZUS Transfer Import template is defined, the list on the right shows the following default fields: Principal s account number, ZUS account number, Payer s short name, Payer s NIP (tax identification number), Payer s second ID, Type of credit payment. The list on the left of the format features remaining fields according to the specification of fields in the ZUS transfer format. If a Tax Transfer Import template is defined, the list on the right shows the following default fields: Principal s account number, Amount, Tax authority s account number, Taxpayer s name, Complementary ID type, complementary ID, Form or payment s symbol, Commitment period type, Commitment identification The list on the left of the format features the remaining fields according to the specification of fields in the Tax transfer format. If a Direct Debit Import template is defined, the list on the right shows the following default fields: Amount, Debtor s short name, Debtor s account number, Creditor s account number, Creditor s NIP (tax identification number), Payment ID.

The list on the left of the format features the remaining fields according to the specification of fields in the Direct Debit format. If a T101 Transfer Import template is defined, the list on the right shows the following default fields: Contractor s name, Contractor s country, Amount (incl. currency), Contractor's account number, SWIFT code, Name and country of the Contractor s bank, Principal s account number, Payment details, cost sharing manner. The list on the left of the format features the remaining fields according to the specification of fields in the T101 transfer format. If a Domestic Contractor Import template is defined, the list on the right of the format shows the following default fields: Contractor s short name, Contractor s account number. The list on the left of the format features the remaining fields according to the specification of fields in the Domestic Contractor details format. If a Foreign Contractor Import template is defined, the list on the right of the format shows the following default fields: Short name, Full name of the Contractor, Contractor s country, name and country of the Contractor s bank, Contractor bank s SWIFT/BIC, Contractor s account number. The list on the left of the format features the remaining fields according to the specification of fields in the Foreign Contractor details format. If an Import template for Direct Debit Debtors is defined, the list on the right shows the following default fields: Short name, account number of the Debtor. The list on the left of the format features the remaining fields according to the specification of fields in the Direct Debit Debtor details format. When you click on the Save button, the template is recorded in the database. This action is available only when a template is defined by the user. If templates are predefined globally (e.g. ulticash PLI or PLA), there is no option to modify or remove such templates. 2. Defining/odifying Export Templates Defining an Export template Company: Template type: Account history Defining/Edi ting the template Account History

Export template definition/modification includes the following: Establishing the type of data to be exported, Specifying the template name, Choosing a separator character, Choosing a code page (code pages available are the following: Windows1250, ISO88592, CP 852, ANSI without Polish characters, UTF8) Specifying the choice and sequence of fields from a defined list specific to given dictionary (export template type) left and right screen. By default the screen on the right is empty. Choosing a date format from a defined list; formats available are the following: yy-mm-dd, dd-mm-yy, mm-dd-yy, yyyymmdd. Taking into account the Text fields in quotation marks option. Taking into account the Text fields in header option. Option to choose date separator any character Option to choose a decimal separator : dot or comma. When defining a new Export template, you will see two lists displayed next to each other. The list on the left contains field names available for a given template type. The list on the right contains field names that have been added to the template; their sequence on the list is the same as the sequence in the file line. Fields listed on the left of the format, available for a given template type, are similar to the field specification for specific formats where the export command is available: Account history/statement/t940 global template predefined, Card account statement, List of card transactions, Review of executed transfers, Review of rejected transfers, BR/T940 Statement global template predefined by the Bank, Credit account history/t940 global template predefined by the Bank, Domestic contractors, Foreign contractors, Debtors in Direct Debit T940 global template predefined by the Bank 3. Predefined import template: ulticash PLI General information on domestic payment file The Payment instruction file format complies with the standard applicable in the Polish clearing system Elixir developed by KIR SA.

Requirements Payment instruction file contains no header. One payment instruction file may contain data pertaining to a number of payment instructions. Every line is a separate transfer instruction. <CR> <LF> is the mark for a new line to separate specific lines/instructions. Text fields are always placed in quotation marks ( ). A comma (,) is the separator for specific fields inside the instruction. Fields containing several lines (e.g. payment details) have a pipe sign " " (Hex 7C) as a separator of lines. The code page for Polish characters is: CP852. All data should be written in capital letters. File format for ordinary domestic orders Format description Field andatory Length (L)/Type ()/Optional (O) (T) Field description 1 3n F The code indicates operation type (110) 2 D Payment date 3 15n V Amount to be paid, e.g. 410050 for 4,100.50 4 8n F Clearing number of the principal s bank 5 1n F Unused; value 0 6 26n F Principal s account number in NRB (Bank Account Number) format 7 26n F Contractor s account number - NRB (Bank Account Number) format 8 4*35a V Principal s name and address (lines separated by pipe sign (Hex 7C) 9 4*35a V Contractor s name and address (lines separated by the pipe sign (Hex 7C) 10 1n F Unused; value 0 11 8n F Clearing number of the contractor s bank 12 4*35 a V Payment details (lines separated by the pipe sign (Hex 7C) 13 empty empty 14 empty empty

15 2n F Instruction classification (51) 16 O 6*35a V Client reference number [16a] (lines may be separated by the pipe sign (Hex 7C), e.g. request for confirmation of order execution. System read firt chain characters only. Char : will be replace to char (space) 17 <CR><LF> End-of-line mark. Sample content of a file containing 3 ordinary orders 110,20040129,410050,16001114,0,"13160011140004070963852001","4316001055000 2321858585001","PHU KOWALSKI PLK. STANISLAWA DABKA 56/2 00000 WARSZAWA","BIURO PODROZY HALLERA 1234 81000 WARSZAWA",0,16001303,"PRZEDPLATA FV 2004/0012 ","","","51","REFERENCE1" 110,20040129,5200000,16001114,0,"13160011140004070963852001","431600105500 02321858585001","PHU KOWALSKI PLK. STANISLAWA DABKA 56/2 00000 WARSZAWA","ABC KWIATOWA 487/98 02000",0,16001169,"ZAPLATA ZA FAKTURE 154/04 ","","","51","REFERENCE2" 110,20040129,650000,16001114,0,"13160011140004070963852001","4316001055000 2321858585001","PHU KOWALSKI PLK. STANISLAWA DABKA 56/2 00000 WARSZAWA","ZAKLAD TRANSPORTOWY BIESZCZADZKA 12 / 4321 00000 SWIETOCH",0,16001055,"FV 4578 USLUGI TRANSPORTOWE ","","","51" Format of a file containing transfer orders in favour of tax authorities Differences between a transfer instruction in favour of a tax authority and an ordinary transfer instruction: Instruction classification in respect of payment in favour of tax authorities (field 15): 71 Payment in favour of tax authorities requires specific formatting of data contained in the payment details field (field 12) Format of the payment details field in transfer instructions in favour of tax authorities

ethod 1: Code word Name of the segment /TI/ ID type and features /OKR/ Period for which the tax payment is made /SFP/ Payment form symbol /TXT/ nature of the commitment, commitment identification andatory status Format Type: 1a F Features: 14a V Year: 2n F Period type: 1a F Period number: 2n F (if the period type is R, period number is not to be specified) Definition of the segment Type: N NIP, R Regon, P Pesel, 1 ID series and number, 2 Passport series and number. Features: ax 14 characters, e.g.: /TI/N84425767 89 Year: e.g. 03 for 2003. Period type: R year, K quarter, month, D decade. Period number: e.g. 05 ay; example: /OKR/0312 for Dec 2003 6a V List of form symbols is presented in item 2.4 hereof. Example: /SFP/PIT37 O 21a V Any text max. 21 characters. Example: /TXT/PIT37XII 2003 Example of a fully completed field: "/TI/N8442576789/OKR/03R/SFP/PIT37 /TXT/PIT37XII2003 ". NOTE: If an encoded segment does not fit in one line, the next line (containing further part of the same segment) shall start with the // characters: "/TI/N8442576789/OKR/0312/SFP/PIT3 //7/TXT/PIT37XII2003 " Example of file contents: 110,20040129,9600000,16001114,0,"13160011140004070963852001","9010101140 01 43682221000000","PHU KOWALSKI PLK. STANISLAWA DABKA 5 00000 WARSZAWA","URZAD SKARBOWY W SOPOCIE ",0,10101140,"/TI/ N8442576789/OKR/03R/SFP/PIT37 /TXT/PIT37XII2003 ","","","71"

ethod 2: It consists in entering personal data in the lines with no need to use code words. Line number Name 1 ID type and features 2 Period for which the tax payment is made 3 Payment form symbol andatory Format status Type: 1a F. Features: 14a V Year: 2n F. Period type: 1a F. Period number: 2n F (if the period type is R, period number is not to be specified) Line description Type: N NIP, R Regon, P Pesel, 1 ID series and number, 2 Passport series and number. Features: ax 14 characters, e.g.: N8442576789 Year: e.g. 03 for 2003. Period type: R year, K quarter, month, D decade. Period number: e.g. 05 ay; example: 0312 for Dec 2003 6a V List of form symbols is presented in item 2.4 hereof. Example: PIT37 4 Nature of the commitment, commitment identification O 21a V Any text max. 21 characters. Example: PIT37XII2003 Example of a fully completed field: "N8442576789 0312 PIT37 PIT37XII2003" Example of file contents: 110,20040129,5800000,16001114,0,"13160011140004070963852001","9010 10114001 43682221000000","PHU KOWALSKI PLK. STANISLAWA DABKA 5 00000 WARSZAWA","URZAD SKARBOWY W SOPOCIE ",0,10101140,"N8442576789 0312 PIT37 PIT37XII2003","","","7 1"

4. Predefined import template: ulticash PLA General information on foreign currency payment file The format of a file for foreign currency payment orders (PLA) is based on the SWIFT T100 standard Requirements A payment instruction file should have the following extension:.pla Payment instruction file starts with a header. One payment instruction file may contain data pertaining to a number of payment instructions. A segment containing payment instruction data shall start with the ("{") character and finish with the ("}") character. The instruction segment header is placed in the first section of such a segment. Designations included in format descriptions Requirement /O - andatory/o - Optional Field length e.g. 34 max 34 characters Format (L/T) Field type: n only digits 0-9 a alphanumeric d - date F fixed length Example /O Format (L/T) eaning 26n F Required, always 26 digits O 4*35a V File header Field description /O Format :01:Reference 16 a V :02: Total of the payment 17 n V instruction amounts comprised in the payment instruction file (regardless of the currency) :03:Number of instructions in the file 5 n V :04:ID of the principal s bank O 11 a V

:05:Name and address of the principal. Data may be entered in several lines. Each line must be separated by the end-of-line character <CR><LF> 4*35 a V :07:File name 12 a V Payment instruction segment header {1:F01 Fixed nnnnnnnnxxxx ID of the principal s bank (completed to 12 characters with the x bbbb characters bbbb Subsequent payment instruction file number (generated automatically from the range: 0001 to 9999) tttttt} Subsequent payment instruction number in the payment instruction file (generated automatically from the range: 0001 to 999999) {2:I100 Fixed xxxxxxxxxaaaa ID (SWIFT) of the contractor s bank y payment type N 00 standard transfer U 10 payment via telex or SWIFT A 20 bill of exchange, ordinary transfer B 21 bill of exchange, registered transfer C 22 bill of exchange, express transfer D 23 bill of exchange, registered express transfer E 30 bill of exchange drawn on the principal F 31 bill of exchange drawn on the principal, registered transfer G 32 bill of exchange drawn on the principal, express transfer 1} Fixed Subsequent payment instructions are separated by the character $. Subsequent fields in a payment instructions are separated by the character <. Segment containing instruction details Description /O Format :20: Principal s reference 16 a V :32A: 6 n F Sub-field 1: Instruction value date (YYDD) Sub-field 2: Currency code Sub-field 3: Amount displayed with two decimal places 3 a F 15 n V

:50: Principal s name and address (lines with max. 35 characters each separated by the character <CR><LF>) 4*35 a V :52D: Sub-field 1: Principal s account <CR><LF> Sub-field 2: Account for charges <CR><LF> Sub-field 3: Counter currency code Sub-field 4: Statistical code <Empty> (ASCII 32) Contractor s country code <Empty> (ASCII 32) Country code of the contractor s bank max. 34 n V max. 34 n V 3 a F 14 n V 2 a F 2 a F :57A: SWIFT code of the contractor s bank or Identifier of the contractor s bank :57D: Name and address of the contractor's bank (if no SWIFT address has been specified) :59: Sub-field 1: Character "/" Sub-field 2: Contractor s account number Sub-field 3: <CR><LF> Contractor s name and address (max. 4 lines of 35 characters each. Specific lines are separated by <CR><LF>) :70: Payment details (max. 4 lines of 35 characters each. Specific lines are separated by <CR><LF>) :71A: Cost settlement BN1: 0 Fees charged by the principal s bank are payable by the principal, other costs are charged to the payment beneficiary BN2: 1 all costs are charged by contractor 2 OUR: 3 all costs are charged to the principal O 11 a V 4*35 a V 1 a F 34 a V 4*35 a V 4*35 a V 3 a F

:72: Sub-field 1: Indications (max. four codes) (doubledigit codes separated by a space (ASCII 32)) 01 Payment only for the contractor 02 Payment by cheque only 6* 35 separated by the character <CR><LF> 4*2 n F O 35 a V 4*35 a V 04 Payment only upon identification 06 Advice for the contractor s bank via phone 07 Advice for the contractor s bank via facsimile 09 Advice for the contractor via phone 10 Advice for the contractor via facsimile Sub-field 2: Contact person Sub-field 3 to Sub-field 6: Additional information to field :52D: (max four lines separated by the character <CR> <LF>) Sample content of a file containing 2 orders :01:REF0223100836001 :02:31500,00 :03:2 :04: :05:PHU KOWALSKI PłK. STANISłAWA DĄBKA 5 00-000 WARSZAWA :07:04022301.PLA {1:F0116001114XXXX0001000001}{2:I100GEBAESBARXN1}{4: :20: :32A:040223EUR25000,00 :50:PHU KOWALSKI PťK. STANISťAWA D BKA 5 00-000 WARSZAWA :52D:13160011140004070963852001 13160011140004070963852001 PLN100000,00 B00 ES ES :57A:GEBAESBAR :57D:FORTIS BANK, S.A., SUCURSAL EN ESPA NA PASEO DE GRACIA 85 BARCELONA :59:/528745-898541-555-000-144 LCF CTLN.

PASSEIG. DE LA BARCELONETA 1234 BARCELONA :70:INV. 2004/528 :71A:OUR :72:00 00 00 00 USLUGI TRANSPORTU USLUGI TRANSPORTU -}${1:F0116001114XXXX0001000002}{2:I100GEBAESXXXXN1}{4: :20: :32A:040223EUR6500,00 :50:PHU KOWALSKI PťK. STANISťAWA D BKA 5 00-000 WARSZAWA :52D:13160011140004070963852001 13160011140004070963852001 PLN26000,00 B00 ES ES :57A:GEBAES :57D:FORTIS BANK, S.A., SUCURSAL EN ESPA ADRID :59:/5845784874512584698 GERARD Y GARCIA SA P. DE LA CASTELLANA 8795 ADRID 70:INV 128421/04 :71A:OUR :72:00 00 00 00 USLUGI TRANSPORTU -} 5. Export daily statement (T940) T940 message containing an aggregate daily statement from FBP includes designation STARTSU in field :20. Daily statement structure Designations included in the descriptions of formats Column: aximum length in bytes v = Field variable length f = Field fixed length Column: Format an = alphanumeric Letters A to Z, digits 0 to 9, no special characters n = numeric Only digits from 0 to 9, no special characters

Column: Required/Optional o = Optional field m = Required field YY = Year number without century number = DD = onth with leading zeros Day with leading zeros T940 message general outline Field name Values entered in the field :20: essage start :25: Account holder s number (IBAN) :28C: ulticash statement number :60F: Initial balance and date :61: Transaction line :86: Transaction details :62F Final balance and date Detailed order of information in the transaction line (:61:) Field name Value date Posting date Debit DR/Credit CR sign Total Posting code Customer s reference // Bank reference Values entered in the field exactly 6 characters, numeric; Date in the YYDD format exactly 4 characters, numeric; 1-2 characters C = Credit; RC = Reversal credit; D = Debit; RD = Reversal debit and third letter ISO code e.g. CN when ISO code is PLN; CD - when ISO code is USD 1-15 numeric characters; Total in decimal format exactly 4 alphanumeric characters; S + 3 digits 1-16 alphanumeric characters. RNR customer ID. If not present, NONREF is entered ID of payment posted on the Bank s side

Detailed order of information in the transaction details line (:86:) Field code: aximum length Format /O Name NOTES 3 f n m Bank s transaction code 00 27 v a o Posting description 2027 8*27 v an o payment details 30 12 v an o 31 24 v an o Contractor s bank number Contractor s account number 32-33 54 v an o Contractor s name and address 2 x 27 characters. 38 34 f n o Contractor s account number - NRB (Bank Account Number) format 60-63 108v an o Contractor s account number - NRB (Bank Account Number) format Example of T 940 statement contents :20:1 :25:/PL68160011270003012206715001 :28C:160/2009/BPL :60F:D090903PLN000002623569,48 :61:0909030903CN000000004988,01N723NONREF//CENT123123123 For accounts in NRB format, checksum and contractor s bank account are provided, i.e. ccaaaaaaaa 16 digits of the account number, i.e. bbbbbbbbbbbbbbbb Full bank account number (NRB) for CC 3.0 Full bank account number (NRB) for CC 2.12 :86:723^00PRZELEW OTRZ ELIXIR ^34000 ^3010600076 ^20faktura 1360/07/2009/RL 404/^2107/2009/ D ^32TRANSPORT REGIONALNY^33T PIOTR GORA UL. OGRODOWA ^3882106000760000326000742451 ^62A 18 55-106 KRAKOW :61:0908030803CN000000001130,83N721NONREF//CENT123123124

:86:721^00PRZELEW OTRZYANY ^34000 ^3016001169 ^201319/07/2009/RTL ^32Forters Sp ka z o.o. ul. G^33runwaldzka 48 Krakow ^3838160011690003013153742001 :61:0908030803CN000000010866,80N632ABC9999999//CENT123123125 :86:632^00POLEC ZAPťATY UZNANI ^34000 ^30 ^31 ^20/NIP/5213110552/IDP/037635/^21TXT/ KOSOWSKA 1393/07/200 ^229/RTL ^32PRESTIGE - AGDALENA KOSOWSKA 60 :61:0909040903CN000000152500,00N723REF1221312312//CENT123123126 :86:723^00PRZELEW OTRZ ELIXIR ^34000 ^3095841021 ^20Zapˆata za f-r Proforma nr^21 332/09/ 2009 z dn.31.07.20 ^2209r. albumy historyczne ^32TRANSPORT REGIONALNY^33ALFRED ZIELONY LUBLIN 2 ^3849958410212003030054250001 ^62A 55-095 LUBLIN :61:0908040803CN000000032500,00N723REFERENCE1//CENT123123127 :86:723^00PRZELEW OTRZ ELIXIR ^34000 ^3011401065 ^20AtQSZ -P^21bASCeNa CA20/11779/09 ^32SOPOCKIE TOWARZYSTWO UBEZPI^33ECZEN. ERGO HESTIA S.A. UL. ^3819114010650000227556432117 ^62HESTII 1 81-731 SOPOT :61:0908030803CN000000668198,05N761NONREF//CENT123123129 :86:761^00ZLECENIE SALDO ^34000 ^30 ^31 ^20zlecenie saldo 3011/3012 AI^21P ^32 :62F:D090803PLN000001753385,79