Verified on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4).
In the morning, something completely different opens up. Yesterday you installed an extension update (a modified printed form, your own report, or a programmer's fix), and today the report won't open, the form is "shifted," or 1C reports on login that the extension is incompatible. The first question of a practicing accountant: "What version of the extension is currently installed, and when did it appear?" The answer is stored here — in the ExtensionVersions catalog. This is a technical "medical history" of extensions: which versions were loaded, under what name, and at what moment. Rarely does one need to open it manually, but when something breaks after an update — this is exactly where both the admin and the external 1C specialist look.
1. Purpose
ExtensionVersions is a service catalog. It stores records of configuration extension versions (external modifications, add-ons applied on top of the standard Trade Management for Kazakhstan). This is not an accounting object: it does not participate in bookkeeping, does not affect VAT, mandatory pension contributions, individual income tax, or tax calculations. Its task is technical: to provide a reference point when analyzing "what changed after the update."
2. Where to find it
This is a service catalog, so it is not found in the regular menu sections ("Sales," "Purchases," "Finance"). It can be opened in two ways.
- Via a navigation link (the most reliable way). Main menu → Service → Show navigation link (or directly the link input field), insert:
e1cib/list/Справочник.ВерсииРасширенийand click "Go." The list will open even if the item is not in the menu. - Via "All functions." Main menu → Functions for technical specialist (or "All functions," if enabled) → "Catalogs" section → ExtensionVersions.
To enable "All functions": Main menu → Settings → Parameters → checkbox "Display command 'All functions'".
Extension management itself (loading, deleting, enabling) is located elsewhere — Main menu → Settings → Configuration extensions (or via the Configurator). The catalog is a log of records of already loaded versions.
2a. How to find out your release
Main menu → Help → About the program. In the window that opens you will see:
- Platform version ("1C:Enterprise 8.3.xx.xxxx");
- Configuration version — here it should say "Trade Management for Kazakhstan, edition 3.4," release 3.4.5.21.
The release matters: the interface and the composition of service catalogs change between versions, and the instruction is tied specifically to 3.4.5.21.
3. How to fill it in
The main rule: this catalog is usually not filled in manually. Records in it are created by the extension mechanism when loading or updating an extension. You work with the list in a "read and understand" mode, not "create a document." But it is useful to know the fields — you read the picture through them.
| Field | Why it's needed | What happens if filled in incorrectly |
|---|---|---|
| Code (required) | Unique record number in the catalog. Assigned automatically. | Duplicates and confusion in references; no need to change manually. |
| Name (required) | Name of the extension/version by which you recognize it in the list. | You won't be able to distinguish one version from another during rollback. |
| Identifier / extension name | Technical attribute indicating which extension the version belongs to. | Easy to mix up versions of different extensions and "roll back" the wrong one. |
| Version | Extension version number (e.g., 1.0.5). | You won't understand whether yours is newer or older; version comparison will break. |
| Date / moment | When the version appeared. This is your reference point when analyzing "what changed yesterday." | You'll lose the chronology and won't be able to link the failure to the update. |
Requires verification on your release: the exact composition of attributes of the "ExtensionVersions" service catalog may differ depending on the version of the standard subsystems library embedded in 3.4.5.21. Opening a list item, you will see the actual set of fields.
Practical conclusion: do not create or edit items manually. If you need to change the composition of extensions — do it via Settings → Configuration extensions, and only read the catalog.
4. Worked example
There are no accounting figures (amounts, VAT, invoices) for this object — it is technical. So the "example" here is about a real incident analysis, not about Dr/Cr.
Situation. On 09/23/2026, an accountant complains: the modified invoice stopped printing. The day before, an external specialist had sent an update for the "PrintForms_Modification" extension.
What you do:
- Open
e1cib/list/Справочник.ВерсииРасширений. - Sort the list by date. You see two records for the "PrintForms_Modification" extension: version 1.0.4 dated 09/01/2026 and version 1.0.5 dated 09/22/2026.
- The conclusion is obvious: the failure coincided with the appearance of version 1.0.5 dated 09/22/2026 — the update is the cause.
- Go to Settings → Configuration extensions, disable (or delete) the problematic version, restart 1C. Printing is restored — meaning the defect is in 1.0.5, return the version to the developer for a fix.
There are no and cannot be accounting entries here: the catalog does not move accounting registers, does not form revenue (6010), cost of sales (7010), or VAT payable (3130). It only showed you the version and date — that was enough to find the culprit.
5. Operation types
The catalog does not "perform operations" in the accounting sense. In practice the following regular catalog actions are available:
- Viewing the list of extension versions;
- Opening an item — to see the version, name, date;
- Filtering and sorting by date/name — to find the required version;
- Marking for deletion (only deliberately, usually cleanup is handled by the extension mechanism).
Loading, enabling/disabling, and deleting the extensions themselves are not done in this catalog, but in Settings → Configuration extensions.
6. What is generated upon posting
Nothing in the accounting sense. This is a catalog, not a document — it has no "Post" button, no movements in accounting registers, no Dr/Cr entries, and it does not create ESF or STN. Electronic documents (ESF via the ESF IS, STN) are generated by sales/receipt documents, not by service catalogs. The only "result" of working with it is a record of the version, which the extension mechanism uses when the program starts.
7. Printed forms
There are no printed forms for the ExtensionVersions catalog — there's no need to print an "extension version." If you need to record the composition, use the standard command More → Output list (exporting the list to a spreadsheet document/Excel) — this is a universal feature of 1C lists, not a specialized printed form.
8. Common errors
"System integrity violation" / "Extension is not compatible with the current configuration" on login. Reason: the extension version does not fit the updated standard Trade Management 3.4.5.21. Solution: launch 1C without extensions (in the Configurator or with a startup key), disable the problematic version in Settings → Configuration extensions, request a compatible version from the developer.
"Insufficient rights" / the catalog doesn't open for the accountant. Service objects are visible to the administrator. Solution: open under a user with administrator rights or via a technical specialist.
The item is not in the menu, can't find the catalog. Solution: use the navigation link
e1cib/list/Справочник.ВерсииРасширенийor enable "All functions."Deleted a record manually — the extension "broke." Records are maintained by the extension mechanism; manual deletion breaks the link. Solution: don't clean the catalog manually, manage the composition through Configuration extensions; if there's a problem — reinstall the extension from the file.
9. FAQ
Is this a document or a catalog? A catalog, and a service one at that. It has no posting, entries, or printed forms.
Does it make accounting entries or affect VAT? No. It is technical. It has no effect whatsoever on VAT (16% rate in Kazakhstan in 2026), individual income tax, mandatory pension contributions, accounts 1210/3310/6010, etc.
Can records be edited manually? No need to. Records are created and maintained by the extension mechanism. Manual edits lead to extension loading failures.
Where do you enable and disable the extensions themselves? Main menu → Settings → Configuration extensions (or in the Configurator). The catalog is just a log of versions.
How do you know which extension version is currently active? Open the list, sort by date and by extension name — the most recent record is the current version. Do the final check in "Configuration extensions."
After an update, a report/form broke — where do you start? Compare the date of the failure with the date of the last version record in this catalog. A match points to the culprit update; disable it and check.
Does the catalog generate ESF or STN? No. ESF (via the ESF IS) and STN are generated by sales/transfer documents, not by service catalogs.
How do you find the catalog if it's not in the menu?
Via the navigation link e1cib/list/Справочник.ВерсииРасширений or via "All functions."
Can old versions be deleted to "clean up"? Only deliberately and not manually from the catalog — manage the composition of extensions in "Configuration extensions." Otherwise you risk violating integrity.
Does this catalog affect month-end closing or reporting in Kazakhstan? No. It has no effect on regulated operations, forms 200.00, 300.00, or other reporting.
10. Related documents
- What triggers the creation of a record: loading or updating an extension via Settings → Configuration extensions (or the Configurator). The catalog record is a consequence of this operation.
- What is "entered based on" it: nothing. This is not a base document for accounting documents. Sales, receipts, ESF, STN are created by their own documents and are not related to this catalog.
- What it's used together with: the "Configuration extensions" mechanism (composition management) and the event log (Main menu → Service → Event log) — there you can see extension loading/error events with dates.
How to find out your release
Main menu → Help → About the program. The configuration line will show "Trade Management for Kazakhstan, edition 3.4," release — 3.4.5.21. The 1C:Enterprise platform version is also shown there.
This instruction was prepared for release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4). On other releases, the composition of fields in the service catalog may differ.