--- title: "Guide to \"External Components\" in 1C:Accounting for Kazakhstan 3.0 — Complete Instruction" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-07 canonical: https://buhgpt.kz/suraqtar/spravochnik-vneshnie-komponenty-v-1s-buhgalteriya-dlya-ka-en source: BuhGPT --- # Guide to "External Components" in 1C:Accounting for Kazakhstan 3.0 — Complete Instruction > **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) in the ESF information system — and 1C responds: "Failed to load external component" or "Cryptography component is not connected" . Or you connected --- Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0). You click "Sign and Send" on the electronic invoice (ESF) in the ESF information system — and 1C responds: "Failed to load external component" or "Cryptography component is not connected". Or you connected a new fiscal registrar, but the cash register does not open: the program does not see the driver. In both cases, the path leads to one service directory — "External Components". Here are stored the connected modules (add-ins) through which Accounting works with digital signatures, encryption, barcode scanners, and cash equipment. Let's figure out how it is structured and how to fix it. 1. Purpose The directory stores external components (add-ins) — binary modules that extend the capabilities of the platform: cryptography and digital signatures for ESF and SNT, communication with government agencies, trade and cash equipment, scanners. 1C loads the necessary module from this directory when starting the operation. This is a technical directory for the administrator, not an accounting document — it does not generate movements in accounts and taxes. 2. Where to find There is no separate item "External Components" in the accounting menu — this is a service object. You can open it in three ways: - Main menu (icon ≡ top left) → "All Functions" → "Directories" → "External Components". If the "All Functions" item is missing — enable it: "Service" → "Settings" → check "Show the 'All Functions' command". - Administration → Maintenance — section for working with additional modules and components (for components provided by the vendor). - Through the navigation link — the most direct way. 1C Navigation link: e1cib/list/Directory.ExternalComponents Copy it, then in 1C: "Service" → "Go to navigation link" (or Main menu → "File" → in older builds), paste it and click "Go". The directory will open as a list. Components for cash registers and scanners are often created automatically through the section Administration → Connected Equipment, but they are physically registered in the same directory. 2a. How to know your release The menu "Help" → "About the Program" (or icon ≡ → "Help" → "About the Program"). In the window, you will see two lines: - Platform version — for example, "1C:Enterprise 8.3.24.xxxx" (for external components this is critical: old platforms do not load the Native API of new versions). - Configuration — "Accounting for Kazakhstan, version 3.0 (3.0.74.2)". It is the second line that should match the header of this instruction. 3. How to fill In most cases, you do not create an item "from scratch manually", but upload the component file — 1C will automatically pull the parameters from the manifest. But you need to know the fields because they determine whether the module will connect or not. Field Purpose and what will happen in case of error Name (required) A human-readable name in the list ("Digital Signature NUC RK", "FR Driver Port"). It does not affect anything technical, but if you name it unclearly — you won't find the necessary module among a dozen similar ones later. Object Identifier (ProgID) (required) The program name by which the configuration requests the component, in the form AddIn.ComponentName. Set by the module developer. If you make a mistake in one character — the code will call AddIn.Crypto, but you have AddIn.Crypto, and 1C will say that the component was not found. Used / Usage (flag) Allows loading. Unchecked = the module is in the database but is not loaded. Useful for temporarily disabling a faulty driver without deleting it. Component File The add-in itself: .dll/.so or (the correct option) a ZIP archive with the manifest MANIFEST.XML inside. It is from the archive that 1C reads the versions and the list of OS. Uploading a "bare" dll without a manifest — some properties will remain empty, and on a 64-bit platform, the module may not be picked up. Version (read from the manifest) The version of the module itself. Automatically filled after the file is uploaded. Do not modify manually. Integration Version (Native API) (read from the manifest) The version of the Native protocol. If it is higher than what your platform supports, the component will not load — first, update the platform. Supported OS (read) Windows / Linux / macOS. If the server is on Linux, and the component is only for Windows — it will not work on the server. Supported Integration Modes (read) Thin client, web client, external connection, server. Cryptography for background sending of ESF must support "External Connection"/"Server", otherwise the background task will not start it. Supported Architectures (x86/x64) (read) Bitness. A 64-bit thin client requires a 64-bit build of the component. Step-by-step actions: - Open the list (see section 2) and click "Create" — or, if the component already exists, open it for editing. - Fill in Name. - Click "Upload"/"Upload Component File" and specify the ZIP archive with the manifest (preferably) or dll. - Check that the fields Version, Integration Version, Supported OS have been populated — this is a sign of a correct archive. - Verify the Object Identifier against what the configuration expects. - Check the "Used" flag. - Save and close. Restart the 1C session — components are loaded at startup. 4. Analyzed Example Situation. The accountant of LLP "Astana-Trade" issued an ESF for the sale of goods to the buyer: the amount excluding VAT is 1,000,000 ₸, VAT at a rate of 16% = 160,000 ₸, total 1,160,000 ₸. When sending to the ESF information system, 1C gives: "Failed to create an external component object with identifier AddIn.CryptoPro". The signature is not applied, the ESF hangs in the status "Not sent". What to do: - Open the directory via the link e1cib/list/Directory.ExternalComponents. - See the item "Cryptographic Provider for Digital Signature" — the "Used" flag is unchecked, the "Version" field is empty. This means that during the last update, the module was lost. - Download the current ZIP archive of the cryptography component, click "Upload Component File". - After uploading, the Integration Version field shows "2.11", Supported Modes — "Thin Client, External Connection". Set the "Used" flag, save. - Restart 1C, open the ESF again, click "Sign and Send" — the signature is applied, the document goes to the ESF information system. Accounting entries for this operation: there are none. Loading the component is a technical action. Accounting entries are generated not by this directory, but by the sales document to which the ESF is attached: Debit Credit Amount, ₸ Description 1210 6010 1,000,000 Revenue from sales 1210 3130 160,000 VAT 16% payable 7010 1330 (cost) Write-off of the cost of goods Thus, a functioning external component is a condition for the ESF for these 1,160,000 ₸ to be sent to the government system at all. The directory itself does not interfere with these entries. 5. Types of Operations (What Can Be Done) The directory does not "conduct operations" in the accounting sense, but provides the following actions: - Upload Component File — record the add-in in the database. - Update Component — replace the file with a new version (when updating the configuration or driver). - Enable / Disable (the "Used" flag) — manage loading without deletion. - View Manifest Properties — versions, OS, modes, architectures. - Delete (mark for deletion) — if the component is no longer needed. 6. What is Formed When Recording Honestly and to the point — there are no accounting consequences: - Debit/Credit Entries — are not formed. - ESF / SNT — this directory does not create them (it only ensures the operation of cryptography, which signs them). - Tax Registers (VAT, PIT, OPE, SO, social tax) — are not affected. - What actually happens: the component file is saved in the value storage within the directory item, and at the next session start, the platform picks up the module and makes the call AddIn. available in the configuration code. If someone promises you "entries from external components" — this is a mistake: movements in accounts are generated by documents (sales, receipts, payments), not by a service directory. 7. Printed Forms Standard accounting printed forms (invoice, act, waybill) for this object do not exist — there is nothing to print here. Only the service view of the component properties (version, OS, integration modes) is available in the item card. When diagnosing, the technical registration log is useful: "Administration → Maintenance → Registration Log" — it shows the events of loading the component and errors. 8. Common Errors "Failed to create an external component object with identifier AddIn.XXX". Reason: the component is not loaded, disabled (the "Used" flag is unchecked) or the ProgID in the directory does not match what the code requests. Correction: open the item, check the identifier character by character, upload the file, enable the flag, restart the session. "The external component does not support this client architecture (x64/x86)". Reason: you have a 64-bit thin client, but the archive contains only a 32-bit build. Correction: upload a ZIP archive with a manifest containing both bitnesses, or run the 32-bit client. "The version of the external component is not supported by the current version of the platform". Reason: "Integration Version (Native API)" is higher than what your platform can handle. Correction: update the 1C:Enterprise platform (section 2a will show the current version), then repeat the upload. "The file is not an external component" / properties did not fill after upload. Reason: uploaded a "bare" dll without a manifest or a corrupted archive. Correction: use a ZIP archive with MANIFEST.XML inside — then the Version and OS list will be pulled in. "The component works for the operator, but not in the background task (scheduled sending of ESF fails)." Reason: the component does not have the "External Connection"/"Server" mode. Correction: check the "Supported Integration Modes"; for server-side cryptography, a server build is needed. 9. FAQ Does the directory "External Components" have entries? No. This is a service directory for the administrator. Entries are generated by accounting documents (sales, receipts, payments), not by it. How is this directory related to ESF and VAT 16%? Directly — it has no relation to the amounts. But the cryptography component from this directory is needed to sign the ESF with a digital signature and send it to the ESF information system. Without a working component, the document with VAT 16% will not go to the government system. Where did the component go after the configuration update? During the update, the component file may have been replaced or the "Used" flag may have been unchecked. Open the item, upload the current file, enable the flag, restart the session. What file format to upload — dll or zip? Preferably a ZIP archive with a manifest: from it, 1C reads the version, OS list, and modes, correctly loads the required bitness. A "bare" dll does not always work. Why does the component not load on the server under Linux? Check the "Supported OS" field. If it lists only Windows — it will not work under Linux, a cross-platform build is needed. Can I temporarily disable a faulty driver without deleting it? Yes. Uncheck the "Used" flag and restart the session — the module will stop loading but will remain in the database. Who should work with this directory — the accountant or the administrator? Usually the administrator or the 1C support person. The accountant only accesses it in case of signature/equipment errors, more often at the suggestion of technical support. Is it mandatory to restart 1C after uploading? Yes. The platform connects external components at the start of the session. Until you restart — the changes will not apply. Where to get the current component file? From the functionality provider: the cryptographic provider — from the website of the digital signature/NUC developer, equipment driver — from the cash register vendor or from 1C through the update service. Does the directory affect month-end closing or reporting (PIT, OPE, SO)? No. The calculation of taxes and contributions (PIT, OPE 10%... --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_