EGAIS at the POS: Beer, UTM, and Common Errors

A receipt with beer won't process, the POS displays "not accepted by UTM"—and the line keeps growing. In retail, beer and low-alcohol beverages are recorded in EGAIS differently from spirits with mandatory scanning of every bottle, but the "POS → UTM → EGAIS" chain is shared between them, and most errors boil down to a few typical causes.

1. Scheme: POS → UTM → EGAIS#

UTM (Universal Transport Module) is a middleware program installed on a POS computer or terminal that serves as the only legal communication channel between a venue and EGAIS: it signs documents with a digital signature, encrypts them, and forwards them to the EGAIS server. The POS or inventory management system does not communicate directly with EGAIS — it communicates with a locally running UTM (usually at an address like localhost:8080), and the UTM itself talks to the FSRAR servers.

What exactly is recorded for beer and low-alcohol beverages:

• Kegs ("on tap" draught) — unit accounting per keg: placing a keg on tap is recorded as a separate operation, while the sale itself on tap (by glass/draught) is written off after the fact, without scanning a mark for each serving — there are no physical marks on kegs for draught sales.
• Retail bottle/can — recording is usually not done "per item at the POS" for each sale, but by writing off inventory balances at the end of the day via a write-off report generated based on POS sales for the shift. The rules are gradually tightening — check the official FSRAR/EGAIS website for current requirements regarding your category and sales volume; specific deadlines and order numbers are deliberately omitted here.

2. "Receipt Not Accepted by UTM": Step-by-Step Diagnostics#

Follow the order from top to bottom — most "receipt not accepted" issues break down at steps 1–2 (UTM is simply not running), and substantive certificate or time errors are reached only if the module itself is active.

3. "Receipt TIN does not match the TIN field of the GOST certificate"#

The POS signs and sends a document with one TIN (its own organization's), while the certificate installed in the UTM is issued to a different TIN or legal entity — a common scenario after changing organizations, an error when installing a certificate at a new location, or if the certificate was copied from another computer instead of a proper reissuance.

1. Check the TIN specified in the settings of your POS / inventory management software — verify it against your organization's details.
2. Open the certificate section on the UTM self-diagnostics page — compare the certificate's TIN with the same detail.
3. If the TINs do not match — reissue the certificate through the EGAIS personal account for the correct organization, and reinstall the RSA certificate in the UTM from scratch; when moving the UTM to a new computer, certificates must be reinstalled, not just copied as files from the old machine.

4. "Verification failed: time of sale"#

This error indicates a clock desynchronization: the time on the receipt (according to the POS clock) differs significantly from the time seen by the UTM or EGAIS server when receiving the document. The acceptable desynchronization window for EGAIS is small — in practice, it is a matter of minutes, not hours.

1. Check the system time on the POS computer/terminal against the actual time (time zone of the point of sale, automatic time synchronization in the OS).
2. Make sure that time synchronization in the OS is enabled (NTP) and not manually disabled for the sake of "stability" — this is a common cause of gradual clock drift on older or long-running POS machines.
3. After synchronization, retry sending the document — usually, simply adjusting the clock is enough, and no additional actions in EGAIS are required.

5. UTM Freeze or Failure to Start#

1. Restart the UTM service — the standard approach, rather than "rebooting the computer just in case": a freeze is often resolved by restarting this exact service.
2. Check the transport_info logs (or a similar UTM log file; the path depends on the version/installation) — the specific cause is usually visible there: insufficient memory, unresponsive EGAIS server, or a certificate error on startup.
3. Disk space. UTM actively writes logs and a local document database — a full disk on the POS PC/terminal often prevents startup or writing new documents.
4. Port conflict. If the port that UTM listens on (usually 8080) is occupied by another process (a second UTM instance, another service on the same port), the module will not start — free up the port or change it in both the UTM and POS software settings simultaneously.

6. Expired GOST/RSA Keys#

How to check the expiration date. The validity period of certificates is visible on the UTM self-diagnostics page (certificates section) — approaching expiration is also usually displayed there in advance; you should monitor it several weeks prior, rather than on the day sales have already come to a halt.

Reissuance. It is done through the EGAIS personal account using a valid QES (qualified electronic signature) of the manager/authorized person — without a valid QES, it is impossible to reissue the certificate, so along with the expiration date of the GOST/RSA key, you should also monitor the expiration date of the QES itself.

How long it takes. Approximately — from a few hours to a couple of business days, depending on the workload of the certification authority and the correctness of the submitted documents; plan the reissuance in advance, not on the expiration date.

What happens to sales during this time. Alcohol sales (including beer, where EGAIS reporting is already mandatory) without a functioning UTM and valid certificates are not allowed — as a general rule, alcohol sales are suspended during the reissuance period, rather than trying to issue receipts "as is" expecting to fix them retroactively.

7. Daily Beer Write-Offs: Why and How to Automate#

Even when every single bottle is not scanned individually, alcohol inventory balances in EGAIS must match the actual venue stock — discrepancies surface during reconciliation and appear as shortages or surpluses that will have to be explained. Daily write-offs of the sold volume at the end of a shift using a write-off act based on POS sales is a way to keep these balances in line with reality without waiting for a scheduled inventory count.

Automation. In a mature inventory management system, write-offs in EGAIS are not created manually at the end of the day, but automatically based on actual POS sales for the shift: the system itself generates a write-off act for alcohol menu items and transmits it via UTM, so the cashier and accountant do not need to manually reconcile receipt by receipt.

8. Example#

A cafe sells draft beer from kegs. In the morning, a keg was put on tap and registered in EGAIS as normal. During the day, the cashier rings up another portion — the POS freezes with "no response from UTM". Step-by-step check from §2: UTM is running (step 1), the self-diagnostics page does not open (step 2) — the module has frozen. Restarting the UTM service (§5) restores operation within a minute, the receipt goes through as normal, and the sales accumulated during the failure are recorded with the next actual write-off.

9. How to do this in Cenaly#

• The EGAIS/UTM module is configured in the product catalog: the "alcoholic item" flag for an item and local UTM connection parameters are specified in the POS settings.
• The checkout side operates via Cenaly Hardware Bridge — the "Equipment" section displays the UTM connection status alongside the POS and scanner status, which is convenient for diagnostics per §2.
• Cenaly generates beer write-offs at the end of a shift based on actual POS sales for the shift — manually reconciling each receipt is not required.
• On-tap kegs are registered via a separate "tap connection" operation in the EGAIS module, after which sales from this tap are written off automatically when a receipt is issued.

10. Frequently Asked Questions#

UTM is running, but EGAIS still doesn't accept documents — should I contact the integrator right away? No, first go through the diagnostics in §2 step by step: most often the cause lies in certificates (§3) or system time (§4), rather than UTM itself — you can check this on your own in a couple of minutes using the self-diagnostics page.

Can I sell beer if UTM is temporarily unavailable, but the cash register is working? No — logging alcohol sales in EGAIS is mandatory; a working cash register without a working UTM does not replace EGAIS workflow. Resolve the UTM failure (§5) before continuing sales.

A keg was put on tap, but we forgot to register it in EGAIS — what now? Register it retroactively as soon as you notice, and reconcile the actual volume sold with cash register sales for that period — you may need a separate write-off act for the period prior to registration.

How does an EGAIS correction receipt differ from a cash register correction receipt under 54-FZ? These are two independent systems: a cash register correction receipt resolves a cash register compliance violation with the tax authority, whereas adjustment in EGAIS (via registration/write-off acts) is done separately using UTM tools — one document does not replace the other.

Related articles: Cenaly Hardware Bridge · marking at the POS · receipts not sending to OFD

This material is for reference purposes only and does not replace consultation with an EGAIS specialist or service integrator. Primary sources: documentation and guidance materials of FSRAR/EGAIS (fsrar.gov.ru), 171-FZ, 54-FZ.