--- title: "Directory \"DriversEquipment\" — Technical Description (Accounting for Kazakhstan 3.0.74.2)" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-07 canonical: https://buhgpt.kz/suraqtar/spravochnik-drayveryoborudovaniya-tehnicheskoe-opisanie-b-en source: BuhGPT --- # Directory "DriversEquipment" — Technical Description (Accounting for Kazakhstan 3.0.74.2) > **TL;DR:** 1. Identification Parameter Value Object Type Catalog Name DeviceDrivers Full Name Catalog.DeviceDrivers ( Catalogs.DeviceDrivers ) Synonym Device drivers Configuration Accounting for Kazakhstan, edition 3.0, version 3.0.74.2 Hierarchy Flat list (no hierarchy) Navigation Link --- 1. Identification Parameter Value Object Type Catalog Name DeviceDrivers Full Name Catalog.DeviceDrivers (Catalogs.DeviceDrivers) Synonym Device drivers Configuration Accounting for Kazakhstan, edition 3.0, version 3.0.74.2 Hierarchy Flat list (no hierarchy) Navigation Link e1cib/list/Catalog.DeviceDrivers Purpose. The DeviceDrivers catalog is the central registry of drivers for connected trading equipment (cash registers, barcode scanners, scales, acquiring terminals, customer displays, etc.). It is used by system administrators and implementation specialists to manage driver versions, install them on client workstations, and update them. The catalog contains both predefined (standard) drivers supplied with the 1C distribution and custom drivers uploaded from files. It is used relatively rarely — during the initial setup of workstations with equipment or during scheduled driver updates. The catalog is a service (administrative) object of the "Connected Equipment" subsystem and does not participate in accounting, tax, or management accounting — it does not store monetary indicators and does not generate movements in registers. Where to find in 1C: section "Connected Equipment" → "Device Drivers". 2. Attributes and Table Parts 2.1 Header Attributes Name Type Mandatory Purpose EquipmentType EnumerationReference.ConnectedEquipmentTypes Mandatory (check ShowError) Defines the category of equipment (cash register, scanner, scales, etc.) for which the driver is intended. Used for filtering when connecting devices. ObjectIdentifier String Optional Unique string identifier of the driver for programmatic access and data caching. DriverHandler EnumerationReference.DriverHandlersForConnectedEquipment Optional Reference to a specific external processing or component that implements interaction with the equipment. SuppliedByDistribution Boolean Optional Indicates a predefined driver from the standard configuration delivery. Protects standard drivers from accidental deletion. UploadedDriver ValueStorage Optional Binary content of the driver file (ZIP archive with external processing or native component) uploaded by the user. DriverFileName String Optional Name of the original driver file upon upload (e.g., EquipmentDriver_v2.3.epf). DriverTemplateName String Optional Name of the configuration template containing the driver (for predefined drivers from the distribution). DriverVersion String Optional Driver version in the format X.Y.Z. Used to control relevance and compatibility during updates. Deprecated Boolean Optional Indicates an outdated driver not recommended for use. Blocks application in new connections. Standard attributes of the catalog: Code, Name, DeletionMark, Predefined. 2.2 Table Parts Table parts are absent. The catalog has a flat structure — all attributes are placed in the header. 3. Forms Form Purpose ElementForm Main form for editing the driver (about 80 controls). Contains commands for uploading/downloading driver files and installing the driver on the client workstation. The key form for the user — all work with driver parameters is done here. ListForm Form for the list of drivers (about 44 elements). Includes a command to add a new driver from a file and filtering by equipment type and support status. 4. Key Module Procedures No specific BSL code is attached in evidence, so below are typical handlers of this type of object in configurations on BSP (Library of Standard Subsystems), subsystem "Connected Equipment". Object Module: - FillProcessing — filling in attributes when creating a driver from a file (parsing the name, determining the version). - CheckFillProcessing — control of the mandatory attribute EquipmentType (ShowError); if necessary, check for non-empty content of UploadedDriver or DriverTemplateName. - BeforeWriting — updating the driver cache, controlling changes to predefined drivers (SuppliedByDistribution). - BeforeDeleting — prohibiting the deletion of drivers supplied by the distribution. Element Form Module: - OnCreateOnServer / OnReadOnServer — setting the availability of commands (upload/download/install) depending on SuppliedByDistribution and Deprecated. - Commands UploadDriverFromFile, DownloadDriverToFile, InstallDriverOnClient — working with UploadedDriver through ValueStorage, placing/extracting through temporary storage (PlaceFile / GetFile). List Form Module: - ConnectedEquipmentAddDriverFromFile (or similar command) — creating a new element with uploading binary content. Requires verification: the exact names of procedures and commands in the modules are version-specific for release 3.0.74.2 — to be clarified with the configurator. 5. Posting and Movements The catalog is not posted and does not generate movements in accounting registers. It is a service object for equipment configuration — it does not have monetary attributes, does not affect accumulation/accounting registers, and does not participate in the formation of postings. Indirectly, the driver is involved in the chain of fiscal document flow: the device (cash register) configured through it participates in the processing of retail sales, which are already reflected in sales documents. It is these documents, not the driver catalog, that generate accounting movements according to the standard chart of accounts of the RK, for example (values for Kazakhstan 2026): Operation Debit Credit Comment Sale of goods 1210 "Short-term receivables from customers" 6010 "Revenue from sales" Amount of revenue excluding VAT VAT Accrual 1210 3130 "VAT payable" VAT 16% Cost of Goods Sold 7010 "Cost of goods sold" 1330 "Goods" Cost of sold goods Receipt of payment 1030 "Cash in current accounts" 1210 Payment from the customer The sale is accompanied by electronic documents of the RK — ESF (ESF IS) and, if necessary, SNT. VAT rate — 16%. Once again: the driver catalog itself has no relation to these movements and is presented here only for understanding the role of the equipment in the overall context. 6. Related Objects and Input on Basis - Enumeration.ConnectedEquipmentTypes — category of equipment (attribute EquipmentType). - Enumeration.DriverHandlersForConnectedEquipment — specific driver handler. - Catalog.ConnectedEquipment — instances of workstation devices; refer to the driver when setting up the connection. - Information Register.ConnectedEquipmentExchangeRules / ConnectedEquipmentSettings (depending on the BSP release) — store the binding of devices and workstations to drivers. - Subsystem "Connected Equipment" of BSP — all logic for installation, connection testing, and interaction with the driver. Input on basis for this catalog is not provided. Creating an element is done manually or via the "Add driver from file" command from the list form. 7. Extension Points - Configuration Extensions. Adding attributes (e.g., references to the internal registry of certified equipment of the RK) and columns to the list form through an extension without removing from support. - Event Subscriptions. BeforeWriting / BeforeDeleting — for implementing corporate policy on driver versions and prohibiting rollback to unsupported versions (Deprecated). - Redefinable BSP modules of the "Connected Equipment" subsystem — for registering custom driver handlers and equipment types. - Additional processing/reports (BSP "Additional reports and processing") — for mass downloading/inventory of drivers by workstations. - Fill Check — extension of CheckFillProcessing with additional rules (mandatory DriverVersion, format of ObjectIdentifier). Requires verification: the specific composition of redefinable modules and subscription names depends on the version of BSP embedded in release 3.0.74.2. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_