Directory "Bank Accounts Attached Files" — Technical Description

1. Identification

Purpose. The catalog stores files attached to the elements of the “Bank Accounts” catalog: scans of banking service agreements, cards with signature samples, notifications of account opening/closing, bank details, and other documentation. The object is part of the standard library subsystem “File Management” (BSP) and is created automatically when a file is attached in the owner account card. Direct manual creation of elements is not provided — access is through the owner’s attached files interface. The catalog stores both the file metadata (name, size, extension, author, versions) and the binary data itself — in the information base or on file storage volumes.

This is a service catalog of the file storage infrastructure. It does not contain any accounting data (amounts, accounting accounts, taxes) and does not participate in accounting/tax accounting. The country parameters of the RK listed below are provided for the context of the configuration but do not apply to this object.

2. Header Attributes and Table Parts

2.1 Header Attributes

The standard attribute Name is used as the file name (without extension). The binary data of the file is stored either in the internal attribute/value storage of the object (when stored in the IB) or on file storage volumes (information register of the file management subsystem) — the path is fixed in FilePath.

2.2 Table Parts

The object does not have table parts. Versioning (file version history) is implemented not as a table part but as a separate version catalog of the BSP subsystem (see section 6).

3. Forms

If separate forms in the object are not redefined, auto-generated and common forms of the “File Management” BSP subsystem are used (attached files forms, file addition, version selection).

4. Key Module Procedures

The attached evidence contains only the facets of “purpose” and “fields” — the original BSL modules of the object are not attached. Therefore, below are typical handlers for this type of object (catalog of attached files BSP). Specify the exact lines according to your delivery code.

Manager Module / Common Modules of the Subsystem:

• Registration of the object in the subsystem through the common module FileManagementServerCall / FileManagement — determining that the catalog is a storage of the owner’s attached files BankAccounts.
• PlaceFile / UpdateFileVersion — creating a catalog element when adding a file: filling Author, CreationDate, UniversalModificationDate, Size, Extension, ImageIndex, placing binary data in the IB or on the volume.

Object Module:

• BeforeWriting — control of file editing occupancy (EditingUser), updating ModifiedBy and UniversalModificationDate.
• BeforeDeleting — deleting related binary data on the storage volume and file versions.

Element/List Form Module:

• Handlers for commands to open, save, edit, finish editing, add/check EP, encrypt/decrypt.
• OnCreationOnServer — configuring the availability of commands based on user rights and file status.

Requires verification (version-specific): the exact names and signatures of procedures in the common BSP modules depend on the version of the Standard Subsystems Library included 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 registers, accumulation, or information in an accounting sense. Transactions (including according to the standard chart of accounts of the RK: 1030 “Cash on Current Accounts”, 1210 “Short-term Accounts Receivable”, 3310 “Accounts Payable”, 3130 “VAT”, 6010 “Revenue from Sales”, 7010 “Cost of Sales”) generate accounting documents (bank statements, invoices, etc.), not files attached to the account.

Technical records related to file storage (when stored on volumes) are performed by the BSP subsystem in service information registers of file storage — these are infrastructural, not accounting movements.

6. Related Objects and Input Based On

• Owner: Catalog.BankAccounts — the sole owner; the life cycle of the file is tied to the account.
• Users: Catalog.Users — attributes Author, ModifiedBy, EditingUser.
• Text Extraction Statuses: Enumeration.TextExtractionStatusFiles.
• File Versions: catalog of versions of attached files BSP (stores the history of file replacements).
• Volumes and Storage: service information registers of the “File Management” subsystem (storage volume, path, binary data).
• Cryptography: electronic signature and encryption subsystem (attributes SignedEP, Encrypted).

Input based on is not provided: elements are created exclusively through the file attachment mechanism in the bank account card.

7. Extension Points

• Configuration extension of the bank account attached files form — adding custom commands/attributes to the form without removing it from support.
• Event subscriptions BeforeWriting/BeforeDeleting of the catalog — for auditing, integration with external document storage, automatic classification of scans.
• Configuration of file storage volumes — moving binary data from the IB to disk for volume control (attributes FilePath, Size).
• Full-text search — using TextStorage and TextExtractionStatus for searching the content of attached agreements/notifications.
• Electronic signature/encryption — integration with corporate certificates; when exchanging with the ESF/SNT IS, scans to the account can complement the document package but are signed by the means of the respective subsystems, not this catalog.