Reference Guide "Goods and Services Receipt Attached Files" (Accounting for Kazakhstan 3.0)

1. Identification

Purpose. The catalog stores files attached to the “Goods and Services Receipt” documents: scans of invoices, electronic invoices (ESF), acts of completed work, photographs of goods and materials, and other electronic documents confirming the fact of receipt. It is part of the BSP file management subsystem and ensures electronic document flow and archiving of supporting documents. It supports versioning, electronic signatures, and storage both in the information base and in volumes on disk. Work is conducted from the owner document form through the attached files panel; the catalog is usually not opened directly as a separate list.

Where to find (navigation link): e1cib/list/Catalog.GoodsAndServicesReceiptAttachedFiles In the interface — the “Attached Files” command on the “Goods and Services Receipt” document form.

2. Attributes and Structure

The catalog is built according to the BSP “Attached File” template, so its attributes are standardized. The catalog has no tabular parts — file versions and metadata are stored in related objects (see section 6).

2.1 Attributes (from evidence)

2.2 Standard BSP Attributes, Additional Set

In addition to those listed in evidence, the attached file template in BSP usually includes: FileStorageType (InInformationBase / InVolumesOnDisk), StorageVersion and CurrentVersion (reference to the active version from the version catalog), Name (file name without extension, standard attribute), DeletionMark, Code.

Requires verification: the exact composition of version storage attributes depends on the version of BSP embedded in 3.0.74.2.

3. Forms

The standard set of forms for the attached file in BSP:

The main user interface is the general form “AttachedFiles” (or the form element “Attached Files”), called from the document form GoodsAndServicesReceipt. Through it, file addition from a file/scanner, viewing, editing, versioning, and electronic signature signing are performed.

4. Key Procedures of Modules

Evidence with module texts (BSL, path:string) is not attached. Below are standard handlers for the attached files catalog, implemented through common BSP modules.

• OnCreateOnServer / BeforeWrite (object module) — auto-filling Author, CreationDate, UniversalModificationDate, ImageIndex (by extension).
• FileManagement.AddFile / AddFiles — attaching a file to the owner, creating a catalog item and the first version.
• FileManagementService.* — reading/writing binary data, processing volumes (FilePath), checking for occupancy (EditingUser).
• ElectronicSignature.* / setting SignedByES — signing and verifying the electronic signature of the file.
• Versioning — when the file is changed, a new version is created, CurrentVersion, ModifiedBy, UniversalModificationDate are updated.
• Cleanup Handler — when marking the owner document for deletion, marking/deleting related files.

Specific procedure names and strings should be checked in the modules FileManagement, FileManagementService, FileManagementServiceClient of the specific build 3.0.74.2.

5. Posting and Movements

The catalog is not posted and does not generate movements in registers — it is a data storage object, not a document. Accounting movements and postings are generated by the owner document “Goods and Services Receipt”; attached files merely accompany it as electronic copies of primary documents.

For context — the standard logic of posting the owner document in the typical chart of accounts of the RK:

Movement registers of the owner document: “Materials in warehouses”, “VAT to be refunded”, settlements with counterparties, etc. The VAT in the examples is at the rate of 16% (RK, 2026). An attached file (for example, an electronic invoice (ESF) from the ESF IS or SN) does not affect the amounts of movements.

The VAT rate of 16%, accounts 1330/3310/1420/1030, and electronic documents (ESF, SN) are provided according to the current regulations of the RK for 2026; for the file catalog, they are for reference.

6. Related Objects and Input on Basis

• Document.GoodsAndServicesReceipt — owner of the files (attribute FileOwner). Files are attached from its form.
• Catalog.GoodsAndServicesReceiptAttachedFilesVersions (standard paired version catalog) — stores versions of the file's binary data; reference CurrentVersion points to the active one.
• Catalog.Users — fills Author, ModifiedBy, EditingUser.
• File storage volumes (register/catalog of BSP volumes) — when FileStorageType = InVolumesOnDisk, physical placement by FilePath.
• Electronic Signature Subsystem — storage of certificates/signatures when SignedByES = True.

Input on basis: not provided and not applicable — the element is created only by the mechanism of attaching a file to the owner document, not by the “Create on basis” command.

7. Extension Points

• Additional attributes/information — through the BSP characteristic types plan (it is not recommended to change the composition of service attributes directly).
• Configuration extension — adding handlers BeforeWrite/OnWrite of the object module or overriding procedures of common modules FileManagement* for custom logic (extension validation, size limitation, auditing).
• Storage type — switching between storage in the information base and in volumes on disk through file subsystem settings.
• Integration of EDO RK — attaching generated electronic invoices (ESF)/SN as files; when modifying, it is necessary to rely on the owner GoodsAndServicesReceipt, not to change the file catalog.
• Signing events — intercepting the setting/removal of electronic signatures for additional control.

When modifying, maintain compatibility with the standard BSP file management mechanisms: changing service attributes breaks versioning and synchronization.