--- title: "Directory \"General External Components\" in 1C:Accounting for Kazakhstan 3.0" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-07 canonical: https://buhgpt.kz/suraqtar/spravochnik-obshchie-vneshnie-komponenty-v-1s-buhgalteriy-en source: BuhGPT --- # Directory "General External Components" in 1C:Accounting for Kazakhstan 3.0 > **TL;DR:** Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0). You click "Sign and Send" on the electronic invoice (ESF) — and instead of a signature, you get "Failed to connect to the external component." Or you connect a barcode scanner, fiscal registrar, but the equ --- Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0). You click "Sign and Send" on the electronic invoice (ESF) — and instead of a signature, you get "Failed to connect to the external component." Or you connect a barcode scanner, fiscal registrar, but the equipment does not "see" the driver. Or after updating the configuration, the exchange module stopped working. In all these cases, there is only one way — to the directory "Common External Components". Here lie the components themselves (small software modules-add-ons) that 1C loads to work with encryption, equipment, and electronic documents. Let's figure out how to get here, what to load, and why the component "does not connect". 1. Purpose The directory "Common External Components" stores external components (add-ins) — service software modules that extend the capabilities of 1C: cryptography for signing ESF and SNT, working with trade and cash equipment, data exchange, scanning. This is a technical (service) directory: it does not participate in accounting and does not generate entries. Its task is to ensure that the required component is loaded, of the current version, and enabled. 2. Where to find You can open it in three ways: - Through the section: Administration → Maintenance (or Internet Support and Services) → an item related to external components. In the release section, the list is available from Administration → Printed Forms, Reports, and Processing. - Through "All Functions": Main Menu (icon ≡ at the top left) → All Functions → Directories → Common External Components. If the "All Functions" item is not present — enable it: Service → Parameters → checkbox Show "All Functions" command. - The fastest way is the navigation link. Main Menu → Service → Go to Navigation Link, paste: e1cib/list/Directory.CommonExternalComponents This directory can be opened by a user with administrator rights. A regular accountant will likely have the upload buttons hidden — this is normal. 2a. How to know your release Main Menu → Help → About the Program. In the opened window, you will see the platform version (for example, 8.3.24.xxxx) and the configuration release (for example, "Accounting for Kazakhstan, version 3.0 (3.0.74.2)"). These two numbers should be mentioned when contacting support regarding components: some connection issues are resolved by updating the configuration or platform. 3. How to fill out the card Records in this directory are usually not created manually "from scratch" — the component is loaded from a file (usually .zip) or obtained with an update. But it is useful to understand the fields. Field Purpose and what happens in case of an error Name (required) A human-readable name by which you will find the component in the list. If you make a mistake — you will just confuse yourself, it does not affect the work. Identifier (required) The program code by which 1C accesses the component from its code. The most critical field. If the identifier does not match what is "hardcoded" in the configuration, the component will not connect, even though the file is loaded. Do not change it manually. Version The version of the loaded module. It shows whether the component is current. An old version is a common reason why the signature or equipment "fails" after an OS/platform update. Component File (component data) (required for operation) The body of the component itself — loaded with the Load from File button. Without the loaded file, the record is "empty" and will not work. Disabled / Use Enable flag. If "Disabled" is checked — 1C ignores the component. This is the first thing to check when "not connecting". Supported Clients / OS For which modes (thin client, web client) and operating systems the file is suitable. If you loaded a build not for your OS/architecture — there will be a loading error. Comment Your service note: where you got the file, date, for what purpose. Helps during the next update. Buttons on the list/card form: - Load from File — load .zip with the component. - Save to File — export the current component (for example, to transfer to another computer). - Update — replace the file with a new version. 4. Analyzed Example: Loading Crypto Component for Signing ESF Situation. An accountant of LLP "Astana-Trade" is trying to sign an ESF in the ESF IS directly from 1C. An error occurs when connecting the crypto component. Actions: - Open e1cib/list/Directory.CommonExternalComponents. - Find the line with the cryptographic component. We see: Version — outdated, the flag "Disabled" is unchecked, but the file does not load under the current OS. - Download the current distribution of the component (from the supplier's website / from the 1C update), file .zip. - Go to the card → Update (or Load from File) → select .zip → Save and Close. - Check: Identifier has not changed, Version has been updated, the flag "Disabled" is unchecked. - Re-enter 1C and repeat the ESF signing — now it goes through. Important about "entries". This directory is service. It does not generate any accounting entries Dr/Cr, amounts in tenge, VAT calculations (16% in 2026), individual income tax (IIT) or mandatory pension contributions (MPC). It only enables the technical possibility to sign and send the document. The already sent electronic invoice for sale will give standard entries in accounting — for example: Dr 1210 Cr 6010 (income from sales), Dr 1210 Cr 3130 (VAT payable, 16%), Dr 7010 Cr 1330 (cost of goods). But these movements are made by the sales document, not the component directory. 5. Types of Operations (What the Directory Can Do) There are no separate "types of operations" like in documents. There is a set of actions: - Load component from file — first add the module. - Update component — replace with a new version. - Save to file — export for transfer/backup. - Enable / disable — manage the usage flag. - View properties — version, identifier, supported platforms. Functionally, components in this directory serve such areas: cryptography and digital signatures (signing ESF, SNT, reporting), connected equipment (scanners, cash registers/fiscal registrars, scales, acquiring), exchange and integration, working with files and printing. 6. What is Formed When Recording - No entries. The service directory does not write to accounting and tax records. - Does not generate electronic documents (ESF/SNT). It only provides a technical tool for their signing and sending; the ESF and SNT themselves are created by specialized documents (sales, transfer, etc.) and go to the ESF IS. - No movements in accounting registers. - When loading/updating, the component file is saved inside the directory record, and the attributes "Version", "Identifier", and information about supported clients are updated. After that, the component becomes available to the configuration code. 7. Printed Forms This directory does not have printed forms in the accounting sense (it is not a document). Only a service export is available: Save to File — saving the component itself in .zip. A standard report like "Directory List" can be output through the typical list printing command, but it has no practical value. 8. Common Errors and How to Fix "Failed to connect to the external component". Reasons by frequency: the component is disabled (uncheck the "Disabled" flag); the file loaded is not for your OS/architecture (load the correct build); the .zip is corrupted (re-download); no rights to run the component in the browser (for the web client, a trusted environment is needed). "External component not installed" / "Component not found by identifier". The file is not loaded or the Identifier does not match. Open the card, check that the file is loaded and the identifier has not been manually changed. If changed — restore the original (reload the component from the distribution). "Version of the external component is not supported". After updating the platform/OS, the old build stopped working. Click Update and load the current version. "Insufficient rights" when opening/loading. Working with this directory is under administrator rights. Contact the person who manages the database settings. The component works in the thin client but not in the web client. Check the "Supported Clients" field: for the browser, a web build and permission for the 1C extension in the browser are needed. 9. FAQ 1. How do "Common External Components" differ from regular settings? This is a repository of software modules-add-ons (crypto, equipment, exchange), not accounting data. It includes technical capability but does not calculate anything itself. 2. Does the directory generate entries or ESF? No. It does not create Dr/Cr entries or ESF/SNT. It only allows signing and sending electronic documents, which are created by other objects. 3. Why does 1C complain about the component after signing the ESF? Most often, the component is disabled or outdated. Open the card, uncheck "Disabled" and click Update, loading the fresh version. 4. Where to get the component file itself? Usually, it comes with the configuration/platform update or is downloaded from the supplier's website for the crypto tool or equipment manufacturer in the form of .zip. 5. Can the component be transferred to another computer? Yes. On the source database — Save to File, on the target — Load from File. The identifier must remain the same. 6. What to do if I accidentally changed the identifier? Restore the original: reload the component from the original distribution. The configuration will not find the component by the incorrect identifier. 7. Are administrator rights needed? Yes, for loading, updating, and enabling. A regular user usually sees the directory only for viewing or does not see it at all. 8. Why does the component not work in the browser, although everything is fine in the thin client? For the web client, a web build of the component and the installed extension for working with 1C in the browser are needed. Check the "Supported Clients" field. 9. Does this directory affect VAT amounts, IIT, MPC? No. Rates and calculations (for example, VAT 16%, IIT 10%/15%, basic deduction 30 MRP) are calculated by accounting and payroll documents, not by the component directory. 10. Will the component update itself when the configuration is updated? Components supplied with the configuration are updated along with the release. Components that you manually loaded (for specific equipment, for example) need to be updated independently. 10. Related Objects - Based on what it is used: in demand when working with documents requiring digital signatures and sending — ESF (ESF IS), SNT, electronic reporting; when connecting equipment in the section Administration → Connected Equipment. - What it is related to: settings for cryptography and electronic signatures (Administration → Exchange of Electronic Documents), settings for connected equipment, internet support settings. - What is introduced "based on": nothing — no documents are created from this service directory. It ensures the operation of other objects "in the background". How to know your release Main Menu → Help → About the Program: there you can see the version of the 1C:Enterprise platform and the configuration release. Check the release before contacting support — some problems with components are solved by updating. This material was prepared for "Accounting for Kazakhstan", version 3.0, release 3.0.74.2. In other releases, the location of menu items and the set of card attributes may differ. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_