Catalog "Connected Equipment" (Catalogs.ConnectedEquipment)

1. Identification

Purpose. The catalog is used for registering and configuring peripheral trading equipment integrated with the configuration: barcode scanners, electronic scales, fiscal registrars (KKT), acquiring and POS terminals, customer displays, magnetic card readers, etc. Each element is a single physically connectable device linked to a driver and a workplace. The catalog is used by administrators during the initial setup of the point of sale, equipment replacement, and re-registration of fiscal accumulators, as well as by cashiers when selecting a device at the workplace.

Where to find in 1C:

• Section “Administration” → “Peripheral Equipment”.
• Direct navigation link: e1cib/list/Catalog.PeripheralEquipment.

The catalog is not an accounting (document) object: it does not itself generate accounting entries and movements in registers. It defines the technical configuration of devices on which fiscal documents (KKT receipts, electronic invoices (ESF), sales reports) and exchange with the ESF/OFD information systems rely. Numerical norms of the RK (VAT 16%, MRP 4,325 ₸, etc.) are applied not in the catalog itself, but in the sales documents/receipts that use the equipment registered here (see section 5).

2. Attributes of Headers and Table Parts

2.1 Header Attributes

Additionally, standard attributes of the catalog are present: Code, Name, DeletionMark, Predefined (not used).

2.2 Table Parts

The catalog generally does not contain its own table parts: all additional attributes (port, driver parameters, key bindings, etc.) are stored in the attribute Parameters (type ValueStorage) as a serialized structure formed by the specific driver configuration form. This approach allows one catalog to service drivers with different sets of settings without changing metadata.

3. Forms

If specialized forms for specific operations are not defined, the platform uses auto-generated forms based on the set of attributes.

4. Key Module Procedures

In the attached evidence, the original BSL code of the modules is not provided. Below are typical handlers characteristic of the peripheral equipment catalog of the BSP (subsystem “Peripheral Equipment”). Exact names/signatures in version 3.0.74.2 require verification in the configurator.

Object Module (ObjectModule):

• FillProcessing(FillingData, ...) — setting default values: DeviceInUse = True, substituting organization and workplace from user settings.
• BeforeWriting(Refusal) — control of compatibility between equipment type and selected driver; when changing parameters, setting flags RequiresInstallation / RequiresReinstallation.
• OnCopy(CopyObject) — clearing DeviceIdentifier and SerialNumber so that the copy does not duplicate unique identifiers.

Element Form Module:

• OnServerCreation — reading parameters from ValueStorage, configuring field visibility depending on EquipmentType.
• ConnectEquipment / TestDevice (client) — calling methods of the “PeripheralEquipmentClient” subsystem to establish a connection and check communication with the device.
• ConfigureDriver — opening the driver configuration form and saving the result in Parameters.

Common modules of the subsystem (BSP): PeripheralEquipment, PeripheralEquipmentClient, PeripheralEquipmentService — methods for connecting devices, sending commands to drivers, registering/fiscalizing KKT, and exchanging with OFD.

5. Posting and Movements

The catalog is not posted and does not generate accounting entries and movements in registers — it is a configuration object, not an accounting one. It affects accounting indirectly, through documents that use the registered equipment.

A typical chain (using the example of retail sales through KKT registered in the catalog), applying RK norms 2026 and a typical chart of accounts:

• Issuing a KKT receipt generates a fiscal document on the device and a record in OFD; simultaneously, a sales document / retail sales report is created.
• Sale of goods (based on the receipt data) results in entries:
  • Dr 1210 (or 1030 when paid in cash/card) — Cr 6010 “Revenue from Sales” — for the sale amount excluding VAT;
  • Cr 3130 “VAT Payable” — VAT amount at the rate of 16%;
  • Dr 7010 “Cost of Goods Sold” — Cr 1330 “Goods” — write-off of cost.
• Settlements with the equipment supplier upon its purchase (incoming document, not the catalog): Dr 1330/fixed assets — Cr 3310 “Short-term Payables to Suppliers”.
• Electronic documents: for sales where applicable, an ESF (ESF IS) is issued, and when moving goods — SNT. Data from KKT and OFD linked to the device from the catalog are used when generating fiscal receipts.

Example of VAT amount. Sale of 116,000 ₸ including VAT: base = 100,000 ₸, VAT 16% = 16,000 ₸ (Cr 3130), revenue 100,000 ₸ (Cr 6010).

Norms of individual income tax/social tax (basic deduction 30 MRP/month, but not more than 360 MRP/year; individual income tax 10% up to 8,500 MRP and 15% above; social tax 10% with a base cap of 50 MZP; OPR 3.5%; VOSMS 2%; OSMS 3%; CO 5%; social tax 6%; MRP 4,325 ₸, MZP 85,000 ₸) in this catalog are not applied — they relate to salary calculations and are provided here only as a country context of the configuration.

6. Related Objects and Input on Basis

References to:

• Catalog.EquipmentDrivers — device driver;
• Catalog.Workplaces — workplace (cash register/warehouse);
• Catalog.Organizations — owner of the equipment;
• Enumerations EquipmentTypes, OfflineExchangeTransportTypes.

References / uses:

• Documents and retail processes (KKT receipts, retail sales reports, cashier workplace);
• Information registers of the “Peripheral Equipment” subsystem (matching equipment to workplaces, driver installation status);
• Exchange mechanisms with OFD/ESF IS (via WebServiceEquipmentIdentifier).

Input on basis: for the peripheral equipment catalog, a typical input on basis is not provided. Registration of KKT and related operations are performed by the form commands (“Configure…”, “Register KKT”, “Test Device”), not by the “Input on Basis” mechanism.

7. Extension Points

• Custom drivers. Support for new devices is implemented through Catalog.EquipmentDrivers (external driver processing according to the BSP standard “Peripheral Equipment”) without changing the catalog.
• Attribute Parameters (ValueStorage). Allows storing an arbitrary set of driver settings; extended on the driver configuration form side, not metadata.
• Configuration extensions (Extensions). Adding attributes (e.g., additional fields for integration with specific OFD), overriding handlers BeforeWriting, FillProcessing, adding commands to forms.
• Event subscriptions and common BSP modules. Interception of element recording for synchronization with external equipment registers.
• Additional attributes and information (subsystem “Properties”) — for accounting inventory characteristics, location, and responsible parties without modifying the configuration.

Deprecated attributes RemoveDriverHandler and RemoveExchangeFormatVersion should not be used in extensions — they are marked for removal and left only for data conversion.