--- title: "VerlionsSuppliedExtensions\" reference guide in UT for Kazakhstan 3.4: what it is and what it's for" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-24 canonical: https://buhgpt.kz/suraqtar/spravochnik-versiipostavlyaemyhrasshireniy-v-ut-dlya-kaza-en source: BuhGPT --- # VerlionsSuppliedExtensions" reference guide in UT for Kazakhstan 3.4: what it is and what it's for > **TL;DR:** Verified on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4). You updated the configuration, opened the database — and something new appeared in the extensions list that you didn't install. Or the opposite: the SNT/ESF printed form stopped printing after the up --- Verified on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4). You updated the configuration, opened the database — and something new appeared in the extensions list that you didn't install. Or the opposite: the SNT/ESF printed form stopped printing after the update, and the vendor's tech support asks: "What is your version of the delivered extension?". This is where you end up in the "VersionsOfDeliveredExtensions" catalog. Let's warn you right away: this is a service catalog. The accountant doesn't enter documents here or make postings. But understanding what's stored here and why it shouldn't be deleted manually is useful — otherwise one wrong move can break the database's updatability. 1. Purpose The catalog stores versions of extensions delivered together with the configuration (by the vendor — 1C company or its partner for the KZ version). Each record is a specific release of one delivered extension: its binary image, version number, and service attributes. The mechanism is needed so that when the configuration is updated, accompanying extensions (e.g., customizations for ESF IS, SNT, fiscalization) are automatically pulled in and updated, not just the main release. 2. Where to find it There is no direct item in the "Sales", "Purchases" or "Treasury" sections for this catalog — it is not intended for daily work. You can open it in two ways. - Through the extensions list: "Master data and administration" → "Administration" → "Printed forms, reports and processing" → "Extensions" (or "Main menu" → "Settings" → "Extensions" at the platform level). Here you see what is installed. - Directly via a navigation link. Menu "Service" → "File" → "Go to navigation link" (or the shortcut in the main menu), paste: e1cib/list/Справочник.ВерсииПоставляемыхРасширений The list will open even if there is no item in the menu. This is the most reliable way if you need the actual contents of the catalog, not the extension management window. 2a. How to find out your release Everything described below is tied to the version. To see it: "Help" → "About the program" (the ⓘ icon in the top right corner or the main menu). The window that opens will have two key lines: - Platform version (e.g., 8.3.24) — the 1C:Enterprise engine. - Configuration version — this should show "Trade Management for Kazakhstan, 3.4.5.21". If your release is lower, the set and versions of delivered extensions will be different — check against your own number. 3. How to fill it in The main rule: you do not fill in this catalog manually. Records are created and updated by the extension delivery mechanism itself when the configuration is updated. You should only view it here. Below is what the fields mean, so you understand what you're looking at. The exact set of attributes is an internal, version-dependent part of the mechanism, and it may differ between platform releases. Field What it's for and what happens with an incorrect value Name / Version (required) The extension release number. From it, the mechanism understands whether the delivery is newer than the one already installed. If you manually set a lower number, the update will "decide" there is no new version and won't apply it. Owner / Extension (required) Reference to the delivered extension itself that the version belongs to. This link must not be broken: an orphaned version won't be picked up. Binary data (extension image) The actual .cfe content of the extension in storage. This is exactly what the platform connects. If empty or corrupted, the extension won't install, and printed forms/processing will disappear. Delivery/update date When the version arrived with the update. An informational field for incident analysis. "Disabled"/"Active" flag Controls whether this version is applied. Deactivating the needed one will disable functionality (e.g., a fiscal receipt customization). Checksum / identifier Service integrity check. A discrepancy is a signal that the image has been tampered with or corrupted. If you need to add your own extension (not delivered by the vendor) — this is done not here, but in the "Extensions" window with the "Add from file" button. This catalog is only for delivered ones. 4. Worked example The catalog has no postings — it's not a business transaction, but an element of the update mechanism. So the "example" here is a breakdown of what you'll actually see. Situation. You had Trade Management for Kazakhstan 3.4.5.18, with the delivered extension "Exchange with ESF IS" version 1.0.7. You updated to 3.4.5.21. You open e1cib/list/Справочник.ВерсииПоставляемыхРасширений and see two rows for one owner: Owner (extension) Version Delivery date Active Exchange with ESF IS 1.0.7 12.06.2026 No Exchange with ESF IS 1.0.9 23.09.2026 Yes What happened: the update brought version 1.0.9, the mechanism marked it active, and left the previous 1.0.7 in history with the "inactive" flag. There are no amounts, tenge, or VAT here — and there shouldn't be, the catalog is technical. How this relates to money. The "Exchange with ESF IS" extension itself is involved in issuing the ESF for sales. Postings are generated not by it or this catalog, but by the sales document. For example, a typical sale of goods for 116,000 ₸ (incl. VAT 16% = 16,000 ₸), cost price 70,000 ₸: Dr Cr Amount, ₸ Description 1210 6010 100,000 Revenue from sale (excl. VAT) 1210 3130 16,000 VAT payable 16% 7010 1330 70,000 Cost of goods sold written off And the delivered extension (whose version you looked at in the catalog) only ensures correct upload of this sale to the ESF IS. That's the whole connection: the catalog is about the version of the customization, the money is in the primary document. 5. Operation types There are no separate "operation types" like a document has for this catalog. There are only record states managed by the mechanism: - New version delivered — a record is created upon update. - Version active — this is the one applied in the database. - Version inactive (in history) — a previous release, kept for rollback. 6. What is generated upon posting The catalog is not posted and does not create movements in accounting registers, does not generate Dr/Cr postings, does not issue ESF or SNT. All of this is done by documents (sales, purchases, payments), not the service version catalog. The only "effect" of changing a record here is enabling or disabling the corresponding extension at the next database startup. Electronic documents (ESF in ESF IS, SNT) are generated by sales/transfer documents, and the extension from this catalog only helps upload them correctly. 7. Printed forms The catalog has no printed forms of its own — there's no need to print the version number. If you need to record the composition of what's installed, use the "Extensions" window: there you see the list with versions, and can take a screenshot for tech support if needed. Printed forms (invoice/ESF, delivery note, SNT) belong to documents, not to this object. 8. Common errors "Failed to connect extension… integrity violation". Appears when the version image is corrupted or the active flag is removed from the needed record. Fix: don't edit the catalog manually — repeat the configuration update to 3.4.5.21 so the mechanism reinstalls the correct version. "Extension update not completed" / extension remains the old version. Usually due to exclusive mode: other users are in the database. Fix: end all sessions, log in exclusively and run the update again. "Extension configuration load error" after manually deleting a record. If you deleted a version row in the catalog, the delivered extension becomes orphaned. Fix: restore from backup or reinstall the update — you cannot manually "recreate" the version. Extension disabled itself. Often due to platform version incompatibility. Check in "Help" → "About the program" that the platform is not lower than required for release 3.4.5.21, and update it. 9. FAQ 1. Can old versions be deleted from this catalog? Manually — no. Inactive records are kept for rollback and are cleaned up by the mechanism itself. Manual deletion breaks updatability. 2. Why do I have several rows for one extension? This is the version history: one (the latest) is active, the rest are previous releases kept in case of rollback. 3. Are there postings here or an effect on VAT? No. The catalog is a service one. VAT 16%, revenue and cost price are generated by sales and purchase documents, not by it. 4. How do I know which version of the extension is currently working? Open e1cib/list/Справочник.ВерсииПоставляемыхРасширений and find the row with the active flag for the needed owner, or check the "Extensions" window. 5. Can I add my own extension here? No. Your own extensions are installed via "Extensions" → "Add from file". This catalog is only for vendor-delivered ones. 6. After updating, ESF/SNT printing disappeared — is the catalog to blame? Indirectly: the delivered extension's version probably wasn't activated. Repeat the update exclusively; if the error repeats, contact support with the release number and the version from the catalog. 7. Do I need to make a backup before updating because of this catalog? A database backup should always be made before an update — then the extension versions will roll back together with the entire database. 8. Does the catalog affect month closing or OPV/IPN/social tax? No. Tax and contribution calculations (IPN, OPV 10%, social tax 6%, etc.) are performed by settlement documents and accounting settings; the version catalog is unrelated to them. 9. Why isn't the catalog in the regular section menu? It's technical and not meant for daily work, so it's opened via a navigation link or from the administration window. 10. Related documents - What it's based on: records are created by the configuration update mechanism when installing a release (update via "Configurator" or the update service). There is no separate basis document. - What it's related to: the "DeliveredExtensions" catalog (record owner) and the "Extensions" subsystem in administration. - What is "entered based on" it: nothing — no documents are created from the service catalog. Real primary documents (sales, purchases, ESF, SNT) are entered in the corresponding sections, and their correct upload is ensured by the already-connected extension versions from here. How to find out your release. Menu "Help" → "About the program": the platform version line (e.g., 8.3.24) and the configuration line — "Trade Management for Kazakhstan, 3.4.5.21". Check these numbers before taking any actions with extensions. This guide was prepared for release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4). On other releases, the composition and versions of delivered extensions may differ. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_