--- title: "GISM Attached Files reference (GISM Exchange Protocol) in \"Trade Management for Kazakhstan\": where marking exchange files are stored and how to work with them" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-23 canonical: https://buhgpt.kz/suraqtar/spravochnik-gismprisoedinennye-fayly-protokol-obmena-gism-en source: BuhGPT --- # GISM Attached Files reference (GISM Exchange Protocol) in "Trade Management for Kazakhstan": where marking exchange files are stored and how to work with them > **TL;DR:** Verified on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4). You sent a package to the labeling system, and the exchange "hung" with a red error. In the exchange log there's a line like "received a response with an error," but what exactly was sent and what ca --- Verified on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4). You sent a package to the labeling system, and the exchange "hung" with a red error. In the exchange log there's a line like "received a response with an error," but what exactly was sent and what came back — you can't see. That's where this reference guide comes in. It holds the actual exchange files: the XML request that was sent, and the response that came back. You open it, look at the error text from the operator — and immediately understand what's wrong: an incorrect product code, an expired certificate, a duplicate GTIN. No need to guess and resend at random. Let's be upfront about the nature of this object. GISMAttachedFiles is a service (technical) catalog for storing attachments. Its synonym in the configuration is "GISM Exchange Protocol." It is subordinate to the "File Handling" mechanism of the standard subsystems library and stores binary attachments linked to objects exchanged with the labeling system. This is not an accounting document: it does not generate accounting entries, does not create e-invoices/e-waybills, and does not move cost-of-goods or VAT registers. All it "does" is reliably store a file, show it to you, and let you sign it with a digital signature. That's why I honestly address the sections on accounting entries below: they're not here, and I explain why. 1. Purpose The catalog stores attached files (XML packages of requests and responses, receipts, protocols) for exchange with the state labeling system — GISM. You access it when you need to view the contents of a specific exchange, find the text of an operator error, or save/sign a file manually. 2. Where to find it There is no direct menu item to "open the list of all attachments" for a service catalog — and that's normal. You almost always reach the files from the owner object, not from a general list. - Usual path: section Reference and Administration → GISM Integration / Exchange with the Labeling System → open the desired document or exchange record → command Attached Files (the "Files" link paperclip). - From the exchange workstation: GISM exchange log → double-click a row → on the package card, the link Files / Exchange Protocol. - Open the object's list directly in 1C: Main menu → Service → Navigate by Navigation Link (or Ctrl+navigation key) → paste: e1cib/list/Справочник.ГИСМПрисоединенныеФайлы This opens the service list of all attachments. It's useful for an admin and for incident review; a regular accountant will find it more convenient to enter from the document. 2a. How to find out your release Menu Help → About the Program (or the "i" icon). The window that opens shows two lines: the platform version (e.g., 8.3.24.xxxx) and the configuration release — "Trade Management for Kazakhstan, edition 3.4 (3.4.5.21)." This guide is written for release 3.4.5.21. If your number is different — the location of commands may differ slightly. 3. How to fill it in (file card fields) A file card is rarely created manually — usually an attachment appears automatically during exchange. But you can open it, complete it, and sign it. Here's a breakdown of each field: what it's for and what happens if filled incorrectly. Field What it's for What happens if filled incorrectly Name (required) The file's name in the list. You use it to find the package you need. An empty name cannot be saved. A vague name ("File1") — later you won't find the right response among dozens of exchanges. Write meaningfully: "GISM Response 09.23." Owner (required, service field) The object the file is attached to (exchange record/document). Filled automatically when added "from the object." Don't touch it manually. Changing the owner will "detach" the file from the exchange — it will be lost from the document's card. File / data (required) The body of the attachment itself — XML, PDF, receipt. Add / Upload button. Without data, the card is meaningless. Upload the wrong file — you'll mislead yourself when analyzing the error. Extension File type (xml, pdf, p7s). Populated from the name. Wrong extension — the file will open with the "wrong" program or not open at all. Comment Your note: "resent," "product code error." Doesn't affect the exchange, but saves colleagues time. Don't be lazy. Author Who added the file. Set to the current user. Rarely changed; useful when reviewing a disputed situation to see who uploaded it. Creation / modification date When the file was added and edited. Set automatically. Manual editing not needed — you'll lose the exchange chronology. Signed with digital signature (flag) Shows that a digital signature is attached to the file. Set by the Sign command. Don't remove manually — you'll "lose" the legally significant signature of the package. Encrypted (flag) The file is protected by encryption. An encrypted file cannot be read without the recipient's certificate — this is normal for part of the packages. The required minimum for the card to work: Name, Owner, the file data itself. Everything else is auxiliary. 4. Worked example Situation. On September 23, 2026, you send a notification of putting a batch of labeled goods into circulation to GISM. The exchange completed with an error. What you do step by step: - You open the GISM exchange log, find the row from 09.23.2026, status — "Error." - Following the Files link, you go into the GISMAttachedFiles catalog. There are two cards: Request_09232026.xml and Response_09232026.xml. - You open Response with a double-click → View. You see the text: Product code (GTIN) not found in the national catalog. - You understand the cause: the product isn't registered in the labeling catalog. You fix the item card (add the correct GTIN), form the package again, and resend it. - In the Comment of the old file, you write: "GTIN corrected, resent 09.23 15:40" — so a colleague doesn't resend a duplicate. So where are the accounting entries? There aren't any — and that's correct. The exchange file itself doesn't change accounting. Accounting consequences will appear later, when you post the sale/receipt document for the labeled goods. For illustration, I'll show what "real" accounting entries for such a batch would look like in Kazakhstani accounting — but they are generated by the sales document, not by this catalog. Suppose you then sold this batch for 1,160,000 ₸ including 16% VAT, with a cost of goods of 700,000 ₸: Operation Dr Cr Amount, ₸ Revenue from sale (with VAT) 1210 6010 1,000,000 VAT payable (16%) 1210 3130 160,000 Cost of goods written off 7010 1330 700,000 Payment received to account 1030 1210 1,160,000 VAT check: 1,000,000 × 16% = 160,000 ₸. These exact amounts will go into the e-invoice via the IS ESF system, and the movement of labeled goods will be documented by an e-waybill. The GISM protocol file you examined in this catalog is the technical proof that the labeling codes were correctly sent to the system before shipment. 5. Types of operation There are no separate "operation types" as with a document — there is a set of actions on a file: - View — open the content (XML/PDF/receipt). - Save as… — export the file to disk (e.g., to send to operator support). - Edit / Open — open with an external program and return the edited version. - Sign with digital signature — attach a digital signature to the file. - Encrypt / Decrypt — if the package requires encryption. - Version management — view the file's change history, roll back to a previous version. - Mark for deletion — remove an unnecessary attachment (actual deletion — via "Delete marked objects"). 6. What is generated during operation Honestly and to the point: - There are no accounting entries. The attachments catalog does not move accounts 1210/1330/3130/6010/7010, etc. - It doesn't create e-invoices or e-waybills either. Electronic documents are generated by sales/receipt documents and the exchange module with the IS ESF and the e-waybill system. The GISM file is only an exchange protocol for labeling. - Movements in accounting registers (cost of goods, settlements, VAT) — it does not perform. - What actually happens: the file is saved in storage (volume or database), its version, author, and date are recorded, and upon signing, a digital signature is attached, with the "Signed"/"Encrypted" flags updated. All this is service data of the "File Handling" subsystem. If you need accounting entries and electronic documents — work with the owner document (sale, receipt, e-waybill); come here only for the exchange content. 7. Printed forms The catalog has no regulated printed forms of its own — it is not a primary document. Something else is available: - View the file's content (XML/PDF) right in 1C. - Print the opened PDF/receipt using the viewer program. - Save to disk for subsequent printing or sending to the operator/support. Printed forms (invoice/e-invoice, waybill, e-waybill) should be sought at the related sales and receipt documents. 8. Common errors "File not found in storage volume" The file is physically not on disk (the volume was moved/deleted, no access to the network folder). Check in the section Administration → File Handling Settings → File Storage Volumes whether the directory is accessible and the user has rights. "Insufficient rights to view the file" The user does not have the role for working with attached files. The administrator adds the right via Administration → User and Rights Settings. "Failed to decrypt the file: certificate private key not found" The package is encrypted for a certificate that isn't on this workstation. Decrypt on a computer with the required digital signature key, or obtain the file in unencrypted form. "File locked for editing by another user" Someone opened the file for editing and didn't finish (the "Finish editing" button). Ask the colleague to close it or remove the lock via the version list. "GISM response: product code (GTIN) not found in the national catalog" This is not a 1C error but a labeling operator error. Register the product in the national catalog, fix the GTIN in the item card, and resend the package. "Exchange completed with a certificate error: expired" The digital signature certificate used to sign the package has expired. Reissue the digital signature and re-sign the file using the Sign command. 9. FAQ 1. Can a file be created in this catalog manually? Technically yes — via the list using the navigation link, or with the "Add" command from the owner object. But usually attachments appear on their own during exchange with GISM; they're rarely added manually, more often to attach a receipt. 2. Does this catalog generate 16% VAT entries? No. Entries and VAT (16% in 2026) are generated by the sales/receipt document. Here there are only exchange files. 3. Why does the catalog have the synonym "GISM Exchange Protocol"? Because it stores exactly the protocols (requests and responses) of exchange with the state labeling system. The name GISMAttachedFiles is technical, the synonym is descriptive. 4. How do I view the error text returned by the operator? Open the response file card and click "View." The error text will be inside the XML — look for the node with the description (result/error). 5. Where are these files physically stored? Either inside the information base, or in storage volumes on disk/server — as configured in "File Handling Settings." This affects the database size: volumes offload it. 6. Will deleting a file also delete the exchange itself? No. You'll only delete the attachment. The exchange record (owner) will remain. But you won't be able to restore the package's content after deletion. 7. Do these files need to be signed manually with a digital signature? As a rule, the signature is applied automatically when sending. Manual signing with the "Sign" command is needed if you generate or resend the package outside the standard exchange. 8. Does it generate e-invoices or e-waybills? No. The e-invoice is sent via the IS ESF system from the sales document, the e-waybill — from the corresponding goods accompanying document. The labeling attachments catalog is only adjacent to them in meaning. 9. Can this file be used to tell whether the labeling codes were sent correctly? Yes. The request file shows which codes/GTINs were sent, and the response file shows whether the operator accepted them. This is your proof of correct labeling before shipment. 10. What should I do if the file opens as "gibberish"? It's most likely encrypted or in a binary format. Decrypt it with the required certificate, or save it to disk and open it with the appropriate program (XML — with a browser/editor, p7s — with a digital signature tool). 10. Related documents - Generated on the basis of: records and documents of exchange with the GISM labeling system (notification packages for putting into circulation, taking out of circulation, relabeling). The file is always subordinate to the owner object. - Related in meaning to: sales and receipt documents for labeled goods — these are what generate accounting entries (accounts 1210, 1330, 3130, 6010, 7010, 1030) and produce the e-invoice (IS ESF) and e-waybill. - What is opened alongside it: the GISM exchange log, the item card (GTIN/labeling code), digital signature settings, and file storage volume settings. How to find out your release Help → About the Program. This shows the "1C:Enterprise" platform version and the configuration release. This guide has been verified on "Trade Management for Kazakhstan," edition 3.4, release 3.4.5.21. If your number differs — check the update contents: the location of file handling commands may have changed. Prepared for release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4). --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_