Swedish fiscalization can sound abstract until you follow a single sale through the system. What actually happens between a cashier pressing “pay” and a compliant receipt printing? This guide traces that path end to end — from the point-of-sale software, through the cloud control system (TCS), to the control code on the receipt — and shows where a POS vendor’s responsibilities begin and end.
What is cloud fiscalization?
Cloud fiscalization is the model, introduced through SKVFS 2020:9, where a certified control system runs as a service and signs each transaction over an API — instead of a physical control unit doing the signing on-premise. The register sends transaction data to the cloud control system, which returns a control code (avstämningskod) for the receipt and maintains the counters Skatteverket uses to verify sales.
The result is the same compliance outcome as the old hardware model, delivered through software: no box to install, one integration to maintain.
The signing flow, step by step
Here is what happens when a POS makes a sale through SIGN SE:
-
The POS sends the transaction to the fiskaly Unified API (UAPI) — a standard sale, a return, a copy, or another supported record type.
-
The UAPI validates and routes the request, then forwards the signing job to the certified cloud control system (Infrasec TCS).
-
The TCS signs the transaction, generates the 113-character control code, and updates the relevant cumulative counters.
-
The control code is returned to the POS, which prints it on the receipt alongside the other mandatory fields.
From the integrator’s side, this is a single API interaction. The counter management and signing logic happen behind the API — the POS never touches the TCS internals directly.
Where Skatteverket sits — and doesn’t
A frequent point of confusion: fiskaly does not talk to Skatteverket on the merchant’s behalf. The tax agency connection is a merchant’s relationship with Skatteverket for registration and notification.
-
✅ fiskaly ↔ POS: transaction signing, control codes, status, counters
-
✅ Merchant ↔ Skatteverket: registering the control unit and cash register, notification
-
❌ fiskaly ↔ Skatteverket: no direct interaction
This matters for scoping an integration. The POS vendor builds against the fiskaly API; the merchant completes registration with Skatteverket using the artifacts (like the tillverkningsnummer) that the system surfaces.
The daily register status check
Before any sale can be processed, a Swedish POS has to confirm the control system is reachable and healthy. On startup, the POS sends an opening intention to the API, which checks register status with the TCS. The TCS returns a status code, and the API gates POS access on the result: a healthy status allows sales with a control code; other states either allow offline notes only or block sales entirely until resolved.
In other words, SIGN SE uses the returned status information to determine whether signed transactions can proceed or whether offline procedures must be followed.
What the POS still owns
Cloud fiscalization removes the signing burden, but the POS vendor still owns the parts closest to the customer and the merchant’s own systems:
-
❌ SIGN SE does not replace the POS software — it is an API layer
-
❌ It does not manage the journal memory — that stays a POS responsibility
-
❌ It does not interact with Skatteverket — the merchant registers manually
-
✅ The POS handles receipt layout, journal storage, and the merchant-facing flows
Knowing this split up front keeps an integration project scoped correctly.
How fiskaly helps
SIGN SE delivers Swedish cloud fiscalization through one REST API, using the same authentication and integration pattern as fiskaly’s other SIGN products. It generates the control code for receipts that require signing, maintains the cumulative counters transparently via the certified TCS, returns the mandatory Swedish status messages for printing, and enforces the startup gate so no sale proceeds before status is confirmed.
For a vendor already integrated with SIGN in another market, adding Sweden is an incremental effort rather than a fresh build — the shape of the integration is familiar.
Free API testing — no commitment. Talk to our experts about integrating cloud fiscalization for Sweden.
Frequently asked questions
Does fiskaly send my data to Skatteverket? No. fiskaly handles transaction signing and returns control codes and status to the POS. Registration and notification are a direct merchant-to-Skatteverket process; fiskaly has no direct connection to the tax agency.
What is the 113-character control code? It is the avstämningskod the certified control system generates for each signed receipt. The POS prints it on the receipt as part of the mandatory content, and it is what makes the receipt verifiable.
What happens if the control system is offline? The register status check returns a status that permits offline cash notes (kontantnota) only, without a control code, until contact is re-established. Some states block sales entirely and require escalation.
How much of this do I have to build myself? You build against one API. Signing and counter management sit behind it. You remain responsible for the POS itself, receipt layout, and journal storage, and the merchant handles Skatteverket registration.
Next steps
Cloud fiscalization in Sweden follows a clear path: the POS sends a transaction, the certified cloud control system signs it and returns a control code, and the POS prints a compliant receipt — with a startup status check ensuring the system only trades when it can trade compliantly. Helping to ensure that signed transactions are only processed when the control system is in an operational state. fiskaly handles the signing; the merchant handles Skatteverket.
Request a meeting to see the SIGN SE integration for Sweden — with free API testing and no integration commitment.
Related reading: Hardware vs. cloud control units, Swedish receipt requirements: the 13 mandatory fields, How to register a cash register with Skatteverket.
Last updated: October 2026. This article is general guidance, not legal advice. Confirm requirements against Skatteverket’s current rules at skatteverket.se.
