Directory "EDO Subscribers" - Technical Description (Accounting for Kazakhstan 3.0)

Catalog "AbonentsEDOC" (Catalogs.AbонентыЭДОК)

Service directory of the electronic document management subsystem. Stores exchange participants (own subscribers and counterparties' subscribers) for the "1C:EDO" service in the configuration "Accounting for Kazakhstan 3.0".

Where to find: e1cib/list/Catalogs.AbонентыЭДОК (in the standard delivery, the directory is not displayed in the command interface — it is opened via the navigation link or from the service processing of the EDO subsystem).

1. Identification

Purpose. The directory stores a list of electronic document management subscribers — accounts of organizations and sole proprietors in the EDO operator's system participating in the exchange of electronic documents through the "1C:EDO" service. Each subscriber is identified by BIN (legal entities) or IIN (individuals and sole proprietors). The directory simultaneously maintains:

• own subscribers — accounts of organizations in the information base, on behalf of which documents are sent (indicator OwnSubscriber = True);
• counterparty subscribers — parties to whom documents are sent and from whom incoming documents are received.

The directory is a service, "flat" (identifier directory). It is primarily filled automatically: when connecting to the EDO service, when checking the counterparty's status, and when receiving incoming electronic documents. The accountant rarely opens the subscriber card manually — the exchange occurs through the connection wizard, incoming document processing, and status check commands.

In the Kazakhstan EDO framework, the directory addresses the parties to the exchange of documents such as ESF (electronic invoice, ESF IS) and SNT (accompanying invoice for goods).

2. Attributes and Tabular Parts

2.1 Header Attributes

The standard fields of the directory (Code, Name, DeletionMark, Predefined) are provided by the platform. The display field in lists is FullName/Name.

2.2 Tabular Parts

No tabular parts are defined ("tabular_sections": []). All subscriber data is stored in the header attributes — this is a flat identifier directory.

3. Forms

No custom forms are defined in the object card ("forms": []). The directory uses automatically generated forms by the platform:

The main interaction with subscribers occurs not through the card, but through the connection wizard to EDO, processing incoming documents, and counterparty status check commands.

4. Key Module Procedures

No specific BSL code in evidence is attached. For the service identifier directory, the following handlers are typical (object module / manager module):

• ProcessingFilling (object module) — pre-filling attributes when creating a subscriber from EDO service data (transferring BIN/IIN to IdentificationNumber, names to FullName, setting LegalEntityIndividual and OwnSubscriber).
• BeforeWriting / OnSettingDeletionMark — control of the consistency of the identifier and service indicators.
• Manager module methods (typical for the EDO subsystem) — search/create subscriber by identifier (FindCreate... by BIN/IIN), matching subscriber with counterparty and organization. These are called from the connection wizard, processing incoming documents, and status check commands, automatically filling the directory.

Requires verification for the specific version: exact names and signatures of server methods of the EDO subsystem manager module — they relate to the service API and may change between releases.

5. Posting and Movements

The directory is not posted and does not generate movements in registers/postings — like any object of the "Directory" type. It serves as a measure/addressing in the EDO subsystem.

Postings and movements occur not in the directory itself, but in accounting documents to which electronic exchange is attached (sales, receipts, etc.). For reference, typical postings of such documents according to the RK chart of accounts:

Sale of goods (from the seller's side), an ESF is issued:

Receipt of goods (from the buyer's side), incoming ESF received:

Payment is reflected in account 1030 (cash in current accounts). The VAT rate in the RK for 2026 is 16 %. The directory "AbonentsEDOC" only records the parties between which these electronic documents (ESF, SNT) circulate.

6. Related Objects and Input Based On

No input based on is provided for the service directory. Logical connections:

• Directory "Counterparties" — counterparty subscriber is matched with the counterparty element by BIN/IIN (IdentificationNumber).
• Directory "Organizations" — own subscriber (OwnSubscriber = True) is matched with the organization in the information base.
• Enumeration LegalEntityIndividualEDOC — defines the type of subscriber (legal/individual).
• Objects of the EDO subsystem — EDO accounts, exchange documents (incoming/outgoing electronic documents), connection wizard, processing incoming documents and checking counterparty status; these read and fill the directory.
• Accounting documents (sales, receipts, etc.) to which electronic ESF/SNT are attached — in them, the subscriber acts as the recipient/sender of the electronic document.

7. Extension Points

• Configuration extension. Adding attributes (for example, additional contact information of the subscriber, date of last synchronization) through object extension — without removing from support.
• Event subscriptions. Subscription to BeforeWriting/OnWriting of the directory for auto-matching the subscriber with the counterparty/organization by IdentificationNumber in custom scenarios.
• Forms. Creating a custom element/list form in the extension if a manual service interface for EDO diagnostics is required (no forms are included in the standard delivery).
• Additional attributes and information (PVC mechanism) — if necessary, mark subscribers by internal indicators without changing metadata.
• Matching processes. External/built-in processing for mass matching of subscribers with counterparties by BIN/IIN — a typical customization point during the initial connection to EDO.

Requires verification for the specific version: the complete composition of the service API of the EDO subsystem to which the directory refers (method names of the manager module) — clarified for release 3.0.74.2.