Guide "Power of Attorney Attached Files" - Technical Description (Accounting for Kazakhstan 3.0.74.2)

1. Identification

Role in the configuration. This is a service catalog of the file management subsystem of the BSP (standard subsystem "File Management"). For each owner object that is allowed to attach files, the platform/configuration creates a separate catalog of the type <Owner>AttachedFiles. This catalog serves the document Power of Attorney: the user interacts with it indirectly through the power of attorney form (commands "Attached Files", "Attach File", drag-and-drop). The catalog supports versioning, electronic signature, encryption, and storage of the file both in the information base and on external volumes.

Note: the catalog is not accounting — it does not generate accounting entries and does not participate in tax calculations of the RK (VAT 16%, PIT, social contributions, etc.). The calculation logic (rates, accounts of the RK plan) is implemented in the owner document "Power of Attorney" and related documents of sale/receipt, not in the file catalog.

2. Attributes of the header and table parts

2.1 Header Attributes

The name (Name, standard attribute) stores the file name without the extension; the full name is formed as Name + "." + Extension.

2.2 Table Parts

The catalog does not have its own table parts. Binary data of files stored "in the database" is placed:

• in the value storage through the information register of the file subsystem (for BSP — BinaryFileData / storage of volumes), or
• on an external volume (Catalog.FileStorageVolumes), when FileStorageType = OnVolume; in this case, the attribute FilePath is significant.

File versions and attached electronic signatures are stored in separate service objects of the subsystem (registers/catalogs of versions and EP), not in the table parts of this catalog.

3. Forms

As an element of the file subsystem, the catalog primarily uses common BSP forms, not its own:

4. Key Procedures of Modules

No application BSL code is attached to the evidence — the catalog does not carry calculation logic. Processing is performed by standard mechanisms of the "File Management" subsystem of the BSP. Standard handlers of this type of object:

Object Module:

• BeforeWriting — recording indicators of changes, control of file occupancy by editing (attribute EditingUser), updating UniversalModificationDate and ModifiedBy.
• OnCopying / FillCheckFilling — control of mandatory attributes Author, CreationDate, FileStorageType (ShowError flag).

Manager Module:

• Functions for creating a file element and recording binary data (through the common module FileManagementService / AttachedFilesService BSP): receiving the file stream, determining the extension, size, image index, setting Author, CreationDate.

Forms (handlers):

• AttachFile / AddFile — uploading a file from disk or scanner, creating an element, linking to FileOwner.
• Open / FinishEditing — unloading to temporary storage, locking via EditingUser, receiving the modified version back.
• SignEP / Encrypt — working with cryptography, setting SignedEP / Encrypted.

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

5. Posting and Movements

The catalog is not posted and does not generate movements in either accounting registers or accumulation/information registers of the accounting circuit. Accordingly:

• it does not create entries in the RK chart of accounts (1210, 1030, 1330, 3310, 3130, 6010, 7010, etc.);
• it does not participate in VAT calculations (16%), PIT, social contributions (10%), social contributions for the self-employed (3.5%), VOSMS (2%), OSMS (3%), social tax (6%);
• it does not participate in the exchange of electronic invoices (ESF) (IS ESF) and SNF — these documents are related to sales/movement, not to the storage of the power of attorney scan.

The only records accompanying the element are service records: information about binary data/versions, electronic signatures, and extracted text (TextStorage, TextExtractionStatus) for full-text search. This data is stored in the registers of the BSP file subsystem.

6. Related Objects and Input on the Basis

Input on the basis for the service file catalog is not provided. Elements are created only through the file attachment mechanism from the power of attorney form. The power of attorney can be opened from the file card via the attribute FileOwner.

7. Extension Points

• Format and size restrictions. Allowed extensions and maximum size are set in the settings of the "File Management" subsystem (constants/register of settings of BSP), not in the catalog itself.
• Storage. Switching "in database / on volume" through FileStorageType and the catalog of volumes; expandable by adding new volumes without changing metadata.
• Additional attributes/information. Through the BSP properties mechanism (CharacteristicTypes.AdditionalAttributesAndInformation), attributes can be added to files without changing the configuration on support.
• Subscriptions to events / configuration extensions. The processing of BeforeWriting/OnWriting of the element can be supplemented in the extension for auditing, auto-numbering, or integration with external storage.
• Full-text search. Text extraction (TextStorage, TextExtractionStatus) is configured by a regulatory task; expandable for new file types.
• Cryptography. EP and encryption profiles are configured in the BSP electronic signature subsystem; the catalog only stores indicators (SignedEP, Encrypted).