--- title: "Processing \"Upload Download EnterpriseData\" in 1C:Trade Management for Kazakhstan 3.4: complete guide" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-23 canonical: https://buhgpt.kz/suraqtar/obrabotka-vygruzka-zagruzka-enterprisedata-v-1s-upravleni-en source: BuhGPT --- # Processing "Upload Download EnterpriseData" in 1C:Trade Management for Kazakhstan 3.4: complete guide > **TL;DR:** Tested on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4). The head office sent you a file Export.xml — they say "it has all the sales and receipts for the month, just load it into your database." Or the other way around: accounting is kept in a separate datab --- Tested on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4). The head office sent you a file Export.xml — they say "it has all the sales and receipts for the month, just load it into your database." Or the other way around: accounting is kept in a separate database "Accounting for Kazakhstan", while you make sales in "Trade Management", and once a month the data needs to be transferred — but no one wants to set up full synchronization for a one-time transfer. This is where you open "EnterpriseData Export Import". This is a manual tool: one button to export selected documents and reference books into a single XML file, another to load such a file into your database. No schedules, no exchange nodes, no rule configuration. Let's break it down step by step: how to export, how to import, what happens to documents and postings in the process, and where people most often stumble. 1. Purpose The processing performs a one-time (manual) export and import of data in the universal EnterpriseData format — an XML file that all modern 1C configurations "understand". Useful for transferring documents and reference books between databases, one-time migration, transferring data to a contractor or another configuration without setting up permanent synchronization. 2. Where to find it This is a service processing, it is not in the regular interface sections. It can be opened in two ways: - Main menu → "All functions" → "Processing" → "EnterpriseData Export Import". If the "All functions" item is not visible: "Service and settings" (gear icon) → "Settings" → "Parameters" → enable the checkbox "Display the 'All functions' command". - Via a navigation link. Copy the line below, then in 1C: "Service" → "Go to navigation link" (or Main menu → "File"), paste it and click "Go": e1cib/list/Обработка.ВыгрузкаЗагрузкаEnterpriseData Rights to open it are available to a user with full rights or the exchange administrator role. An ordinary sales manager will not see it. 2a. How to find out your release "Help" → "About the program" (or the "i" icon in the menu). In the window that opens, the top line is the platform version (e.g. 8.3.24), below it is the configuration release ("Trade Management for Kazakhstan, edition 3.4", version 3.4.5.21). This guide is based on 3.4.5.21; in neighboring releases the set of form fields is the same. 3. How to fill it in When opened, the processing asks what you want to do: export data or import. The fields differ after that. "Data export" mode Field What it's for and what happens on error Export file (required) The path and name of the XML file you are creating. If the directory is not writable, the export will not start. Specify a local folder, not a restricted network one. Format version (required) The EnterpriseData version. Choose one supported both by your database and by the receiving database. The receiver won't be able to read a too "new" version; take the highest common one. Data composition (required) A tree of data types: documents (Sales, Receipt, Payments), reference books (Items, Counterparties, Organizations). Check what to export. If you forget to check, say, "Counterparties" — sales won't load on the receiving side, because there's no one to attribute them to. Period filter Restricts documents by dates. If you don't set a period, all documents of the checked types will be exported, and the file will swell to hundreds of megabytes. Organization filter Leaves only documents of the required organization. In a multi-company database, without this filter someone else's data will be sent out. Check what's needed and click "Export data". When finished, a message will appear with the number of exported objects and the file path. "Data import" mode Field What it's for and what happens on error Import file (required) The very XML you were sent or that you exported. The processing will not accept a file of a different format (not EnterpriseData). Check before import The processing verifies references: whether it can find the counterparties, items, organizations from the file in your database. Unresolved references are the main risk: a document will load "empty" or fail to post. Import data Starts the import. Objects are created or updated by internal identifiers (GUID): if an object with the same ID already exists, it will be overwritten with data from the file. Important before importing: back up the database. The import overwrites objects by identifier, and it cannot be rolled back through standard means. 4. Worked example with postings Situation. A branch exported and sent you a file with one sale. You import it into your database, post it, and get the entries. The document in the file: "Sale of goods and services" dated 09/23/2026, buyer LLP "Astana-Snab", goods — 100 units at 11,600 ₸. - Amount with VAT: 100 × 11,600 = 1,160,000 ₸ - VAT 16% (included): 1,160,000 ÷ 116 × 16 = 160,000 ₸ - Amount excluding VAT (revenue): 1,000,000 ₸ - Cost of these goods in your warehouse: 700,000 ₸ The processing itself does not create postings — it only creates the document in the database. Postings appear when you post this imported document (or it posts automatically on import, if the posting flag was set). Entries per the Kazakhstan chart of accounts: Dr Cr Amount, ₸ Description 1210 6010 1,000,000 Revenue from sale (excluding VAT) 1210 3130 160,000 VAT payable 16% 7010 1330 700,000 Cost of goods written off Total buyer's receivable (1210) — 1,160,000 ₸, revenue (6010) — 1,000,000 ₸, VAT liability (3130) — 160,000 ₸. Gross profit on the transaction: 1,000,000 − 700,000 = 300,000 ₸. Practical takeaway: EnterpriseData transfers the document data, not the postings. After import, check that the document is posted and the amounts match the source. If the branch had VAT 16% and your contract mistakenly has 0%, the amounts will diverge, and this needs to be caught right away. 5. Operation types The processing provides exactly two modes: - Data export — creating an XML file from selected objects of your database. - Data import — receiving an XML file into your database. Within each mode there are options by depth: - Full export of checked types (no filter); - Filtered export (period, organization); - Import with creation of new objects; - Import with update of existing ones (match by internal identifier). 6. What is generated On export — a single XML file in EnterpriseData format with the selected objects and their attributes. Postings do not end up in the file: the source document data is transferred, and the recipient recalculates the entries themselves. On import in your database: - reference books are created or updated (Counterparties, Items, Organizations, Contracts) — first them, then the documents that reference them; - documents are created (Sales, Receipts, Payments, etc.); - register entries (mutual settlements, cost, VAT, item balances) and postings appear when the imported documents are posted — following the usual logic of those documents. Electronic documents (ESF, SNT) are not issued by the processing. EnterpriseData transfers accounting data, not electronic invoices. After importing a sale, issue the ESF in the ESF IS and, if the goods require accompanying documents, the SNT — from the sales document itself in your database, as usual. 7. Printed forms The processing has no printed forms in the usual sense — its result is an XML file and an import log on screen (how many objects were imported, which references were not resolved, which documents were not posted). Printed forms (invoice, tax invoice, act) are printed from the imported documents after they are posted. 8. Common errors "File is not an EnterpriseData format file" / "Failed to read data from the file". You were sent the wrong file (a regular XML export, dt, csv). Only import a file created by the "Data export" mode of this same or a compatible processing. "Object not found by reference" / unresolved references in the log. The file has a document, but not the reference book item it refers to (counterparty, item). Ask the source to export data together with the reference books, or preload the reference books with a separate file beforehand. "Format version <…> is not supported". The source exported in a newer format version than your release understands. Have them export in a lower version (common to both databases). "Document not posted: required fields not filled" / "VAT rate not specified". The data was loaded, but the document is missing a required field (VAT rate, warehouse, contract). Open the document, fill in the missing data (for Kazakhstan check the 16% VAT rate) and post it. "Data exchange is prohibited" / "Insufficient rights". The user does not have exchange administrator rights. Log in with full rights. 9. FAQ Do I need configured synchronization to use the processing? No. That's the whole point — it's a manual one-time mechanism without exchange nodes or schedules. Configured synchronization is needed for regular automatic exchange. Will postings appear immediately after import? Postings are made not by the processing, but by the document itself upon posting. Check that the imported sales/receipts are posted; post manually if needed and verify the amounts. Why isn't there an ESF or SNT after importing a sale? Because EnterpriseData transfers accounting data, not electronic documents. The ESF is issued in the ESF IS, and the SNT is issued separately from the document in your database. Does import create duplicate documents? No, if an object with the same internal identifier already exists, it will be updated, not duplicated. Duplicates only appear if the same document was previously created manually from scratch — then the identifiers differ. Can I export just one month and just one organization? Yes. Set the period and organization filter in export mode — only the selected data will go into the file. What should be exported first — reference books or documents? The processing itself orders the import: first the reference books, then the documents. But if you export manually in parts, include the reference books in the file too, otherwise the documents will "hang" on unresolved references. Can the import be rolled back if something goes wrong? There is no standard "undo import" button. So always back up the database (or a test copy) before importing, and load into that copy first. Will VAT match when transferring between Kazakhstan databases? The rate is carried over from the source document. If the original database had VAT 16%, that's what will be loaded. Problems arise when the receiving database's contract or item has a different default rate and the document is recalculated — check the amounts against the source. Is the processing suitable for transferring from "Trade Management" to "Accounting for Kazakhstan"? Yes, both configurations support EnterpriseData. Export documents together with the reference books and make sure the format version matches. 10. Related documents - What it works from: the source is documents and reference books already created in the database — Sale of goods and services, Receipt of goods and services, Write-off/Receipt of non-cash funds, Items, Counterparties, Organizations. - What appears after import: the same documents and reference books in the receiving database. Based on them, you then enter ESF, SNT, payment documents, adjustments — as for regular, manually entered objects. - Alternative: for ongoing exchange, instead of manual processing, "Data synchronization" is configured (Master data and administration → Data synchronization settings) — it uses the same EnterpriseData format, but on a schedule. How to find out your release: "Help" → "About the program" — it shows the platform version and configuration release. This guide was prepared for 1C:Trade Management for Kazakhstan, release 3.4.5.21 (edition 3.4). Rates and limits — per Kazakhstan regulations for 2026: VAT 16%, MCI 4,325 ₸, minimum wage 85,000 ₸. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_