Document "ElectronicDocumentIncomingEDOC" — technical description (BK 3.0.74.2)

1. Identification

Purpose. The object is an accounting "wrapper" (envelope) over an incoming electronic document received from a counterparty via an EDF operator: a waybill, act, invoice, agreement, etc. It stores the attributes of the received document (type, number, date, amount, name, description), its identifiers in the EDF system, the link to the primary document of the accounting database, as well as the list of recipients/signatories and the requirements placed on them.

The document is a transport-and-accounting node: it records the fact of receipt and the requirements to participants, but by itself does not affect the balance. The separation of roles within the subsystem is important:

• ЭлектронныйДокументВходящийЭДОК — stores the incoming document itself;
• СообщениеЭДОК — each state change (status history, requirements, signatures);
• the linked primary accounting document (receipt, act, ESF, etc.) — reflects the business transaction and makes the postings.

Amounts are stored in the document currency (attribute ВалютаДокумента); the base accounting currency is tenge (₸).

2. Header attributes and tabular sections

2.1 Header attributes

2.2 Tabular section ПолучателиИПодписанты

The tabular section describes the exchange participants and the status of their actions on this incoming document; the signing/rejection acts themselves are performed by means of the EDF subsystem and recorded by СообщениеЭДОК documents.

3. Forms

Since the composition of forms is not explicitly attached in the evidence, below is a typical set of EDF subsystem forms for this type of object:

Where to find: the "EDF" section/workplace → "Incoming electronic documents" list. Navigation link: e1cib/list/Документ.ЭлектронныйДокументВходящийЭДОК.

4. Key module procedures

The BSL modules are not attached in the evidence, so typical handlers for an EDF subsystem "wrapper" document are provided. The specific signatures and the presence of procedures in this version are version-specific and require verification against the modules of configuration 3.0.74.2.

Object module:

• ОбработкаЗаполнения(ДанныеЗаполнения, ...) — filling in attributes upon creation from EDF data/on the basis of (type, number, date, amount, currency, EDF identifiers, recipients).
• ОбработкаПроверкиЗаполнения(Отказ, ПроверяемыеРеквизиты) — control of mandatory fields (for example, presence of a correct ИдентификаторДокументаПрекращающегоДействие upon annulment).
• ПередЗаписью(Отказ, РежимЗаписи, РежимПроведения) — service write logic; posting is not performed.

Document form module:

• ПриСозданииНаСервере / ПриОткрытии — form initialization, availability of requirement-processing commands.
• Navigation commands: open the linked primary document (СсылкаНаПервичныйДокумент), open the status history (СообщениеЭДОК), generate an outgoing EDF document with the current one as the basis.
• Requirement execution handlers (sign/reject) — call procedures of the EDF subsystem's common modules.

EDF subsystem common modules — creating the object during synchronization, registering states, working with subscribers and requirements (implementation outside this object).

5. Posting and movements

The document is not posted and generates no register movements. The object itself has no accumulation/information registers, it does not make accounting postings and does not affect the balance. This is a fundamental feature: ЭлектронныйДокументВходящийЭДОК is a transport-and-accounting envelope.

The actual accounting consequences are reflected by the linked primary document (СсылкаНаПервичныйДокумент), which is created/selected based on the type of the incoming document. It is this document that generates the postings under the standard RK chart of accounts. Indicative logic (figures and rates — Kazakhstan, 2026):

The VAT rate in RK for 2026 is 16 %. Electronic invoices (ESF, ESF IS) and consignment notes for goods (CTA) are separate primary/tax documents, linked via СсылкаНаПервичныйДокумент and EDF identifiers. Accruals and tax rules (IIT 10 %/15 % with a threshold of 8,500 MCI of annual income, deduction of 30 MCI/month and no more than 360 MCI per year, MPC 10 % with a cap of 50 MMW, EMPC 3.5 %, MHIC 2 %, SHIC 3 %, SC 5 %, social tax 6 %; MCI = 4,325 ₸, MMW = 85,000 ₸) have no direct relation to this object — it does not participate in tax calculation and does not generate their movements.

6. Related objects and entry on the basis of

Entry on the basis of: the typical scenario is creating a primary accounting document or an outgoing electronic EDF document on the basis of the incoming one (the link is preserved via ДокументОснование/СсылкаНаПервичныйДокумент). The specific set of "Create on the basis of" commands in 3.0.74.2 is determined by the EDF subsystem settings.

7. Extension points

• Fill handler (ОбработкаЗаполнения) — additional configuration of mapping EDF data into attributes during synchronization.
• Fill check (ОбработкаПроверки�эаполнения) — additional attribute control (for example, requiring СсылкаНаПервичныйДокумент for certain document types).
• Forms (configuration/SSL extension) — adding commands, attributes and recipient tabular section columns without removing from support.
• EDF subsystem common modules — overridable procedures for object creation, requirement processing and state registration.
• Event subscriptions (ПередЗаписью/ПриЗаписи) — integration with external systems, audit of incoming document receipt.
• Linking with the primary document — extending the auto-selection/auto-creation logic of the primary document by ВидДокумента.

Version-specific and requiring verification against 3.0.74.2: the exact composition of forms, the presence and signatures of module procedures, the set of "Create on the basis of" commands and the rules for automatic linking with primary documents.