Directory "Invoice to the Buyer Attached Files" — Technical Description

1. Identification

Where to find: the object is service-related, does not have a separate menu item — file management is done from the "Customer Invoice" document form via the panel/hyperlink "Attached Files". Direct navigation link to the list:

e1cib/list/Catalog.CustomerInvoiceAttachedFiles

This is part of the standard BSP mechanism "Attached Files": for each owner object that has file management enabled, there exists a similarly named catalog <Owner>AttachedFiles in the configuration. This catalog exclusively serves the document "Customer Invoice".

2. Header Attributes and Table Parts

The catalog is an implementation of the standard object "Attached File" in BSP. It does not contain table parts — all data is stored in header attributes; binary file content and electronic signatures are moved to separate information registers (see section 5).

2.1 Header Attributes

2.2 Standard Attributes and Predefined Fields

Binary file data (ValueStorage) and electronic signatures are not stored in the attributes of the catalog itself — they are moved to separate information registers for optimization and support of storage on volumes on disk.

3. Forms

User interaction with the invoice does not occur directly through these forms, but through the standard BSP form "AttachedFiles" (common form/panel), which is embedded in the "Customer Invoice" document form and displays files from this catalog with commands for adding, viewing, versions, signing, and encryption.

4. Key Module Procedures

There is usually no direct BSL code of business logic in the object module of this catalog — behavior is provided by common modules of the "Attached Files" BSP subsystem (FileManagement, FileManagementService, FileManagementServerCall, AttachedFiles). Evidence with specific lines of modules for this object is not attached, so below are typical handlers and points for this type of object:

• ObjectModule → OnWrite / BeforeWrite — fixing attributes ModifiedBy and UniversalModificationDate, updating indicators SignedEP, Encrypted, recalculating ImageIndex by Extension.
• CommonModule FileManagementService — creating a file item, writing binary data to storage (database or volume), forming versions, locking/unlocking for editing (attribute EditedBy).
• CommonModule FileManagement (client) — commands "Open", "Edit", "Finish Editing", "Save As...", adding a file from disk/scanner.
• Signature/encryption handlers — placing electronic signatures and encrypting with certificates, recording results in information registers and setting flags SignedEP / Encrypted.
• ElementForm.OnCreateOnServer — filling Author, CreationDate upon initial creation; managing the availability of commands based on rights and lock status.

"Requires verification" (versioned): the exact set of common forms and the presence/absence of a custom object module depend on the version of the built-in BSP in 3.0.74.2 — clarified in the configurator.

5. Posting and Movements

The catalog is not a document — it does not post and does not generate accounting entries. This is fundamental: attached files do not affect accounting registers, mutual settlements, VAT, or taxes. Economic movements are generated by the owner document "Customer Invoice" and related sales/payment operations.

The catalog only participates in information registers of the file management subsystem:

For reference — movements are generated by not the file, but the owner document "Customer Invoice" and subsequent sales (Kazakhstan, 2026):

• reflecting sales: Dr 1210 "Short-term receivables from customers" — Cr 6010 "Revenue from sales";
• VAT at the rate of 16% (current rate in RK for 2026): Dr 1210 — Cr 3130 "VAT payable" (or broken down by product price);
• cost of goods sold: Dr 7010 "Cost of sales" — Cr 1330 "Goods";
• payment from the customer: Dr 1030 "Cash in current bank accounts" — Cr 1210.

Electronic documents accompanying settlements (not the catalog of files itself): ESF (IS ESF) and SNT. Currency of accounting — tenge (₸).

Example: an invoice for 1,160,000 ₸ with VAT of 16% contains VAT of 160,000 ₸ and a cost excluding VAT of 1,000,000 ₸. The PDF scan attached to this invoice is an item of the catalog under consideration, which does not participate in the posted entries.

6. Related Objects and Input Based On

• Document CustomerInvoice — owner object. Files are created/viewed from its form; deleting the owner document makes the files "orphaned" (normally cleaned by the deletion service).
• Catalog Users — source of values for attributes Author, ModifiedBy, EditedBy.
• Information Registers of storage, signatures, and encryption (see section 5).
• Input based on: not provided for this catalog and does not make sense — items are created exclusively by the mechanism of attaching a file to the owner document, not by the "Create Based On" command.

7. Extension Points

• Additional attributes/information through the characteristic types plan of BSP — for classifying files (e.g., "Document Type": scan, specification, contract), without changing the configuration.
• Configuration extension: adding attributes to the catalog, redefining element/list forms, adding custom commands to the attached files form.
• Event subscriptions BeforeWrite/OnWrite of the catalog — for auditing attachment/modification of files or integration with external storage/EDMS.
• File storage settings: switching between storage in the database and on volumes on disk (attribute FilePath is used when on volumes) — standard setting of the subsystem, not an enhancement of the object.
• Exchange rules (RIB/synchronization): attribute UniversalModificationDate — standard point for version control during exchange; to be considered when setting up file migration.

"Requires verification" (versioned): the availability of specific mechanisms for additional attributes and volume options depends on whether the corresponding functional options are included in 3.0.74.2.