DocumentValidationError (code 9) — is a response from the fiscal server of the State Tax Service, which means that the receipt or report failed validation due to an error in the data of the generated fiscal document.
Code 9 is not the cause, but only an error class. The real cause is always specified in the text after the code.
This material is intended for users and system administrators who have basic skills in working with the operating system, Windows services, and Microsoft SQL Server. All actions described are performed at your own risk: incorrect changes to settings, services, or the database may lead to data loss or program inoperability. Before making changes, it is recommended to create an up-to-date backup of the database, check free disk space, and ensure there are no active users in the system. If you are not confident in the correctness of your actions or in understanding the consequences, you should contact technical support.
When the DocumentValidationError occurs
The error occurs during:
opening or closing a shift (Z-report);
switching the software ECR from offline mode to online mode.
The error is critical: the cash register cannot complete the operation.
How to understand what exactly caused error code 9
a message appears: Error code: 9 DocumentValidationError;
the receipt is not fiscalized / the offline package of documents cannot be accepted;
the error text contains an additional explanation (amount, address, key, time, etc.).
Why the software ECR returns code 9
The most common causes of error code 9:
1
mismatch of amounts in the receipt (rounding, partial payments);
2
mixing fiscal and non-fiscal goods;
3
invalid or revoked QES;
4
mismatch of the outlet address;
5
time synchronization error;
6
temporary failure on the side of the State Tax Service server.
Solution: what to do
Step 1. Be sure to read the text after «Error code: 9»
It is this text that determines the correction scenario. Below are typical cases.
Scenario A. Mismatch of amounts in the receipt
Error text (example):
The amount by lines X.XX is not equal to the total amount Y.YY
Cause
fiscal and non-fiscal goods in one receipt;
partial payment on an outdated program version;
the receipt was generated in offline mode with rounding errors.
Solution
1
Open Settings → Software ECR → Analytics.
2
Delete the problematic document (offline package).
3
Process fiscal and non-fiscal goods in separate receipts.
4
Update Torgsoft to version
2022.0.59 or higher.
Scenario B. Problem with the electronic key (QES)
Error text:
The signer's certificate is revoked (Revoked / EnCrSuperseded)
Cause
the key was revoked by the user at the key certification center.
Solution
2
Replace the key file:
in the software ECR settings;
in the employee (cashier) card.
3
If the error «No available business units» appears, register the key through the electronic cabinet of the State Tax Service (form 5-ПРРО).
Scenario C. Outlet address error (POINTADDR)
Error text:
Incorrect value of XML element '/CHECK/CHECKHEAD/POINTADDR'
Cause
The address in the Torgsoft settings does not match character-by-character with the address in the registration data of the State Tax Service.
Solution
1
Update the Torgsoft program to version 2022.0.59 or higher.
Scenario D. Time Stamp error
Error text:
The message cannot contain a content time stamp
Cause
local software ECR settings files are damaged.
Solution
1
Update the Torgsoft program to version 2022.0.60 or higher.
Scenario E. gzip decompression error
Error text:
Data decompression error 'gzip'
Cause
Temporary failure on the side of the State Tax Service server.
Solution
do not change anything in the settings;
How to check the result
the receipt is fiscalized and has a fiscal number;
the Z-report was successfully accepted by the tax server;
in the software ECR analytics, the document(s) status is — «Sent».
Prevention
use the latest current version of Torgsoft;
monitor the validity period of the QES;
Summary
DocumentValidationError (code 9) — is not a program error, but a rejection from the State Tax Service server.
The algorithm is always the same:
read the text after the code → identify the scenario → eliminate the cause → repeat the fiscalization.
Go back to the previous step