---
title: "Document \"Data Exchange Scenarios\" in 1C: Accounting for Kazakhstan 3.0 - Setting Up Automatic Data Exchange"
country: KZ
lang: en
author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti)
date: 2026-09-07
canonical: https://buhgpt.kz/suraqtar/dokument-scenarii-obmenov-dannymi-v-1s-buhgalteriya-dlya--en
source: BuhGPT
---

# Document "Data Exchange Scenarios" in 1C: Accounting for Kazakhstan 3.0 - Setting Up Automatic Data Exchange

> **TL;DR:** Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0). You have two databases. In one, you maintain operational accounting or trade, and in the other — accounting. Every morning, you manually click "Synchronize," wait, then do it again for the second node, and 

---

Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0).

You have two databases. In one, you maintain operational accounting or trade, and in the other — accounting. Every morning, you manually click "Synchronize," wait, then do it again for the second node, and then for the third. Sometimes you forget — and the data diverges: there are no yesterday's sales in accounting, and you are already preparing the electronic invoice (ESF). The document "Data Exchange Scenarios" closes this routine. You compile all your exchanges into a list once, set a schedule — and at night, 1C runs them sequentially by itself. In the morning, the data is already in place.

First, it's important: this is a service (technical) document, not an accounting one. It does not make entries, does not create ESF and tax returns, and does not affect the balance. It manages when and which exchanges are initiated. Therefore, there will be no sections "debit/credit entries" and "print forms" in the usual sense — and this is correct, not an omission.

1. Purpose

"Data Exchange Scenarios" combine several exchange settings (nodes) into a single package and link a schedule to it. One document — one scenario, within which the exchanges performed together, automatically, according to the specified schedule through a scheduled task are listed.

2. Where to find

Path in the interface:

- Administration → Data Synchronization (Data Exchange) → Data Exchange Scenarios → button Create.

If the synchronization section in the interface is hidden, enable it: Administration → Data Synchronization Settings → checkbox "Data Synchronization". Until exchanges are configured, the item may not be displayed.

Open the list directly from 1C: Service → Go to navigation link and paste:

e1cib/list/Document.DataExchangeScenarios

2a. How to find out your release

Help → About the program (in the upper right menu — the "i" icon or "Function Menu → Help → About the program"). There are two lines: platform version (for example, 8.3.24) and configuration release — "Accounting for Kazakhstan, version 3.0 (3.0.74.2)". The instructions below are tied specifically to the configuration release: in another version, field names and menu paths may differ.

3. How to fill out

Before creating a scenario, you must have the exchanges (nodes) themselves configured — the scenario only combines the ready settings but does not create them. If there are no synchronizations, first go through Administration → Data Synchronization → Data Synchronization Settings → Create.

Document fields:

Field
Purpose and what happens in case of an error

Name (mandatory)
The name of the scenario by which you will find it in the list and in the scheduled task log. Write meaningfully: "Night exchange UT → Accounting". Empty or "Scenario 1" — you won't understand later what and where it sends.

Date, Number
Service fields. The number is assigned automatically; do not change the date without reason — it does not affect the operation of the exchange.

Active / Use (key)
Flag for activation. If unchecked — the scenario is "paused," the schedule does not work, but you can still manually start the exchange. If you forget to set it — nothing will be executed at night, and you will think you have configured it.

Table part with exchange settings (mandatory — at least one line)
A list of exchanges included in the scenario. In each line, you select Exchange Setting (node) and, as a rule, direction — "Send," "Receive," or "Send and Receive." The order of lines = order of execution. An empty table — the scenario will be formally conducted, but there will be nothing to do.

Flag "Execute" in the line
Allows temporarily disabling a specific exchange without deleting the line. If unchecked — the line is skipped.

Schedule (key)
Link/button that opens the standard schedule dialog for the scheduled task: frequency (daily), time (for example, 02:00), days of the week, repeat during the day. If you do not set a schedule — the scenario will only be for manual launch. If you set too frequent a repeat (every 5 minutes) — exchanges will start to "overlap" each other and load the server.

Number of attempts / repeat on error
How many times to try if the session fails (connection drop, database busy). The presence and exact name of this field is version-specific and requires verification in your release. Reasonable 2–3 attempts with an interval of several minutes.

After filling out, click Save, then Conduct. Conducting registers the scenario and activates the related scheduled task.

4. An example explained

Task. You have two databases: "Trade Management" (UT) and "Accounting for Kazakhstan" (BK). Two exchange nodes are configured. It is necessary that every night, first documents of sales go from UT to BK, and then payments and statuses of mutual settlements return from BK to UT.

Filling out the scenario:

- Name: "Night exchange UT ↔ BK"

- Flag Active — set.

- Table part:

No.
Exchange Setting (node)
Direction
Execute

1
Exchange with "UT" (sales, nomenclature)
Receive
✔

2
Exchange with "UT" (payments, mutual settlements)
Send
✔

- Schedule: daily, 02:00, repeat — none.

Click Conduct.

What will happen instead of entries. This document does not generate debit/credit entries — the amounts do not change. Instead of entries, service movements and events appear:

- at 02:00, the scheduled task of the scenario is launched;

- 1C executes line 1 — receives 47 invoices from UT for the day;

- then line 2 — exports 31 payment to UT;

- the result of each session is written in the registration log and in the synchronization monitoring: "Exchange completed, errors 0".

In the morning, you open Administration → Data Synchronization → Results and Warnings and see a green status. Sales are already in the database — you can generate ESF for them. The ESF and entries are created by the documents "Sales of Goods and Services," not the scenario: it just delivered the data on time.

5. Types of operations

The document does not have the usual "Type of operation" field like an invoice. Its "types" are options for operation:

- Manual launch — opened the scenario and clicked "Execute"/"Synchronize". Run here and now.

- By schedule (automatic) — the scheduled task launches the scenario by itself.

- Only sending — the lines selected the direction "Send".

- Only receiving — the direction "Receive".

- Bidirectional — "Send and Receive" or two lines for one node in the required order.

- Disabled (pause) — the flag "Active" is unchecked: the schedule does not work, but the settings are saved.

6. What is generated upon conducting

Once again, honestly: this document does not create entries, ESF, and tax returns. Upon conducting, the following occurs:

- The scheduled task of the exchange by the scenario is activated (a record with your schedule appears/enables in the list of tasks).

- A record in service information registers of the data exchange subsystem is made (composition of the scenario, schedule, status).

- With each actual run, exchange sessions are created: message packets are unloaded/loaded between nodes.

- The result of each session is written in the registration log and in the synchronization monitoring (success/error, number of objects, conflicts).

Electronic documents (ESF in the ESF IS, tax returns) and accounting entries are generated by the primary documents that the exchange transferred to the database — not the scenario.

7. Print forms

The document does not have its own print forms — it is a service object, it is not printed or issued to the counterparty. What you need "on paper" or for control is not here:

- Report on synchronization results (exchange monitoring) — statuses, errors, conflicts.

- Registration log filtered by the scheduled task of the scenario — detailed protocol.

8. Common errors

"The scheduled task is not executed because the schedule is missing." You enabled the scenario but did not set a schedule. Open the schedule, set the frequency and time, and re-conduct the document.

"Exchange not completed: exchange setting (node) not found." The node specified in the line has been deleted or renamed. Open the table part, select the active setting again; delete the unnecessary line.

"Data synchronization is not enabled." The mechanism itself is turned off in administration. Go to Administration → Data Synchronization Settings and check the "Data Synchronization" checkbox.

"Failed to connect to <receiving-database>." Connection drop, incorrect address or password in the node settings, database under maintenance. Check the connection parameters in the exchange setting itself and try again. The scenario is not to blame — it just launches the ready node.

Scheduled tasks on the file database do not run at night. In the file version, tasks work only while the 1C session is open. If the computer is turned off — the exchange does not start. Either keep the session open or move the database to a server (client-server version).

Exchanges "overlap" each other. Too frequent repeats in the schedule — a new run starts while the previous one has not finished. Increase the interval or remove the repeat during the day.

9. FAQ

Does this document make entries in accounts (1210, 1030, 3310, etc.)?
No. This is a service document for managing exchanges. Entries are generated by primary documents (sales, payments) that the exchange transfers between databases.

Does the scenario create ESF or tax returns?
No. ESF is issued in the ESF IS based on the sales document, tax returns — separately. The scenario only delivers data on time so you can issue them.

How does the scenario differ from a regular synchronization setting?
The setting (node) describes one exchange with one database. The scenario combines several settings and assigns them a common schedule and order of execution.

Can exchanges with different databases be included in one scenario?
Yes. Add one line for each node. They will be executed sequentially from top to bottom — consider the order if one exchange depends on the result of another.

The exchange starts automatically, but data does not arrive. Where to look?
Open Administration → Data Synchronization → Results and Warnings and the registration log filtered by the scenario task: there you can see errors, conflicts, and the number of processed objects.

How to temporarily stop the exchange without deleting the setting?
Uncheck the "Active" flag on the document (pause the entire scenario) or the "Execute" flag in a specific line (pause one exchange). Manual launch remains available.

Why does the exchange not run at night on the file database?
Scheduled tasks in the file version work only with an open 1C session. A turned-off computer = no exchange. The solution is a client-server database or a constantly open session.

How many scenarios can be created?
As many as needed. The practice is to separate by time and purpose: "night full," "daytime for payments every 30 minutes," etc. This makes it easier to diagnose and not overload the server.

What happens if the database is busy with another user during the exchange?
The exchange will either wait for the release or finish with an error and repeat according to the number of attempts. Heavy full exchanges should be planned at night when there are no users.

Does the configuration release affect this document?
Yes. Field names, menu paths, and the presence of the "Number of attempts" field may differ by versions. Check against your release (see the section "How to find out your release").

10. Related documents

- Data Synchronization Settings (exchange nodes) — the basis: the scenario refers to them, without them it cannot be filled out. Created in Administration → Data Synchronization → Data Synchronization Settings.

- Scheduled tasks — the scenario, when conducted, includes the related task; you can manage the schedule and view the history of launches from there as well.

- Primary exchange documents (sales, receipts, payments, nomenclature) — what is actually transferred between databases. They generate entries in RK accounts (1210, 1030, 1330, 3310, 3130, 6010, 7010), ESF, and tax returns — already in the receiving database, after the scenario has delivered the data.

How to find out your release: "Help" → "About the program" — there you will find the platform version and configuration release.

The manual is prepared for "Accounting for Kazakhstan," version 3

---
_BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_