Documents.ESFAttachedFiles — Technical Description

1. Identification

Purpose. The object is intended for storing files attached to electronic invoice documents (Document.ESF) in the tax accounting system of the Republic of Kazakhstan. It provides a link between the owner document “ESF” and its file attachments: XML files of invoices for the ESF information system, scans, electronic signature files (ES), and accompanying documents. The object belongs to the electronic document management subsystem (ESF, SNT) and is created by the standard mechanism “Attached Files” of the Standard Subsystems Library (BSP).

Users (accountants responsible for electronic document management) work with attachments through the ESF document form, rather than directly with this object. The object ensures versioning of files, storage, and the presence indicator of the electronic signature, file locking during editing, and integration with full-text search.

Note on type: in the Kazakh version, attached files for ESF are implemented as a metadata object of the type Document (object_type_ru: "Документ"), although functionally it is a storage for attachments generated by the BSP subsystem. Below, the structure is described according to the actual evidence.

2. Attributes and Table Parts

2.1 Header Attributes

In addition to the listed, it is typical for this type of BSP objects to have service attributes: VersionStorage/links to file version data, StorageVolume, and FileStorage (binary data when stored in the IB). The composition of the data storage depends on the chosen storage method (in the database or on volumes).

2.2 Table Parts

The object has no table parts — it is a flat storage of a single file attachment (one record = one file attached to one ESF). The multiplicity of attachments is implemented by multiple records with one FileOwner.

3. Forms

Forms are generated by the “Attached Files” subsystem of BSP. Standard composition:

In practice, work is conducted through the embedded table “Attached Files” on the ESF document form (commands “Add”, “View”, “Sign ES”, “Save”), while the object's own forms are rarely opened.

4. Key Module Procedures

No separate application BSL code is attached in evidence — the behavior of the object is defined by the general mechanisms of the “Attached Files” subsystem of BSP. Standard handlers for this type of object:

• Object Module → FillProcessing — filling Author, CreationDate, UniversalModificationDate when creating an attachment.
• Object Module → BeforeWriting / OnWriting — fixing ModifiedBy, updating UniversalModificationDate, refreshing Size/Extension, resetting the text extraction status when changing content.
• Object Module → FillCheckProcessing — control of mandatory attributes Author and CreationDate (ShowError mode).
• Common BSP Modules — FileManagement, FileManagementService, FileManagementServerCall: adding a file, reading/writing binary data, extracting text for full-text search (filling TextStorage, TextExtractionStatus), managing locking (EditingBy), working with ES (SignedByES, Encrypted) and storage on volumes (FilePath, StorageVolume).

Version-specific: the exact names of procedures and breakdown by common modules depend on the version of BSP integrated into 3.0.74.2 — when refining, clarify with the configurator.

5. Posting and Movements

The object is not a posted document in the accounting sense: it has no movements in accounting and accumulation registers and it does not generate postings. This is a storage for file attachments — the “Posting” attribute and the mechanism for generating movements for it are not used.

Accounting movements are generated by the owner document ESF and related primary documents of sales/purchases, while attached files only store their electronic images (XML, ES). For reference — the standard logic of postings for documents to which ESF belongs (numbers and accounts for RK in 2026):

• Sale of goods (standard chart of accounts RK):
  • Dr 1210 Cr 6010 — revenue from sales;
  • Dr 1210 Cr 3130 — VAT at the rate of 16 % (for example, with a base of 1,000,000 ₸ the VAT amount = 160,000 ₸);
  • Dr 7010 Cr 1330 — write-off of the cost of sold goods.
• Receipt of goods:
  • Dr 1330 Cr 3310 — receipt of goods;
  • Dr 1420/1330 Cr 3310 — VAT to be credited (16 %).
• Payment: Dr 1030 Cr 1210 (from the buyer), Dr 3310 Cr 1030 (to the supplier).

These postings belong to the ESF/sales/purchase documents, not to the object ESFAttachedFiles.

6. Related Objects and Input Based On

• Owner Document: Document.ESF — through the attribute FileOwner. One ESF document can have several attached files.
• Adjacent EDO Objects: Document.SNT (accompanying invoices for goods) and other electronic documents have their own attached file objects according to the same BSP scheme.
• Reference.Users — attributes Author, ModifiedBy, EditingBy.
• Enumeration.TextExtractionStatuses — attribute TextExtractionStatus.
• Data Storage: binary data and versions — in IB (ValueStorage) or on file storage volumes (attributes FilePath, volume).
• Input Based On: manual input based on is not provided and makes no sense — records are created automatically when a file is attached to the ESF through the BSP mechanism.

7. Extension Points

• Configuration Extension: adding attributes (for example, attachment type, document category, storage period) and borrowing forms for refining the attachment card.
• Event Subscriptions: BeforeWriting/OnWriting of the object — for additional auditing, auto-numbering of versions, integration with external archives.
• Common BSP Modules “File Management”: overridable procedures (FileManagementOverridable, FileManagementServiceClientServer) — managing storage methods, limiting extensions/sizes, processing ES.
• Exchange Rules/Integration: exporting attachments to the ESF information system and external archives; controlling the SignedByES indicator before sending.
• Full-text Search: configuring text extraction through TextExtractionStatus/TextStorage for searching the content of XML/PDF attachments of ESF.
• Roles and RLS: restricting access to attachments by Author/organization of the owner document.

Version-specific: the list of overridable procedures of BSP and the presence of subscriptions in the 3.0.74.2 delivery should be clarified in the configurator before refinement.