Implementation guide
Local payments in Poland
The Elixir format
Version 1.2.1
Publishing date 23 January 2018
Implementation guide
The Elixir format - Local payments Page 2 (12) Version 1.2.1 Publishing date 23 January 2018
Table of contents
1 INTRODUCTION ...................................................................................................................................... 3
1.1 History .............................................................................................................................................................. 3
2 INFORMATION ABOUT THE SERVICE ................................................................................................. 4
2.1 Restrictions to the service ................................................................................................................................ 4 2.2 Parties .............................................................................................................................................................. 4 2.3 Agreement ........................................................................................................................................................ 4
3 SCENARIO: LOCAL PAYMENT ............................................................................................................. 5
4 FORMAT OVERVIEW .............................................................................................................................. 6
4.1 Business rules .................................................................................................................................................. 6 4.2 Format structure ............................................................................................................................................... 6 4.3 Payment types ................................................................................................................................................. 6
4.3.1 NORMAL PAYMENT ..................................................................................................................................................... 6 4.3.2 TAX PAYMENT/CUSTOMS DUTY ................................................................................................................................ 6 4.3.3 SORBNET ON REQUEST ............................................................................................................................................. 6
5 IMPLEMENTATION GUIDELINE ............................................................................................................ 7
5.1 Data format rules .............................................................................................................................................. 7 5.1.1 DESCRIPTION OF THE FIELD STATUS ...................................................................................................................... 7 5.1.2 DESCRIPTION OF THE FORMAT ................................................................................................................................ 7
5.2 Content ............................................................................................................................................................. 7 5.3 Field description ............................................................................................................................................... 8
5.3.1 DETAILS OF PAYMENT (FIELD PLI_12) FOR TAX PAYMENT/CUSTOMS DUTY ....................................................... 9 5.4 Business example .......................................................................................................................................... 10
5.4.1 BUSINESS EXAMPLE: NORMAL PAYMENT .............................................................................................................. 10 5.4.2 BUSINESS EXAMPLE: TAX PAYMENT/CUSTOMS DUTY ......................................................................................... 10 5.4.3 BUSINESS EXAMPLE: SORBNET ON REQUEST ..................................................................................................... 11
5.5 File example ................................................................................................................................................... 12 5.5.1 FILE EXAMPLE: NORMAL PAYMENT ........................................................................................................................ 12 5.5.2 FILE EXAMPLE: TAX PAYMENT/CUSTOMS DUTY ................................................................................................... 12 5.5.3 FILE EXAMPLE: SORBNET ON REQUEST ................................................................................................................ 12
Implementation guide
The Elixir format - Local payments Page 3 (12) Version 1.2.1 Publishing date 23 January 2018
1 Introduction
Handelsbanken’s implementation guide for the Polish Elixir format for local payments describes in detail
the information to be included and how it is to be specified when initiating a local payment from an account
held at Handelsbanken Poland.
The description is specific to Handelsbanken’s services and routines and may be used only when
communicating with Handelsbanken.
1.1 History
At Handelsbanken, changes to version numbers are made according to the following guidelines. The
original version is 1.0.0. Older versions without a version number are designated with a date.
The last digit is changed when the format descriptions are changed, for example text clarifications
and examples.
The second digit is changed if minor changes are made to the format such as new countries or
changes in the payment type.
The first digit is changed (thus becoming a completely new version) if the format changes mean
that the customer will have to make adaptations in order to continue using the service. In this case,
all customers affected are informed of the new version and what the changes involve.
Version Date Description
1.2.1 2018-01-23 ZUS payment type is no longer available
1.0.1 2016-12-12 Updated - minor clarifications
1.0.0 published 2009-01-15
Implementation guide
The Elixir format - Local payments Page 4 (12) Version 1.2.1 Publishing date 23 January 2018
2 Information about the service
This guide contains a description for local payments. When communicating with an Elixir message a
customer is able to request a local payment from an account held at Handelsbanken Poland to an account
held at a Polish bank. Customers are able to request normal payments, tax payments/customs duty and
Sorbnet on request payments.
2.1 Restrictions to the service
In communications with Handelsbanken it is not possible to request Direct Debit and Special payment.
2.2 Parties
Name of party Description
Customer Customer or its software provider
Bank Handelsbanken
2.3 Agreement
A customer has to be connected to Handelsbanken’s Electronic Banking service GlobalOn-Line and must
have the authority to send files to the bank. Please see separate agreement/Power of Attorney for further
details.
Furthermore, a test file must be submitted by the customer. When the test file has been approved by the
bank the customer can send files to the bank containing payment orders to be executed.
For further information, please contact your local branch.
Implementation guide
The Elixir format - Local payments Page 5 (12) Version 1.2.1 Publishing date 23 January 2018
3 Scenario: Local payment
Description: This scenario illustrates the process when a customer requests a local payment from an account
held at Handelsbanken Poland through Handelsbanken’s Electronic Banking service GlobalOn-Line.
1) The Customer uploads the file with payment orders via GlobalOn-Line
2) The Bank receives the payment file and validates the file format and the content of the file.
3) The Bank accepts or rejects the file and the payment orders. A payment status report can be sent with
information about rejected payment orders, if applicable.
4) The file is authorised by the authorised user/(s) according to the mandate
5) The Bank debits the account/(s) and executes the payment orders on the execution date
6) The status of the payment (for example Rejected, Pending, Processed) is always shown under Search
payment in GlobalOn-Line.
Local payment
BankBank
CustomerCustomer
Local payment
Customer
compiles
information for the
payment
Bank receives
the payment
Bank executes the
payment
Bank accepts or
rejects the
payment
Customer sends
the payment to the
bank
Information about
rejected and pending
payments are
presented via
GlobalOn-Line
Implementation guide
The Elixir format - Local payments Page 6 (12) Version 1.2.1 Publishing date 23 January 2018
4 Format overview
This section contains a business oriented description of the Elixir local Payment format that is approved for
communication with Handelsbanken.
Exceptions at field level for the Handelsbanken implementation of the Elixir local Payment Format are
explicitly specified in the “Comment” column in chapter 5. In communication with Handelsbanken, please
pay attention to the following rules:
4.1 Business rules
[1] For payments with due dates on a Saturday, Sunday or other banking holidays, the payment day
will be moved to the closest following banking day.
[2] The payment date can be stated for a maximum of 12 months ahead.
[3] The payment date can be exceeded by a maximum of 20 days. In that case the payment will be
executed the following banking day. If the payment date is exceeded by more than 20 days the
payment will be rejected.
[4] Only payments in PLN are allowed.
4.2 Format structure
The Elixir local payment format consists of one record with information necessary to create a local payment
in Poland.
4.3 Payment types
Accepted payment types are Normal payments, Tax payments/Customs duty and Sorbnet on request.
4.3.1 NORMAL PAYMENT
In order to request a normal payment a message to the beneficiary is mandatory. See business example
4.3.2 TAX PAYMENT/CUSTOMS DUTY
You can pay two types of taxes, government tax and department tax, and customs duty.
The beneficiary account number is the number of the tax office/customs authority. It is mandatory to have a
reference to the beneficiary, see business example
4.3.3 SORBNET ON REQUEST
It is possible to create a Sorbnet payment with an amount below 1 000 000 PLN. Sorbnet payments are
processed on-line and have therefore an extra cost.
All payments above 1 000 000 PLN are executed as Sorbnet payments even though they are prepared as
normal payments. These payments are sent in a separate file to the National Bank of Poland which sends
them for execution to the beneficiary bank.
Implementation guide
The Elixir format - Local payments Page 7 (12) Version 1.2.1 Publishing date 23 January 2018
5 Implementation guideline
In this chapter technical rules and guidelines for the Handelsbanken application is stated.
5.1 Data format rules
One file may contain multiple transactions of one type.
[1] Each payment begins with code:
110 = Normal local payment, Sorbnet on request payment and Tax payment
[2] Records are separated by end-of-line: <CR><LF> (ASCII 13 + 10).
[3] Field separator is comma (,) (Hex 2C)
[4] Text fields are between inverted commas (““) (Hex 22).
[5] The line separator in field is pipe (|) (Hex 7C).
[6] If the last field is empty, it can be omitted.
5.1.1 DESCRIPTION OF THE FIELD STATUS
M – Mandatory
O – Optional (the inverted commas must be present)
A - Accepted but not acted upon
If fields are marked with “Accepted but not acted upon” values in these fields will be ignored by
Handelsbanken. Please note that some fields are mandatory in the Handelsbanken application but optional
in the original format description.
5.1.2 DESCRIPTION OF THE FORMAT
n – Numerical 0-9,
a – Alphanumerical; in inverted commas (Hex 22); subfield separated by pipe (Hex 7C)
d – Date YYMMDD
F – Fixed length
V – Variable length
5.2 Content
This section contains the format description with the exceptions and additions required by Handelsbanken
to ensure proper processing of the payments.
Implementation guide
The Elixir format - Local payments Page 8 (12) Version 1.2.1 Publishing date 23 January 2018
5.3 Field description
The Elixir payment record contains one record with necessary information to request a local payment from
an account held at Handelsbanken Poland.
Field No.
Field description Field status
Format Comment
PLI_1 Code of payment:
110
M 3 n F
PLI_2 Date of payment:
YYYYMMDD
M 8 d F
PLI_3 Amount without any separators (no commas, spaces) The two last digits are decimals.
M 15 n V
PLI_4 Sort code of the ordering party:
22500001
M 8 n F Svenska Handelsbanken AB S.A. Oddzial w Polsce
PLI_5 Unused – value 0 M 1 n F
PLI_6 Account number of the ordering party
26 digits without any separators.
M 34 a V The value is also permitted to be in IBAN format: 2 alphanumeric letters + 26 digits.
PLI_7 Beneficiary’s account number
26 digits without any separators.
M 34 a V The value is also permitted to be in IBAN format: 2 alphanumeric letters + 26 digits.
PLI_8 Name and address of the ordering party
Subfield separator pipe “|” (Hex 7C)
M 35 a V
PLI_9 Beneficiary’s name and address. M 4*35 a V Subfield 1 is mandatory. Subfield 2-4 are optional.
PLI_10 Unused – value 0 M/A 1 n F Accepted but not acted upon.
PLI_11 Beneficiary’s bank sort code M 8 n F
PLI_12 Details of payment
M 4*35 a V For Normal & Sorbnet on request payments subfield 1 is mandatory and subfields 2-4 optional. For Tax payment/Custom Duty the field has structure as described below under Details of payment field PLI 12.
PLI_13 Empty field M 2 a F
PLI_14 Empty field M 2 a F
PLI_15 Transaction code:
“51” for Normal payments and Sorbnet on request payments
“71” for Tax payments/Customs duty payments
M 2 a F
PLI_16 Client – Bank information
Subfield separator pipe “|” (Hex 7C)
M/A 6*35 a Accepted but not acted upon
End of transaction M <CR> LF>
Implementation guide
The Elixir format - Local payments Page 9 (12) Version 1.2.1 Publishing date 23 January 2018
5.3.1 DETAILS OF PAYMENT (FIELD PLI_12) FOR TAX PAYMENT/CUSTOMS DUTY
Subfield No. 12
Field flag Field status
Format Exception
1 /TI/ (=introducing characters)
Type of identification:
N - NIP (10 digits)
P – PESEL (11 digits)
R – REGON (9 or 14 digits)
1 – ID Card Number(max. 14 characters)
2 – Passport number (max. 14 characters)
3 – Other document (max.14 characters)
After Type of identification, Payer’s identification (max 14 characters)
M 4 a + 1 a F + 9-14 n or a V
2 /OKR/ (=introducing characters) Period of the payment YYXWWWW:
YY – year,
X – type of period (R – year, P – semi annual, K – quarter, M – month, D – decade, J – day)
WWWW – number depend on type of period (R – empty, P – two digits 01 or 02, K – two digits 01, 02, 03 or 04, M – two digits 01-12, D – four digits (01-03, 01-12), J – four digits (01-31, 01-12)
M 5 a + 7 a V
3 /SFP/ Form code/Payment (np. PIT-37) M 7 a V
4 /TXT/ (=introducing characters) Free text
Payment ID, max 40 characters.
O 5 a + 40 a V
Implementation guide
The Elixir format - Local payments Page 10 (12) Version 1.2.1 Publishing date 23 January 2018
5.4 Business example
In this section, business examples of Elixir payments are presented. The examples illustrate payment types
that are approved in communication with Handelsbanken expressed from a functional point of view.
Corresponding file examples are presented below.
5.4.1 BUSINESS EXAMPLE: NORMAL PAYMENT
This is an example of a normal payment
Field name Value Comments
Code of payment (PLI_1) 110 Code for normal and tax payment
Date of payment (PLI_2) 20171030
Amount (PLI_3) 500 The two last digits in this field are decimals. 500 = 5,00 PLN
Payer’s bank sort code (PLI_4) 22500001 225 – Handelsbanken, 00001 – branch number
Payer’s account number (PLI_6) PL30225000010000009000021251 Accepted accounts: IBAN, BBAN (NRB).
Beneficiary’s account number (PLI_7)
PL50102055581111100804700027 Accepted accounts: IBAN, BBAN (NRB).
Beneficiary’s name and address (PLI_9) Subfield 1
TULIPAN POLSKA SP. Z O.O.
Beneficiary’s name and address (PLI_9) Subfield 2
Beneficiary’s name and address (PLI_9) Subfield 3
02-616WARSZAWA
Beneficiary’s name and address (PLI_9) Subfield 4
Beneficiary’s bank sort code (PLI_11)
10205558
Details of payment (PLI_12) Subfield 1
FAKTURA NR 50/09/TL/03
Transaction code (PLI_15) 51
5.4.2 BUSINESS EXAMPLE: TAX PAYMENT/CUSTOMS DUTY
This is an example of a Tax payment/Customs duty. The beneficiary account number is the number of the
tax office/customs authority. It is mandatory to have a reference to the beneficiary and it must be stated in
the field “details of payment”.
Field name Value Comments
Code of payment (PLI_1) 110 Code for normal and tax payment
Date of payment (PLI_2) 20171030
Amount (PLI_3) 1023 The two last digits in this field are decimals. 1023 = 10,23 PLN
Payer’s bank sort code (PLI_4)
22500001
Payer’s account number (PLI_6)
PL30225000010000009000021251 Accepted accounts: IBAN, BBAN (NRB).
Beneficiary’s account number (PLI_7)
17101010100000392221000000 Accepted accounts: IBAN, BBAN (NRB).
Beneficiary’s name and address (PLI_9) Subfield 1
URZAD SKARBOWY
Implementation guide
The Elixir format - Local payments Page 11 (12) Version 1.2.1 Publishing date 23 January 2018
Field name Value Comments
Beneficiary’s name and address (PLI_9) Subfield 2
WARSZAWA TARGÓWEK
Beneficiary’s/ name and address (PLI_9) Subfield 3
DĄBROWSZCZAKÓW 14
Beneficiary’s name and address (PLI_9) Subfield 4
03-000 WARSZAWA
Beneficiary’s bank sort code (PLI_11)
10101010
Details of payment (PLI_12) Subfield 1
/TI/N8567349219/OKR/05R/SFP/CIT/TXT|/Payment ID |LAW IN POLAND
Transaction code (PLI-15) 71
5.4.3 BUSINESS EXAMPLE: SORBNET ON REQUEST
If the amount is 1 million PLN or more the payment will automatically be treated as a Sorbnet payment. It’s
also possible to create a Sorbnet on request by using the the Sorbnet on request function at the GlobalOn-
Line web site.
Field name Value Comments
Code of payment (PLI_1) 110 Code for normal and tax payment
Date of payment (PLI_2) 20170621
Amount (PLI_3) 200000000 The two last digits in this field are decimals. 200000000 = 2000000,00 PLN
Payer’s bank sort code (PLI_4) 22500001
Payer’s account number (PLI_6) 69225000010000000000000000 Accepted accounts: IBAN, BBAN (NRB).
Beneficiary’s account number (PLI_7)
71106000760000409940091107 Accepted accounts: IBAN, BBAN (NRB).
Beneficiary’s name and address (PLI_9) Subfield 1
TULIPAN POLSKA SP. Z O.O.
Beneficiary’s name and address (PLI_9) Subfield 2
GOSZCZYŃSKIEGO 12
Beneficiary’s name and address (PLI_9) Subfield 3
02-616WARSZAWA
Beneficiary’s bank sort code (PLI_11)
10600076
Details of payment (PLI_12) Subfield 1
FAKTURA NR 50/09/TL/03
Transaction code (PLI_15) 51
Implementation guide
The Elixir format - Local payments Page 12 (12) Version 1.2.1 Publishing date 23 January 2018
5.5 File example
This file examples corresponds to the business examples presented above.
5.5.1 FILE EXAMPLE: NORMAL PAYMENT
110,20171030,500,22500001,0,"PL30225000010000009000021251
","PL501020555811 11100804700027","BRATEK SP. Z O.O.||PSZCZELARSKA 3A|02-
793WARSZAWA","TULIPAN POLSKA SP. Z O.O.||GOSZCZYŃSKIEGO 12|02-616
WARSZAWA",0,10205558,"FAKTURA NR 50/09/TL/03","","","51"
5.5.2 FILE EXAMPLE: TAX PAYMENT/CUSTOMS DUTY
110,20171030,1023,22500001,0,"PL30225000010000009000021251
","17101010100000392221000000","BRATEK SP. Z O.O.||PSZCZELARSKA 3A|02-793
WARSZAWA","URZAD SKARBOWY|WARSZAWA TARGÓWEK|DĄBROWSZCZAKÓW 14|03-000
WARSZAWA",0,10101010,"/TI/R8567349219/OKR/05R/SFP/CIT/TXT/PAYMENT ID|LAW
IN POLAND","","","71"
5.5.3 FILE EXAMPLE: SORBNET ON REQUEST
110,20170621,200000000,22500001,0,"69225000010000000000000000","711060007
60000409940091107","BRATEK SP. Z O.O.||PSZCZELARSKA 3A|02-
793WARSZAWA","TULIPAN POLSKA SP. Z O.O.||GOSZCZYŃSKIEGO 12|02-616
WARSZAWA",0,10600076,"FAKTURA NR 50/09/TL/03","","","51"