Unique receipt identifier

What it means

The unique receipt identifier, or UID, is a unique code that the eKasa system assigns to every receipt printed by a cash register. The code confirms that the sale data was sent to the Financial Administration server and is recorded there.

The identifier is printed on the receipt together with a QR code. Customers can use a mobile app or the Financial Administration website to check that the receipt was properly recorded, thereby helping to monitor revenue reporting. The check also feeds into the national receipt lottery.

If an online cash register has no connection to the server, it issues the receipt in offline mode. Instead of a UID, the receipt carries the merchant's verification code generated by the device itself, and the data must be sent to the server within the statutory period once the connection is restored.

How it works in practice

Merchants should check that receipts issued offline were actually sent once the connection was back. Operating without a connection for long periods or leaving receipts unsent can lead to findings of non-compliance and penalties during an inspection.

When selling through a virtual cash register on a phone or computer, the UID is assigned in the same way, because the receipt is created directly on the server. A virtual register only works online, however, so sales cannot be recorded during an internet outage.

The UID also makes handling complaints and exchanges easier, since the receipt can be found unambiguously in the system. For bookkeeping, eKasa data can be downloaded from the Financial Administration portal and compared with the daily sales summary in the accounts.

What to watch out for

A receipt without a UID or verification code, let alone failing to issue a receipt at all, breaches the Cash Register Act. Inspectors often make test purchases, and failing to issue a cash document can lead to a penalty and, for repeated breaches, closure of the premises.

When replacing or repairing a cash register or switching to a new device, the procedure for registering and deregistering it in eKasa must be followed. A misconfigured device may issue receipts that never reach the server, and the merchant may only find out during an inspection.