Processing "DataUploadDownloadLinkReplacementStream" (UT for Kazakhstan 3.4.5.21)

1. Identification

This data processor belongs to the infrastructure of the SSL/standard export-import subsystem. It is not a document, does not get posted, and does not generate accounting entries on its own (see Section 5).

2. Attributes and tabular sections

Technological data processors of this class have a minimal set of attributes; data is passed through procedure parameters and through the export/import context object, rather than through form attributes. Typical composition:

Attributes (header / data processor attributes):

Tabular sections: the reference replacement data processor generally has no tabular sections of its own. Working data sets (reference mappings, object queue, matching errors) are stored in temporary value tables/structures in memory for the duration of the export-import session.

3. Forms

If no specialized forms exist in the configuration, the data processor operates programmatically (without interactive forms) as part of the overall export/import process.

4. Key module procedures

The attached evidence does not include BSL source code (only the "purpose" facet is available). Therefore, listed below are the typical handlers for this type of object within the data export/import subsystem. When working with a specific version, verify the signatures against the object module.

• ПриВыгрузкеДанных(Контейнер, ...) — registers objects and their references in the export container; builds the data stream for subsequent reference replacement.
• ПередЗагрузкойДанных(Контейнер, ...) / ПриЗагрузкеДанных(...) — accepts the object stream and initializes the source-to-target reference mapping table.
• ЗаменитьСсылки(ОбъектДанных, ТаблицаСоответствия) — the core of the processing: traverses the object's reference attributes and replaces old identifiers with the target identifiers according to the mapping table (by GUID or by natural keys — code, name, TIN/BIN).
• СопоставитьОбъект(ОбъектИсточника) — looks for the matching object in the target; if not found, registers the creation of a new one or places it in the queue of unresolved references.
• ПослеЗагрузкиДанных(Контейнер, ...) — a "second pass": resolves deferred references (cyclic and mutual dependencies), records unmatched objects in the error log.
• ПолучитьЗависимости() / СтруктураПотока() — describes the processing order and this stream's dependency on other export-import streams.

"Requires verification" (genuinely version-specific): the exact handler names and signatures depend on the SSL/subsystem release; in 3.4.5.21 verify against the object module.

5. Impact on data, posting, and register entries

The data processor does not post and does not generate register entries directly and does not create accounting entries. Its result is correctly transferred and matched data, for which document posting subsequently generates standard entries according to the configuration's rules.

To make the description practically useful, below is what the entries of transferred documents look like after reference replacement — using the standard Kazakhstan chart of accounts and current 2026 Kazakhstan figures (VAT rate 16%):

Example: sale of goods for 1,000,000 ₸ (excl. VAT), VAT 16% = 160,000 ₸, total payable 1,160,000 ₸.

Payment received from customer:

Goods received from supplier (1,160,000 ₸ incl. VAT 16%):

Kazakhstan electronic documents (ESF in the ESF IS, SNT) are issued for transferred documents by the configuration's standard mechanisms — the reference replacement processor itself does not generate them, but it ensures reference integrity (counterparty, contract, item, tax attributes), without which issuing an ESF/SNT is not possible.

Reference (current Kazakhstan 2026 norms, for verifying transferred settlement data): MCI = 4,325 ₸, minimum wage = 85,000 ₸; basic individual income tax deduction = 30 MCI/month (not exceeding 360 MCI/year); IIT 10% up to 8,500 MCI of annual income and 15% above; mandatory pension contributions 10% (base cap of 50 minimum wages), employer pension contributions 3.5%, voluntary social health insurance contributions 2%, social health insurance contributions 3%, social contributions 5%, social tax 6%.

6. Related objects and entry based on

• Entry based on does not apply to this service data processor (it is not a document).
• Related objects:
  • The shared "Data Export and Import" wizard/data processor — invokes this stream as one of the stages.
  • Other subsystem "streams" (data export, change registration, serialization) — this stream depends on them and runs in a defined order.
  • Exchange plans and conversion rules (when transferring between different configurations/databases).
  • All reference objects involved in the transfer: counterparties, contracts, items (1330), organizations, accounting accounts — their GUIDs are reassigned.
• Registers: the data processor accesses information and accumulation registers only to match/register reference mappings, but does not write application-level register entries.

7. Extension points

• Configuration extension (adaptation without losing support status): overriding the ЗаменитьСсылки, СопоставитьОбъект, ПослеЗагрузкиДанных handlers to add custom matching rules (for example, by counterparty BIN/IIN or item code).
• Natural-key matching rules: configuring the list of identifier attributes used to link a source object to the target when there is no GUID match.
• Programmatic invocation from external scenarios: using it in custom migration/consolidation data processors as a ready-made reference replacement mechanism.
• Logging: hooking into processing events to record unmatched references and conflicts in the event log.
• Additional SSL handlers ("ПередЗагрузкойДанных", "ПриВыгрузкеДанных") — for fine-tuning the composition of exported/imported references.