Document "ElectronicDocumentOutgoingEDOC" (Accounting for Kazakhstan 3.0)

1. Identification

Purpose. The document is an accounting “wrapper” (envelope) over the outgoing electronic document that the organization sends to the counterparty through the EDO operator: invoice, act, bill, agreement, electronic invoice (ESF), etc. It stores the details of the sent document (type, number, date, amount, name, description), its identifiers in the EDO system (IS ESF / operator), and the connection with the primary document of the accounting database, as well as the list of recipients/signatories and the requirements presented to them.

Important about role separation:

• the sent document itself stores this object (transport and accounting node of the outgoing direction, mirroring the incoming);
• each change of state (delivered, signed, rejected) — a separate document MessageEDOK;
• the economic operation is reflected by the primary accounting document (ESF, sale, act), from which the outgoing ED is formed.

The object does not make accounting entries and does not have movement registers — it is a transport and accounting document.

2. Attributes of Header and Table Parts

2.1 Header Attributes (by evidence and standard model of EDO)

In addition to the listed, the object stores “card” attributes of the sent document: type, number, date, amount, name, description of the sent ED.

2.2 Table Part RecipientsAndSignatories

List of recipients and the requirements presented to them with the results of the approval.

3. Forms

An explicit list of forms in evidence is not attached; below is the standard composition for a document of this type (to be specified for a specific assembly):

The EDO workplace (general form of the subsystem) serves as the initiation point for creating and sending outgoing documents.

4. Key Procedures of Modules

Evidence with paths path:string and BSL code for this object is not attached. Below are standard handlers for documents of this type (transport object of EDO, without entries):

• Object Module → CheckFillingProcessing — control of mandatory attributes: Organization, filling of recipients (RecipientED), when responding in the chain — DocumentBasis.
• Object Module → BeforeSaving / OnSaving — fixation/actualization of EDO identifiers and connection with the primary document; service logic of the EDO subsystem.
• Document Form → OnCreationOnServer — initialization from the primary document/incoming ED, filling in card attributes and recipients.
• Document Form → EDO subsystem commands — “Sign with EDS”, “Send to operator” (fills DocumentIdentifierEDO, AuthorIdentifierEDO), “Cancel” (fills DocumentIdentifierTerminatingAction).
• Status Update — synchronization of ResultOfRequirementToRecipient, DateOfFulfillment, ExplanationOfResultOfRequirement based on data from related MessageEDOK.

Requires verification (version-specific): exact names of procedures and modules of the specific assembly 3.0.74.2, as the code of modules in evidence is not provided.

5. Entries and Movements

The document is not recorded in accounting/tax accounting and does not generate movements:

• accounting registers — none;
• accumulation/information registers from this object — none (except for service mechanisms of the EDO subsystem);
• entries — none.

All actual accounting operations are reflected by the related primary accounting document (DocumentBasis). It is the one that generates entries according to the standard Chart of Accounts of the RK, for example:

The example illustrates the accounting of the primary document, not the envelope of EDO itself. The VAT rate for the RK in 2026 is 16 %. MRP = 4,325 ₸, MZP = 85,000 ₸.

Electronic forms to which the envelope relates: ESF (IS ESF) and SNT.

6. Related Objects and Input on Basis

Related Objects:

• MessageEDOK — records each change of state (delivered/signed/rejected); chronology of approvals for the document.
• Primary accounting document (ESF, sale, act, bill, agreement) — source of data and carrier of entries; reference in DocumentBasis.
• Incoming ED (ElectronicDocumentIncomingEDOK, mirror object) — as a basis when responding in the EDO chain.
• Subscribers/accounting records of EDO — recipients/signatories (RecipientED).

Input on Basis / Formation:

• Outgoing ED is formed from the primary accounting document or from the EDO workplace (scenario 3.1).
• Response to incoming (scenario 3.4): outgoing is created with indication of the incoming ED in DocumentBasis and DocumentBasisIdentifierEDO.

7. Extension Points

• Filling Check Processing — adding controls (matching recipients to EDO subscribers, correctness of basis reference, mandatory attributes).
• Subscriptions to Events (BeforeSaving/OnSaving) — integration with external EDO operators, logging, auto-filling identifiers.
• Forms (configuration extension) — adding commands/status indicators, columns in table part RecipientsAndSignatories.
• Exchange and Conversion Rules — mapping types of outgoing ED (ESF, SNT) during integration.
• Reporting on EDO — building registers of outgoing documents and approval results based on attributes and MessageEDOK.

Since the object does not participate in entries, extension points for registers/movements are absent — it is advisable to extend transport and validation logic.