Directory "Termination from Organizations Attached Files" — Technical Description

1. Identification

Purpose. The reference stores files attached to the documents “Termination from organizations.” HR specialists and accountants use it to attach scans of resignation letters, orders, clearance forms, settlement documents, and other files accompanying the employee termination process. The object is technical: it works in conjunction with the standard file handling subsystem of the platform and is generally not opened directly by the user — access to files is made from the owner document form via the “Attached files” command. The frequency of use is determined by the intensity of termination HR operations in the organization.

Note. This is a standalone reference of attached files, linked to one type of owner document (TerminationFromOrganizations). In the standard configuration, a separate reference “...AttachedFiles” is created for each object that supports attachments.

2. Header Attributes

The object has no tabular parts — all information about the file is stored in the header attributes. Binary data of versions, if versioning is enabled, is maintained in a separate information register of the file handling subsystem.

Logic of the pair “FileStorageType ↔ data”.

• InDatabase — data is stored in FileStorage, attributes Volume/FilePath are not filled.
• OnDiskVolumes — Volume and FilePath are filled, FileStorage is empty.

Attributes EditingUser/CheckoutDate form the mechanism for checking out the file for editing: while the file is checked out, re-editing by other users is blocked.

3. Forms

Service references of attached files primarily use the common forms of the file handling subsystem. Standard composition:

In practice, working with elements is done through the common forms of the BSP/file subsystem (CommonForm.AttachedFiles, version viewing form, etc.), rather than through the reference's own forms.

4. Key Module Procedures

Application BSL code in the modules of the object is usually minimal — all processing is moved to the common modules of the “File Handling” subsystem. Standard handlers for this type of object:

Object module:

• BeforeWriting(Refusal) — control of mandatory attributes filling (Author, CreationDate, FileStorageType), fixing ModifiedBy/UniversalModificationDate.
• BeforeDeleting(Refusal) — when stored externally, deletion of the physical file from the disk (Volume + FilePath) along with the reference element.

Manager and common modules of the file subsystem:

• FileHandling/FileProcessing — adding a file, reading/writing binary data, creating versions, checking out and releasing for editing.
• Text extraction and filling TextStorage/TextExtractionStatus for full-text search — as a background task.

There is no separate attached BSL-evidence for this object; the listed is the standard implementation of attached files in the standard configuration. The exact composition of common modules may vary between releases (version-specific).

5. Posting and Movements

The reference is not posted and does not generate movements in accounting registers — like any object of type “Reference,” it only stores data. The postings and register movements (settlements with personnel, accruals during final settlement) are generated by the owner document Document.TerminationFromOrganizations, not the file storage.

For context — according to the standard logic of final settlement upon termination in the RK (dates: Kazakhstan 2026), the owner document addresses withholdings and contributions from the payroll fund:

• Individual Income Tax (IIT) — 10% up to 8,500 MRP of annual income, 15% above; basic tax deduction for IIT — 30 MRP per month, not more than 360 MRP per year.
• Mandatory Pension Contributions (MPC) — 10% (base ceiling 50 MZP), Mandatory Pension Insurance Contributions (MPIC) — 3.5%, Social Health Insurance Contributions (SHIC) — 2%, Obligatory Social Medical Insurance (OSMI) — 3%, Social Tax — 5%, Social Tax — 6%.
• Reference values for 2026: MRP = 4,325 ₸, MZP = 85,000 ₸, VAT rate for standard operations — 16%.

The reference of attached files itself does not calculate anything from the above and does not participate in accounting movements.

6. Related Objects and Input on Basis

Input on Basis. The reference does not have standard “input on basis” mechanisms. Elements are created automatically when a file is attached to the termination document (from the owner document form), not manually and not through “Create on Basis.”

7. Extension Points

• Configuration Extension. Redefinition/addition of handlers BeforeWriting, BeforeDeleting; addition of custom attributes (for example, “TypeOfHRDocument”) for classifying attachments.
• Additional Attributes and Information. Connection through the “Properties” subsystem (if available in the configuration), if it is necessary to mark files with additional indicators.
• File Subsystem Events. Interception of file addition/modification through common file handling modules for logging, automatic application of EP, or format checking.
• Full-text Search. Management of text extraction through TextExtractionStatus/TextStorage — rules for indexing HR scans can be extended.
• Storage. Configuration of policy through FileStorageType/Volume — transferring the storage of termination attachments to volumes on disk to relieve the database.

Version-specific: the specific set of common forms and modules of the file handling subsystem and the presence of the “Properties” subsystem should be verified with release 3.0.74.2.