Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0).
The counterparty has sent you an act via EDO. In "Current EDO Affairs," a red "Requires reflection in accounting" is flashing, and the list of receipts is empty. You open the incoming message, see the electronic document file, the supplier's signature, and next to it, a "Create Document" button. The amount in the act is 1,160,000 ₸, but you had a different amount in the contract. This screen is where the work with the "EDO Message" document begins: it is not an accounting entry; it is a envelope containing the electronic document from the counterparty (or your outgoing one), its signatures, and the exchange history with the operator.
1. Purpose
The "EDO Message" is a service document-container for electronic document management. It stores a single exchange message with the counterparty through the EDO operator: the electronic document itself (act, invoice, payment request, UPD-analog, and in the RK — linkage with the ESF and SCT), electronic signatures, delivery status, and history. It does not create entries by itself — based on it, you create "real" accounting documents (Receipt, Sale, ESF), which then move the accounts.
2. Where to find
- Through the EDO workplace: section "Sales" or "Purchases" → "EDO" → "Current EDO Affairs". Here you see incoming and outgoing messages by status ("To be reflected in accounting," "Requires signature," "Awaiting confirmation"). A double click on the line opens the message.
- Document list: section "Sales" / "Purchases" → journal "Electronic Documents" (or "EDO Messages").
- Direct navigation link 1C:
e1cib/list/Document.EDOMessage— copy it, then "Service" → "Go to navigation link" (or Ctrl+F in the main menu → "Go to link") to open the list directly.
Creating this message manually "from scratch" is almost never necessary — it appears automatically when sending or receiving a document through the EDO operator.
2a. How to find out your release
Main menu (☰ icon or "Service") → "Help" → "About the program". In the opened window: "Platform version" (for example, 8.3.24.x) and the line "Accounting for Kazakhstan, version 3.0 (3.0.74.2)". If your numbers differ from those indicated in the header — the interface and the set of fields may slightly differ from this manual.
3. How to fill out
During normal operation, the fields are filled automatically from the received or sent document. However, it is essential to know what each field is responsible for — then you will understand where the exchange "broke."
| Field | Mandatory | Purpose and what happens in case of error |
|---|---|---|
| Organization | ✅ | Your company (recipient/sender). If the wrong organization is substituted, the ESF will go out with the wrong BIN — the operator will reject it. |
| Counterparty | ✅ | Sender (incoming) or recipient (outgoing). Determined by the BIN from the card. No BIN — the message will "hang" without identification. |
| Message type | ✅ | Incoming / Outgoing. Determines who signs first and what document is created based on it. |
| Electronic document | ✅ | Type of attachment: act of completed works, invoice, payment request, ESF, SCT. The type determines what accounting document 1C will suggest creating. |
| Status | — (auto) | Draft → Awaiting confirmation → Delivered → Signed by the counterparty → Requires reflection in accounting → Completed. Not editable manually — changes during the exchange. |
| Identifier | auto | Unique message number with the operator. It is used to search for loss: if the status is "Sent," but the recipient does not see it — the identifier is checked. |
| Date / Number | auto | Date of the exchange event, not the date of the economic operation. The date of the entry is set in the accounting document created based on it. |
| Comment / Reason for rejection | — | If you or the counterparty reject the document, the reason is written here (for example, "the amount does not match the contract"). |
The main buttons on the message form:
- "Sign and send" / "Approve" — applies your digital signature.
- "Reject" — with indication of the reason (the incoming document will return to the sender for correction).
- "Create document" / "Reflect in accounting" — turns the attachment into an internal document (Receipt, Sale).
- "Match" — links the nomenclature and the counterparty's contract to your directories.
4. An example with entries
The supplier LLP "Astana-Snab" sent you an electronic invoice and ESF for a batch of goods via EDO.
Conditions:
- Goods — 1,000,000 ₸ (excluding VAT);
- VAT 16% — 160,000 ₸;
- Total amount due — 1,160,000 ₸.
Your actions:
- In "Current EDO Affairs," open the incoming message with the status "Requires reflection in accounting."
- Verify the amount of 1,160,000 ₸ with the contract — it matches.
- Click "Match": link the item "Cable VVG 3×2.5" to your nomenclature and account 1330 "Goods".
- Click "Create document" → "Receipt of goods and services". 1C generates the receipt document, and the EDO Message is marked as reflected in accounting.
- Post the created "Receipt."
The receipt document creates the entries (not the message itself):
| Dr | Cr | Amount, ₸ | Description |
|---|---|---|---|
| 1330 | 3310 | 1,000,000 | Goods received |
| 1420 | 3310 | 160,000 | VAT accounted for deduction (16%) |
Total credit of account 3310 "Short-term payables to suppliers" — 1,160,000 ₸.
When paying from the settlement account later, it will be formed: Dr 3310 Cr 1030 — 1,160,000 ₸.
The reverse situation (you are the seller). Sale of 1,000,000 ₸ + VAT 16% = 1,160,000 ₸. The accounting document "Sale" will give: Dr 1210 Cr 6010 — 1,000,000; Dr 1210 Cr 3130 — 160,000 (VAT payable); Dr 7010 Cr 1330 — cost of goods sold. The "EDO Message" will only deliver the signed copy to the counterparty and return its signature to you.
5. Types of operations
The document serves both directions of exchange:
- Incoming — reflection in accounting: received invoice/act → create Receipt.
- Incoming — signing: the counterparty sent a document for your signature → you sign with a digital signature or reject it.
- Outgoing — sending: you created Sale/Act → sent the electronic document to the counterparty.
- Outgoing — receiving confirmation: waiting for the counterparty's signature, the status changes to "Signed by both parties."
- Service: notifications of receipt, notifications for clarification, withdrawal/cancellation of the document, invitations to exchange.
6. What is formed during posting
The "EDO Message" does not create accounting entries. During its processing, the following occurs:
- EDO information registers: document statuses, linking the electronic document to the accounting one, storage of signature files and the XML itself.
- Creation of an accounting document (Receipt, Sale, Payment request) — it is this document that provides entries upon posting (1330/1420/3310, 1210/6010/3130/7010).
- Connection with the ESF IS: the electronic invoice is issued/received in the ESF information system; the ESF status ("Delivered," "Viewed") is pulled into the message.
- Connection with SCT: if the goods require accompaniment — linkage with the accompanying invoice for goods (virtual warehouse).
7. Printed forms
- Print of the electronic document in external printed form (act, invoice, payment request) — button "Print" in the message form.
- Card of the electronic document with marks about electronic signatures (who, when, certificate).
- Exchange protocol / history of message statuses.
- Printed forms of the accounting document created based on it (for example, invoice F-2, payment request) — from the Receipt/Sale itself.
8. Common errors
"Failed to decrypt/verify the signature. Certificate not found or not installed." The root certificate of the CA is not installed or the private key is missing. Install the certificate in the storage, check in "Administration" → "Exchange of electronic documents" → "EP settings".
"Counterparty not found by BIN." The counterparty's card has an empty or incorrect BIN/IIN. Fill in the BIN — it is the key to identification in EDO.
"Document cannot be reflected in accounting: nomenclature not matched." Items from the supplier's invoice are not linked to your directories. Click "Match" and specify the nomenclature, units, accounting accounts.
"The amount of the electronic document does not match the amount of the accounting document." Discrepancy in price/quantity/VAT between the attachment and the created receipt. Open both, verify the lines and the rate (in RK from 2026 — 16%, not 12%), correct or reject the incoming with a reason.
"Sending error: exceeded the subscription/tariff limit of the EDO operator." The package of outgoing documents is exhausted. Top up the tariff with the operator; after that, sending resumes, press "Send" again on the same message.
"ESF rejected in the ESF IS." The reason is visible in the status — usually an incorrect TN VED code, product origin indicator, or date outside the issuance period. Correct in the underlying document and resend.
9. FAQ
Below are the questions most frequently asked about this document.
10. Related documents
Based on the "EDO Message," the following are created:
- Receipt of goods and services (incoming invoice/act);
- Sale of goods and services — confirmed by signature through the outgoing message;
- Payment request to the buyer/from the supplier;
- Electronic invoice (ESF) — linkage with the ESF IS;
- Accompanying invoice (SCT) — for goods in the virtual warehouse.
The "EDO Message" is generated from:
- Sale of goods and services, Act of completed works — when clicking "EDO → Send electronic document";
- Payment request to the buyer;
- ESF statement — when sent through the operator.
How to find out your release
Main menu → "Help" → "About the program". The line "Accounting for Kazakhstan, version 3.0" and the release number (you should have 3.0.74.2), as well as the version of the 1C:Enterprise platform. If the release is newer — the location of the EDO buttons may have changed, but the exchange logic remains the same.
This manual is prepared for "Accounting for Kazakhstan," version 3.0, release 3.0.74.2. All rates and limits are according to RK norms for 2026: VAT 16%, MRP 4,325 ₸, MSP 85,000 ₸.