Alza has opened up a new logistics centre Zdiby
Due to the constant growth as the number one player on the Internet market in Czech Republic and Slovakia, Alza will be opening another logistics centre on 2 July 2018....
On this page, you will find information, relating to electronic document interchange with Alza.cz a.s. The transfer of documents takes place in structured data format via electronic data interchange – the so-called EDI communication. Automation of document processing with the help of EDI is key to Alza and is one of the necessary conditions for functional cooperation.
Hearing about EDI communication for the first time?
Here you will find more details about what EDI communication is.
Due to the constant growth as the number one player on the Internet market in Czech Republic and Slovakia, Alza will be opening another logistics centre on 2 July 2018....
Alza.cz a.s. introduces throughout 05/2018 new checks of content of the documents that they send and receive through EDI. The goal of these new checks...
Alza.cz, a.s. has announced a change of the company's registered seat. The change took effect on 14th May 2018. The new seat is now at Jankovcova 1522/53,...
These errors can be found in COMDIS message that Alza.cz sends in case of discrepancies. COMDIS messages can be found in Orion among other messages under the menu Communication > Incoming messages. To display only COMDIS messages, you can use a field Type in the basic filter.
In messages INVOIC 380, 381 and 83 we always expect in the field for GLN of invoicing place a value corresponding to the country of delivery.
The reason for this is the fact that we have a full VAT registration in every country where we allow goods to be received in logistics centres or warehouses and we require the relevant invoicing information – VAT Reg. No. to be provided in tax documents for deliveries in these countries. We have separate GLN for each of these VAT Reg. Nos.
You can always find the correct value for the corresponding GLN of place of delivery in an updated table of GLN in the column “Related GLN”.
You may resend the corrected EDI message.
...
NAD+IV+8594177951002::9++ Alza.cz a.s.+ Jankovcova 1522/53+ Praha 7 – Holešovice++ 17000+CZ' … for example, for a delivery to Slovakia enter a Slovak billing place
...
The field specified for writing is:
HDRNAD2 – GLN of the billing place in segment <party> with IV qualifier
Viz
<party>
<party_qualifier>IV</party_qualifier>
<party_id>8594177951002</party_id>
…
</party>
These are data in the fields:
HDR29 – GLN of the billing place
These are data in the fields:
NAD3 – GLN of the billing place in NAD line with IV qualifier
Viz
NADIV 8594177951002
These are data in the fields:
HDR29 – GLN of the billing place
In messages INVOIC 380, 381, 83 we expect from Czech VAT payer invoicing in foreign currency to provide exchange rate for recalculation into CZK, with which the value added tax in Czech currency has been calculated in the document according to the Act on VAT.
If you have received a negative COMDIS with this error, add the missing information into the original message and resend it.
...
CUX+2:EUR:4:1+3:CZK:10E+25.442' … conversion rate
DTM+134:20180417:102' … date of the currency conversion rate
…
These are data in the fields:
HDR14 – Date of the currency conversion rate
HDR16 – Currency conversion rate to local currency
Viz
…
<currency_target_code>CZK</currency_target_code>
<currency_exchange_rate>25.442</currency_exchange_rate>
<currency_rate_value>1</currency_rate_value>
<currency_exchange_date>2018-04-17</currency_exchange_date>
…
These are data in the fields:
HDR41 – Date of the currency conversion rate
HDR42 – Currency conversion rate to local currency
These are data in the fields:
HDR54 – Date of the currency conversion rate
HDR55 – Currency conversion rate to local currency
This format does not include domestic invoices in foreign currency. Agree with your EDI solution provider in another format variant.
In messages INVOIC 380, 381, 83 we expect from payers from other EU countries, invoicing in other than local currency that during invoicing in this currency, they will provide exchange rate against their local currency in which also the recapitulation of VAT is provided in the document.
If you have received a negative COMDIS with this error, add the missing information into the original message and resend it.
...
CUX+2:EUR:4:1+3:CZK:10E+25.442' … conversion rate
DTM+134:20180417:102' … date of the currency conversion rate
…
These are data in the fields:
HDR14 – Date of the currency conversion rate
HDR16 – Currency conversion rate to local currency
Viz
…
<currency_target_code>CZK</currency_target_code>
<currency_exchange_rate>25.442</currency_exchange_rate>
<currency_rate_value>1</currency_rate_value>
<currency_exchange_date>2018-04-17</currency_exchange_date>
…
These are data in the fields:
HDR41 – Date of the currency conversion rate
HDR42 – Currency conversion rate to local currency
These are data in the fields:
HDR54 – Date of the currency conversion rate
HDR55 – Currency conversion rate to local currency
This format does not include domestic invoices in foreign currency. Agree with your EDI solution provider in another format variant.
In messages INVOIC 380, 381, 83 kindly check the VAT recapitulation in invoicing currency so that the sum of entries of each VAT rate is provided in the appropriate field for the corresponding tax base, including the field Tax base of tax group 0 (exempt) in the cases when it concerns deliveries in the mode Exempt.
With reverse charge entries, you can either proceed in a simplified way (VAT rate in this mode is stated in documents as “0”) and the sum of these entries is stated in Base of tax group 0, or in a common way (for reverse charge entries you specify the applicable tax rate) and then it is necessary to use the correct fields for tax base “reverse charge” in the recapitulation.
The total price excluding VAT then expresses the sum of individual tax bases.
If you have received a negative COMDIS with this error, correct the setup and the data in the original message and resend it.
...
LIN+1++8591234567890:SRV'
…
MOA+203:1200'
…
TAX+7+VAT+++:::15'
LIN+2++8591234567899:SRV'
…
MOA+203:105000'
…
TAX+7+VAT+++:::21+AE'
LIN+3++8591234567888:SRV'
…
MOA+203:100'
…
TAX+7+VAT+++:::21'
UNS+S'
CNT+2:3'
MOA+86:106501'
MOA+79:106300'
MOA+125:106300' … total VAT base (total price excluding VAT)
MOA+176:201' … VAT total
MOA+9:106501'
TAX+7+VAT+++0:::0'
MOA+125:0' … base at the rate 0 %
MOA+124:0'
TAX+7+VAT+++1:::15'
MOA+125:1200' … base at the rate 15 %
MOA+124:180' … VAT at the rate 15 %
TAX+7+VAT+++1.2:::10'
MOA+125:0' … base at the rate 10 %
MOA+124:0'
TAX+7+VAT+++2:::21'
MOA+125:100' … base at the rate 21 %
MOA+124:21' … VAT at the rate 21 %
TAX+7+VAT+++2AE:::21+AE'
MOA+125:105000' … base at the rate 21 % using reverse charge
…
These are data in the fields:
SUM5 – Total price excluding VAT
SUM25 – Tax Group
SUM26 – The basis of the tax group
SUM27 – Tax Group Rate
SUM28 – VAT of the Tax Group
SUM29 – Reverse charge
SUM30 – VAT in converted (local) currency
SUM31 – Total VAT
See:
…
<summary>
…
<price_invoiced>106501.00</price_invoiced>
<items_price>106300.00</items_price>
<taxable_amount>106300.00</taxable_amount>
…
<tax_details>
<vat>
<vat_group>1</vat_group>
<vat_basis>1200</vat_basis>
<vat_rate>15.00</vat_rate>
<vat_total>180</vat_total>
<reverse_charge>N</reverse_charge>
<local_currency>N</local_currency>
</vat>
<vat>
<vat_group>2</vat_group>
<vat_basis>100</vat_basis>
<vat_rate>21</vat_rate>
<vat_total>21</vat_total>
<reverse_charge>N</reverse_charge>
<local_currency>N</local_currency>
</vat>
<vat>
<vat_group>2</vat_group>
<vat_basis>105000</vat_basis>
<vat_rate>21.00</vat_rate>
<vat_total>0.00</vat_total>
<reverse_charge>A</reverse_charge>
<local_currency>N</local_currency>
</vat>
<vat_total>201.00</vat_total>
…
</tax_details>
</summary>
…
These are data in the fields:
SUM2 – Basis of tax group 0 (exempt)
SUM3 – Basis of tax group 1 (reduced rate)
SUM4 – Basis of tax group 2 (base rate)
SUM37 – Basis of tax group 1.2 (secondary reduced rate)
SUM44 – Basis of Tax Group 1 (Reduced Rate) – Reverse Charge Mode
SUM45 – Basis of tax group 1.2 (secondary reduced rate) – Reverse Charge Mode
SUM46 – Basis of tax group 2 (base rate) – Reverse Charge Mode
SUM5 – Total price excluding VAT
It must be fulfilled: SUM5 = SUM2+SUM3+SUM4+SUM37+SUM44+SUM45+SUM46
SUM8 – VAT of tax group 1 (reduced rate)
SUM9 – VAT of tax group 2 (base rate)
SUM39 – VAT of tax group 1.2 (secondary reduced rate)
SUM10 – VAT total
It must be fulfilled: SUM10 = SUM8+SUM9+SUM39
These are data in the fields:
SUM2 – Basis of tax group 0 (exempt)
SUM3 – Basis of tax group 1 (reduced rate)
SUM4 – Basis of tax group 2 (base rate)
SUM26 – Basis of tax group 1.2 (secondary reduced rate)
SUM31 – Basis of Tax Group 1 (Reduced Rate) – Reverse Charge Mode
SUM32 – Basis of tax group 1.2 (secondary reduced rate) – Reverse Charge Mode
SUM33 – Basis of tax group 2 (base rate) – Reverse Charge Mode
SUM5 – Total price excluding VAT
It must be fulfilled: SUM5 = SUM2+SUM3+SUM4+SUM26+SUM31+SUM32+SUM33
SUM8 – VAT of tax group 1 (reduced rate)
SUM9 – VAT of tax group 2 (base rate)
SUM28 – VAT of tax group 1.2 (secondary reduced rate)
SUM15 – VAT total
It must be fulfilled: SUM15 = SUM8+SUM9+SUM28
These are data in the fields:
SUM2 – Basis of tax group 0 (exempt)
SUM3 – Basis of tax group 1 (reduced rate)
SUM4 – Basis of tax group 2 (base rate)
SUM37 – Basis of tax group 1.2 (secondary reduced rate)
SUM44 – Basis of Tax Group 1 (Reduced Rate) – Reverse Charge Mode
SUM45 – Basis of tax group 1.2 (secondary reduced rate) – Reverse Charge Mode
SUM46 – Basis of tax group 2 (base rate) – Reverse Charge Mode
SUM5 – Total price excluding VAT
It must be fulfilled: SUM5 = SUM2+SUM3+SUM4+SUM37+SUM44+SUM45+SUM46
SUM8 – VAT of tax group 1 (reduced rate)
SUM9 – VAT of tax group 2 (base rate)
SUM39 – VAT of tax group 1.2 (secondary reduced rate)
SUM10 – VAT total
It must be fulfilled: SUM10 = SUM8+SUM9+SUM39
In messages INVOIC 380, 381, 83 we expect from those VAT payers, invoicing in other than local currency (i.e. those issuing domestic invoices in foreign currency) that during invoicing in this currency, they will also provide exchange rate of the invoicing currency against their local currency and VAT recapitulation in their local currency:
It is necessary to provide this information:
VAT recapitulation in local currency – for the rates used provide VAT base and VAT amount in local currency, see the list below:
If you have received a negative COMDIS with this error, add the missing data to the original message and resend it.
...
CUX+2:EUR:4:1+3:CZK:10E+25.442' … conversion rate
DTM+134:20180417:102' … date of the currency conversion rate
…
UNS+S'
…
TAX+7+VAT+++0:::0'
MOA+125:1464:EUR' … basis at the VAT rate 0 % in the invoice currency
MOA+124:0:EUR' … VAT rate 0 % in the invoice currency
MOA+125:37247.09:CZK:10E' … basis at the VAT rate 0 % in local currency
MOA+124:0:CZK:10E'
TAX+7+VAT+++1:::15'
MOA+125:3000' … reduced rate VAT basis in the invoice currency
MOA+124:450' … VAT reduced rate in the invoice currency
MOA+125:76326:CZK:10E' … reduced rate VAT basis in local currency
MOA+124:11448.9:CZK:10E' … reduced rate VAT in local currency
TAX+7+VAT+++1.2:::10'
MOA+125:1200'
MOA+124:120'
MOA+125:30530.4:CZK:10E'
MOA+124:3053.04:CZK:10E'
TAX+7+VAT+++2:::21'
MOA+125:0'
MOA+124:0'
MOA+125:0:CZK:10E'
MOA+124:0:CZK:10E'
TAX+7+VAT+++2AE:::21+AE'
MOA+125:25000' … basic rate VAT basis in reverse charge mode
MOA+125:636052:CZK:10E' … basic rate VAT basis in reverse charge mode in local currency
…
These are data in the fields:
HDR14 – Date of the currency conversion rate
HDR16 – Currency conversion rate to local currency
SUM25 – Tax Group
SUM26 – The basis of the tax group
SUM27 – Tax Group Rate
SUM28 – VAT of the Tax Group
SUM29 – Reverse charge
SUM30 – VAT in converted (local) currency
See:
…
<currency_target_code>CZK</currency_target_code>
<currency_exchange_rate>25.442</currency_exchange_rate>
<currency_rate_value>1</currency_rate_value>
<currency_exchange_date>2018-04-17</currency_exchange_date>
…
<tax_details>
<vat>
<vat_group>0</vat_group>
<vat_basis>1464</vat_basis>
<vat_rate>20.00</vat_rate>
<vat_total>0</vat_total>
<reverse_charge>N</reverse_charge>
<local_currency>N</local_currency>
</vat>
<vat>
<vat_group>0</vat_group>
<vat_basis>37247.09</vat_basis>
<vat_rate>0</vat_rate>
<vat_total>0</vat_total>
<reverse_charge>N</reverse_charge>
<local_currency>A</local_currency>
</vat>
…
<vat>
<vat_group>2</vat_group>
<vat_basis>25000</vat_basis>
<vat_rate>21.00</vat_rate>
<vat_total>00</vat_total>
<reverse_charge>A</reverse_charge>
<local_currency>N</local_currency>
</vat>
<vat>
<vat_group>2</vat_group>
<vat_basis>636052</vat_basis>
<vat_rate>21.00</vat_rate>
<vat_total>00</vat_total>
<reverse_charge>A</reverse_charge>
<local_currency>A</local_currency>
</vat>
…
</tax_details>
These are data in the fields:
ERT2 – Basis of tax group 0 (exempt) in local currency
ERT3 – Basis of tax group 1 (reduced rate) in local currency
ERT4 – Basis of tax group 2 (base rate) in local currency
ERT5 – VAT of tax group 1 (reduced rate) in local currency
ERT6 – VAT of tax group 2 (base rate) in local currency
ERT7 – Basis of tax group 1.2 (secondary reduced rate) in local currency
ERT8 – VAT of tax group 1.2 (secondary reduced rate) in local currency
ERT9 – Basis of tax group 1 (reduced rate) in local currency – reverse charge mode
ERT10 – Basis of tax group 1.2 (secondary reduced rate) in local currency – reverse charge mode
ERT11 – Basis of tax group 2 (base rate) in local currency – reverse charge mode
These are data in the fields:
HDR54 – Date of the currency conversion rate
HDR55 – Currency conversion rate to local currency
SUM10 – Basis of tax group 0 (exempt) in local currency
SUM11 – Basis of tax group 1 (reduced rate) in local currency
SUM12 – Basis of tax group 2 (base rate) in local currency
SUM13 – VAT of tax group 1 (reduced rate) in local currency
SUM14 – VAT of tax group 2 (base rate) in local currency
SUM29 – Basis of tax group 1.2 (secondary reduced rate) in local currency
SUM30 – VAT of tax group 1.2 (secondary reduced rate) in local currency
SUM34 – Basis of tax group 1 (reduced rate) in local currency – reverse charge mode
SUM35 – Basis of tax group 1.2 (secondary reduced rate) in local currency – reverse charge mode
SUM36 – Basis of tax group 2 (base rate) in local currency – reverse charge mode
This format does not include domestic invoices in foreign currency. Agree with your EDI solution provider in another format variant.
In tax correction documents (messages INVOIC of type 381 and 83) we always expect a value in the field Reference invoice number (no. of the original invoice to which the tax correction document is issued).
In case of aggregate documents, it is also possible to provide a number of at least one of the original tax documents to which the tax correction document is issued.
Providing the reference document serves, besides others, to check that exchange rates, VAT rates and VAT modes of the tax correction document match against the original invoice.
If you have received a negative COMDIS with this error, add the missing information to the original message and resend it.
"...
RFF+IV:1236542 … the original invoice number
DTM+171:20150226:102' … the date of issue of the original invoice
..."
The fields for writing are:
HDR39 – The meaning of the invoice reference number
HDR40 – Invoice reference number (proforma invoices, etc.)
HDR41 – The date relating to the invoice reference number
HDR42 – The time related to the invoice reference number
See:
<meaning_of_reference_number>IV</meaning_of_reference_number>
<reference_number>1236542</reference_number>
<reference_number_date>2018-02-23</reference_number_date>
<reference_number_time>10:48</reference_number_time>
These are data in the fields:
HDR20 – Meaning of the invoice reference number (indicates what is the reference number, use "IV" for the original invoice)
HDR21 – Invoice reference number (proforma invoices, etc.)
HDR22 – The date relating to the invoice reference number
These are data in the fields:
HDR33 – Meaning of the invoice reference number (indicates what is the reference number, use "IV" for the original invoice)
HDR34 – Invoice reference number (proforma invoices, etc.)
HDR35 – The date relating to the invoice reference number
HDR36 – The date relating to the invoice reference number – the format qualifier
These are data in the fields:
HDR20 – Meaning of the invoice reference number (indicates what is the reference number, use "IV" for the original invoice)
HDR21 – Invoice reference number (proforma invoices, etc.)
HDR22 – The date relating to the invoice reference number
In messages INVOIC 380, 381 and 83 we always expect information about incorporation of vendor in Commercial or other public register.
If you have received an acknowledgment message with the identification of this error, it may indicate that your document does not include this entry at all or you have put it in the wrong field.
This information has a dedicated field Incorporation in commercial register.
Kindly check the setup in new documents. The error is currently in test mode of new controls and it is not being evaluated as blocking, it is not necessary to resend the original message because of this error. (This does not apply to cases when this error was discovered in combination with other, blocking errors and the message was rejected by APERAK or negative COMDIS. In such case it is necessary to resend the message after eliminating the errors).
After the test mode has ended (from Q3/2018) the error will be included in the blocking controls and documents containing this error will be rejected.
...
FTX+AAI+++Obch.reg. KOS Kopec odd. B, vložka 63284'
...
The field for writing is:
HDR17 – Supplier's record mark – entry in the Commercial Register
See:
<registration>Obch.reg. KOS Kopec odd. B, vložka 63284</registration>
The format does not have a separate field for information on enrollment in the Commercial Register.
To transfer this information, the first 140 characters of the TXT text note line are used.
Specifically, the TXT2 and TXT3 fields.
TXTObch.reg. KOS Kopec odd. B, vložka 63284
If you have the text filled in at the right place, then contact your EDI provider and clarify the situation.
There is a separate line AAI for this detail:
AAI2 – Entry in the Business Register
See:
AAIObch.reg. KOS Kopec odd. B, vložka 63284
This is an indication in the field:
HDD24 – Entry in the Business Register
In messages INVOIC 380, 381 and DESADV we always expect a value in the field Entry type according to a codebook of field codes in this way:
If you have received a negative COMDIS with this error, add the missing entry types to the original message and resend it.
...
IMD+F++:::Z' … The Item type field – fill in the data as described
...
The field for writing is:
LIN9 – Item type
See:
<item_type>Z</item_type>
This is the data in the field:
LIN5 – Item type
This is the data in the field:
LIN8 – Item type
This is the data in the field:
LIN5 – Item type
In messages INVOIC 380, 381 and 83, we always expect information about the VAT mode in the document, according to the Act on value added tax.
If you have received an acknowledgment message with the identification of this error, it may indicate that your document does not include this entry at all or you have put it in the wrong field.
This information is compulsory when the document contains entries in the reverse charge mode or if they concern deliveries into other EU countries.
This information has a dedicated field IHDR92 <reg_text_1>; EDIFACT „FTX+REG:“
Recommended texts
Reverse charge <reg_text_1>The tax will be paid by the customer</reg_text_1>
(text according to the Act on VAT)
Delivery into another EU country <reg_text_1>Exempt EU</reg_text_1>
(other text may be also used in accordance with the legislation)
Kindly check the setup in new documents. The error is currently in test mode of new controls and it is not being evaluated as blocking, it is not necessary to resend the original message because of this error. (This does not apply to cases when this error was discovered in combination with other, blocking errors and the message was rejected by APERAK or negative COMDIS. In such case it is necessary to resend the message after eliminating the errors).
After the test mode has ended (from Q3/2018) the error will be included in the blocking controls and documents containing this error will be rejected.
...
FTX+REG+++ The tax will be paid by the customer '
...
The field specified for writing is:
HDR18 – Texts required by the tax laws
See:
<regulatory_information> The tax will be paid by the customer </regulatory_information>
There is separate line REG for this entry:
REG2 – Texts required by the tax laws
See:
REGThe tax will be paid by the customer
There is separate line REG for this entry:
REG2 – Texts required by the tax laws
See:
REGThe tax will be paid by the customer
There is separate line REG for this entry:
REG2 – Texts required by the tax laws
See:
REGThe tax will be paid by the customer
In tax correction documents (messages INVOIC of type 381 and 83), we always expect the same VAT mode as was stated in the original tax document. Tax rate, exchange rate in the case of foreign currency as well as the flag of reverse charge or the mode „EU export“ should match the values in the original document that is listed as Reference invoice number.
If you have received a negative COMDIS with this error, check the tax correction document against the values in the Reference invoice, correct the faulty values in the tax correction document and resend it to us.
In invoices (message INVOIC of type 380), we expect this information in the field Buyer order no. (in the header as well as at the level of entries, if the document has multiple entries):
Invoice for common deliveries of goods into warehouse no. of our order „OByyxxxxxx“
Invoice for deliveries of goods in DROP mode no. of customer order that we send through API (does not include prefix, e.g. „1754912051“)
Invoice for service deliveries (service repairs) no. of our order, or no. of the document Price proposal „CNyyxxxxxx“
In tax correction documents (messages INVOIC of type 381), we expect this information in the field Buyer order no. (in the header as well as at the level of entries, if the document has multiple entries):
Credit memo for goods claimed by customer no. of our document Service request „SETxxxxxxxxx“; alternatively no. of claim if the no. of Service request is not available
Credit memo for undelivered or returned goods no. of our document Return receipt „VPyyxxxx“
Credit memo for undelivered goods in DROP mode no. of customer order that we send through API (does not include prefix, e.g. „1754912051“)
Credit memo for claimed goods in DROP mode as in the case of claimed goods from common deliveries, i.e. no. of our document Service request „SETxxxxxxxxx“; alternatively no. of claim, if the no. of Service request is not available
In all cases we search for the exact format of this reference according to the structure mentioned above and it is not possible to add to these fields various notes or supplements before/after the reference document no.
If you have received a COMDIS with this message, add the correct reference to the INVOIC message and resend it.
...
RFF+ON:8123456' … the Order number of the subscriber data field – fill in the data as described
...
The fields specified for writing are:
HDR22 – Subscriber Order Number in Header
LIN28 – Subscriber Order Number for Items
Viz
<order_number>201188591</order_number>
This is the data in the fields:
HDR14 – Subscriber Order Number in Header
LIN21 – Subscriber Order Number for Items
This is the data in the fields:
HDR17 – Subscriber Order Number in Header
LIN28 – Subscriber Order Number for Items
This is the data in the fields:
HDR14 – Subscriber Order Number in Header
LIN21 – Subscriber Order Number for Items
29 years on the market
2 000 + satisfied customers
3 000 000 + electronic documents transferred every month
18 000 + cups of coffee annually increase the performance of our employees