How the Tax Service Analyzes Your Cash Register: ASK KKT and Audit Triggers

Every printed receipt is sent via the OFD not only to your personal account, but to the unified tax information system — ASK KKT. This is not an abstract threat of "someone watching somewhere," but a specific set of automated reconciliations capable of detecting a discrepancy faster than you can. We break down what exactly the tax authority sees in real time, which anomalies trigger an audit, and what you should monitor internally to avoid being targeted.

1. What the FTS Sees in Real Time via ASK KKT#

ASK KKT (the automated control system for cash registers) receives a copy of every fiscal document from the OFD: sales and return receipts, shift opening/closing reports, and correction receipts — along with all tags (amount, VAT rate, payment method, transaction type, seller TIN, shift number, FPD). The system cross-checks data for each specific cash register and for the merchant as a whole:

• how many shifts were opened/closed and whether this matches the expected operating hours;
• total revenue per cash register by day/week/month and its trends;
• the share of returns and correction receipts relative to total transactions;
• gaps — periods when the cash register should have been operating (based on historical data), but no receipts were recorded.

This is not "monitoring" in the sense of live surveillance over a specific person, but background analytics: it processes every receipt via the OFD regardless of whether it comes from a small kiosk or a chain of fifty locations.

2. Discrepancy between POS revenue and tax return#

One of the most direct automated triggers is matching total revenue according to register data (how much passed through cash registers across all of the merchant's locations) with the amounts in the tax return. If register revenue is higher, it is a signal that part of the payments was not reflected in accounting or that the tax return was filed with an error. The reverse situation (more in the tax return than in the register) also draws attention — this is often income received outside the register where a receipt was nevertheless required.

Register data is also reconciled separately against payment terminal turnover and bank statements — if the total amount of payments processed through the terminal differs significantly from the total of cashless receipts, this is also visible automatically without inspector involvement.

3. Complaint via the "Receipt Check" App#

A customer can scan the QR code on a receipt using the Federal Tax Service "Receipt Check" app, or if no receipt was issued at all, submit a complaint directly through the same app, specifying the time, location, and purchase amount. What happens next is typical:

1. The complaint is registered in the FNS system linked to the specific merchant/location.
2. The tax inspectorate checks it against OFD data: whether a receipt for a similar amount was issued by this POS at the specified time.
3. If the receipt is not found or a discrepancy is confirmed, an inquiry is sent to the merchant or an inspection event is scheduled.
4. A one-off complaint usually does not trigger an immediate on-site inspection, but an accumulation of several complaints for a single location is a noticeable risk indicator that the system takes into account when setting priorities.

What to do if an inquiry arrives and the complaint is justified can be found in the article "Fines under 54-FZ and How to Legally Avoid Them", including cases where the receipt can still be voluntarily corrected.

4. Is a sharp drop in average bill or revenue really a trigger?#

Yes, but not by itself — rather in combination with context. OFD analytics sees changes in metrics for a specific location over time: if the average bill or daily revenue suddenly and significantly drops relative to the location's own history, this can mean either an actual sales slump or that some payments are no longer being processed through the POS. The system does not distinguish these reasons on its own — it merely flags the anomaly as a reason for closer attention, not as proof of a violation.

Seasonal and explainable fluctuations (renovations, location change, a one-time promotion) are not a problem in themselves — but if you know about such a dip in advance, be prepared to justify the reason upon request, rather than guessing after the fact.

5. Test Purchase: How It Works#

1. The inspector or a person engaged by them makes a regular purchase disguised as an ordinary customer — they are not required to warn the seller in advance.
2. After the payment, the following are checked: whether a receipt was issued (printed or sent electronically upon the customer's request), whether mandatory details are correct (amount, VAT rate, payment attribute, item name), and whether the printed amount matches the amount paid.
3. If a receipt was not issued or the details are incorrect, a test purchase report is drawn up, which serves as the basis for further administrative offense proceedings.
4. If the receipt is in order, the inspection usually ends there, and the seller may receive no separate notification at all.

That is why basic operational hygiene — issuing a receipt for every payment, with no exceptions for "friends" or "small transactions" — is the most reliable protection against the consequences of a test purchase. For more details on who actually needs an online cash register and where the line of a "payment" is drawn, see the article "Who Needs an Online Cash Register in 2026".

6. Risk Indicators: What to Monitor Internally#

By regularly checking these same metrics internally for each outlet, you essentially look at your POS through the same eyes as automated tax authority analytics — and catch the issue before an inquiry arrives.

7. Automated STS: tax is calculated directly from POS data#

Automated STS is a special tax regime in which the tax authority calculates the tax amount itself based on POS and bank data, without tax returns or income/expense ledgers required from the business owner. This is possible precisely because all POS revenue is already visible to the tax authority in real time — Automated STS turns this transparency into the official basis for tax calculation, rather than just a background control tool.

The regime is suitable for small businesses with a straightforward income structure, where time saved on reporting outweighs scale limitations (revenue and employee count limits, availability limited to certain regions). If part of the revenue bypasses the POS register, Automated STS will not offer the same simplicity, as the tax base is formed specifically from cash register and bank data. Check the conditions and availability of the regime in your region on the tax authority website.

8. Example#

A coffee chain with three locations noticed that the share of refunds at one location tripled over a month compared to the other two, despite comparable revenue. Checking staff reports revealed that almost all refunds were processed by a single cashier at the end of the shift. The manager reviewed the reports and video footage before external analytics could flag the same indicator (detailed analysis in the article “POS Security: Passwords, Roles, Fraud”).

9. How to Do This in Cenaly#

• Reports on refunds and corrections broken down by employee and shift — in the POS → Receipts section (receipts); the same indicators used by external analytics are visible to you without waiting for a request from tax authorities.
• POS shift with expected/actual balance control highlights discrepancies upon closing, without waiting for monthly reconciliation.
• For physical POS terminals via Cenaly Hardware Bridge, the audit log is synchronized with fiscal data — reconciliation in case of suspicion uses a single source rather than scattered Z-reports.
• Cashier roles and PIN codes restrict high-risk operations (refund, correction) from front-line staff — reducing the very likelihood of an anomaly.

10. Frequently Asked Questions#

Does triggering a risk indicator mean we will definitely be audited? No, indicators are merely a basis for prioritizing attention within a risk-oriented approach, not an automatic trigger for an on-site audit. Many anomalies are resolved at the data reconciliation level without contacting the seller.

Is a single customer complaint via "Receipt Check" already an audit? Usually no, a one-off complaint is cross-checked against OFD data in the background. The trigger for an inquiry is a confirmed discrepancy or an accumulation of multiple signals for a specific location.

Can we see the same data that the FNS sees through ASK KKT? ASK KKT is not directly accessible, but all the data that enters it consists of your own receipts and Z-reports available in your OFD account and in the POS system (section 9).

Is AutoUSN available to everyone using an online POS? No, the regime has restrictions on income, number of employees, type of activity, and regions of application — check the details on the FNS website.

A sharp drop in revenue at one location in a chain — what to do in advance? Document the objective reason (renovations, seasonality) in writing and check against your own risk indicators (section 6) — if the discrepancy is explained by actual circumstances, this resolves most questions in case of an inquiry.

Related articles: fines under 54-FZ · POS security: passwords, roles, fraud · who needs an online POS in 2026 · POS shift without errors · USN and VAT-2026 in receipts

This material is for informational purposes only and does not replace professional accounting or legal advice. Primary sources: Federal Law No. 54-FZ "On the Use of CCP", Art. 14.5 of the Administrative Code of the RF, methodological recommendations and materials of the FNS on the operation of ASK KKT and the AutoUSN regime (nalog.gov.ru), FNS "Receipt Check" app.