---
title: "Error: Invalid JSON File When Importing FNO 200.00 into ISNA"
country: KZ
lang: en
author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti)
date: 2026-09-23
canonical: https://buhgpt.kz/suraqtar/oshibka-nekorrektnyy-json-fayl-pri-importe-fno-200-00-v-i-en
source: BuhGPT
---

# Error: Invalid JSON File When Importing FNO 200.00 into ISNA

> **TL;DR:** The problem occurs because the FNO 200.00 report form was generated before the 1C configuration update. Because of this, the export file does not match the current format expected by ISNA, and the system returns an "Invalid JSON file" error during import. How to fix it You nee

---

The problem occurs because the FNO 200.00 report form was generated before the 1C configuration update. Because of this, the export file does not match the current format expected by ISNA, and the system returns an "Invalid JSON file" error during import.

How to fix it

You need to recreate the report from scratch — do not try to re-upload the old file, but generate a new FNO 200.00 form after the database has been updated to release 3.0.71. After that, export the JSON file again and upload it to ISNA.

The procedure is simple:

1. Delete or stop using the old report form that was created before the update.

2. Reopen the FNO 200.00 form in the updated 1C database.

3. Generate the report again — the program will rebuild it according to the current format changes.

4. Export the new JSON file.

5. Upload the resulting file to ISNA.

As a rule, after the form is recreated, the file passes without errors, since the JSON structure is brought into line with the current requirements.

Frequently asked questions

Why can't the old file just be fixed manually?

The issue is not a single data error but the fact that the file structure itself became outdated after the configuration update. It is simpler and more reliable to recreate the entire report than to manually correct the JSON.

Do I need to update the database before recreating the report?

Yes, if the error appeared specifically because of a version mismatch, it is important that the report be generated in the current release — in this case, 3.0.71.

Can the error recur the next time the report is filed?

If the form is regenerated each time right before export (rather than using previously saved drafts), the risk of this error recurring is minimal.

---
_BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_