Directory "PackageExchangeWithBanksAttachedFiles" (Accounting for Kazakhstan 3.0.74.2)

1. Identification

Purpose. The catalog is intended for storing files attached to documents Document.ExchangePackageWithBanks. It is a technical subsystem for managing attachments in the context of bank integration: uploading, storing, versioning, and tracking documents (statements, payment orders, confirmations, receipts) received from or sent to the bank.

The catalog is built on the basis of the standard subsystem "File Management" in 1C and inherits its structure and behavior (storing content in volumes or in the IB, versions, electronic signatures, encryption). The user interacts with it not directly, but through the owner document card — the list of files is displayed in the exchange package form. Frequency of use — every session of working with bank statements and uploading/downloading payment documents.

Where to find in 1C: section "Electronic Interaction" → "Attached Files (Exchange Package with Banks)". Direct navigation: e1cib/list/Catalog.ExchangePackageWithBanksAttachedFiles.

2. Attributes and Table Parts

2.1 Header Attributes

In addition to the listed attributes, the catalog inherits the standard set of attributes of the "File Management" subsystem: Extension (file type without a dot), FileStorageType (in IB / in volumes on disk), TextStorage (extracted text for full-text search), CurrentFileVersion (reference to the current version), FileStorageVolume, DeletionMark. Standard attributes are Code, Name (file name).

2.2 Table Parts

The prefix Remove is a standard convention in 1C: attributes/table parts marked for deprecation, data migrated, but structure retained for updates from previous releases.

3. Forms

For catalogs of this type, attachment management is performed not by their own forms, but by the common forms of the "File Management" subsystem (CommonForm.AttachedFiles, forms for adding/viewing versions, signing window). The own forms of the catalog are minimal and serve an auxiliary role.

4. Key Procedures of Modules

In the attached evidence, BSL code (paths and strings) is not transmitted. Below are standard handlers of the attached files catalog of the "File Management" subsystem. Verify specific procedure names with the release (version-specific).

Manager Module / Common Mechanisms of the Subsystem:

• FileManagementService.AddFile(...) — creating a catalog element when uploading a new file: filling Author, CreationDate, Size, Extension, ImageIndex, writing content to storage/volume.
• FileManagement.SaveFile(...) — saving a new version, updating UniversalModificationDate and ModifiedBy.
• FileFunctionsService.GetFileVersion(...) — obtaining binary content of the current/selected version.
• Processing of ES and encryption — setting indicators SignedByES / Encrypted and writing data to related information registers.

Object Module (Standard Events):

• BeforeWriting — control of filling Author and CreationDate, recalculation of ImageIndex by extension.
• BeforeDeletion — clearing content in the volume on disk (deleting the physical file), deleting versions.
• FillingProcessing — setting Author = UsersClientServer.CurrentUser(), CreationDate = CurrentSessionDate().

Element Form Module:

• Commands "Open", "Edit", "Finish Editing", "Save As", "Sign ES", "Encrypt/Decrypt", "Versions" — delegated to the common module FileManagementClient.

5. Posting and Movements

The catalog is not a document and does not generate movements in registers — it does not create postings according to the chart of accounts. It stores attachments; accounting consequences arise from the owner document ExchangePackageWithBanks and related payment/income documents.

Indirectly, the catalog participates in filling technical registers of the "File Management" subsystem (without accounting meaning):

• information register with electronic signatures of files;
• information register with encryption certificates;
• register of "Uploaded Files" / volume data (accounting for physical storage).

Context of accounting postings of documents to which files are attached (chart of accounts of the RK, for reference):

Example: sale for the amount of 116,000 ₸ with VAT 16% → base 100,000 ₸, VAT 16,000 ₸ (Debit 1210 Credit 6010 — 100,000 ₸; Debit 1210 Credit 3130 — 16,000 ₸). Accompanying electronic documents — ESF (ESF IS) and SNT. The file attachment to these movements is not related — it merely stores a scan/statement/payment order.

6. Related Objects and Input on the Basis

• Owner Document: Document.ExchangePackageWithBanks (attribute FileOwner). Each file is tightly bound to one exchange package document.
• Author Users: Catalog.Users, Catalog.ExternalUsers, Catalog.FileSynchronizationAccounts.
• Subsystem "File Management": information registers of ES and encryption certificates, catalog of storage volumes, file versions.
• Similar catalogs of attached files of other configuration objects (single mechanism, different owners).

Input on the Basis. The classic "Input on the Basis" for the catalog is not applied. Elements are created automatically when a file is attached to the document ExchangePackageWithBanks (buttons "Attach File", "Upload", drag-and-drop, auto-upload during exchange with the bank via FileSynchronizationAccounts).

7. Extension Points

• Configuration Extension: adding attributes (for example, category/type of attachment, verification status), new commands in the list/element form, handlers BeforeWriting/BeforeDeletion through &After/&Instead.
• Additional Attributes and Information: the properties subsystem allows attaching characteristics to elements without changing the configuration.
• Access Restriction (RLS): rights to files are inherited from the owner and Author; custom RLS templates can be added for banking secrecy.
• Storage Volumes / External Storage: configuration of FileStorageType (in IB or in volumes on disk), integration with external file storage.
• Bank Exchange (DirectBank / statements): extension of automatic upload of attachments via FileSynchronizationAccounts.
• Full-text Search: the attribute TextStorage allows searching by the content of uploaded documents.

Requires verification (version-specific): exact names of module procedures, composition of ES/encryption registers, and presence of deprecated table parts Remove... in the specific build 3.0.74.2 — verify with the configurator.