Guide "Receipt of Additional Expenses Attached Files" - Technical Description (BK 3.0.74.2)

1. Identification

Purpose. The catalog stores files attached to the “Additional Expenses Receipt” documents: scanned copies of primary documents, contracts, specifications, acts on additional expenses (transport, TMR, intermediary services, etc.), included in the cost of acquired goods (account 1330 “Goods”). This is a service (subordinate in meaning) object: the end user interacts with it indirectly — through the “Attached Files” command in the owner document form. Directly opening the catalog list is necessary for the administrator during group maintenance of metadata, analyzing storage volumes, or diagnostics.

2. Attributes and Table Parts

2.1 Header Attributes

Standard attributes: Code, Name (matches in meaning with Description), DeletionMark, Predefined (not used), Reference. Binary file data when stored in the database is placed in the storage attribute (FileStorage / stored through the register — see section 5).

2.2 Table Parts

Table parts in catalogs of this type are generally absent: file versions and their binary content are stored in external objects of the subsystem (storage registers and version catalog), not in the owner’s table part. Metadata of versions are linked to the catalog item by reference.

3. Forms

In practice, the user does not work directly with these forms, but through the common forms of the “FileManagement” subsystem (AttachedFiles, form for adding/viewing versions), invoked by the “Attached Files” command from the document form AdditionalExpensesReceipt.

4. Key Module Procedures

Application BSL code in the modules of this catalog is absent or minimal — the logic is moved to the common BSP modules. Below are listed typical handlers of this type of object (evidence by BSL is not attached — version-specific lines require verification with a specific delivery):

Object Module:

• BeforeWriting — recording UniversalModificationDate, ModifiedBy, recalculating Size, updating ImageIndex by extension.
• OnCopy / FillProcessing — setting Author, CreationDate when created from the attachment command.
• BeforeDeletion — clearing related storage data (volume/register) through subsystem methods.

Manager Module / Common BSP Modules:

• FileManagement, FileManagementService, FileManagementServerCall — adding a file, reading/writing binary data, version management, check-out/check-in, encryption and EP signing.
• TextExtractionFromFiles — background text extraction, setting TextExtractionStatus and filling TextStorage.

5. Posting and Movements

The catalog is not posted and does not generate accounting entries and movements in accounting registers — it is a data storage object, not a document. It does not make any entries in the accounting register (entries in RK accounts).

Economic movements are generated by the owner document AdditionalExpensesReceipt. For context — its typical logic on the RK chart of accounts (RK VAT rate from 2026 — 16 %, currency — tenge ₸):

• Attributing the amount of additional expenses to the cost of goods: Dr 1330 “Goods” — Cr 3310 “Payables to Suppliers”.
• Highlighting input VAT 16 %: Dr 1420 “VAT to be Reimbursed” — Cr 3310 (upon confirmation of ESF from the ESF IS).
• Payment to the supplier: Dr 3310 — Cr 1030 “Cash in Current Accounts”.

Example: additional expenses 500,000 ₸ + VAT 16 % (80,000 ₸): Dr 1330 = 500,000 ₸; Dr 1420 = 80,000 ₸; Cr 3310 = 580,000 ₸.

Technical file storage registers (this is not accounting), into which data indirectly enters when recording the item:

• register of binary data file storage in the database (when FileStorageType = FileStorage) — stores the content of versions;
• or volume storage on disk (when stored “on the volume”) — the path is fixed in FilePath;
• service records of versions and EP/encryption indicators.

6. Related Objects and Input Based On

• Owner Document: Document.AdditionalExpensesReceipt (attribute FileOwner).
• Catalogs: Users (Author, ModifiedBy, EditingUser).
• Enumerations: FileStorageTypes, TextExtractionStatuses.
• Subsystem: “FileManagement” (common modules, common forms, storage registers, volumes).
• Electronic Documents: the files themselves may contain printed forms/receipts of ESF (ESF IS) and SCT, but the catalog does not interact directly with the ESF IS.

Input based on for this catalog is not provided: items are created exclusively through the file attachment mechanism from the owner document form (command “Attached Files” → “Add”). As a source for input based on, the catalog also does not serve.

7. Extension Points

• Configuration Extensions: adding attributes (e.g., document type classification, storage period) and subscribing to write events without removing from support.
• Subscriptions to Events BeforeWriting / OnWriting of the object — for integration with external archive, DMS, or quota control.
• Additional BSP Processing (AdditionalReportsAndProcessing) — batch processing, conversion, EP verification.
• Settings of the “FileManagement” subsystem: storage volumes, maximum size, text extraction, encryption, synchronization — set by the administrator without code modification.
• Access Rights (RLS): limiting file visibility through profiles and access groups linked to rights on the owner document.