Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0).
You have updated the configuration, and upon first login, 1C displayed "Processing extensions" or "Failed to apply extension." The button for your external print form has disappeared, an additional report has been lost, and the support specialist asks: "Open the reference VersionsOfExtensions and tell me what is recorded there." You open the list — and inside are incomprehensible lines with long names and sets of numbers. Let's figure out what this is, whether to touch it or not, and what to do in typical situations.
First and foremost: this is a service (technical) reference, not an accounting document. It does not create entries, does not generate electronic invoices (ESF) or tax returns, does not have print forms, and is not related to taxes, VAT, or the chart of accounts. Therefore, you will not see tables with Dr/Cr and amounts in tenge — they are physically absent here, and inventing them would be deceitful. Everything else will be discussed accordingly.
1. Purpose
The reference stores a list of configuration extensions installed in your database and their versions. The information base update mechanism (BSP subsystem "Update IB version") compares the version recorded here with the actual version of the extension. If the version has changed — the data update handlers for that extension are launched. In simpler terms, the reference is 1C's "memory" of which extensions and which versions have already processed their updates.
2. Where to find
This reference cannot be opened through ordinary sections (like "Sales" or "Bank and Cash") — it is intentionally not present in the accountant's interface. You can open it like this:
Main menu → "All functions" → References → "VersionsOfExtensions" (the "All functions" item is enabled in "Service → Settings → Show the "All functions" command").
Faster — via the navigation link. Main menu → "Service" → "Go to navigation link", insert:
e1cib/list/Reference.VersionsOfExtensions
The extensions themselves (not their versions, but the actual files) are managed elsewhere: "NSI and Administration" → "Print forms, reports, and processing" → "Extensions", or through "All functions → Standard → Configuration extension management".
2a. How to know your release
"Help" → "About the program" (or the "i" icon in the upper right corner). In the opened window, you can see the platform version (for example, 8.3.24) and the configuration release — the line "Accounting for Kazakhstan, version 3.0 (3.0.74.2)". The release is important: the composition of the service attributes of this reference depends on the version of the built-in library of standard subsystems (BSP), which is updated along with the configuration.
3. How to "fill"
The key fact: you do not fill this reference manually. Records are created and updated by the platform itself when installing, enabling, and updating extensions. You should only open it for viewing or at the request of support. Nevertheless, it is useful to understand what the columns mean.
| Field | What it means | What will happen if touched incorrectly |
|---|---|---|
| Name / Code | The service name of the extension record. This is how 1C recognizes the extension | Renaming will not link the record to another extension, but may disrupt the mapping |
| Extension Identifier (GUID) | A unique key for the specific extension | If deleted — the mechanism will stop recognizing the extension and will restart the updates |
| Extension Version | The version for which the update handlers have already been processed | If you set "your" version, the actual update handlers will not run — the extension data may remain unprocessed |
| Checksum / hash | The fingerprint of the extension file for change control | Manual editing will lead to a false "extension has changed" and unnecessary updates |
The exact composition of the attributes (names of service fields, presence of hash) depends on the version of BSP within the release and may differ — this is the only point here that should be clarified according to your version. The essence of the mechanism does not change.
Practical rule: do not edit or delete rows "just in case." All correct changes occur automatically when working with the extensions themselves.
4. Analyzed example (what really happens)
There are no entries and amounts in tenge here — I will show a real-life scenario for which you came here.
Situation. A partner implemented an external print form "Reconciliation Act (revised)" for you as an extension of version 1.0.1. A month later, he sent an updated file of version 1.0.2.
- You uploaded the new file in "NSI and Administration → Extensions," restarted 1C.
- Upon login, the platform compared: in the reference "VersionsOfExtensions," version 1.0.1 is recorded, while the actual version connected is 1.0.2.
- Since the versions are different — the update handlers for this extension were launched (for example, layout reconfiguration), and a window "Updating the information base" appeared.
- After successful completion, 1C automatically rewrote the line in the reference: now it shows 1.0.2.
If you had opened the reference before logging in, you would have seen a line with the extension name and version 1.0.1 — from this, support would immediately understand that the new version has not yet been applied. No Dr/Cr, accounting registers, or tax movements are generated in this process.
5. Types of operations
This reference does not have separate "types of operations," like sales or receipt documents — it is not a document. Possible actions are limited to:
- Automatic record creation — upon first connection of the extension;
- Automatic version update — after the update handlers have been processed;
- Viewing — manually, for diagnostics.
There are no postings, cancellations of postings, or copying "based on" here.
6. What is formed
Nothing from the accounting framework. I will explicitly list so you do not search in vain:
- Entries (Dr/Cr) — are not formed. This is not a document, there are no movements in the accounting register.
- ESF / STT — are not formed. The reference is not related to sales, VAT, or the ESF information system.
- Movements in tax and accumulation registers (VAT, PIT, pension contributions, etc.) — are absent.
- The only "result" — the current record of the extension version used by the service mechanism for updating the IB.
7. Print forms
The reference has no print forms. You cannot print the "extension version" as a form. If you need a report on installed extensions — check the list in "NSI and Administration → Extensions" or the system registration log.
8. Common errors
"Failed to apply extension ... Extension usage is impossible." The extension is incompatible with the current configuration release (after the update, the structure of objects has changed). Update the extension from the supplier for the new release or temporarily disable it with a checkbox in the "Extensions" list. Editing the "VersionsOfExtensions" reference will not solve the problem.
"Updating the information base" hangs or crashes upon login. The extension update handler finished with an error, so the version in the reference was not rewritten. Do not clean the reference — contact the extension supplier; often, reinstalling the correct version of the file helps.
"Duplicate extension records" / old versions after database rollback. If the database was restored from a copy, the records here may reflect the state at the time of the copy. The correct solution is to reconnect the current versions of the extensions, not to delete rows manually.
"No access to the reference VersionsOfExtensions." Opening service references requires administrator rights. Ask the administrator or open under an account with full rights.
9. FAQ
Related sections and questions are listed separately below — first, answers to frequently asked ones.
10. Related objects
- Configuration extensions ("NSI and Administration → Print forms, reports, and processing → Extensions") — the actual extension files; their installation generates records in "VersionsOfExtensions."
- Additional reports and processing — often supplied as extensions and also tracked by this mechanism.
- Configuration update / IB update — a general mechanism, part of which is this reference.
- Registration log — shows errors in applying and updating extensions with details.
How to know your release. "Help" → "About the program": the line "Accounting for Kazakhstan, version 3.0 (3.0.74.2)" and the platform version. Provide them when contacting support — the composition of the service mechanisms is tied to the release.
Material prepared for release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0).