Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0).
The counterparty calls: "We do not see your act in the electronic document flow." You are sure you sent it. You open the list of outgoing electronic documents — and see the status "Sending error" or "Awaiting signature." Or vice versa: the document was sent, but the counterparty sent a rejection because they have a different amount. This object exists precisely for such situations. It is not about entries — it is about what exactly, to whom, and in what state you sent via electronic document flow.
1. Purpose
The document "Outgoing electronic document (EDO)" is an envelope for the electronic document that you send to the counterparty through the EDO operator. It stores a link to the underlying document (sale, act, invoice, contract), the file itself in the approved format, electronic signatures, and the current status of the exchange. It does not create accounting entries — they are already present in the underlying document.
2. Where to find
Several ways — whichever is more convenient:
- Section "Sales" → "Current EDO Affairs" — the workplace from where all sending occurs. From here, the document is automatically created when you click "EDO → Send" in the sale or act.
- Section "Purchases"/"Sales" → "EDO Archive" — view already sent documents.
- "Administration" → "Exchange of Electronic Documents" — connection settings, certificates, agreements with counterparties.
To open the list directly: "Service" → "Go to navigation link" and paste the line:
e1cib/list/Document.OutgoingElectronicDocumentEDO
2a. How to find out your release
"Help" → "About the program" (or the "i" icon in the upper right corner). In the opened window — the version of the "1C:Enterprise" platform (for example, 8.3.24) and the configuration release: the line "Accounting for Kazakhstan, version 3.0 (3.0.74.2)". This instruction refers to this release. If your numbers differ — the composition of fields and names of EDO commands may slightly change, check by meaning.
3. How to fill out
In 99% of cases, you do not create the document manually — it is generated from the underlying document. But you need to know the fields to understand what to check.
| Field | Why and what will happen if you make a mistake |
|---|---|
| Organization (MANDATORY) | From whose name you are sending. The digital signature certificate and exchange settings are taken from it. If you make a mistake — you will sign with someone else's key, and the counterparty will reject it. |
| Counterparty (MANDATORY) | To whom the document is sent. The identifier of the EDO participant is selected based on it. If the counterparty is not connected — sending will not be possible. |
| Contract | Link to the agreement. Affects analytics and what package of documents the recipient is expecting. |
| Document type (MANDATORY) | What you are sending: act, invoice, payment request, contract, arbitrary document. Determines the file format and printed form. An incorrect type — the counterparty will not be able to recognize the document on their end. |
| Underlying document | Link to the sale/act/invoice in your database. It takes amounts, nomenclature, and file from it. An empty underlying document = "arbitrary" document, which will need to be attached as a file manually. |
| Date (MANDATORY) | Date of envelope formation. Does not affect accounting but appears in the exchange card. |
| EDO operator | Through whom the exchange occurs. It is taken from the settings. If the operators of you and the counterparty are different — roaming works, and it must be set up in advance. |
| EDO status | Not edited manually — changes during the exchange (see section 6). This is your main indicator: delivered/not delivered. |
| Responsible | Who manages the document. Useful when several people are involved in sending. |
| Comment | Free text. Here you can write, for example, "resent after correcting the amount". |
After filling out, click "Sign and Send" — the program applies the digital signature and sends the file to the operator.
4. An example with numbers and entries
Situation. On September 5, 2026, LLP "Astana-Trade" shipped a batch of goods to LLP "Client" for 300,000 ₸ excluding VAT. VAT at the rate of 16% = 48,000 ₸. Total payable — 348,000 ₸. The cost of goods — 210,000 ₸. The underlying document — "Sale of goods and services".
First, the entries are generated by the sale (not the EDO document itself):
| Debit | Credit | Amount, ₸ | Content |
|---|---|---|---|
| 1210 | 6010 | 300,000 | Income from the sale of goods |
| 1210 | 3130 | 48,000 | VAT payable (16%) |
| 7010 | 1330 | 210,000 | Cost of sold goods written off |
Then in the sale, you click "EDO → Send". The program:
- Creates an "Outgoing electronic document (EDO)" with the type "Invoice", based on your sale, with the amount of 348,000 ₸.
- Signs the file with your digital signature, the status changes to "Awaiting notification receipt".
- After delivery to the counterparty, the status becomes "Awaiting confirmation", and when they sign on their side — "Completed".
The EDO envelope does not create accounting entries — it only records movements in the registers of electronic document flow. Note: VAT is exactly 48,000 ₸ (16% of 300,000), not 36,000 ₸ at the old rate of 12% — if the counterparty sent a rejection due to the VAT amount, it is most often due to outdated rate settings on one of the sides.
5. Types of operations
The "Document type" specifies what exactly is sent to the counterparty:
- Invoice (sale of goods) — shipment of goods.
- Act of completed works (services) — based on the document "Sale of services".
- Payment request — for payment approval.
- Contract — exchange of contractual documents.
- Arbitrary document — any attached file (power of attorney, letter, additional agreement).
Fiscal documents of the RK stand apart: ESF (electronic invoice) goes through the IS ESF, and SNT (accompanying invoice for goods) — through its module. This is not the same mechanism as "EDO counterparty-counterparty," although the interface is similar. Do not confuse: the act in EDO does not replace the ESF.
6. What is generated during processing
- No entries in accounts. Accounting is done by the underlying document.
- Movements in EDO registers — document status, exchange history, linking the digital signature to the file, matching with the underlying document.
- Electronic file in the approved exchange format + container with the electronic signature.
- Technological notifications from the operator (about delivery, receipt, rejection) are automatically pulled in and change the status.
The chain of statuses that you will see: Prepared → Awaiting signature → Signed → Sent → Delivered → Awaiting confirmation → Completed. Deadlocks: Rejected (the counterparty disagrees) and Sending error (connection/certificate issue).
7. Printed forms
From the card of the outgoing electronic document, the following are available:
- Printed form of the underlying document (invoice, act, payment request) — what a person sees.
- Card of the electronic document — service summary: who, to whom, when, which operator, which signatures are applied.
- Protocol (history) of exchange — all statuses with dates and times; it is what is attached when disputing "sent — not sent".
- Information about digital signature certificates — who and when signed.
8. Common errors
"Failed to find EDO settings with the counterparty" — the counterparty is not connected to the exchange or has not accepted the invitation. Go to "Administration → Exchange of electronic documents → EDO settings," send the counterparty an invitation, and wait for their consent.
"Certificate has expired" or "No certificate found for signing" — the digital signature is expired/not installed. Update the key in the NUC RK, add the certificate to the personal storage, and specify it in the signing settings.
"Document has already been sent earlier" — you are clicking send again. Check the status: if "Delivered" — everything has been sent to the counterparty, no need to duplicate.
"Electronic document rejected by the counterparty" — the recipient disagrees (most often due to a discrepancy in amount or VAT). Open the underlying document, correct it (check the rate of 16%), generate a corrected EDO document, and resend it with a comment.
"Sending error: no connection with the operator" — internet connection or operator service issue. Retry sending from "Current EDO Affairs" using the "Send and Receive" button.
9. FAQ
Does this document create accounting entries? No. The underlying document (sale, act) generates the entries. The outgoing EDO document is just an envelope with a file, signature, and status.
Does sending via EDO replace the issuance of ESF? No. ESF is issued separately through IS ESF, and SNT — through its module. Sending an invoice or act via EDO between counterparties does not replace them.
What VAT rate should be applied in 2026? 16%. The rate is taken from the underlying document. If the counterparty rejects due to the tax amount, check that both sides have 16%, not outdated 12%.
The counterparty says they did not receive the document. How to check? Open the card of the outgoing document, check the status, and print the "Exchange Protocol." If the status is "Delivered" or "Completed" — the document is with them, the question is on their side.
Can an already sent document be revoked? An already sent and signed document cannot be revoked — you can send a cancellation or corrected document if the counterparty accepts it.
What is used to sign the document? The electronic digital signature (EDS) of the organization from the NUC RK certificate specified in the signing settings. Without a valid certificate, sending is not possible.
What to do if an error in the amount is discovered after sending? Correct the underlying document, create a new outgoing EDO document (corrective) based on it, and send it to the counterparty with an explanation in the comment.
Does the exchange work if we have different EDO operators with the counterparty? Yes, through roaming. It must be pre-configured in "Exchange of electronic documents"; otherwise, the document will go to the "Sending error" status.
Where are sent documents stored?
In the "EDO Archive" and in the list e1cib/list/Document.OutgoingElectronicDocumentEDO. From there, the file, signatures, and all history are available.
Is it necessary to process this document manually? Usually no — it is created and moves automatically from the EDO workplace. You only intervene manually when resending or attaching an arbitrary file.
10. Related documents
Based on what it is created:
- "Sale of goods and services" → type "Invoice".
- "Sale of services" / "Act of completed works" → type "Act".
- "Invoice to the buyer" → type "Invoice".
- Contract, additional agreement, arbitrary file → type "Arbitrary document".
What is related in accounting:
- ESF (IS ESF) and SNT — separate electronic documents of the RK, issued for the same sales but according to their own rules.
- Incoming electronic documents (EDO) — a mirror object: what the counterparty sends to you.
How to find out your release: "Help" → "About the program" — there you will find the version of the platform and the configuration release.
The manual is prepared for "Accounting for Kazakhstan," version 3.0, release 3.0.74.2. The figures (VAT 16%, RK invoices) are valid for 2026.