1. Identification
| Parameter | Value |
|---|---|
| Object type | Catalog |
| Name | ВидыДокументовЭДО |
| Full name | Справочник.ВидыДокументовЭДО (Catalogs.ВидыДокументовЭДО) |
| Synonym | "EDF Document Types" |
| Configuration | Trade Management for Kazakhstan, ed. 3.4 (version 3.4.5.21) |
| Where to find in 1C | Section "Electronic Interaction" → "EDF Document Types" |
| Navigation link | e1cib/list/Справочник.ВидыДокументовЭДО |
Purpose. A classifier catalog that stores the list of types of electronic documents exchanged by the organization via EDF (electronic document flow). In the context of Kazakhstan, these are primarily document types of state information systems — ESF (electronic invoice, ESF IS) and SNT (waybill for goods) — as well as other formats of electronic interaction with counterparties and EDF operators. Catalog items are used as a dimension/attribute when configuring routes for processing incoming and outgoing electronic documents, when matching document formats, and for filters in EDF workplaces. The catalog itself is reference and regulatory information (RRI) and does not generate accounting or tax movements on its own.
2. Header attributes and tabular sections
The catalog belongs to the classification (simple) type — as a rule, without tabular sections. Composition of header attributes (typical for EDF document type classifiers):
| Attribute | Type | Purpose |
|---|---|---|
Code |
String/Number | Unique code of the item (standard catalog attribute). |
Description |
String | Representation of the EDF document type (e.g., "Electronic Invoice (ESF)", "SNT"). |
DeletionMark |
Boolean | Standard deletion mark attribute. |
Predefined |
System | Predefined item flag (standard EDF document types are supplied as predefined). |
Tabular sections: none (classifier without nested tables).
Note: the specific set of additional attributes (format identifier, direction, government system flag) is version-specific — requires verification in the specific 3.4.5.21 build via Configurator. The basic composition (Code/Description) is always present.
3. Forms
| Form | Purpose |
|---|---|
Item Form (ФормаЭлемента) |
View and edit a single EDF document type: description, code, system flags. |
List Form (ФормаСписка) |
Main workplace of the catalog: viewing the list of document types, search, filtering, deletion mark. Opened via the navigation link. |
Selection Form (ФормаВыбора) |
Value selection when filling attributes of type СправочникСсылка.ВидыДокументовЭДО in EDF settings and related documents. |
If specialized forms are not defined in the metadata, the platform uses auto-generated list/item/selection forms.
4. Key module procedures
The attached evidence does not include BSL code (paths path:line), so below are the typical handlers for a classifier catalog of this type. Specific implementations should be checked in the form module and manager module of build 3.4.5.21.
Object module:
FillingProcessing(FillingData, StandardProcessing)— filling in attributes of a new item when entered based on/by parameters.BeforeWrite(Cancel)— validity checking before writing (checking that the description is filled in, uniqueness).FillCheckProcessing(Cancel, CheckedAttributes)— checking required attributes.
Manager module:
- Procedures for obtaining predefined values and system functions for selecting the EDF document type by format/document identifier (used by the EDF subsystem when parsing incoming files).
List/item form module:
OnCreateAtServer(Cancel, StandardProcessing)— configuring visibility, filters, conditional formatting.- Handlers for selecting and opening an item from EDF workplaces.
5. Posting and movements
The catalog is not posted and does not independently generate register movements or accounting entries — it is an RRI object. Catalog values are involved in EDF document flow indirectly: they define the type/format of the electronic document, while actual movements are generated by related accounting documents (sales, receipts, invoices) to which the electronic document is linked.
To illustrate the end-to-end logic — movements are generated, for example, by a sales document corresponding to an electronic document of the "ESF" type. Figures and accounts — according to the standard chart of accounts of Kazakhstan and a VAT rate of 16% (2026):
Sale of goods for 116,000 ₸ (including VAT 16% = 16,000 ₸, cost of goods 70,000 ₸):
| Dr | Cr | Amount, ₸ | Description |
|---|---|---|---|
| 1210 | 6010 | 100,000 | Revenue from sales to customers |
| 1210 | 3130 | 16,000 | VAT payable (16%) |
| 7010 | 1330 | 70,000 | Write-off of cost of goods |
Payment from the customer to the current account: Dr 1030 Cr 1210 — 116,000 ₸. Settlements with suppliers on accounts payable: Cr 3310 (upon receipt).
When issuing an electronic invoice in the ESF IS and preparing an SNT, the source documents use the EDF document type from this catalog for routing and status control; accounting movements are generated by the primary documents, not by the catalog.
Other Kazakhstan 2026 rates for related calculations (for reference only, not directly related to this object): individual income tax (IIT) 10% up to 8,500 MCI of annual income and 15% above; basic IIT deduction — 30 MCI/month (no more than 360 MCI/year); mandatory pension contributions (OPV) 10% (base cap 50 MMW), employer pension contributions (OPVR) 3.5%, mandatory social health insurance contributions (VOSMS) 2%, social health insurance contributions (OSMS) 3%, social contributions (SO) 5%, social tax 6%. MCI = 4,325 ₸, MMW = 85,000 ₸.
6. Related objects and entry based on
- EDF subsystem: catalog items are used in electronic document exchange settings, in generating and receiving ESF/SNT, in "Current EDF Tasks" workplaces.
- Source documents: sale of goods/services, receipt of goods/services, invoices issued/received — electronic documents of the corresponding type are linked to them.
- Information registers of the EDF subsystem (statuses, format correspondences, exchange history) use the EDF document type as a dimension/attribute.
- Entry based on: not typical for a classifier; items are usually created manually or supplied as predefined.
7. Extension points
- Configuration extension: adding attributes (e.g., a custom format identifier, exchange direction) and predefined items without removing support.
- Object module handlers
BeforeWrite/FillCheckProcessing— for additional validation. - Additional attributes/information (properties subsystem) — for classifying EDF document types without changing the metadata structure.
- Catalog write event subscriptions — for integration logic (synchronization with the EDF operator).
- List/item form extension — adding filters, commands, formatting in EDF workplaces.
