Skip to content
SiopKA is awaiting cash register type approval by the President of the Central Office of Measures (GUM). Until then it runs as a pilot on the Ministry of Finance test environment. Details

Technology

What happens inside the register, step by step

Five mechanisms that make sure no receipt gets lost, none changes after recording and every one reaches the MF. We describe them as they work in the register's code.

Mechanism 1

One queue for every entry

The register screen, an app on the same phone and a remote station all join the same queue, with the same safeguards. There is no back door.

  1. Stage 1 Sale The register screen, SiopTAK or your own system through the API. Every entry joins the same register queue. state: started
  2. Stage 2 Signed record The register assigns the number, signs the document and adds the previous one's hash. From now on the record cannot change. state: recorded
  3. Stage 3 Delivery to the MF The document waits in the queue and reaches the Central Repository of Cash Registers on schedule. No network only delays this stage. state: delivered
  4. Stage 4 Issued to the customer A printout, an e-receipt or an invoice. A printer error never undoes the record: you issue the document again. state: issued
Each stage has its own state, visible in the register and the panel. A later stage never undoes an earlier one.
Mechanism 2

Signatures and the document chain

Every document is signed and contains the previous one's hash, so records cannot be quietly changed or deleted.

  1. Receipt 411 9f2c…41a7
  2. Receipt 412 c07e…d93b
  3. Receipt 413 5ab1…0e6f
  4. Receipt 414 e48d…7c21
Illustration: each document contains the hash of the previous one, so changing one record breaks the chain and shows at once.

An electronic receipt is a signed JWS structure. The register computes its SHA-256 hash and puts it in the verification code, and the next document carries a link to the previous one.

At start-up the register checks its database. If the check finds a changed record, the register will not start selling.

Mechanism 3

Record first, network second

A sale does not wait for the Ministry's answer. The document is recorded at once, and delivery runs from the queue.

No signal, a slow network or a break on the MF side only delay delivery. The register remembers what it has sent and never sends anything twice after a break.

When an answer does not arrive, the register treats the result as unknown and checks the state before trying again.

Document queue to the MF Online
  • Receipt 0412 · PLN 36.00 Accepted by the MF
  • Receipt 0413 · PLN 18.50 Accepted by the MF
  • Receipt 0414 · PLN 74.00 Accepted by the MF
Illustration with sample data: without a network the register keeps selling and sends the recorded documents when the connection returns.
Mechanism 4

Time and the fiscal day

The register counts the day by official Polish time and keeps track of the clock and daylight saving changes.

  • Every moment is recorded unambiguously, and the sales day is counted in the Europe/Warsaw time zone.
  • The register compares the phone clock with time servers and limits corrections as the rules require.
  • The change from summer to winter time does not confuse the daily report: its time never goes back relative to the previous one.
Mechanism 5

Industry profiles as program data

Industries differ in data, not in code. So a new version of the taxi app does not change the register program.

  • A profile sets the register category, the typed industry data with validation, the document types, the output channels and the remote station rules.
  • The profile recorded at fiscalization is fixed. The register refuses to fiscalize with a profile that lacks a required function.
  • Cooperating apps, SiopTAK included, talk to the register only through the general API, like any integrator.

Start with your first receipt

Buy a licence in the shop and we will agree the installation of the pilot version with you after the purchase. You can also book a free demo: we will show the register, the taxi app and the panel on your own case.

Necessary cookies remember your appearance and language choice, protect forms and keep the panel session. They do not need consent, because without them the site cannot work the way you ask it to.

Necessary

Always on: appearance, language, cookie choice, form protection, panel session.

This site uses no analytics or advertising cookies and loads no third-party tracking tools.

Read the cookie policy