Verified on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4).
You need to raise a clean database copy for testing the new 16% VAT rate, or transfer counterparty and item catalogs to another database, or hand a programmer a data "snapshot" without a full .dt file. You open "Data Export and Import", select what exactly to export, get a single file — and load it into another database. This work is handled by the family of service processing objects that includes DataExportImportDataExportHandlerManager. Let's go through the entire mechanism so you can use it confidently.
Important and honest. This is a service (technical) processing object from the Standard Subsystems Library (SSL). It is not an accounting document: it does not create postings, does not generate e-invoices/e-waybills, and has no printed forms. Its task is to service data transfer between information bases of the same configuration. Below is how to use it correctly without losing data.
1. Purpose
The processing object is part of the "Data Export and Import" mechanism and is responsible for calling registered handlers (procedures) that prepare objects during export to a file. In simple terms, it is the "engine" that, during export, decides which objects to export and how, and which to skip. You typically don't open it separately "by hand": you work with the common "Data Export and Import" form, and this manager operates under the hood.
2. Where to find it
- Via the interface: section "Master Data and Administration" → "Maintenance" → group "Data Export and Import" → command "Export data to file" or "Import data from file".
- Direct launch of the service processing object itself (for a technical specialist) — via the 1C navigation link through "Tools" → "Go to navigation link":
e1cib/list/DataProcessor.DataExportImportDataExportHandlerManager
Paste the string into the navigation link field and click "Go". The service processing form will open.
The mechanism can be used by a user with administrator rights. A regular sales manager will not see the commands.
2a. How to find out your release
Menu "Help" → "About" (or the ℹ️ icon in the top right corner). In the window that opens you will see:
- the platform version (e.g., 8.3.24.xxxx);
- the configuration release — "Trade Management for Kazakhstan", edition 3.4, version 3.4.5.21.
Everything described below relates specifically to this version. On other releases, the set of fields and handlers may differ.
3. How to fill it in
The handler manager itself has no user-facing fields — it works automatically. You set all the options in the common "Data Export and Import" form. Let's go through it step by step.
Step 1. Select the mode
- "Export data to file" — create a snapshot file from the current database (source).
- "Import data from file" — accept a file into another database (receiver).
Step 2. Fields on export
| Field | Why it's needed | What happens on error |
|---|---|---|
| Export file name (required) | Path and name of the resulting file (.zip format). |
If the folder is not writable — export will fail with an access error. |
| Export all data / Selectively | A full snapshot or only selected object types. | A full export of a large database may take a long time and weigh gigabytes. |
| Data composition (object types) | For a selective export, you mark catalogs, documents, registers. | Skip a related object — references in the receiver will "break", the object will load partially. |
| Filter by period / organization | Limit document export. | Too narrow a filter — some needed documents won't get into the file. |
Step 3. Fields on import
| Field | Why it's needed | What happens on error |
|---|---|---|
| Import file name (required) | Path to the previously exported file. | A "foreign" file is specified (from another configuration/edition) — import won't start. |
| Import into empty / working database | SSL recommends loading into a clean database of the same configuration and edition. | Loading into a non-empty database will overwrite objects by internal identifiers — the receiver's data may be lost. |
Mandatory compatibility rule: the configuration and edition of the source and receiver must match (both — "Trade Management for Kazakhstan" 3.4). Otherwise an incompatibility message will appear and the import will not run.
4. Worked example
Situation: before switching to 16% VAT from 2026, you want to test month-end closing on a copy of the data, but without accounting documents — only catalogs and balances.
What you do:
- Master Data and Administration → Data Export and Import → Export data to file.
- Mode: "Export selectively".
- Mark types:
Catalog.Counterparties,Catalog.Items,Catalog.Organizations,Catalog.Warehouses. - File name:
D:\Exchange\ut_kz_catalogs.zip. - Click "Export data". The handler manager iterates through the objects, applies preparation procedures, and writes the XML structure to the archive.
Export result:
| Object type | Exported, pcs. |
|---|---|
| Counterparties | 1,240 |
| Items | 8,517 |
| Organizations | 3 |
| Warehouses | 7 |
- In the clean receiver database: Import data from file → specify
ut_kz_catalogs.zip→ "Import data".
What you will NOT see (and that's correct):
- no postings Dr/Cr — the processing does not affect the accounting register (accounts 1210, 1330, 3310, 6010, etc. do not move);
- no e-invoices or e-waybills — electronic documents are not generated;
- no printed forms — only the technical data structure is transferred.
That is exactly why the mechanism is safe for testing: it copies data rather than performing business transactions.
5. Types of operations
The mechanism provides two operations:
- Export data to file — creating a portable archive (fully or selectively, with filters).
- Import data from file — accepting the archive into another database of the same configuration.
The service processing object "...DataExportHandlerManager" participates only in the first operation — it controls calling handlers at the export stage.
6. What is created during execution
| Operation | What is created | Postings / e-invoices / registers |
|---|---|---|
| Export | A single .zip archive file with an XML description of objects and their references |
No postings. No e-invoices/e-waybills. Accounting registers are not affected — read-only access only |
| Import | Objects in the receiver database (catalogs, documents, register records as data) | Records appear in the receiver, but this is not document posting, it's direct data writing |
Technically, on import objects are written by their GUIDs (internal identifiers), so matching objects in the receiver are overwritten. This is the key reason to load only into an empty database.
7. Printed forms
The processing object has no printed forms. This is a service data-transfer mechanism — it is not designed for printing documents. The result of its work is an export file, not a paper/PDF form.
8. Common errors
Error: "The configuration or edition of the source database does not match the receiver". Reason — you are loading a file from a different configuration or edition (e.g., from "Accounting for Kazakhstan" into "Trade Management for Kazakhstan"). Fix: transfer data only between identical configurations and editions; for heterogeneous databases use "Data Conversion" / EnterpriseData format.
Error: "Insufficient rights to perform the operation". Reason — a user without an administrator role. Fix: log in as administrator or add the role in the "Users" section.
Error: "Failed to open the file for writing / reading".
Reason — the folder is not accessible, the file is locked by another program, no rights to the folder. Fix: choose another folder (e.g., local C:\Exchange\), close the archiver, check permissions.
Problem: "Receiver data disappeared after import".
Reason — you loaded into a working (non-empty) database, objects were overwritten by identifiers. Fix: always load into a clean database; make a .dt backup before importing.
Problem: "Objects in the receiver with 'broken' references". Reason — during selective export you did not mark related types (e.g., you exported Items without Units of Measure). Fix: include all dependent catalogs in the export, or export all data.
9. FAQ
1. Does this processing create postings on accounts 1210, 1330, 6010? No. This is a service data-transfer mechanism. It does not create a single posting in the accounting register.
2. Are e-invoices or e-waybills generated during export? No. The mechanism does not create or send electronic invoices and waybills to the e-invoice system.
3. How is this different from exporting to a .dt file?
.dt is a full snapshot of the entire database (only for the same platform and configuration, loaded via "Configurator"). "Data Export and Import" can transfer selectively individual object types and works from user mode.
4. Can data be transferred to a configuration of a different edition? No, the edition and configuration must match. To transfer between different configurations, the EnterpriseData format and "Data Synchronization/Conversion" are used.
5. Is it safe to load a file into a working database? It is not safe. Objects are overwritten by internal identifiers — the receiver's data can be wiped out. Load only into an empty database and make a backup.
6. Where do I get the navigation link to open the processing directly?
e1cib/list/DataProcessor.DataExportImportDataExportHandlerManager — paste it into "Tools → Go to navigation link".
7. Who can run export and import? A user with administrator rights. Regular users do not have access to the commands in the "Data Export and Import" section.
8. Are the 16% VAT settings and Kazakhstan accounting parameters transferred along with the data? If you include the relevant catalogs and information registers with settings (VAT rates, accounting policy) in the export, they will get into the file. For a selective export, check that the needed registers are marked, otherwise the settings will have to be re-entered in the receiver.
9. Why does the export take a long time and the file is large? You selected "Export all data" on a large database. Limit the composition to the needed object types and set a filter by period/organization.
10. A version mismatch message appeared — what should I do? Update both databases to the same release (in our case — 3.4.5.21) and repeat the import. The mechanism requires identical metadata structure.
10. Related documents and mechanisms
- "Export data to file" / "Import data from file" — user commands that call the described handler manager.
- Service processing objects of the same family:
DataExportImportExportDataManager,...ImportDataManager,...Auxiliary— together they form the SSL "Data Export and Import" mechanism. - Data synchronization (EnterpriseData) — for regular exchange between different configurations (e.g., "Trade Management for Kazakhstan" ↔ "Accounting for Kazakhstan").
- Export/import of
.dtin Configurator — for a full one-to-one database transfer. - Backup — before any data import into an existing database.
How to find out your release
"Help" → "About": the window shows the 1C:Enterprise platform version and the configuration release "Trade Management for Kazakhstan". Compare the number (here — 3.4.5.21) with the version in this guide.
This guide was prepared for release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4). On other releases, the set of handlers and fields may differ.