POS and fiscal requirements for restaurants in Uzbekistan

The question every new restaurateur asks is "do I really need a cash register?". The answer is almost always yes, but the question itself is framed wrongly. The better one is: how is a sale documented, and where does that record go?

Important: what follows explains general practice and concepts. Registration procedures, technical requirements and liability change over time — verify the specific requirements with the tax authority's official source or with your own accountant. This article is not legal advice.

A pre-bill and a fiscal receipt are not the same thing

A restaurant prints two different documents, and they are constantly confused:

• Pre-bill — what you bring the guest before payment. An internal document: dishes, total, service charge. It has no fiscal standing.
• Fiscal receipt — the document generated after payment. This is what actually records the sale.

Plenty of venues hand over the first and never issue the second. To a guest the difference may be invisible; from a compliance standpoint they are two entirely different situations.

What makes an online cash register different

An old register printed a receipt and the data stayed inside the machine. Under the online model, sale data is transmitted outward at the moment of printing — meaning the tax authority sees turnover close to real time.

In practice this means:

1. Every sale is recorded as its own document
2. The data is transmitted and stored — a receipt cannot be deleted after the fact
3. The receipt is issued in a form the guest can verify, usually via a QR code

Which is why "we will buy a register later" does not work: the register is not a printer, it is the entry point of your entire sales accounting.

What a fiscal receipt normally contains

The exact layout is set by regulation, but in practice you will almost always see:

• Company name and tax identification number
• Address of the point of sale
• Receipt number, date and time
• Per line: item name, quantity, unit price, amount
• Tax (VAT) shown separately where it applies
• Payment method — cash and card recorded separately
• A fiscal mark and a QR code for verification

One item deserves special attention: the goods and services classifier code (referred to in practice as IKPU/MXIK). Every menu position needs the appropriate code assigned, and with a large menu this takes real time. Do not leave it to opening day.

The parts that are hard specifically for restaurants

Split payment methods

A guest pays 200,000 UZS in cash and the rest by card. The receipt must show the methods separately — otherwise neither the daily report nor the cash in the drawer will reconcile.

Splitting the bill

A group divides the bill between themselves. Each share needs its own document rather than one shared receipt.

Refunds and voids

When a served dish is returned, that is not "deleting a receipt" — it is a separately documented operation. Decide in advance who authorises it and what reason gets recorded.

Internet outages

The restaurant keeps working; the guest will not wait. So the POS must be able to operate offline and transmit once connectivity returns. Ask this question early when choosing a solution.

Delivery and takeaway

Sales outside the dining room are documented the same way. Cash brought back by a courier has to reach the till and produce a document.

Why enforcement keeps tightening

The logic is straightforward: food service turns over a lot of cash. Undocumented sales shrink the tax base, so the state wants to see the sale at its source — at the till. For a restaurant that treats this as a rule of the game rather than a punishment there is an upside: documented revenue also gives the owner honest numbers about their own business.

Pre-opening checklist

1. Legal form and tax regime settled (with an accountant)
2. POS solution chosen and its registration procedure confirmed
3. Classifier codes assigned to menu positions
4. Payment methods configured: cash, card, mixed
5. Refund and void procedure written down, with a named authoriser
6. Cashiers trained on opening and closing a shift
7. A defined plan for what happens when the internet drops
8. Every requirement confirmed against the tax authority's official source

The last item outweighs the rest: figures and deadlines circulating online may be out of date, while the liability stays with you.

Technically, what a restaurant needs is a POS that records the sale correctly and can pass it to the fiscal layer. In VKassa the classifier code is attached to the menu position, payment methods are stored separately, and the local server keeps running through a connectivity loss, sending data once the link is restored.