1. Identification of the Object
| Parameter | Value |
|---|---|
| Object Type | Document (Documents) |
| Name | ElectronicActOfCompletedWorks |
| Full Metadata Path | Document.ElectronicActOfCompletedWorks |
| Synonym | “Electronic Act of Completed Works” |
| Configuration | Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) |
| Navigation Link | e1cib/list/Document.ElectronicActOfCompletedWorks |
| Where to Find in the Interface | Section “Sales” → “Electronic Act of Completed Works” (lists of incoming and outgoing acts) |
Purpose. The electronic act of completed works (EAWR/AR) is an object of electronic document management (EDM) in the integration framework with the Information System of Electronic Invoices (IS ESF) of the Republic of Kazakhstan. The document records the fact of work performed or services rendered in electronic form with a legally significant electronic signature (E-Signature) and ensures bilateral exchange between the performer (supplier) and the customer (recipient). The document goes through a life cycle: formation → signing → sending → confirmation / rejection / termination. This is a document management, not an accounting object: it does not reflect the economic operation in accounting records (see section 5), but serves as a transport and legal shell for the act in the format of IS ESF.
2. Header Attributes and Table Parts
2.1 Header Attributes
| Attribute | Purpose | Mandatory |
|---|---|---|
| DateOfWorkCompletion | Date of actual completion of work / services reflected in the act | Mandatory |
| CurrencyCode | Currency code of the document. For domestic operations in the RK — tenge (398, ₸) |
Mandatory |
| Direction | Indicator “Outgoing / Incoming” — determines the role of the organization (performer or customer) and the available set of actions by scenarios | Mandatory |
Other header attributes (document number, date, organization, EDM status, link to related ESF, signature attributes) are filled in automatically during formation and exchange.
2.2 Table Part “Suppliers”
Attributes of the performing party.
| Column | Type | Purpose | Mandatory |
|---|---|---|---|
| SupplierName | String | Name of the performing organization (supplier of works/services) | Mandatory |
2.3 Table Part “Recipients”
Attributes of the customer party.
| Column | Type | Purpose | Mandatory |
|---|---|---|---|
| RecipientName | String | Name of the customer organization (recipient of works/services) | Mandatory |
2.4 Table Part “Services”
Line-by-line composition of completed works / rendered services.
| Column | Type | Purpose | Mandatory |
|---|---|---|---|
| ServiceName | String | Name of the work / service | Mandatory |
| CostExcludingIndirectTaxes | Number | Cost excluding VAT (tax base of the line) | Mandatory |
| VATRate | — | VAT rate for the line. The current standard VAT rate in the RK for 2026 is 16% | Mandatory |
| CostIncludingIndirectTaxes | Number | Cost including VAT (base + VAT amount) | Mandatory |
Example of line calculation (rate 16%): base 1,000,000 ₸ → VAT 160,000 ₸ → cost including indirect taxes 1,160,000 ₸.
2.5 Service Table Part “TypicalErrors”
Stores validation results and errors of exchange with IS ESF.
| Column | Type | Purpose |
|---|---|---|
| Text | String | Error message text |
| Field | String | Identifier of the field to which the error relates |
If any of the mandatory fields (sections 2.1–2.4) are not filled in, the platform will not allow the document to be processed/sent and will issue a message like “Field … is not filled in”.
3. Forms
The composition of forms typical for the EDM document of this type:
| Form | Purpose |
|---|---|
| DocumentForm | Main form for editing the act: header, table parts “Suppliers”, “Recipients”, “Services”, EDM status panel and exchange commands (sign, send, confirm, reject, terminate) |
| ListForm | List of documents; practically divided by the Direction attribute into lists of outgoing and incoming acts |
| SelectForm | Selecting an act from other objects (for example, when entering based on or selecting a related document) |
| Error Display Form | Output of the contents of the table part “TypicalErrors” — validation results and responses from IS ESF |
4. Key Procedures of Modules
In the attached evidence, the original BSL code (paths
path:string) is not provided. Below is the typical composition of handlers for the EDM document of this type; specific names of procedures are specified by module in the delivery 3.0.74.2.
Object Module:
ProcessingConducting(Refusal, ConductingMode)— for this object, movements in accounting registers are not formed (see section 5); conducting manages the status of document management and/or registration in the registers of EDM status information.ProcessingFilling(FillingData)— filling in attributes when entering based on (transferring parties and composition of services).CheckFilling()/ProcessingCheckFilling(Refusal, CheckedAttributes)— control of mandatory fields:DateOfWorkCompletion,CurrencyCode,Direction,SupplierName,RecipientNameand columns of the table part “Services”; filling the table part “TypicalErrors”.
Document Form Module:
OnCreationOnServer— setting the visibility of exchange commands depending onDirectionand the current EDM status.- Handlers of scenario commands (section 3 evidence): “Sign and Send”, “Confirm”, “Reject”, “Terminate”, “Issue Corrected Act”.
General/Managerial Exchange Modules: formation of XML package in IS ESF format, applying E-Signature, sending/receiving, parsing responses and recording statuses and validation errors.
5. Conducting and Movements in Registers
The document does not create movements in accounting registers. This is purely a document management object for exchange with IS ESF. Registration is only conducted in specialized information registers for tracking the statuses of electronic documents (status of signing/confirmation/rejection/termination, identifiers of IS ESF, exchange history).
How the Operation is Reflected in Accounting
The financial result for completed works/services is conducted by other (accounting) documents of the configuration (implementation of works/services), with which the act is related. According to the standard logic of the RK chart of accounts, the implementation of services is reflected as follows:
| Entry | Dr | Cr | Content |
|---|---|---|---|
| Recognition of income | 1210 “Short-term Receivables from Customers” | 6010 “Income from Sales” | At cost excluding VAT |
| Accrual of VAT (16%) | 1210 | 3130 “VAT Payable” | VAT amount at the rate of 16% |
| Write-off of cost | 7010 “Cost of Sales” | 1330 “Goods” (or expense/unfinished goods account) | At the cost of completed works |
Example: service for 1,000,000 ₸ excluding VAT → Dr 1210 Cr 6010 = 1,000,000 ₸; Dr 1210 Cr 3130 = 160,000 ₸ (VAT 16%). Payment from the customer — Dr 1030 “Cash in Current Accounts” Cr 1210.
The EAWR itself does not make these entries — it merely accompanies the operation with a legally significant electronic act and exchange with IS ESF.
6. Related Objects and Entry Based On
- ESF (electronic invoice) — the act is part of the overall framework of IS ESF; a link is maintained between the act and the ESF by operation.
- SNT (accompanying invoice for goods) — a related electronic document in the IS ESF framework (for operations with goods).
- Documents of implementation of works/services — accounting documents that form entries (section 5); the act can be formed based on the implementation and vice versa transfer the composition of services and parties when entering based on.
- Information registers of EDM statuses — service objects for storing exchange history.
Lifecycle Scenarios (from evidence)
| No. | Scenario | When Applied |
|---|---|---|
| 3.1 | Creating and Sending Outgoing Act | The performer has completed works/services and sends the act to the customer for signing |
| 3.2 | Confirming Incoming Act | The customer received the act and confirms the completion of works |
| 3.3 | Rejecting Incoming Act | The customer disagrees with the content (volumes, prices, composition of works) |
| 3.4 | Terminating Confirmed Act | After confirmation, errors are identified, the previously confirmed act is canceled |
| 3.5 | Issuing Corrected Act | The performer received the rejected act and issues a new, corrected act |
7. Extension Points
- Subscriptions to Events (Event Subscription) — on
ProcessingCheckFilling,BeforeRecording,OnRecordingfor additional control of the composition of services and amounts. - Configuration Extension — adding header/table part attributes, changing forms (
DocumentForm,ListForm), borrowing and overriding scenario command handlers. - Validation Rules — adding checks with filling the table part “TypicalErrors” (field
Field+Text). - Exchange with IS ESF — extending export/import XML formats, processing responses and statuses in information registers.
- Formatting amounts and VAT rates — when reflecting in accounting, control the application of the current rate of 16% (not the outdated 12%).
Requires verification (version-specific): exact names of procedures of object/form modules and the composition of information registers of EDM statuses in the specific assembly 3.0.74.2 — specified by metadata of the delivery.