Verified on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4).
You are deleting a duplicate counterparty. There are two "Astana Logistics LLP" entries in the database — one has receipts posted against it, the other has payments. You click "Delete," and the program says: "Object cannot be deleted, there are references to it." To delete it safely, all references from the old counterparty need to be redirected to the correct one. This is exactly the moment when the DataExportImportReferenceReplacementStream processing kicks in under the hood. You will most likely never open it manually — but understanding what it does is useful, since your database's integrity depends on it.
To be upfront: this is a service (technical) processing, not an accounting document. It doesn't post transactions, doesn't calculate 16% VAT, IIT, or OPV contributions, and doesn't issue ESF/SNT. It transfers data in a stream and, in the process, replaces old references with new ones. That's why there are no sections for "Dr/Cr entries" or "printed forms" in the usual sense here — making them up would be misleading. Below is a breakdown of what it actually does and where you encounter it.
1. Purpose
The processing serves the data transfer "stream" mechanism: when exporting/importing a set of objects, it replaces references to objects being substituted (e.g., ones being deleted) with references to the replacement objects. It is used by the platform mechanisms "Find and Delete Duplicates," "Replace References," and "Data Export and Import," and is not opened for manual entry.
2. Where to find it
There is no direct "human-facing" path to this service processing in the interface sections — it is invoked programmatically. You can open its form (if the release even provides one) only via a navigation link:
- Main menu → Tools → Show navigation link, paste and go to:
e1cib/list/Обработка.ВыгрузкаЗагрузкаДанныхПотокЗаменыСсылок - The mechanisms that use it are accessible as follows:
- Master Data and Administration → Maintenance → Data Correction → Find and Delete Duplicates
- Master Data and Administration → Maintenance → Data Correction → Replace References
- Administration → Data Export and Import (technical exports for transferring between databases)
If the form doesn't open via the navigation link, or opens blank — that's normal: the processing isn't designed for manual work.
2a. How to check your release
Main menu → Help → About (or "i" in the top right corner). The window that opens shows the "1C:Enterprise" platform version (e.g., 8.3.24.x) and the configuration release ("Trade Management for Kazakhstan," edition 3.4, version 3.4.5.21). Everything in this guide has been verified on 3.4.5.21; on other versions, the set of fields and mechanism behavior may differ.
3. How it works (and what you actually configure)
You don't need to open the processing itself. You work with the "wrappers" — "Replace References" and "Find and Delete Duplicates" — and the processing runs internally. The key parameters you set:
| What you set | Where | Why, and what happens if you get it wrong |
|---|---|---|
| Object to be replaced (REQUIRED) | "Replace References" → "What are we replacing" | The item whose references are being removed (the old duplicate). Get it wrong, and you'll redirect references to the wrong place, sending documents to the wrong counterparty/item. |
| Replacement object (REQUIRED) | "Replace References" → "What are we replacing it with" | The correct item that will remain. Must be of the same type. If the type doesn't match, the replacement won't run. |
| Deletion method | "Find and Delete Duplicates" | "Mark for deletion" (safe) or "Delete immediately." For a production database, always mark first. |
| Search scope / filter | "Find and Delete Duplicates" | Limits where duplicates are searched for. Too broad a filter risks merging unrelated objects. |
| Action on references | Replacement wizard | "Don't delete, only replace references" / "Replace and mark for deletion." Determines what happens to the source. |
For a technical export/import between databases (Administration → Data Export and Import), you specify:
- Export file (REQUIRED) — path to
.xml/.zip. No write access to the folder — the export will fail. - Data composition — which objects to export. It's important not to "cut off" related objects: if you export a document without its counterparty, then during import into another database, the reference replacement stream will be needed to "attach" the document to an already existing catalog entry.
Important: before any reference replacement and duplicate deletion, make a backup (Administration → Maintenance → Backup). The operation is irreversible.
4. Worked example
Task. The database has two "Astana Logistics LLP" counterparties:
- Astana Logistics (old) — has "Purchase of Goods and Services" No. 15 dated 03/03/2026 for 1,160,000 ₸ (incl. 16% VAT — 160,000 ₸) posted against it.
- Astana Logistics (main) — the correct card, receiving payments.
What you do.
- Master Data and Administration → Replace References.
- "What are we replacing" — Astana Logistics (old). "What are we replacing it with" — Astana Logistics (main).
- Click "Replace References." The program finds all places of use: the receipt document, the contract, the invoice, the register movements.
- The
…ReferenceReplacementStreamprocessing runs through these objects as a stream and changes the referenceold→mainin each.
Result. The receipt document now belongs to the correct counterparty. Its own postings are not recalculated or changed — the amount, accounts, and VAT remain the same, only the reference "owner" changes:
| Dr | Cr | Amount, ₸ | Meaning |
|---|---|---|---|
| 1330 "Inventory" | 3310 "AP to suppliers" | 1,000,000 | Receipt of goods (amount excl. VAT) |
| 1420 "VAT recoverable" | 3310 "AP to suppliers" | 160,000 | 16% VAT per supplier invoice |
These lines were generated by the receipt document — the processing does not create or touch them. It only ensured that the document, its postings, and the "Counterparty" sub-account all point to Astana Logistics (main). After the replacement, the old card can be marked for deletion — there are no more references to it.
Example conclusion: the processing doesn't "post 16% VAT entries" — it preserves existing movements while reassigning their reference. That's exactly why it's important not to mix up the object being replaced and the replacement object: redirect references to the wrong place, and the correct document for 1,160,000 ₸ will end up linked to the wrong counterparty.
5. Operation types
There's no separate "Operation type" field here, unlike a document. Functionally, the processing runs in three scenarios:
- Reference replacement — substituting references to the object being replaced, as part of the "Replace References" mechanism.
- Duplicate deletion — the same replacement stream as a stage of the "Find and Delete Duplicates" mechanism (first, references to the duplicate are transferred to the original, then the duplicate is deleted).
- Data import as a stream — during technical import of a set of objects, matching and substituting references to items that already exist in the receiving database.
6. What is generated during execution
Honestly, without making anything up:
- No postings. The processing isn't an accounting one; it doesn't create its own account movements (1210, 1030, 3130, 6010, 7010, etc.).
- No electronic documents. No ESF is issued in the ESF IS, and no SNT — those are functions of sales/transfer documents, not this service processing.
- What actually changes: reference values in objects and their movements (attributes, sub-accounts, register dimensions) wherever the object being replaced appeared. Existing amounts and accounts in these movements are preserved.
- Registration log: the fact of replacement/deletion is recorded in the log (Administration → Support and Maintenance → Registration Log) — you can later see who replaced what.
7. Printed forms
The processing has no printed forms — it's a service object and doesn't print forms (invoice, waybill, act). After the "Replace References"/"Find and Delete Duplicates" mechanism runs, only an on-screen results report is available: a list of processed objects and places where the reference was replaced, with the ability to follow a hyperlink to each one. It can be saved/printed using the form's tools (spreadsheet document buttons), but this is a service log, not a standardized printed form.
8. Common errors
- "Object cannot be deleted because it is referenced by other objects" — you're deleting a duplicate without replacing its references first. Run "Replace References" first (redirect to the original), then delete.
- "The object being replaced and the replacement object are of different types" — you're trying to replace, say, a counterparty with a contract. The type must match. Choose objects of the same type.
- "Failed to replace references in … (object is locked by another user/session)" — the document where the reference is being changed is open or being posted by someone. Close the document, ask users to log out, and perform the replacement in exclusive mode.
- "Insufficient rights to write the file" (during technical export) — no access to the folder. Specify a directory with write permissions, or run as a user with the required rights.
- Amounts/analytics "shifted" after replacement — you mixed up what's being replaced with what. Restore from the backup made before the operation, and repeat with the correct objects.
9. FAQ
Do I need to open this processing manually? No. It's an internal service object. You work with "Replace References" and "Find and Delete Duplicates," and the processing runs automatically.
Does it change amounts and VAT in documents? No. Amounts, accounts, and 16% VAT remain as they were. Only the reference changes (which counterparty/item the object points to).
Does it generate an ESF or SNT? No. Electronic documents are issued by sales/transfer documents, not by this processing.
Can reference replacement be rolled back? There's no built-in "undo." The only reliable rollback is restoring from a backup, which is why one is made before the operation.
What's the difference between "Replace References" and "Find and Delete Duplicates"? "Replace References" only transfers references. "Find and Delete Duplicates" finds identical items, transfers references to the original (using the same stream), and then deletes the duplicates.
Is it safe to merge counterparties that have postings and mutual settlements? Yes, the mechanism is designed exactly for this, but always with a backup and in exclusive mode, outside a closed period. Check mutual settlements after the operation.
Why is the form blank or won't open via the navigation link? The processing isn't meant to be opened manually. A blank form is expected behavior for a service object.
Does the replacement affect a closed/filed period? References will also be replaced in documents from a closed period. Amounts don't change, but it's better not to touch periods for which reporting has already been filed unless truly necessary.
Are special permissions required? Yes, data correction operations are usually available only to a user with administrator rights.
What mode should it be run in? Preferably exclusive mode (all users logged out) — this reduces locks and the risk of errors.
10. Related documents and mechanisms
- Replace References (Master Data and Administration → Maintenance → Data Correction) — the main "calling" mechanism.
- Find and Delete Duplicates — uses the same replacement stream as a stage before deletion.
- Data Export and Import (Administration) — technical export/import between databases; during import, references to existing objects are matched by this same mechanism.
- Backup (Administration → Maintenance) — a mandatory "companion" before any replacement/deletion.
- Registration Log — where to check what was replaced and by whom.
How to check your release
Main menu → Help → About: this shows the "1C:Enterprise" platform version and the configuration release. Cross-check: this guide is current for "Trade Management for Kazakhstan" 3.4.5.21 (ed. 3.4). On other versions, the behavior of service mechanisms may differ.
Material prepared for release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4).