XML of corrected SNT does not upload in 1C

Short answer: most often a corrected SNT fails to load into 1C not because of a program error, but because of the wrong import section and an incorrect file format. A corrected SNT must be loaded into the "Received SNT" section (not "Issued"), and from the IS ESF portal you should export specifically the XML file of the corrected consignment note, not a file in xsl format. Once these two conditions are met, the import into 1C:Accounting for Kazakhstan goes through and the data is updated correctly.

Why the error occurs

An SNT (consignment note for goods) in the information system has a "direction": for one party to the transaction it is issued, for the other it is received. When you open the wrong section in 1C, the program expects a document of a different type and cannot match the loaded XML with the existing data. Outwardly this looks like "the file does not load" or "the data is not updated," although the file itself may be correct.

The second typical reason is the format of the exported file. On the IS ESF portal a document can be saved in different representations. To load it into an accounting system you need a machine-readable XML, not xsl (a visual/tabular representation intended for viewing and printing, not for import). If you export the wrong format, 1C will not recognize the data structure.

The logic of "Issued" and "Received"

• Issued SNTs are the consignment notes that you drew up and sent as the sender of the goods.
• Received SNTs are consignment notes that arrived to you from a counterparty, including their corrected versions.
• A corrected SNT that comes to you from a supplier/sender is an incoming document, so its place is in the "Received SNT" section.

If you confuse the direction and try to import a corrected consignment note into "Issued," the data update will not go through, even if the XML itself is generated correctly.

Step-by-step correction procedure

1. Determine the direction of the document: a corrected SNT that arrived to you belongs to received, not issued.
2. Go to the IS ESF portal and find the required corrected consignment note (not the original one it replaces).
3. Export the document specifically in XML format. Make sure you downloaded a file with the .xml extension, not .xsl.
4. In 1C:Accounting for Kazakhstan, open the "Received SNT" section.
5. Start the import and specify the saved XML file of the corrected SNT.
6. Verify that the document has loaded and the data for the consignment note has been updated.

How to make sure you exported exactly XML

• Check the file extension: it should be .xml. The .xsl format is not suitable for import.
• When opening the XML in a text viewer, you see the tagged data structure, not a ready-made printed form.
• If the portal offers several saving options, choose the export of the document data, not "print" or "view."

What else to check if the file still does not load

When the section is chosen correctly and the format is XML, but the import still does not go through, pay attention to the following:

• Relevance of the 1C release. The formats of electronic documents change periodically; on an outdated configuration the structure of the new XML may not be recognized. Check that the current configuration update is installed.
• Matching of counterparty and organization. The participants of the consignment note (organization and counterparty) must be entered in the database with correct details (BIN/IIN), otherwise there is nothing to match the document against.
• Presence of the original SNT. A corrected consignment note is linked to the original one. If the original document is missing from the database, loading the correction may not work as expected.
• File integrity. Make sure that the file was not damaged or truncated during download, and that you are loading exactly the required document, not the old (original) one.
• Document status on the portal. Check that the corrected SNT on the IS ESF portal has the correct status (drawn up/confirmed) and is not in an intermediate state.

Typical mistakes

• Importing a corrected SNT into the "Issued" section instead of "Received."
• Exporting a file from the portal in xsl format instead of XML.
• Downloading the original rather than the corrected version of the consignment note.
• Attempting to load on an outdated configuration release.
• Absence in the database of the required counterparty or the original SNT to which the correction relates.

What to check

• The import section — "Received SNT", not "Issued."
• The file format — XML (extension .xml), not xsl.
• You exported exactly the corrected consignment note, not the original.
• The details of the organization and counterparty in the database match the data of the consignment note.
• The current release of 1C:Accounting for Kazakhstan is installed.
• After loading, the data for the SNT in 1C has actually been updated.

Conclusion: the key point is not to confuse the "Issued" and "Received" sections during import and to ensure that the export from the IS ESF portal is done specifically in XML, not in xsl. Meeting these conditions, along with a current release and correct details, ensures the successful loading of a corrected SNT and the update of data in 1C.