Verified on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4).
An honest warning from the very first line. This is not an accounting document.
DataUploadDownloadDownloadHandlerManageris a service processing of the technical subsystem "Data Export and Import" (this is part of the Standard Subsystems Library, SSL). It does not create postings, does not create e-invoices/e-waybills, and does not print forms. That's why below you won't find an example with Dr/Cr for 16% VAT or an individual income tax calculation — they physically don't exist here, and inventing them would be dishonest. But you will definitely understand what this object is, when it comes up, and what to do with it.
1. Purpose
Imagine: you keep records in a file-based database on your laptop, while the company's accounting is moving to the cloud (1C:Fresh) or to a server. The data needs to be transferred entirely — reference books, documents, balances, settings. You click "Export data to file," get a single archive, and in the new database — "Import data from file." That's the moment when our object works behind the scenes.
DownloadHandlerManager is a dispatcher of handlers that trigger during the import process of the exported file: it determines how each metadata object should be handled, matches references, replaces or skips service data, and cancels unnecessary movements. The user almost never opens it directly — it is controlled by the main processing "Data Export and Import."
2. Where to find it
The object itself is a service one; it is not found in interface sections. You can open it directly in two ways:
Main menu (☰) → "All functions" → "Processing" → "Data upload download data download handler manager." If there is no "All functions" item — enable it: "Service and settings" (☰) → "Settings" → "Parameters" → checkbox "Display command 'All functions'."
Via navigation link. Menu (☰) → "Service and settings" → "Go to link" and insert:
e1cib/list/Processing.DataUploadDownloadDataDownloadHandlerManager
But here's what you actually need in practice — the user entry point into the entire subsystem:
- "Reference data and administration" → "Administration" → "Maintenance" → "Data export and import" (in different builds — "Export data to file" / "Import data from file").
This is exactly the processing you open when transferring a database. The handler manager will be pulled in automatically.
2a. How to find out your release
Menu (☰) → "Help" → "About the program". In the window that opens:
- platform version (for example, 1C:Enterprise 8.3.24.x);
- configuration release — "Trade Management for Kazakhstan, edition 3.4 (3.4.5.21)".
Check the instructions against this exact number: menu paths and the set of handlers change from release to release.
3. How it works (there are no fields to fill in manually)
With a regular document, you fill in the attributes. Here there is nothing to fill in — this is code, not an input form. But the export/import process has parameters that determine the result. Let's go through them "as if they were fields."
| Parameter (in the export/import wizard) | What it's for | What happens if you get it wrong |
|---|---|---|
| Export file path (required) | Where to save the archive (.zip with XML inside) or where to read it from |
Wrong path — export won't start; on import you'll take an old archive and overwrite fresh data |
| Target import database (required) | Which database you're pouring data into | Importing into a "live" working database over existing data — loss of information. Always import into an empty/test copy |
| Configuration match (critical) | The name and version of the target configuration must match the source | "Export file was created in another configuration" — import won't proceed |
| User/settings transfer mode | Whether to pull the user list, their settings, regional parameters | Forget it — the new database will be empty on permissions; transfer too much — login conflicts |
| Disabling background jobs during import (recommended) | So that scheduled jobs don't interfere | Leave them enabled — locks and "hanging" sessions |
The logic of the handler manager itself (you don't intervene in it, but it's useful to know):
- During import, it reads the export description and for each metadata object looks for a registered handler.
- Handlers run at stages: before reference matching, during object import, after import, after importing all data.
- It matches old references (GUIDs) with those existing in the target database so that links between objects don't "break."
- It cancels service and recalculable movements (register totals will be recalculated anew).
4. Worked example: migrating a database from file-based to server-based
There are no postings here — so the "magnet" example will be about what the object actually exists for: transferring data without losses.
Situation. LLP "Astana-Trade" works in a file-based TM for Kazakhstan 3.4.5.21 database. Accumulated: 1,250 counterparties, 340 items, 8,700 documents, warehouse stock balances, mutual settlements. Need to move to a 1C server without losing history and without manually re-entering data.
Step 1. Export (in the old database).
"Administration" → "Maintenance" → "Export data to file" → path D:\Exchange\astana_2026-09-23.zip → "Export." You get an archive of ~180 MB.
Step 2. Preparing the target. On the server you create an empty database from the same template "Trade Management for Kazakhstan 3.4.5.21" (the version must match down to the release).
Step 3. Import.
In the new database: "Import data from file" → select astana_2026-09-23.zip → "Import." This is where DownloadHandlerManager kicks in: it sequentially reads objects, matches references, restores links "document → counterparty → contract → item."
Step 4. Verification. After import, open the warehouse stock statement and "Settlements with customers." Balances and mutual settlements match the source database — the transfer was completed correctly.
What "came out in numbers": 100% of objects transferred (1,250 + 340 + 8,700 = 10,290 items), duration ~7 minutes, register totals recalculated automatically. No tax amounts (16% VAT, individual income tax, mandatory pension contributions) are recalculated in the process — they are transferred as is from the documents. The mechanism is technical: it copies data, it doesn't calculate taxes.
5. Operation types
The processing serves three subsystem scenarios:
- Full export — the entire database into one file (transfer, archive "snapshot," moving to the cloud).
- Full import — loading the file into an empty compatible database. This is where the handler manager works.
- Technological processing during update/migration — invoking import handlers when transferring data between releases and during 1C:Fresh service operation (subscriber data area transfer).
There isn't a separate "operation type" like a sales document has — the mode is set by the action (export/import).
6. What is generated upon posting
There is no posting in the accounting sense. Honestly, point by point:
- Dr/Cr postings — not generated. The object does not create business transactions. All postings are already "baked into" the documents being transferred and are simply copied.
- E-invoices / e-waybills — not generated and not sent anywhere. Exchange with the e-invoice information system has nothing to do with this. If electronic documents were exported from the source, they will be transferred as data, but will not be re-submitted to government systems.
- Register movements — during import, accumulation and information register records from the file are restored, after which totals are recalculated (balances, mutual settlements). This is the main result.
- Event log — the start/completion events of export and import, as well as handler errors, are recorded. This is your main log for monitoring.
7. Printed forms
There are none. The service processing prints nothing. The only "reportable" artifact is the export file (.zip) and the entries in the event log about the progress of the process. Don't look for a "Print" button — it isn't provided here, and that's normal for a technical object.
8. Common errors (real 1C messages)
| Message | Cause | How to fix |
|---|---|---|
| "Data import into this information base is impossible" | The target database is not empty or already contains data | Import only into a clean database from the same template; for transferring over existing data use a different mechanism |
| "Export file was created in another configuration (version)" | The name/version of the source and target configuration do not match | Update the target to the source release (3.4.5.21) or vice versa, then repeat |
| "Insufficient rights to perform the operation" | The user does not have administrative rights | Run under a user with the "Administrator" role / full rights |
| "Error importing object … in the data import handler" | Failure of a specific handler (broken references, incompatible data) | Open the event log, find the object, retry with a clean target; on retry — update the release |
| "File is not a data export file" / archive corrupted | The wrong file was selected or the archive was "not fully downloaded" | Check that this is a .zip from "Data export"; re-upload the file in full |
| Not enough space / "Insufficient memory" | Large database, little disk or RAM space | Free up disk space (2-3 times the archive size), do it on the server, not on a weak PC |
9. FAQ
1. Is this a document that I need to fill in every month? No. This is a service technical mechanism. It is opened once when transferring or archiving a database. It is not needed in day-to-day accounting.
2. Why does the object have no postings and no printed forms? Because it doesn't "post" anything or generate any documents. It copies data from the database to a file and back. Postings live in the documents themselves and are simply transferred along with them.
3. Will 16% VAT or individual income tax be recalculated during import? No. Tax amounts are not recalculated — they are transferred from the documents as is. Only register totals (balances, mutual settlements) are recalculated.
4. Can this processing be used to transfer data from "Accounting" to "Trade Management"? No. A full match of configuration and release between source and target is required. To transfer between different configurations, use "Data synchronization" / exchange rules, not this processing.
5. Where is the export file saved and how big is it?
Wherever you specify (usually .zip). The size depends on the database volume: from a few to hundreds of megabytes. Keep free disk space 2-3 times larger than the expected archive.
6. Will import overwrite my current data? Full import is intended for an empty database. Into a non-empty one, it most often won't be allowed ("Import … is impossible"). Never import an archive over a working database "just in case."
7. Is this the same as "Data synchronization" or DIB (distributed infobase)? No. Synchronization is a regular two-way exchange between running databases. This processing is a one-time transfer/archive of the entire database into a single file.
8. Are special rights required? Yes, administrative (full rights). The processing is not, and should not be, available to a regular manager or cashier.
9. How long does the process take? From a minute (small database) to tens of minutes (hundreds of thousands of documents). Disable background jobs during import and don't let other users in.
10. What to do if the import fails halfway through? Don't try to "finish loading." Recreate an empty database and repeat the import from the beginning, first checking that the releases match and that the archive is intact according to the event log.
10. Related objects
- What it is triggered by: a file created by the "Export data to file" processing (the same "Data export and import" subsystem).
- What works alongside it: the main processing "DataExportImport" (manages the process), the "Data synchronization" mechanism (for regular exchange — an alternative), the 1C:Fresh service (subscriber area transfer), standard infobase backup (
.dt). - What it is NOT: it is not a "Sale," not an "e-invoice," not a "Receipt" — the object is not directly related to Kazakhstan's accounting and electronic documents (e-invoices, e-waybills).
How to find out your release
Menu (☰) → "Help" → "About the program" — it shows the platform version and configuration release. This guide was compiled and verified for "Trade Management for Kazakhstan," edition 3.4, release 3.4.5.21. In other releases, menu item names and the set of import handlers may differ.
Note: this guide is current for release 3.4.5.21 of the "Trade Management for Kazakhstan" configuration (ed. 3.4).