--- title: "Processing \"Data Exchange Execution\" in UT for Kazakhstan 3.4.5.21: How to Manually Run Synchronization" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-23 canonical: https://buhgpt.kz/suraqtar/obrabotka-vypolnenie-obmena-dannymi-v-ut-dlya-kazahstana--en source: BuhGPT --- # Processing "Data Exchange Execution" in UT for Kazakhstan 3.4.5.21: How to Manually Run Synchronization > **TL;DR:** Verified on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4). Morning. The head office accountant writes: "Yesterday's sales aren't in my Accounting, where's the money?" The nightly synchronization failed — the server was rebooted. There's no time to wait for t --- Verified on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4). Morning. The head office accountant writes: "Yesterday's sales aren't in my Accounting, where's the money?" The nightly synchronization failed — the server was rebooted. There's no time to wait for the next scheduled run, reporting deadlines are looming. You open the "Data Exchange Execution" processing tool, select the needed setting, and run the exchange manually. A minute later, the documents move to the receiver, and your colleague sees them. This processing tool is the "engine" of synchronization: it's the one that reads and writes the exchange message when you click "Synchronize." 1. Purpose "Data Exchange Execution" is a service processing tool of the synchronization subsystem. It performs one exchange session for a selected setting: it exports changes to a file (or web service), imports the incoming message, and records what has already been sent. It doesn't create postings itself — those are created by the documents that arrive through it. 2. Where to find it The usual user path: - Master Data and Administration → Data Synchronization Settings → Data Synchronization → select a setting → the "Synchronize" button. Direct call to the processing tool itself (for diagnostics and manual launch of a specific direction): - Menu "Tools and Settings" (gear icon) → Functions for Technical Specialist → Processing, or via a navigation link. 1C navigation link: e1cib/list/Обработка.ВыполнениеОбменаДанными Copy it and open it via "Tools and Settings" → "Go to Navigation Link" — the processing tool will open right away. The processing tool is not available in the section menus like a regular document: it's a technical object. If the link doesn't open, your role doesn't have "Administration" rights — contact whoever administers the database. 2a. How to find out your release "Tools and Settings" → Help → About the Program. The window shows: the platform version (for example, 8.3.24) and the configuration release — a line like "Trade Management for Kazakhstan, edition 3.4 (3.4.5.21)." This guide is written for release 3.4.5.21. On neighboring releases the forms are almost the same, but command names may differ slightly. 3. How to fill in (launch parameters) Here the "fields" are exchange session parameters, not document attributes. Parameter Purpose and what happens on error Synchronization setting (required) Who you're exchanging with: a specific exchange plan node (for example, "Accounting for Kazakhstan"). If you select the wrong setting, the data will go to the wrong place, and the receiver won't accept it. Exchange direction (required) "Send and Receive," "Send Only," "Receive Only." If you set "Receive Only" when you need to send, your colleague still won't see anything. Message directory/file Only for file-based exchange. The path where to place and from where to read the XML message. An incorrect path results in "file not found" or reading an old message. Full export / changes only By default, only changes are exported (fast). Enable full export only if the receiver has "lost" data and requests everything again — otherwise you'll overload the database. Run in background Background mode doesn't block your session. For a one-time manual synchronization, interactive mode is more convenient (you see progress and the log). Order of operations: open → select setting → select direction → "Synchronize" (or "Execute") → wait for completion → open the log. Don't close the window or shut down the database until the session finishes. 4. A worked example with postings Scenario: yesterday, Trade Management posted a "Sale of Goods and Services" document to buyer LLP "Askom" for 1,160,000 ₸ (item "VVG Cable," base 1,000,000 ₸, VAT 16% = 160,000 ₸, batch cost 700,000 ₸). Overnight, the exchange with Accounting failed. You run "Data Exchange Execution": setting "Accounting for Kazakhstan," direction "Send and Receive." The processing tool itself doesn't create postings — it transfers the document. After it's imported into the receiver, the sale is posted and generates: Dr Cr Amount, ₸ Description 1210 6010 1,000,000 Revenue from sale (excluding VAT) 1210 3130 160,000 VAT on sale, 16% 7010 1330 700,000 Cost of goods written off The buyer's receivables grew by 1,160,000 ₸ (account 1210), income by 1,000,000 ₸ (6010), and the VAT liability by 160,000 ₸ (3130). When "Askom" pays into the current account, a posting will arrive (or be generated): Dr 1030 Cr 1210 — 1,160,000 ₸. What the processing tool did: recorded the document in the exchange message, marked it as sent in the registration, accepted the counter message (if the receiver sent anything back), and printed a log line "Objects exported: … Imported: …". 5. Operation types The processing tool performs one of these modes per session: - Initial (full) export — on the first exchange run or after a failure, when everything needs to be transferred. - Change export — the normal mode: only what changed since the last exchange goes out. - Message import — receiving and recording data from an incoming XML/web service. - Two-way exchange — "Send and Receive" in one pass. - Re-export of an object — after manual registration for export (see FAQ). 6. What is generated during execution - Exchange message file (XML) — for the file-based variant, it's placed in the specified directory. - Changes in receiver data — created/updated catalogs and documents; posted documents generate their own postings and register movements (mutual settlements, cost, VAT). - Exchange plan registration — numbers of the sent/received message, so the same thing isn't imported twice. - Exchange log — a list of exported and imported objects, warnings and errors, collisions. Important: e-invoices (ESF) and consignment notes (SNT) do not go through this processing tool. Electronic invoices go to the ESF Information System, and consignment notes go to the operator, via separate mechanisms. This processing tool synchronizes data between your 1C databases (Trade Management ↔ Accounting, Trade Management ↔ Payroll and HR, distributed infobase), not with government agencies. 7. Printed forms The processing tool has no classic printed forms — it's a technical object. You read the result on screen: - Exchange execution log (warnings/errors) — can be saved to a file; - Synchronization results report — how many objects were sent and received; - List of rejected objects / collisions — if the receiver rejected something. 8. Common errors - "Data synchronization setting not found" — the setting was deleted or a nonexistent one was selected. Open "Data Synchronization Settings" and check that the node is present and active. - "Exchange message was created for a different node" — you're reading someone else's file or mixed up the receive/send directories. Check the paths and node name. - "Received message number is less than the previously received number" — you're trying to import an old message again. Get a fresh file, or, if this is a deliberate re-import, perform a full export from the source side. - "Collisions detected during data synchronization" — the same object was changed in both databases. Open "Synchronization Warnings," decide which version is authoritative, and accept the needed one. - "Timeout exceeded" / no connection to the web service — the receiver's address is unavailable. Check the publication address, login/password, and that the receiver database is running. - "Failed to lock the object" — the document is occupied by another user. Ask them to close it and repeat the exchange. 9. FAQ What's the difference between "Data Exchange Execution" and "Data Synchronization"? "Data Synchronization" is a workplace with a list of settings and history. "Data Exchange Execution" is the executive mechanism itself, which runs when you click "Synchronize." Essentially, it's the internals of the same operation. Can I run the exchange manually if a schedule is set up? Yes. A manual run doesn't break the automatic one — it just performs a session now. The next scheduled run will proceed as usual. Why was the document posted, but it's not in the receiver? Three reasons: the exchange hasn't run yet; the document didn't fall under the setting's filter (for example, by organization or export start date); the document was rejected due to a collision. Check the log and the filter setting. How do I re-export a single document that got "lost"? The synchronization setting has a command to register an object for export (composition of data to send). Mark the document and run the exchange — it will be sent again. Will e-invoices (ESF) and consignment notes (SNT) go through the exchange? No. E-invoices are sent to the ESF Information System, and consignment notes to the operator, separately. This processing tool only synchronizes 1C databases with each other. Is it safe to interrupt the exchange midway? The import is transactional: if interrupted, the incomplete part won't be applied, and the message will be read again on the next run. But it's better to wait for completion so you don't have to deal with partially accepted data. Where can I see exactly what was sent and received? In the log after the session and in the synchronization history: you can see the number of objects, warnings, and errors there. The exchange complains about different configuration versions — what should I do? Update both databases to compatible releases. Exchange between significantly diverged versions (for example, an old Accounting and Trade Management 3.4.5.21) may reject some objects. This is the only point worth double-checking for your specific pair of configurations and exchange rules version. Data with VAT is arriving at the old 12% rate — why? The rate is taken from the source document itself, not from the exchange. In 2026, Kazakhstan has a VAT rate of 16% — check that the document in the source was created with the current rate; then the receiver will also show 16%. How do I find out when the last successful exchange was? In the "Data Synchronization" workplace, each setting shows the date and result of the last session. 10. Related documents - What it relies on: the data synchronization setting (exchange plan node) and the composition of data to send — these are configured before the first run. - What it "brings in": documents and catalogs — "Sale of Goods and Services," "Receipt of Goods and Services," "Payment," "Write-off/Receipt to Account," "Counterparties," "Items," etc., depending on the setup of the database pair. - What to check afterward: the exchange log, "Synchronization Warnings," and in the receiver — postings and reports (turnover balance sheet for accounts 1210, 3310, 6010, 7010). How to find out your release: "Tools and Settings" → Help → About the Program — shows the platform and configuration release. This guide is current for "Trade Management for Kazakhstan," release 3.4.5.21 (edition 3.4). On other releases, check command names in the synchronization workplace. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_