Receipt Layout
EET 2.0 imposes no statutory obligation to print the acknowledgement code or any other fiscal data on the customer receipt. The old requirement to print FIK or PKP does not carry over.
EFR still returns the fiscal data below so it can be printed — many operators choose to, and the test marker is useful during rollout.
Layout
All Fis.Tag elements present in the response should be printed on the receipt. Tags are omitted when there is nothing to show: no POK if the sale was not acknowledged, no test marker in production.
The FN tag carries only the counter, because the unit and the register are already shown by their own tag — so ESR.FN 4303/1/39 is printed as 39. A fiscal number supplied by the cash register that does not follow this form is printed in full instead.
| Name | Label | Content |
|---|---|---|
TaxId | EIC | The registration identification number the sale was reported under |
UnitRegister | jednotka/pokl | Registrating unit ID and point-of-sale ID |
FN | č. účtenky | The receipt number — the counter part of the fiscal number |
Fiscal | POK | The acknowledgement code, 39 characters |
Info | (empty) | *** TEST *** — present only for a non-production answer |
Example Response
The ESR.FN is shown alongside, so the relationship to the printed receipt number is visible.
Registered sale
- XML
- JSON
<TraC SQ="128">
<Result RC="OK"/>
<ESR FN="4303/1/39"/>
<Fis>
<Tag Label="EIC" Value="CZ00000019" Name="TaxId"/>
<Tag Label="jednotka/pokl" Value="4303/1" Name="UnitRegister"/>
<Tag Label="č. účtenky" Value="39" Name="FN"/>
<Tag Label="POK" Value="5586c2a1-72e8-4749-9cfc-986a62bc3d4d-02" Name="Fiscal"/>
</Fis>
</TraC>
{
"TraC": {
"SQ": 128,
"Result": { "RC": "OK" },
"ESR": { "FN": "4303/1/39" },
"Fis": {
"Tag": [
{ "Label": "EIC", "Value": "CZ00000019", "Name": "TaxId" },
{ "Label": "jednotka/pokl", "Value": "4303/1", "Name": "UnitRegister" },
{ "Label": "č. účtenky", "Value": "39", "Name": "FN" },
{ "Label": "POK", "Value": "5586c2a1-72e8-4749-9cfc-986a62bc3d4d-02", "Name": "Fiscal" }
]
}
}
}
Registered sale in test mode
Against the playground the POK ends in -ff and the response carries a test marker.
- XML
- JSON
<TraC SQ="128">
<Result RC="OK"/>
<ESR Test="true" FN="4303/1/39"/>
<Fis>
<Tag Label="EIC" Value="CZ00000019" Name="TaxId"/>
<Tag Label="jednotka/pokl" Value="4303/1" Name="UnitRegister"/>
<Tag Label="č. účtenky" Value="39" Name="FN"/>
<Tag Label="POK" Value="5586c2a1-72e8-4749-9cfc-986a62bc3d4d-ff" Name="Fiscal"/>
<Tag Label="" Value="*** TEST ***" Name="Info"/>
</Fis>
</TraC>
{
"TraC": {
"SQ": 128,
"Result": { "RC": "OK" },
"ESR": { "Test": "true", "FN": "4303/1/39" },
"Fis": {
"Tag": [
{ "Label": "EIC", "Value": "CZ00000019", "Name": "TaxId" },
{ "Label": "jednotka/pokl", "Value": "4303/1", "Name": "UnitRegister" },
{ "Label": "č. účtenky", "Value": "39", "Name": "FN" },
{ "Label": "POK", "Value": "5586c2a1-72e8-4749-9cfc-986a62bc3d4d-ff", "Name": "Fiscal" },
{ "Label": "", "Value": "*** TEST ***", "Name": "Info" }
]
}
}
}
Sale that could not be reported
An offline sale carries no POK tag and the result reports #OFFLINE. Nothing has to be printed in its place — unlike EET 1.0, EET 2.0 has no offline code.
Legacy: EET 1.0 (valid until 2023)
The layout below applied to the registration of sales under Act No. 112/2016, discontinued at the end of 2022. BKP and FIK do not exist in EET 2.0.
Legacy receipt layout guide (valid until 2023)
Layout
Example Response
All Fis.Tag elements in the response must be printed on the receipt.
XML Response
<TraC SQ="2345">
<Result RC="OK"/>
<Fis>
<Tag Label="DIČ" Value="CZ00000019" Name="TaxId"/>
<Tag Label="provoz/pokl" Value="141/1" Name="TLT"/>
<Tag Label="BKP" Value="01234567-89abcdef-01234567-89abcdef-01234567" Name="Sign"/>
<Tag Label="FIK" Value="987a6be5-6af5-44f3-b4fc-987654321000-03" Name="Fiscal"/>
</Fis>
</TraC>