In 2026, if a technical error occurs when importing a TRF into ITAS, the accountant should update 1C to the current release, create a new report instance and generate the file again. The Tax Code does not establish a special procedure for correcting JSON files: Article 111 of the Tax Code of the RK governs the use and registration of cash registers, rather than the submission of tax reporting forms (Article 111 of the Tax Code of the RK).
What the new ITAS is
ITAS stands for the Integrated Tax Administration System. In the rules for the use of cash registers, the ITAS information system is used as the information system of the state revenue authorities through which registration actions involving cash registers are performed. The Tax Code provides for the registration of cash registers, amendments to registration card details and deregistration of cash registers, while the procedure for using cash registers is established by the authorized body (Article 111 of the Tax Code of the RK).
The provisions of Article 111 of the Tax Code of the RK relate specifically to the use of cash registers. They do not establish technical requirements for TRF JSON files or the procedure for resolving errors when importing reports into ITAS.
When working with TRFs, the technical compatibility of the accounting software and the upload format is important for the accountant. A form created in 1C before an update was installed may retain the previous data structure. Therefore, after updating the database, it is advisable not only to repeat the export but also to create a new report instance.
When diagnosing the error, it is necessary to consider not only the installed software release but also exactly when the report was created: before or after the update.
New ITAS account: what to check before submitting reports
Before exporting and importing a TRF, it is useful to perform a brief technical check:
- make sure that the current release of the configuration being used is installed in 1C;
- for “Accounting for Kazakhstan,” use the current 3.0.74.x release line as a reference;
- check for patches intended for the installed release;
- create a new report instance after the update;
- complete the form again and run the built-in validation;
- generate a new file for upload to the ITAS account;
- do not upload the old file if the release or report format changed after it was generated.
Updating the database and recreating the form are two separate actions. Installing the current release updates the reporting generation mechanism; however, a previously created report may retain the data and structure generated by the previous version. Therefore, exporting the same instance again does not always resolve the technical error.
If the new file is accepted by the system, the instance generated after the update should be treated as the working version. If the error persists, the accountant should record the name of the TRF, the tax period, the full release number, the list of installed patches, the message text and the stage at which the failure occurred. This information can be used to sequentially check file generation in 1C and its upload to the account.
“Invalid JSON file” error when importing TRF 200.00
When importing TRF 200.00, ITAS may display the message “Invalid JSON file”. This technical message does not itself indicate which report field caused the rejection. If the form was created before 1C was updated, it should be recreated in the current release and a new file generated using the program’s standard tools.
Practical procedure:
- Check the full number of the installed 1C release and whether the patches intended for it are installed.
- Save the information from the previously created form that is required for reconciliation.
- Create a new TRF 200.00 report in the updated database.
- Complete it again and run the validation provided in 1C.
- Reconcile the figures in the new form with the accounting records.
- Generate a new file and repeat the import into ITAS.
Do not manually modify the structure of the JSON file without an official description of the applicable format. Such editing may damage the document structure or create discrepancies between the report in 1C and the file being uploaded. It is safer to generate a new file using the standard tools of the current version of the accounting system.
Why TRF 300.00 has no save function for ITAS
If TRF 300.00 does not have a command to save the file for subsequent submission to ITAS, first check the full release number and installed patches, and then create a new report instance. For “Accounting for Kazakhstan,” the current release line in 2026 is 3.0.74.x; recommendations for the older versions 3.0.71 and 3.0.71.1 should not be used as guidance for the current database.
The verification sequence may be as follows:
- confirm the full release number, rather than only the main configuration version;
- check whether the patches intended for this release are installed;
- create a new instance of TRF 300.00 after the update;
- check whether the save command is available in the new form;
- complete and validate the report if the required command is available;
- generate a new file for submission.
If the command is still unavailable in the new form instance, the specialist maintaining 1C should be provided with the full release number, the list of installed patches, the name of the TRF and a description of the missing command. Passwords, electronic signature keys and other confidential data are not required for such diagnostics and should not be provided.
What an accountant should do if the new ITAS fails
First, retain evidence of the problem: a screenshot, the exact error text, the date, time and stage of the operation. Then check the 1C release and the availability of patches, and generate a new report instance. After a successful import, verify in the account that the correct form, tax period and report type have been accepted.
If the reporting deadline is approaching, it is better not to postpone the technical check until the last day. The deadline is determined by the type of TRF and the tax period. Article 111 of the Tax Code of the RK does not contain such deadlines because it governs the use of cash registers (Article 111 of the Tax Code of the RK).
Do not create several final files without tracking their versions. Give working files clear names, specify the period and mark which instance was generated after the update. This reduces the risk of uploading an outdated version again.
Frequently asked questions
What does ITAS mean? — It is the Integrated Tax Administration System used by the state revenue authorities.
Why does ITAS reject the JSON file for TRF 200.00 after 1C is updated? — One technical reason may be that the report was created before the update. Create a new instance in the current release, recheck the figures and generate a new file.
What should I do if TRF 300.00 has no save command for ITAS? — Check the full release number and installed patches, then create a new report. The current release line for “Accounting for Kazakhstan” is 3.0.74.x.
Can I simply export the old form again? — Exporting it again may not resolve the error if the report was created by a previous version of the program. After the update, it is advisable to create a new form instance and generate the file again.
Can I correct the JSON file manually? — You should not manually modify its structure without an official description of the format. Use the standard file generation functionality in the current 1C release.
Where can I check the submission deadline for a specific TRF? — The deadline is determined by the type of form and the tax period based on the relevant provisions of tax legislation. The provisions on the use of cash registers in Article 111 of the Tax Code of the RK do not regulate TRF submission deadlines (Article 111 of the Tax Code of the RK).