Verified on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4).
First, let's be honest and to the point. This is not an accounting document. There is no invoice here, no Dt/Ct postings, no ESF/CNT, and no printed forms. This is a service (technical) processing from the "Data Export and Import" subsystem. It is not needed by an accountant in daily work, but by someone who is transferring data from one database to another and has run into "broken" references. Therefore VAT rates, MCI, individual income tax, and the chart of accounts of the RK are irrelevant to this object — imposing them here would be dishonest. Below is an accurate guide specifically for this processing.
1. Purpose
A real-world situation. You exported data from an old "Trade Management for Kazakhstan" database and are loading it into a new one (or deploying a copy on another server). Some objects — counterparties, contracts, items, documents — reference each other by internal identifiers (GUID). During loading, some references "cannot be found": the object with that identifier does not yet exist in the new database, or it received a different GUID. This is where this processing comes into play.
Its task is to recreate and match references: link the old object identifier to its new representation in the destination database, so that documents don't end up with empty fields. Essentially, it's a dispatcher that maintains a mapping table "old reference → new reference" and substitutes the correct values into the loaded data.
2. Where to find it
The processing is a service one and is not shown as a separate menu item in the standard interface — it is called automatically by the export/import mechanism. You can open it directly in two ways.
- Through the main tool: Master data and administration → Maintenance → Data export and import (in different releases the path is: Administration → Maintenance). Then "Data export" / "Data import".
- Directly via a navigation link. Menu Tools → "Go to navigation link" (or Ctrl+click on the link), insert:
e1cib/list/Обработка.ВыгрузкаЗагрузкаДанныхМенеджерПересозданияСсылок
Important. Running the service processing directly only makes sense when debugging a data transfer. In the standard scenario, you work with the "Data export and import" form, and the reference recreation manager operates "under the hood".
2a. How to find out your release
Menu "Help" → "About the program" (or the "i" icon in the top right corner). In the window that opens, you will see:
- the platform version ("1C:Enterprise 8.3.x.xxxx");
- the configuration release — here it should say "Trade Management for Kazakhstan", edition 3.4, version 3.4.5.21.
Use this line exactly to verify that the instructions match your database: the location of the "Data export and import" subsystem changes from release to release.
3. How it works (key parameters)
Since this is a technical object, there are no "document fields" in the usual sense. There are transfer process parameters and a reference mapping table. Let's look at what actually affects the result.
| Parameter | Why it's needed and what happens if there's an error |
|---|---|
| Old reference (source identifier) — REQUIRED | The internal GUID of the object in the source database. The processing uses it to find "who was being looked for". If the identifier is lost, the object in the destination will remain unlinked — the field in the document will be empty. |
| New reference (destination object) — REQUIRED | Which object in the new database the old reference points to. Get the mapping wrong, and the document will pick up the "wrong" counterparty or the wrong item. |
| Object type (metadata) — REQUIRED | Catalog, document, characteristics type plan, etc. The type must match: a reference to "Counterparties" cannot be recreated as "Items". |
| Action with the reference | What to do if the destination object is not found: create a new one (recreate), leave it empty, or abort the load. The wrong choice either creates duplicates or breaks integrity. |
| Recreate missing (flag) | Whether to create "placeholders" in the destination for objects that weren't found. Enable it thoughtlessly, and you'll get empty catalog items without attributes. |
The procedure in the standard scenario:
- Open Data export and import → Data export, generate an export file from the source database.
- In the destination database, run Data import, specify the file.
- At the load stage, the mechanism automatically contacts the reference recreation manager. If ambiguous or missing references are found, it generates a mapping table.
- Check and, if necessary, manually match the problematic positions (old ↔ new).
- Complete the load. References will be substituted according to the table.
4. Worked example
Given. You are transferring the "Trade Management for Kazakhstan" database to a new server. The source contains:
- counterparty LLP "Astana-Snab" (GUID
a1b2…), - document "Sales of Goods and Services" No. UT-000123 dated 15.09.2026 for the amount of 1,160,000 ₸ (including VAT 16% = 160,000 ₸), which references this counterparty.
What happens during loading. In the destination, the counterparty "Astana-Snab" had already been created manually earlier and received a different GUID (c3d4…). The loading mechanism sees: document No. UT-000123 references a1b2…, and there is no such identifier in the destination.
The reference recreation manager generates a mapping row:
| Type | Old reference (source) | New reference (destination) | Action |
|---|---|---|---|
| Catalog "Counterparties" | a1b2… (Astana-Snab) |
c3d4… (Astana-Snab) |
Match |
You confirm the mapping. After loading, document No. UT-000123 correctly points to the existing counterparty c3d4…, no duplicate is created, the amount of 1,160,000 ₸ and all tabular sections are preserved as they were.
No postings are generated in the process: the processing does not touch accounting, it only fixes links between objects. The sales document itself, when you later re-post it in the destination, will operate normally (in Trade Management for RK — movements on sales registers, mutual settlements, and, with regulated accounting maintained, on accounts like 1210/6010/3130 with a 16% VAT rate). But this is done by the sales document, not this service processing.
5. Operation types (modes of operation)
- Matching — link the old reference to an already existing destination object.
- Recreation — create a new object in the destination for a reference that wasn't found.
- Ignoring / clearing — leave the reference unfilled if the object is not important.
- Deferred filling — first load all objects, then "fill in" references afterward, to work around circular dependencies (a document references an object that is loaded later).
6. What is generated upon execution
Honestly and without invention:
- Dt/Ct postings — none. The processing does not make account movements and is not involved in regulated accounting.
- ESF / CNT — none. Electronic invoices and goods accompanying waybills are generated by sales/purchase documents, not by this processing.
- Movements on accounting registers — none. It corrects internal object references, not accumulation/information registers.
- What actually happens: reference attributes of the loaded objects are updated, an identifier mapping table is maintained, and if recreation is enabled, missing destination objects are created. The progress of the process is written to the event log (messages about not-found and recreated references).
7. Printed forms
The processing has no printed forms — it is a service object. You monitor the transfer result via:
- the event log (Administration → Event log) — warnings about references are visible there;
- service messages in the loading window;
- the export/import log file, if it is generated by the mechanism.
8. Common errors
"Reference to object of type … not found. Loading aborted" The source identifier has not been matched or recreated. Open the mapping table and manually specify the destination object, or enable "recreate missing".
"Object types do not match when mapping references" You are trying to link a reference of one type to an object of another (for example, "Counterparties" ↔ "Items"). Correct the mapping: the old and new reference must be of the same metadata type.
"A duplicate catalog item was created" Recreation was enabled where the object already existed in the destination. Undo, match the reference with the existing object, and delete (mark for deletion) the duplicate placeholder.
"Referential integrity violation after loading" Some objects were loaded without "owners" due to circular dependencies. Use deferred reference filling or repeat the file load entirely.
"Source and destination configuration versions differ" Transferring between different releases of Trade Management for RK is risky. Bring the databases to the same release (3.4.5.21) and repeat.
9. FAQ
10. Related objects
- "Data export and import" processing (ВыгрузкаЗагрузкаДанных) — the main tool that calls this manager. The transfer starts with it.
- Database convolution/compression, data exchange (DIB, exchange plans) — alternative transfer mechanisms; they have their own matching rules.
- Loading data from external sources, "Universal XML exchange" — related migration tools.
No accounting documents are entered based on this processing, and it itself is not entered "based on" a document — it services the data transfer process.
How to find out your release
Menu "Help" → "About the program": it shows the platform version "1C:Enterprise 8.3" and the configuration release. For this guide, the reference point is "Trade Management for Kazakhstan", edition 3.4, version 3.4.5.21.
This guide was prepared for release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4).