Ir al contenido
Section navigation

fiskaly SIGN CZ — 2026-09-14

Esta página aún no está disponible en tu idioma.

fiskaly SIGN CZ is a cloud-based fiscalization solution for the Czech market, provided as Software as a Service (SaaS). It enables POS providers (CUSTOMER) and their merchants (END CUSTOMER) to comply with the Czech electronic sales registration EET 2.0 (Elektronická evidence tržeb, interface version 4.1) under the Czech Sales Registration Act. Reportable sales are signed and transmitted in real time to the Czech Financial Administration (Finanční správa), which confirms each accepted sale with a POK code. The service is 100% cloud-based, requires no hardware, and is accessed via the fiskaly Unified API (RESTful) and managed through the fiskaly HUB.

EET 2.0 has no certification regime — any compatible solution may be used — and no customer receipt obligation: no code, QR code or signature has to be printed or handed to the consumer.

fiskaly makes SIGN CZ available to the CUSTOMER as SaaS. The CUSTOMER obtains access to the functionality via the API and may sublicense its use to END CUSTOMERS through an authorisation system. Key aspects include:

  • Provision of a cloud-based sales registration solution in accordance with the Czech Sales Registration Act (EET 2.0).
  • Cryptographic signing of EET messages (WS-Security) with the END CUSTOMER’s cash certificate held in the fiskaly cloud, transmission to the Financial Administration, verification of the authority’s signed response, and storage of the confirmation (POK) and transmission evidence on the record.
  • Non-exclusive, non-transferable right of use, limited to the contract term and the territory of the Czech Republic, sublicensable only to END CUSTOMERS.
  • Data generated by the END CUSTOMER is held by fiskaly for a period of three (3) months.
  • Provision of the current version of fiskaly SIGN CZ, including updates at irregular intervals.
  • Access to a TEST SYSTEM connected to the tax authority’s playground and is using a pre-defined playground taxpayer TEST signing certificate to transmit sale information.
  • Use of the fiskaly HUB for management and administration.
  • Sales registration: Each reportable sale is submitted as a Unified API record (TRANSACTION::RECEIPT). fiskaly maps the record to the EET message, signs it, transmits it to the Financial Administration and stores the returned POK confirmation on the record. One record corresponds to one EET message.
  • Unified API resource model: Taxpayers, locations and systems follow the same resource model as all other fiskaly SIGN products. A location represents a declared business unit (evidenční jednotka) carrying the authority-allocated unit identifier (id_jednotky); a system represents a till carrying the till identifier (id_pokl).
  • Payment channel handling: Payments are classified as contact or remote in accordance with the Act; only reportable payments are included in the transmitted total.
  • Response handling: Authority responses are verified and classified. Retryable rejections and transport failures set the record to FAILED (resend required); terminal rejections set the record to REJECTED (payload defect). Warnings issued by the authority are appended to the record’s logs without blocking the confirmation.
  • Transmission evidence: The authority’s X-Global-Transaction-Id is stored per message and serves as the reference for support requests towards fiskaly and the Financial Administration.
  • Authorisation system: The CUSTOMER manages END CUSTOMER access via user credentials or other approved procedures.
  • Management via fiskaly HUB: Administration and configuration of fiskaly SIGN CZ instances.
  • Continuous monitoring: fiskaly monitors functionality up to the API and eliminates malfunctions.
  • Malfunction management: Priority-based fault reporting and response as defined in the annex “service and malfunctions.”
  • Update management: Updates are announced at least two weeks in advance (e.g., via workspace.fiskaly.com) and deployed during defined maintenance periods (except emergency updates).
  • A valid contractual relationship with fiskaly.
  • An internet connection for integration and operation.
  • Integration of the fiskaly Unified API (SIGN CZ) into the CUSTOMER’s recording system, in accordance with the interface documentation and requirements.
  • Non-blocking or asynchronous integration to ensure uninterrupted recording system operation.
  • The CUSTOMER must ensure operation of the recording system is not limited in case of a potential outage of fiskaly SIGN CZ or of the Financial Administration.
  • For LIVE operation (once available): the END CUSTOMER’s Czech tax identification number (DIČ), the configured taxpayer’s signing certificate, the declaration of every business unit through the tax administration’s DIS+ portal (each receiving an authority-allocated id_jednotky), and a valid cash certificate issued by the tax administration after the unit declaration. Certificates are currently valid for one year and must be renewed by the END CUSTOMER.
  • All amounts must be provided in CZK.

fiskaly is committed to maintaining and updating fiskaly SIGN CZ. fiskaly undertakes to maintain and update the Service with a view to supporting its security, availability, and ongoing alignment with applicable technical and reporting requirements; however, the Customer remains responsible for implementing required updates, migrations, and integration changes on its side. The service is versioned according to semantic versioning; significant changes resulting in new major releases will be documented. Maintenance activities may result in the temporary outage of the service. As far as possible, these activities shall be announced at least two (2) weeks in advance; emergency maintenance activities may deviate from this. fiskaly provides assistance to customers via the fiskaly support portal (https://support.fiskaly.com).

fiskaly provides a TEST SYSTEM for fiskaly SIGN CZ, connected to the Financial Administration’s playground environment. The CUSTOMER can use the sandbox to validate its integration before going live. Confirmations issued by the playground carry test="true" and have no legal standing. New versions of the service are made available in the TEST environment before their LIVE release. fiskaly is not responsible if real data is used in the TEST environment.

Preview-specific limitations (valid until a new dated version of this service description is issued):

  • The Czech Sales Registration Act has not yet been promulgated. All dates, field definitions and obligations described here reflect the published draft and the tax authority’s technical specification (interface v4.1) and may change before the Act enters into force. fiskaly will reflect such changes in new releases; the CUSTOMER remains responsible for implementing them.
  • The LIVE environment is not yet activated. Until activation, fiskaly SIGN CZ transmits exclusively to the tax authority’s playground by using a playground signing certificate; no legally effective sales registration takes place.
  • Cancellation and correction operations (TRANSACTION::CANCELLATION, TRANSACTION::CORRECTION) are not yet available. Until they are released, a recorded sale cannot be reversed or corrected through the API.
  • No automatic store-and-forward queue and no automatic resend are provided yet. A failed transmission leaves the record in the FAILED state; the CUSTOMER must resend such records (see Customer Obligations). An automatic resend mechanism is planned.
  • Non-CZK amounts are not supported and are rejected by the API.
  • Dedicated EET voucher fields are not supported.
  • The process by which an END CUSTOMER’s cash certificate is made available to fiskaly is being finalised with the tax administration and will be documented before LIVE onboarding opens.

General limitations:

  • Functionality outside the API (particularly on recording systems) is not warranted.
  • No warranty for proper integration into the CUSTOMER’s recording system.
  • fiskaly validates identifiers (id_jednotky, id_pokl, DIČ) for well-formedness only; it does not verify them against the tax administration’s DIS+ registry. A well-formed but incorrect unit identifier is accepted by the authority.
  • fiskaly does not validate the business accuracy or tax correctness of the data provided, including the classification of payments as reportable or not reportable.
  • No warranty for other requirements for proper recording system operation beyond the transmission of reportable sales (e.g., receipt content, bookkeeping, archiving).
  • No binding resolution times for malfunctions.
  • Fault reports from END CUSTOMERS directly are not accepted or processed.
  • Responsible for integrating fiskaly SIGN CZ into recording systems at own expense, meeting all framework criteria and system requirements per the interface documentation.
  • Must ensure the recording system’s operation is not limited in case of a potential outage of fiskaly SIGN CZ or of the Financial Administration. Sales must be completed and recorded for later transmission; refusing sales during an outage is not required by the Act and does not fulfil the transmission obligation.
  • Resend obligation (48-hour rule): Under the Act, a sale that could not be transmitted must be resent without undue delay once the cause has ceased and at the latest within 48 hours of the sale; the duty to send survives the deadline. Until fiskaly provides an automatic resend mechanism, the CUSTOMER must implement a retry for records in the FAILED state, including for the Financial Administration’s recurring planned maintenance window (currently every Thursday 20:00–06:00). Records in the REJECTED state must be corrected, not resent unchanged.
  • When resending, the CUSTOMER must not change the sale amount or the till identifier (id_pokl) between attempts, as either change is treated by the authority as a second, different sale.
  • Must classify each payment correctly as contact or remote in accordance with the Act and provide all amounts in CZK.
  • Must enter the DIS+-allocated unit identifier (id_jednotky) exactly as assigned by the tax administration and keep declared business units up to date (changes must be reported to the tax administration within 15 days).
  • Must ensure that the END CUSTOMER’s cash certificate is valid and renewed in time; queued messages are signed at the time of sending.
  • Must ensure all information for implementing fiskaly SIGN CZ is correct and available; faulty information may lead to inadmissible operation and extra costs.
  • Must support fiskaly to a reasonable extent and not engage in hindering conduct (e.g., abusive use of transaction volume, storage, or incorrectly categorised support tickets).
  • Must not misuse the service or negatively affect availability for other customers; data must be free of harmful components.
  • Acknowledges that the END CUSTOMER is responsible for all statutory obligations pursuant to the Czech Sales Registration Act, including the registration with the tax administration (DIS+), the possession of a valid cash certificate, and the reconciliation of recorded sales in DIS+.
  • Acknowledges that during the preview phase the service has no legal effect and must not be relied upon for the fulfilment of statutory obligations.
  • Must notify fiskaly of any changes to company data in writing and in a timely manner.
  • Must keep access credentials confidential and report unauthorised access immediately.
  • Must provide END CUSTOMERS with all necessary information for legal compliance and service use.

Version: v.1 (preview) | Last updated: 2026/09/14