Yandex services are integrated with the ticket offices of partner restaurants, delivery services, and taxi companies. The receipt is generated automatically when the order is transferred through the platform. If there is a technical failure on the platform side — an update, overload, or an API error — the receipt may not be generated at all. According to the law 54-FZ, a check is required when calculating with an individual, its absence threatens with a fine under art. 14.5 of the Administrative Code.
The Federal Tax Service allows two options for correcting the situation. The first is to issue a sales receipt manually after the system is restored: it indicates the date and time of the actual calculation, the amount, the calculation attribute "Arrival", the nomenclature and the VAT rate. The second is a correction check, if the check was not punched at the time of the calculation at all. It specifies the type of correction "independently", the basis (description of the failure, date and time of calculation) and the amount. The correction receipt goes to the tax service through the fiscal data operator — this serves as proof of the voluntary correction of the error.
A note to Article 14.5 of the Administrative Code allows you to avoid liability if the violation is eliminated before it is detected by the inspectors. The condition is a documentary confirmation of the failure. Without it, inspectors have the right to classify the situation as a lack of a receipt, rather than a technical incident.
The evidence base is based on several sources. From the platform side: a screenshot of the error or the "unavailable" status in your personal account, a letter or response from Yandex support about the accident, integration logs with a visible unanswered request. From the business side: bank statement or payment aggregator, internal order report with date, time and amount, correspondence with the client.
Practical scenarios show how it works. Restaurant: API failed at 6:30 p.m., 12 orders were left without receipts. At 19:15, Yandex technical support confirmed the incident. At 20:00, the restaurant manually punched through the receipts for all 12 orders with the date and time of 18:30. The support letter and the upload from the accounting system provided sufficient evidence. Delivery service: 30 unbroken checks accumulated during the day, and the next day they issued correction checks for each amount based on "technical failure of integration with the platform, confirmed by a support letter." Taxi company: the driver accepted the payment, the cashier did not respond. At the end of the shift, a correction receipt was issued with the cashier's log attached.
Common errors in case of failures: replacing the receipt with a terminal slip (the slip does not contain a fiscal sign, FN and FPD numbers, and is not transmitted to the tax service), using strict reporting forms or CRM printouts instead of a fiscal document, ignoring unbroken receipts even with a short failure.
Incident documents should be kept for at least five years — this is the shelf life of cash register documents. The rules in case of a failure should be prescribed in advance: appoint a person responsible for fixing the problem, set up logging of integration statuses and auto-save of API responses, keep the platform's technical support contacts at hand.
The regulatory framework of the issue: Law No. 54-FZ of 05/22/2003, Order of the Federal Tax Service of 09/14/2020 No. ED-7-20/662@ (mandatory details of fiscal documents, including a correction receipt), art. 14.5 of the Administrative Code with a note on the voluntary elimination of violations.
Related materials:
- The Federal Tax Service clarified its position on paper transportation documents: inspections will begin at the end of 2026 — the same approach of the Federal Tax Service: to prove the cause of the failure, and there may be no fine
- Digital ruble from September 1, 2026: who is required to accept and how to keep records is another requirement for accepting payments from buyers
- Internal audit in SMEs: how to keep processes and financial flows under control — how to set up regulations in case of failures in advance
