ВыгрузкаЗагрузкаEnterpriseData" processing (UT for Kazakhstan 3.4.5.21)

1. Identification

Purpose. A service data processor of the Standard Subsystems Library (SSL) that implements manual (file-based) export and import of data in the universal EnterpriseData XML format. It allows exporting a set of infobase objects (documents, catalogs, registers) to an XML file according to the EnterpriseData format version, and, conversely, importing a previously received file into the target database. It is used as a tool for one-time/technical data exchange between different-type configurations (e.g., "Trade Management for Kazakhstan" ↔ "Accounting for Kazakhstan", ↔ external systems), as well as for diagnostics and initial configuration of conversion rules when creating an exchange node "via universal format".

The data processor does not generate accounting entries and does not post documents — it is a transport/conversion tool. It only transfers all amount and tax indicators (VAT 16%, IIT, OPC, etc.) "as is" as part of the exported objects.

2. Attributes and Data Structure

As a service data processor for EnterpriseData, the object has no posting and no permanent set of header attributes typical of an application document. Control parameters are stored in form attributes and in temporary storage for the duration of the session.

Export parameters (export form attributes)

Tabular section "Export Composition" (data types to export)

Import parameters (import form attributes)

3. Forms

The exact list of forms is version-dependent: in different SSL releases, the wizard may be implemented as a single form with steps or as several separate forms. Requires verification against the specific 3.4.5.21 build.

4. Key Module Procedures

No direct evidence from the BSL modules of the data processor is provided, so below are the typical handlers and procedures for this type of SSL object (mechanism ОбменДаннымиXDTO / МенеджерОбменаЧерезУниверсальныйФормат).

Export form module:

• ПриСозданииНаСервере — initializes the list of available EnterpriseData types and format versions.
• ВыполнитьВыгрузку(...) → calls МенеджерОбменаЧерезУниверсальныйФормат.ВыгрузитьВФайл(...) — serializes the selected objects into XML according to the XDTO schema of the selected format version.
• ЗаполнитьСоставВыгрузкиПоУмолчанию — populates tabular section rows based on available types.

Import form module:

• ВыполнитьЗагрузку(...) → МенеджерОбменаЧерезУниверсальныйФормат.ЗагрузитьИзФайла(...) — reads XML, matches according to conversion rules, records objects.
• ПроанализироватьФайл — preliminary XML parsing and display of statistics without recording.

Object module / common modules of the mechanism:

• ОбменДаннымиXDTO, МенеджерОбменаЧерезУниверсальныйФормат — low-level (de)serialization, working with the EnterpriseData schema (XDTO package), handling references and unique identifiers (UUID).
• Conversion rules are stored in the exchange manager module (МенеджерОбмена…) and define the correspondence between format objects and configuration objects.

5. Posting and Register Movements

The data processor is not a document and does not generate register movements or accounting entries.

Important for implementers: register movements and accounting entries are created by the imported application documents when they are subsequently posted in the target database. For the Kazakhstan configuration, the standard logic looks as follows (accounts per the standard Kazakhstan chart of accounts):

Sale of goods (example, VAT rate 16%):

Receipt of goods from supplier:

Payment from customer / to supplier:

VAT calculation example: sale of 1,000,000 ₸ excluding VAT → VAT = 1,000,000 × 16% = 160,000 ₸ (Dt 1210 Ct 3130), total payable 1,160,000 ₸.

Payroll/tax indicators transferred as part of the export when exchanging with the payroll circuit (Kazakhstan 2026 values): MCI = 4,325 ₸, MW = 85,000 ₸; basic tax deduction for IIT — 30 MCI per month (= 129,750 ₸), but no more than 360 MCI per year; IIT 10% up to 8,500 MCI of annual income and 15% above; OPC 10% (base cap — 50 MW = 4,250,000 ₸), OPCE 3.5%, EHIC 2%, SHI 3%, SI 5%, social tax 6%. The data processor itself does not calculate these indicators — it only transfers them from the source objects.

6. Related Objects and Input Based On

• Common modules: ОбменДаннымиXDTO, МенеджерОбменаЧерезУниверсальныйФормат, ОбменДаннымиСервер — the core of the mechanism.
• XDTO package EnterpriseData (corresponding format version) — the exchange data schema.
• "Via universal format" exchange plans — the data processor is used as a manual alternative to automatic exchange via a node.
• Application participant objects: documents (Sales of Goods and Services, Receipt of Goods and Services, Payment Documents), catalogs (Products, Counterparties, Organizations), information registers.
• Electronic documents in Kazakhstan: exported sales/receipt documents are linked to the generation of ESF (ESF IS) and SNT; the electronic documents themselves are generated by dedicated subsystems, while EnterpriseData transfers their base attributes.

Input based on — not supported (a data processor, not a document).

7. Extension Points

• Conversion rules (exchange manager): redefining the correspondence "format object ↔ configuration object", adding custom types for export/import.
• SSL programming interfaces: ПередОтправкой/ПередЗагрузкой handlers in the rules for adjusting data "on the fly".
• Configuration extension: adding handlers to the export/import form modules (e.g., autofilling filters), enabling additional data types.
• EnterpriseData format version: when exchanging between releases, agree on a common supported format version on the source and target.
• Event subscriptions for participant objects to react to change registration during incremental export.