Directory "Incoming Payment Order Attached Files" (BK 3.0.74.2)

1. Identification

Purpose. The catalog stores files attached to documents Document.IncomingPaymentOrder (scans of payment orders, bank confirmations, PDF/XML attachments, electronic signature files). This is a service object of the "File Management" subsystem (BSP). The user interacts with it indirectly through the "Attached Files" command on the owner document form. In the command interface of sections, the catalog is usually not displayed as a standalone list.

For each owner document that supports attached files, the platform/BSP creates a separate storage catalog named <OwnerName>AttachedFiles. This catalog serves as a storage specifically for incoming payment orders. It does not contain accounting (financial) data and does not directly affect the regulated accounting of the RK.

2. Header Attributes and Table Parts

2.1 Header Attributes

The standard attribute Name stores the file name (without extension). The flag DeletionMark is used by the attachment deletion mechanism.

2.2 Table Parts

There are no table parts. The content of the file (when stored in the information base) is stored in the related information register IncomingPaymentOrderAttachedFilesFileStorage (resource type ValueStorage — binary data of the file and its versions). When stored on disk, the file body resides in the volume (Volume + FilePath), while only metadata remains in the information base.

3. Forms

Typically, specialized custom forms are not created — standard BSP forms of the "File Management" subsystem are used, common for all catalogs of attached files, ensuring interface uniformity.

4. Key Module Procedures

There is usually no specific application code in the modules of this catalog — all logic is implemented in the common BSP modules "File Management". Below are standard handlers for objects of this type (evidence by BSL is not attached — a standard scheme is provided).

• ObjectModule → BeforeWriting — control of mandatory attributes (Author, CreationDate, FileStorageType), prohibition of changing a file captured by another user, updating UniversalModificationDate and ModifiedBy.
• ObjectModule → BeforeDeleting — deletion of the file body from the volume when FileStorageType = OnDiskVolumes (cleaning up "orphaned" files on the disk).
• ManagerModule — programmatic addition of attachments: FileManagementService.AddFile(...), AttachedFiles.AddFile(...); obtaining binary data: AttachedFiles.GetFileData(...).
• Common BSP Calls (used by forms) — FileManagement, FileManagementClient, FileManagementService, FileManagementServiceClient: opening, saving, capturing/releasing (EditingUser), text extraction, working with EP and encryption.

Requires verification (version-specific): exact names of common modules and method signatures depend on the version of BSP embedded in 3.0.74.2.

5. Posting and Movements

The catalog is not a document and is not posted — it does not generate movements in accounting/accumulation registers. The postings according to the RK chart of accounts are generated by the owner document IncomingPaymentOrder, not by its file storage.

The only records related to the catalog element are service records:

• information register ...FileStorage — binary data of the file and versions (when stored in the information base);
• data of the full-text index (TextStorage, TextExtractionStatus).

For context — typical postings of the owner document "Incoming Payment Order" (receipt of payment from the customer), according to the typical RK chart of accounts:

Example: the customer pays for the sale in the amount of 1,160,000 ₸, including VAT 16% = 160,000 ₸ (RK VAT rate for 2026 is 16%). VAT and income are accrued by sales documents (Dr 1210 Cr 6010 / Cr 3130), while the incoming payment order merely closes the receivable: Dr 1030 Cr 1210 — 1,160,000 ₸. Electronic documents (ESF via IS ESF, CNT) are issued for the sale, and their file attachments can be stored in the catalogs of attached files of the corresponding documents.

6. Related Objects and Input Based On

• Owner: Document.IncomingPaymentOrder (attribute FileOwner).
• File Body Storage: information register IncomingPaymentOrderAttachedFilesFileStorage.
• Users: Catalog.Users (Author, ModifiedBy, EditingUser).
• Volumes: Catalog.FileStorageVolumes.
• Enumerations: FileStorageTypes, TextExtractionStatus.
• Subsystems: "File Management", "Electronic Signatures" / "Cryptography", "Full-text Search" (all part of BSP).

Input based on is not provided for this catalog. Elements are created only through the mechanism of attaching files to the owner document (drag and drop, "Add → from file / from scanner", from email) or programmatically using BSP methods.

7. Extension Points

• Configuration Extensions: adding custom attributes (for example, the flag "Checked", reference to the responsible person), additional commands on the form, overriding handlers BeforeWriting / BeforeDeleting.
• Additional Attributes and Information (subsystem "Properties") — if a composition of property sets is enabled for the object.
• BSP Programmatic API — FileManagement / AttachedFiles for uploading, downloading, signing, and encrypting attachments from your code.
• Event Subscriptions of the type CatalogReference.IncomingPaymentOrderAttachedFiles — control/audit of operations with files.
• Storage Configuration — switching between "In the information base" and "On disk volumes" through the parameters of the "File Management" subsystem (affects FileStorageType, Volume, FilePath).

When making modifications, do not change the composition of standard file attributes directly — use extensions to maintain compatibility with BSP updates and the standard configuration.