Verified on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4).
The main point right away, honestly. This is a service (technical) processing, part of the library mechanism "Data Export and Import". It is not an accounting document. It has no Dr/Cr entries, no printed forms, it does not generate ESF and SNT and does not calculate VAT, IIT, or OPV. So below you won't find an example with tenge and tax rates — there's simply nowhere to get them from, and inventing them would be misleading. The task of this processing is different: to help correctly transfer data from one database to another without "breaking" the links between objects.
If you need instructions on calculating 16% VAT, IIT with a 30 MCI deduction, or on issuing an ESF — that's a different section of the program, not this processing.
1. Purpose
The processing serves the mechanism "Data Export and Import" (transferring information between information bases via a file). It is responsible for three technical things: the object dependency graph (what depends on what and in what order to load), dictionaries of metadata correspondence, and reference mapping — so that after loading, the same counterparty, product, or organization does not duplicate, but "merges" with existing ones.
Simply put: it ensures that during data transfer, references don't "dangle" and objects are placed in the correct order.
2. Where to find it
This processing is not shown in the menu to a regular user — it is called automatically by the platform within export/import procedures. It can only be opened directly via a navigation link (administrator rights and enabled debug/support mode are required).
- Via 1C navigation link: menu Tools → "Go to navigation link" (or the link icon in the top right corner), insert:
e1cib/list/Обработка.ВыгрузкаЗагрузкаДанныхГрафЗависимостейСловарейСопоставленияСсылок - Standard scenario where it is used: section Master Data and Administration → Maintenance → Data Export and Import (or Administration → Maintenance). From here, database export to file and import from file are launched — the processing works "under the hood".
If the link doesn't open or the menu item is missing — it means your account doesn't have administrator rights. This is normal: a regular accountant doesn't need to touch this object.
2a. How to find out your release
Main menu (≡ icon or "Tools") → Help → About the program. In the window that opens:
- Platform version — for example,
1C:Enterprise 8.3.24.xxxx; - Configuration —
Trade Management for Kazakhstan, edition3.4; - Configuration version —
3.4.5.21.
This instruction applies exactly to this release. If you have a different number, button names may differ slightly.
3. How to "fill in": the processing has no input fields
It's important to dispel a false expectation here. This processing does not have the usual form with attributes for the user to fill in (no "Organization", "Counterparty", "Amount", "VAT Rate"). It works with internal data structures generated by the transfer mechanism itself.
Your actual actions take place not in it, but in the "Data Export and Import" wizard:
| Step | What you do | What happens inside |
|---|---|---|
| 1 | Export data to file (you must specify the path to the .zip/.xml file) |
The dependency graph is built — the order of objects is determined |
| 2 | Selecting the data composition (entire database or individual sections) | The metadata correspondence dictionaries are filled in |
| 3 | In the receiving database — Import data from file (must be the same file) | Reference mapping works: objects are "merged" with existing ones or new ones are created |
| 4 | Completion | Reference integrity is checked |
The only "field" you are responsible for is the path to the export/import file. If you get the path wrong or supply a file from a different configuration, the import will fail with an error (see section 8).
4. Worked example (why there are no entries or tenge here)
Here is a real scenario, but without fictitious amounts and entries — technical processing never has any.
Situation. You are transferring a working TM for Kazakhstan database from one server to another (or giving a copy to a franchisee for development). The database has 400 counterparties, 1,200 item entries, sales and receipt documents.
- In the source database: Master Data and Administration → Data Export and Import → Export data to file → specify
C:\Exchange\ut_kz.zip. - The platform builds the dependency graph: for example, the "Sales" document references "Counterparty", "Agreement", and "Item", meaning these catalogs must be exported and imported before the document. This order is managed by our processing.
- In the receiving database: Import data from file → the same
ut_kz.zip. - Reference mapping kicks in: if the counterparty "Voskhod LLP" with the same internal identifier already exists — it won't be duplicated; if not — it will be created anew, preserving all links.
Result: the database is transferred completely, references are not "dangling", catalogs are not duplicated. No accounting entries are generated in the process — already prepared data is transferred "as is".
If you actually need an example with entries (for example, a sale of goods with 16% VAT: Dr 1210 Cr 6010 for the revenue amount, Dr 1210 Cr 3130 for VAT, Dr 7010 Cr 1330 for cost of goods sold) — that's done by the "Sales of Goods and Services" document, not this processing.
5. Operation types
The processing does not have "operation types" in the accounting sense. Logically, it participates in two modes of the mechanism:
- Export — collecting database data into a file with construction of the dependency graph and dictionaries.
- Import — reading the file with reference mapping and restoring links.
Both modes are launched from the "Data Export and Import" wizard, not from the processing itself directly.
6. What is generated during operation
- Entries (postings to accounting registers): none.
- ESF / SNT and other electronic documents: not generated.
- Movements in accumulation/information registers: the processing itself does not make movements — during import, movements already recorded by documents in the source database are transferred.
- What is actually "generated": the export file (
.zip/.xml) during export, and recorded/mapped objects in the receiving database during import.
7. Printed forms
There are no printed forms. This is a technical processing, there is nothing to print in it. The result of its work is correctly transferred data, not a paper document.
8. Common errors
"File is not a data export file" / "Invalid file format".
Reason: the wrong file is specified (for example, a regular exchange .xml or an archive from another configuration). Solution: import exactly the file obtained via a standard export from a compatible database.
"Import from file is not possible: configuration does not match".
Reason: the release of the receiving database differs from the source database (for example, the file is from 3.4.5.21, but you're importing into an older version). Solution: update the receiver to the same release 3.4.5.21 and try again.
"Insufficient rights to perform the operation on the data". Reason: launched under a user without administrator rights. Solution: perform export/import under a user with full rights.
"Reference integrity violation" / "Object not found by reference". Reason: the export file is incomplete (only part of the database was exported, without dependent objects). Solution: export the full data set or explicitly include dependent catalogs.
Import "hangs" on a large database. Reason: a very large volume, and building the dependency graph requires time and memory. Solution: do not interrupt the process, run in exclusive mode, if necessary — on a server with sufficient RAM.
9. FAQ
Q: Is this a document? Where are its entries? A: No, this is a service processing of the data transfer mechanism. It has no entries and cannot have any — it transfers already prepared data.
Q: How do I set 16% VAT or calculate IIT with it? A: You can't. VAT calculation, IIT (30 MCI deduction, 10%/15% rates), OPV, and other things are handled by accounting and payroll documents, not this processing.
Q: Why don't I see it in the menu? A: It is called automatically by the platform within the "Data Export and Import" wizard. It can only be opened directly via a navigation link with administrator rights.
Q: How is this different from regular data exchange (DIB, synchronization)? A: The "Data Export and Import" mechanism transfers the entire database via a file (transfer/backup export), while synchronization is a regular exchange of changes between running databases.
Q: Can this be used to transfer data from a different configuration (for example, from Accounting)? A: No. The mechanism only works between databases of the same configuration and compatible release. Use "Data Conversion" to transfer from another configuration.
Q: Will counterparties and products duplicate after import? A: No, reference mapping is exactly what prevents this: objects are "merged" by internal identifiers.
Q: Is the same release required in the source and receiver?
A: Yes. If the configuration doesn't match, the import will fail with an error. Bring both databases to 3.4.5.21.
Q: Can you export only catalogs without documents? A: Technically the composition can be limited, but then there's a risk of violating reference integrity. It's safer to export the full data set.
Q: Are special rights required? A: Yes, administrator rights. A regular accountant doesn't need this operation and doesn't have access to it.
Q: Does the processing affect closed periods and reporting? A: By itself — no. It only transfers data; the correctness of periods and reports is determined by the source database.
10. Related objects
- Used on the basis of: launched from the "Data Export and Import" wizard (Master Data and Administration → Maintenance).
- Related mechanisms: "Data Synchronization", "Data Conversion 3.0", "Backup".
- What it transfers: catalogs (Counterparties, Items, Organizations), documents (Sales, Receipts, ESF), registers — i.e., the contents of the database, not a separate document.
How to find out your release
Help → About the program — it shows the platform version 1C:Enterprise 8.3.x and the configuration release Trade Management for Kazakhstan, 3.4.5.21.
This guide was compiled for release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4). When updating the configuration, check the release number in "About the program".