SiopKA fiscal register
An online register that fits in a phone
SiopKA is a software cash register for Android phones. It issues receipts and invoices, keeps the reports, talks to the Ministry of Finance repository on its own and lets several cashiers of the same taxpayer work on it.
What does the SiopKA register do?
The functions of a software cash register plus what you need every day. Each function has a legal source and a state visible in the register and the panel. The President of GUM assesses whether the register type and version meet the requirements in the type approval procedure.
| Function | How it works |
|---|---|
| Receipts and cancelled receipts | A receipt (PR) with industry data, signature and verification code; a cancelled receipt (PA) only where the law allows it. |
| Invoices and KSeF | An invoice for a receipt or without one in the FA(3) structure, sent to KSeF in the background, with corrections and offline24. |
| Reports | Daily, periodic, events, settlement and fiscalization reports, with a preview of every page and a PDF. |
| Cashiers and permissions | Cashiers with PINs, a register administrator and a log of who issued what. In a taxi the cashier is called the driver. |
| Goods and services catalogue | Names, prices and VAT rates programmed in the register; changes only by the register administrator. |
| Offline work | Sales without signal, a document queue and catching up deliveries to the MF when the connection returns. |
| An API for apps | Your app issues documents through the general register API on the same phone or as a remote station. |
How many cashiers can work on one register?
As many as the licence includes: cashiers of the same taxpayer take turns on one register, on its screen or from remote stations paired in the panel.
A remote station is a tablet, phone, POS or partner system that sends sales to the company register. You pair it in the panel with a code or QR code; each has its own key and its own permissions.
Authorisation has two steps: first the server checks it, then the register itself, which keeps its own copy of the pairings. The register always issues the document, never the station.
One register cannot serve several independent payment points or several taxis. A remote register for taxis works only on the MF test environment.
How does the customer get the receipt?
Recording a receipt and issuing it are two separate steps. The receipt is recorded before it reaches the printer, so a printing error never undoes it.
- PrinterA thermal printer connected to the phone over Bluetooth or Wi-Fi; the printer model is agreed in the pilot. Every print attempt is recorded in the issue log.
- Siop PrinterAn app that receives the printout image from the register and saves the full document. More about Siop Printer.
- E-receiptAn electronic receipt when the customer agrees and says how to receive it.
- Customer displayIn vending devices, the sale data on screen for at least 30 seconds or until the next sale.
Which documents and reports does the register keep?
Each has its own symbol and its own numbering. A preview or a reprint never creates a new fiscal report.
| Symbol | Document | When it is created |
|---|---|---|
| RF | Fiscalization report | once, when the register is fiscalized |
| PR | Fiscal receipt | with every sale |
| PA | Cancelled fiscal receipt | when a sale is interrupted, where the law allows it |
| RD | Daily fiscal report | at the end of the sales day, before sales on the next day |
| RP | Periodic report, including monthly | on demand, from the recorded daily reports |
| RZ | Fiscal events report | on demand, from the recorded register events |
| RR | Settlement report | when the register is closed, from the whole history of daily reports |
| NF | Non-fiscal printout | for auxiliary documents, marked as non-fiscal |
What does the register do without signal?
It keeps selling. No network only delays the delivery to the MF, never the receipt.
Every document is first recorded in the register database with its signature. It reaches the MF repository from the queue, in the order of issue; after a break the register sends what is waiting and repeats nothing.
When delivery is impossible for longer, the law provides a separate procedure agreed with the tax office. The register shows since when documents have been waiting.
- 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
What does a register's life look like?
From fiscalization to closure the register stays on one phone, and its records can neither be changed nor deleted.
- FiscalizationThe register connects to the MF, receives its unique number and records the fiscalization report with the register category chosen for your industry.
- Daily workReceipts, invoices, the daily report at the end of the day, delivery to the MF on schedule.
- UpdatesVersions from the manufacturer, verified before installation, installed after the daily report, with the event recorded and a rollback on failure. After type approval only versions covered by it may be installed. Register data stays untouched.
- Replacing the phoneA register is not moved to another phone. You close the current register and fiscalize a new one; the history stays in the reports and the panel.
- Closing the registerThe register issues the last daily report and the settlement report, delivers outstanding data to the MF and switches to read-only mode.
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.