Criteria for mandatory Torgsoft update
Updating the Torgsoft software is mandatory if the current version:
-
does not comply with current legal requirements;
-
causes cash operations to stop;
-
generates incorrect fiscal documents or reports;
-
is incompatible with the current software or hardware environment.
In such cases, updating is a top-priority technical step, not a recommendation.
1. Legal requirements (pECR, fiscal receipts)
An update is mandatory if:
-
New mandatory fiscal receipt details have changed (QR code, change due, payment methods, payment systems, etc.).
-
The receipt format has been changed in accordance with Ministry of Finance orders (in particular, No. 601, No. 632).
-
The STS does not accept or rejects generated receipts.
Minimum versions:
-
From 01.03.2025 — version 2022.0.44 or later is required.
-
To fix errors in annual pECR reports starting from version 2022.0.43 — upgrading to 2022.0.44 is mandatory.
If you do not update:
-
incorrect fiscal documents are generated;
-
non-compliance with STS requirements occurs;
-
the risk of penalties increases.
2. Critical technical errors (pECR / database)
An update is mandatory if you have symptoms:
-
SQL “VALUES” error while closing the Z report.
-
DocumentValidationError during fiscalization.
-
The checkout freezes with the DeviceBusy message.
Mandatory actions
-
Update the software to:
-
2022.0.40+ — for the DeviceBusy error.
-
2022.0.57 / 2022.0.59 — for DocumentValidationError, mixed goods, or rounding issues.
-
Update SQL Server:
-
from SQL Server 2005 → 2014 or later (older versions do not support the current query logic).
If you do not update:
-
you cannot close the shift;
-
fiscal operations may not complete / may be lost;
-
the checkout is blocked and work stops.
3. Banking terminals and payment methods
An update is mandatory if:
-
you connect a new payment terminal model (Newland, PAX, etc.);
-
the bank/acquirer switches to a different protocol or updates integration requirements;
-
you use Tap to Pay or mobile acquiring (a smartphone as a terminal).
Minimum requirements
-
Mobile app — version 2.0.
-
A compatible version of the database and the Torgsoft software.
If you do not update:
-
the terminal works unstably or periodically disconnects;
-
there is no response/confirmation from the bank;
-
payments do not go through, and payment acceptance may be impossible.
4. Compatibility with the operating environment (Windows / SQL / services)
An update is mandatory if:
-
Windows 11 (24H2) is used, or the system has received security updates that block outdated components;
-
the TorgSoftService services do not start or run unstably;
-
SQL Server is incompatible with the current OS version;
-
critical synchronization errors or mobile app issues appear.
Mandatory actions:
-
switch to the current Torgsoft release (or a beta version if the issue occurs specifically on the application server and has already been confirmed as compatibility-related);
-
if needed — update/reinstall the components the services and database depend on (including a compatible version of SQL Server).
Updating Torgsoft is mandatory if there is at least one sign:
-
DocumentValidationError during fiscalization;
-
the receipt has missing or incorrect change due;
-
the checkout freezes while closing the Z report;
-
the payment terminal does not return a response / the payment is not confirmed;
-
fiscal documents do not meet STS requirements or are rejected.
Algorithm: in such cases, troubleshooting starts with checking the version and updating the software to a compatible current release.
-
25.01.2026
Torgsoft-Hybrid Installation and Setup
Torgsoft-Hybrid setup guide: technical requirements, installation, hardware connection, and offline mode operation with subsequent data synchronization.
-
08.01.2026
Transferring Torgsoft to another computer or server
Transferring Torgsoft to another computer or server: backup, SQL database, license, settings and safe launch without data loss
-
06.01.2026
Torgsoft database optimization: indexes and statistics
How to speed up Torgsoft: optimizing indexes and SQL statistics, signs of need, when to perform and what to do with a 10 GB limit









Go back to the previous step