--- title: "Directory \"Document Types of EDO\" in 1C:Trade Management for Kazakhstan 3.4 — how to fill in and use" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-24 canonical: https://buhgpt.kz/suraqtar/spravochnik-vidy-dokumentov-edo-v-1s-upravlenie-torgovley-en source: BuhGPT --- # Directory "Document Types of EDO" in 1C:Trade Management for Kazakhstan 3.4 — how to fill in and use > **TL;DR:** Tested on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4). A counterparty sent you a completed work certificate through an EDI operator. You open the incoming electronic document, and 1C doesn't understand what to do with it: it doesn't offer to create a "Rece --- Tested on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4). A counterparty sent you a completed work certificate through an EDI operator. You open the incoming electronic document, and 1C doesn't understand what to do with it: it doesn't offer to create a "Receipt of services" nor reflect it in accounting. The reason is almost always the same — in the "EDI Document Types" catalog, this document type is either not set up, or mapped to the wrong accounting document type. This is exactly where you come when electronic exchange has "stalled" and you need to explain to the program the difference between a bill of lading and an invoice, and between an e-invoice and a waybill. 1. Purpose "EDI Document Types" is a classifier catalog. It stores a list of electronic document types you exchange with counterparties and government agencies (e-invoice, waybill, bill of lading, certificate, payment invoice, custom document). Each element tells the program how to interpret an incoming or outgoing electronic document and which accounting document to link it to. 2. Where to find it The catalog is a service catalog, so it's not in the main menu section — it opens from the exchange settings. - Via menu: Master Data and Administration → Electronic Document Exchange → EDI Settings → document types section. The catalog is also accessible from the card of any incoming/outgoing electronic document via the type selection button. - Via navigation link (fastest): click "Service" → "Navigate by navigation link" in the menu (or Alt+F1) and paste: e1cib/list/Справочник.ВидыДокументовЭДО This will open the list of all EDI document types set up in the database. 2a. How to find out your release "Help" menu → "About the program". In the window that opens, you will see two lines: the platform version (e.g., 8.3.24.xxxx) and the configuration release — "Trade Management for Kazakhstan, edition 3.4 (3.4.5.21)". This guide is written for release 3.4.5.21. If you have a different one — the set of predefined types and some fields may differ. 3. How to fill it in Most of the required types are already supplied as predefined (e-invoice, waybill, certificate, bill of lading). You only need to create your own element if a counterparty sends a non-standard format. Use the "Create" button in the list. Field Required Purpose and what happens if wrong Name Yes This is how the type is named in selection lists. Get the name wrong — you'll simply confuse the type when manually mapping an incoming document. Code Assigned automatically Don't touch it. Manual changes can lead to duplication and "doubling" of identical types in filters. Direction (incoming / outgoing / any) Yes Determines where the type is offered: in incoming documents, outgoing ones, or everywhere. Set "outgoing" for a certificate that is sent to you — 1C won't substitute it on receipt, and the document will hang unrecognized. Document type / category Yes for non-standard ones This exact field links the EDI type to the accounting document type (sale, receipt, e-invoice, waybill). It determines which accounting document the program will offer to create via the "Reflect in accounting" button. An error here is the most frequent cause of incorrect postings. Use / Active No Uncheck the flag to hide an obsolete type from selection without deleting it (there is already exchange history for it). The rule is simple: don't multiply manual types if a predefined one fits. Creating your own element is only justified for a format that isn't included in the standard delivery. 4. Worked example with postings The catalog itself doesn't create postings — it's a classifier. But the selected type determines exactly which accounting document and which postings you get. Let's go through a complete example. Situation. You sell goods for 232,000 ₸ including VAT. You send the buyer an e-invoice through the E-Invoice IS. In the exchange settings, the outgoing electronic document is mapped to the "E-invoice" EDI type, and that type is mapped to the "Sale (certificate, bill of lading)" accounting document. Figures (VAT rate for Kazakhstan in 2026 — 16%): - Cost of goods: 100,000 ₸ - Sale price excluding VAT: 200,000 ₸ - VAT 16%: 200,000 × 16% = 32,000 ₸ - Total payable: 232,000 ₸ When posting the "Sale" document (created/linked via the "E-invoice" EDI type), the following postings are generated: Dr Cr Amount, ₸ Meaning 1210 6010 200,000 Revenue from sale 1210 3130 32,000 VAT payable 7010 1330 100,000 Cost of goods written off Upon receipt of funds: Dr Cr Amount, ₸ Meaning 1030 1210 232,000 Payment from buyer to current account Role of the catalog in the example: if the EDI type had been mapped, say, not to a sale but to a "Receipt," the program would have offered the wrong accounting document — and you would have gotten a VAT deduction (Dr 1420) instead of an accrual payable (Cr 3130). One wrong choice in the classifier reverses the entire VAT logic. 5. Operation types (what the catalog provides) A catalog element doesn't have "operation types" the way a document does. But through the "Type/category" and "Direction" fields, it covers the following exchange scenarios: - Outgoing: e-invoice (in the E-Invoice IS), waybill (goods accompanying waybill), outgoing sale/bill of lading, payment invoice, work completion certificate. - Incoming: incoming e-invoice from a supplier, incoming waybill, receipt of goods/services, certificate from a contractor. - Custom document — a format that isn't automatically broken down into accounting entries and is stored as an attachment. 6. What is generated when used The catalog element itself is not posted and does not create register movements — this is an inherent property of any catalog. The following is generated when the type is applied in an exchange: - Postings — created by the accounting document (sale, receipt) that the EDI type is configured to reference (see example in section 4). - Electronic documents — an e-invoice goes to the E-Invoice IS, a waybill goes to the waybill module; exchange statuses are recorded in the EDI subsystem's registers. - EDI register movements — when used, the type appears in the information register entries of the exchange subsystem (mapping of incoming documents, status history). The exact composition of service registers is version-specific and requires verification on your release. 7. Printed forms The classifier catalog has no printed forms of its own. What gets printed are the documents to which the type is linked: - E-invoice — printed form of the electronic invoice (from the E-Invoice IS). - Waybill — printed form of the goods accompanying waybill. - Bill of lading for release of stock to a third party (Z-2), Work completion certificate (R-1), Payment invoice — from the corresponding sale/receipt documents. 8. Common errors "Failed to determine EDI document type for incoming document." The counterparty sent a format for which there is no suitable element with the "incoming" direction. Create a type with the required type and direction, then manually map it in the incoming document card. "No accounting document type specified for the document type." The element's type/category field is empty. Open the type, specify which accounting document it corresponds to (sale, receipt, e-invoice, waybill), and repeat "Reflect in accounting." "Catalog element not found" when loading archived exchange. The type was marked for deletion or the "Use" flag was removed. Restore the flag — you must not delete a type that has exchange history. VAT in postings "goes to the wrong place." The EDI type is mapped to the wrong direction of the accounting document: an outgoing e-invoice ended up in a receipt. Check the "Type/category" field — for sales it's a sale (Cr 3130), for purchases it's a receipt (Dr 1420). Duplicate identical types in the selection list. Someone created a manual type instead of using the predefined one. Mark the manual duplicate for deletion, keep the predefined one. 9. FAQ 1. How does "EDI Document Types" differ from the accounting document types catalog? "EDI Document Types" describes what was received/sent via the exchange channel (electronic format). Accounting document types are already accounting objects. The EDI catalog links one to the other. 2. Do I need to create the "E-invoice" type manually? No. E-invoice, waybill, and the main types are supplied as predefined. Manual creation is only for a counterparty's non-standard format. 3. Can I delete an unnecessary type? If there was no exchange for it — yes, via marking for deletion and "Delete marked objects." If there is history — don't delete it, uncheck the "Use" flag instead. 4. Why wasn't the incoming document mapped automatically? There is no suitable type with the "incoming" direction, or the accounting document type isn't filled in. Create/fix the type and map it manually once — after that it will work automatically. 5. Does the document type affect the VAT rate? Not directly. The rate is taken from the accounting document and the item. In 2026, the base VAT rate in Kazakhstan is 16%. The EDI type only determines whether VAT is accrued payable (Cr 3130) or accepted for deduction (Dr 1420). 6. How can one type be linked to several accounting documents at once? It can't: one EDI type = one mapping. For different accounting documents, create different types. 7. Where can I see which type is assigned to a specific electronic document? In the card of the incoming/outgoing electronic document — the "Document type" field. From there you can also go to the catalog and adjust the setting. 8. Is the "Direction" field mandatory? Yes. Without it, the type won't be offered for either incoming or outgoing documents, and exchange won't work for it. 9. Is the catalog reflected directly in postings? No. The catalog doesn't create postings. Postings are generated by the accounting document that the type is configured for (example — section 4). 10. What to do if duplicate types appear? Keep the predefined type, mark the manual duplicate for deletion. Duplicates break automatic mapping. 10. Related documents - Used based on: incoming and outgoing electronic documents of the EDI subsystem, e-invoice (E-Invoice IS), waybill. - Configured alongside: "EDI Settings," "Exchange Settings Profiles," the counterparties catalog (each with its own exchange channel). - Created based on the type: "Sale (certificate, bill of lading)," "Receipt of goods and services," e-invoice, waybill — i.e., the accounting documents into which the electronic document is broken down. How to find out your release "Help" menu → "About the program". The line with the configuration release is the version this guide applies to. Prepared for "Trade Management for Kazakhstan," release 3.4.5.21 (edition 3.4). --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_