--- title: "Reference \"DeleteExchangeExecutionSettings\" in 1C:Accounting for Kazakhstan 3.0: What it is and what to do with it" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-07 canonical: https://buhgpt.kz/suraqtar/spravochnik-udalitnastroykivypolneniyaobmena-v-1s-buhgalt-en source: BuhGPT --- # Reference "DeleteExchangeExecutionSettings" in 1C:Accounting for Kazakhstan 3.0: What it is and what to do with it > **TL;DR:** Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0). You updated the configuration, went to check the list of directories through "All Functions" — and stumbled upon the line "DeleteExchangeExecutionSettings". The name is alarming with the verb "Delete", and --- Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0). You updated the configuration, went to check the list of directories through "All Functions" — and stumbled upon the line "DeleteExchangeExecutionSettings". The name is alarming with the verb "Delete", and inside are some records with nodes and schedules. Or another situation: you have set up an exchange with UNF/retail/HR, something has stopped exporting, you are looking for "where the exchange settings live", and you open this directory based on a hint from an old instruction. Let's figure out what this object is, whether it can be touched, and where to actually configure the exchange today. The main point is: this is a service directory, not an accounting document. It does not create entries, has no printed forms, and does not generate electronic invoices (ESF) or social tax (SNT). The prefix "Delete" in the name is a developer's label: the object is left only for compatibility and data migration, in new releases its functions have moved to the "Data Synchronization" subsystem. It should not be filled in manually. 1. Purpose The directory stored parameters for executing data exchange between your database and other 1C databases (launch schedule, link to the exchange plan node, mode, and export rules). This is a technical "wrapper" of the old mechanism of distributed information bases and exchanges through exchange plans. Now these settings are maintained in the "Data Synchronization" section, and the directory with the prefix "Delete" remains as a container for migrating previously established settings. 2. Where to find Through the interface, it is usually hidden (the object is marked for deletion and is not displayed in the section commands). You can open its list in two ways: - Main menu → "All Functions" → "Directories" → "DeleteExchangeExecutionSettings". If the "All Functions" item is not available, enable it: "Service" → "Options" → check the box "Show the 'All Functions' command". - 1C navigation link. Copy the line and paste it into "File" → "Go to navigation link" (or Alt+F1): e1cib/list/Directory.DeleteExchangeExecutionSettings The current exchange settings are located here: "Administration" → "Data Synchronization" (or the "Data Exchange" / "Data Synchronization Settings" section — depending on which subsystems are enabled). 2a. How to know your release "Help" → "About the program" (in the web client — menu with the logo → "About the program"). In the opened window, you will see two lines: the version of the platform (for example, 8.3.2x) and the release of the configuration — "Accounting for Kazakhstan, version 3.0 (3.0.74.2)". It is the second line that determines which version this instruction refers to. If your release is older — the composition of the exchange subsystem may differ; if newer — the service directory may have been permanently removed. 3. How to fill Honestly: you do not need to create elements in this directory manually. It is filled automatically when setting up or migrating old exchanges. But to understand what you see in existing records, here are the key attributes. Attribute Purpose What happens if set incorrectly Name (mandatory) A clear name for the setting to distinguish one exchange from another Nothing will break, but you will get confused about which node it serves Exchange node / Exchange plan node (mandatory) Link to a specific exchange plan node — "with whom" the exchange is taking place The setting will link to the wrong node, data will go "the wrong way" or the exchange will not start Schedule Regulation for automatic export/import (interval, time) The exchange will either not start or will begin loading the server with frequent empty sessions Direction / mode of exchange Only export, only import, or bidirectional Changes will not reach the second database or, conversely, will be overwritten by incoming imports Execute automatically (checkbox) Enables operation according to schedule through a scheduled task Unchecked checkbox — the exchange will have to be started manually; checked without a schedule — it will not work Do not fill in this directory if you are setting up the exchange for the first time. Use the standard assistant: "Administration" → "Data Synchronization" → "Data Synchronization Settings" → "Configure Data Synchronization". The assistant will create the correct objects in the current subsystem. 4. Analyzed example Accountant Aigul keeps records in "Accounting for Kazakhstan" and simultaneously calculates salaries in "Payroll and HR Management". An exchange was once set up between the databases so that entries for salaries, OPP, OPPR, VOSMS, SO, and social tax would automatically come into accounting. After the update, Aigul notices: the amounts for August did not come through. She opens "All Functions" → directory "DeleteExchangeExecutionSettings" and sees the record: - Name: "Exchange with HR (salary)" - Node: "HR, LLP 'Astana-Service'" - Schedule: daily, 21:00 - Execute automatically: yes Everything looks correct, but the exchange is silent. The reason is typical for releases with this service directory: the setting has "hung" in the old object, and the current subsystem no longer sees it. What does Aigul do: - Goes to "Administration" → "Data Synchronization". - Checks if there is a setting with this node there. It is not there — meaning the migration did not go through. - Runs the assistant "Configure Data Synchronization", selects the HR database, and repeats the node binding. - Manually executes the exchange by clicking the "Synchronize" button. After that, the entries for August come into accounting: Debit Credit Amount, ₸ Description 7210 3350 850,000 Salary accrued for August 3350 3120 76,500 Withheld individual income tax (after deduction: 30 MRP = 129,750 ₸ and OPP) 3350 3220 85,000 Withheld OPP 10% 7210 3210 29,750 SO 5% 7210 3150 51,000 Social tax 6% It is important to understand: these entries are not generated by the exchange directory, but by the documents that came through the exchange (or the salary accrual in the accounting system itself). The directory "DeleteExchangeExecutionSettings" is just a "pipe" through which the data travels. The numbers are given to show why the exchange is needed at all: VAT here is 16%, MRP 4,325 ₸, deduction for individual income tax 30 MRP — this is the context of 2026, not the movements of the directory. 5. Types of operations The service directory does not have "types of operations" in the accounting sense (like a sales or purchase document). Functionally, its records differ by node type and direction: - Bidirectional exchange — export and import (typical for Accounting ↔ HR, Accounting ↔ UNF). - Only export — for example, sending data to a consolidating database. - Only import — receiving data from an external source. 6. What is formed when posting The directory is not posted — it is not a document. When using it, the following occurs: - No entries. Not a single one. Accounting movements are made by documents that come/go through the exchange, not by the setting itself. - No electronic documents. The ESF in the ESF IS and SNT does not issue this object — it is the task of sales/movement documents. - Movements in service registers of exchange: changes for the exchange plan node are registered (what to export), the fact and result of the exchange session are recorded, and a log of errors and warnings of synchronization is maintained. 7. Printed forms There are no printed forms for the directory. It is a service directory, "not printed on paper". The results of the exchange work are viewed not through printing, but through: "Data Synchronization" → "Synchronization Results", as well as in the registration log ("All Functions" → "Standard" → "Registration Log") with a selection by data exchange events. 8. Common errors - "Data synchronization with ... was not performed" — the exchange is set up in the old object but does not start according to schedule. Check the scheduled task: "Administration" → "Maintenance" → "Scheduled and background tasks". Better — recreate the setting through the current synchronization assistant. - "Exchange plan node not found" — the node has been deleted or the receiving database has been reinstalled with a new identifier. The setting needs to be created anew, linking it to the active node. - "Error executing handler ... Setting marked for deletion" — you are trying to work through an outdated directory. Do not edit it; go to "Data Synchronization". - "Data exchange: version format conflict" — databases on different releases. Update both databases to compatible versions, then repeat the exchange. - "Limit exceeded / subscription restriction on exchange" — check the current ITS subscription and exchange service limits; after removing the restriction, repeat the synchronization manually. 9. FAQ Can this directory or its records be deleted? The metadata object itself cannot be deleted — it is part of the configuration. Empty or already migrated records within it can be marked for deletion and removed with the standard processing "Delete marked objects", but only after ensuring that the current exchange is set up in the "Data Synchronization" subsystem. Why is "Delete" in the name? This is a convention of 1C developers: the prefix "Delete..." means that the object is outdated and will be excluded in one of the future releases. It is left for compatibility and migration of previously established data. Does this directory create debit/credit entries? No. It does not generate either accounting or tax movements. Entries are made by documents that circulate through the exchange. Does it issue ESF or SNT? No. ESF (ESF IS) and SNT generate sales, movement, import documents — not exchange settings. Where to correctly set up the exchange now? "Administration" → "Data Synchronization" → "Data Synchronization Settings". There is also the assistant "Configure Data Synchronization". The exchange worked, but after the update, it stopped — where to look? First in "Synchronization Results" and the registration log. Often, recreating the setting through the current assistant helps — an old record in the service directory during updates may "detach". How to open the directory if it is not in the menu? Through "All Functions" → "Directories", or via the navigation link e1cib/list/Directory.DeleteExchangeExecutionSettings in "Go to navigation link". Does this object affect tax calculations — VAT 16%, individual income tax, OPP? Directly — no. It only transfers data between databases. But if the exchange with HR is set up incorrectly, the amounts of individual income tax, OPP 10%, OPPR 3.5%, VOSMS 2%, OSMS 3%, SO 5%, and social tax 6% simply will not reach accounting, and reporting will have to be filled out manually. Is an ITS subscription required for exchange operation? For exchange between local databases according to exchange plans — no. For cloud synchronization and exchange services — yes, there is a subscription limit; when reached, the exchange stops until renewed. Can a schedule be set up for the exchange to run automatically? Yes, through a scheduled task for data synchronization. But set it up in the current subsystem, not in this service directory. 10. Related documents - What is it based on: records are created automatically when setting up the exchange (synchronization assistant) or when migrating settings from previous releases; it is not entered manually "based on" a document. - What is related to it: exchange plan nodes, data synchronization settings, scheduled exchange tasks, registration log. - What actually arrives through the exchange: documents "Salary Accrual", "Receipt of Goods and Services", "Sale of Goods and Services", payment documents — these are the ones that make entries (1210, 1030, 1330, 3310, 3130, 6010, 7010) and generate ESF/SNT. How to know your release: "Help" → "About the program" — there you will find the version of the platform and the release of the configuration. This material was prepared for "Accounting for Kazakhstan", version 3.0, release 3.0.74.2. When transitioning to a new release, check the composition of the "Data Synchronization" subsystem. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_