---
title: "Catalog \"File Versions\" (Catalogs.FileVersions) — Technical Description"
country: KZ
lang: en
author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti)
date: 2026-09-07
canonical: https://buhgpt.kz/suraqtar/spravochnik-versiifaylov-catalogs-versiifaylov-tehnichesk-en
source: BuhGPT
---

# Catalog "File Versions" (Catalogs.FileVersions) — Technical Description

> **TL;DR:** 1. Identification Parameter Value Object Type Catalog Name FileVersions Full Name Catalogs.FileVersions / Catalog.FileVersions Alias File versions (rarely displayed separately in the interface) Configuration Accounting for Kazakhstan, edition 3.0.74.2 Owner Subsystem Library o

---

1. Identification

Parameter
Value

Object Type
Catalog

Name
FileVersions

Full Name
Catalogs.FileVersions / Catalog.FileVersions

Alias
File versions (rarely displayed separately in the interface)

Configuration
Accounting for Kazakhstan, edition 3.0.74.2

Owner Subsystem
Library of Standard Subsystems (BSP), subsystem "File Management"

Purpose
Storing the history of changes to attached files: each edit of a file generates a new version, allowing rollback to previous versions, comparison, and authorship control

Object Characteristic. This is a service (technical) catalog of the file storage infrastructure. It is not an accounting object: it does not contain economic data, does not participate in accounting entries, is not tied to the chart of accounts, VAT, individual income tax, and other tax mechanisms of the RK. The catalog is maintained automatically by the file management subsystem and generally does not require direct user intervention.

Where to find: navigation link e1cib/list/Catalog.FileVersions. In the standard interface, access to versions is provided from the card of the attached file (button/command "Versions"), rather than through a separate menu item. Access control is inherited from the rights to the owner object of the file (document or catalog to which the file is attached).

2. Attributes and Table Parts

2.1 Header Attributes

Name
Type
Mandatory
Purpose

Author
Catalog.ExternalUsers, Catalog.FileSynchronizationAccounts, Catalog.Users (composite)
Optional
User or synchronization account that created this version of the file

UniversalModificationDate
DateTime
Optional
Date and time of the last modification of the file in universal time (UTC); used for synchronization and version comparison

FileModificationDate
DateTime
Optional
Date and time of the last modification of the file in local time; displayed to the user

CreationDate
DateTime
Optional
Date and time of the creation of this version

ImageIndex
Number
Optional
Index of the icon for visual representation of the file type in the interface

Comment
String
Optional
Text description of changes in the version; the only field available for bulk editing

VersionNumber
Number
Optional
Sequential version number (1, 2, 3…), automatically incremented when a new version is created

DeleteFullName
String
Optional
Deprecated field (prefix "Delete…"), not used in the current version

FilePath
String
Optional
Path to the file on the storage volume or identifier in the storage

Size
Number
Optional
Size of the version file in bytes

Extension
String
Optional
File extension (e.g., "docx", "pdf"); determines the type and icon

ParentVersion
Catalog.FileVersions
Optional
Reference to the previous version; forms a chain of versions

TextExtractionStatus
Enumeration.TextExtractionStatusFiles
Optional
Status of text extraction for full-text search (not extracted / extracting / extracted / error)

TextStorage
Value Storage
Optional
Extracted text of the file for full-text search

FileStorageType
Enumeration.FileStorageTypes
Optional
Method of storage (in the database or on the volume)

Volume
Catalog.FileStorageVolumes
Optional
Volume of file storage (when stored on disk)

FileStorage
Value Storage
Optional
Temporary storage of binary data of the file (when stored in the database)

Standard Attributes. In addition to those listed, the object has standard fields for the catalog: Code, Name (usually formed from the file name and version number), Owner (the owner of the version is an element of the catalog of attached files, for example Catalog.<Object>AttachedFiles), DeletionMark, Predefined, Reference.

2.2 Table Parts

The catalog does not have table parts. All information about the version is stored in the header attributes; the sequence of versions is built through the attribute ParentVersion and VersionNumber, not through table parts.

3. Forms

The catalog uses a set of BSP forms. Typically present are:

Form
Purpose

ElementForm
Version card: view attributes (author, dates, size, extension, version number, comment). Service, editing is limited to the "Comment" field

ListForm
List of versions, usually called in the context of a specific file (e1cib/list/Catalog.FileVersions); shows the chain of versions with the author and dates

SelectionForm
Selecting a specific version (e.g., for rollback or comparison)

The main user interaction with versions occurs not through the catalog's own forms, but through the managed forms of the "File Management" subsystem: the card of the attached file and the "File Versions" form, which programmatically refer to this catalog.

4. Key Module Procedures

No custom code in evidence for this object is attached, so below are typical handlers and service procedures characteristic of this service catalog of BSP. Specific names of procedures and modules are clarified according to the version of BSP supplied with 3.0.74.2 (version-specific).

- FillProcessing / BeforeWriting (object module) — filling service fields: VersionNumber, CreationDate, Author, binding ParentVersion.

- Manager Module / common module FileManagement, FileManagementService — creating a new version (CreateVersion/AddFileVersion), obtaining the current and arbitrary version, rolling back to a version, deleting outdated versions.

- Text Extraction — procedures that fill TextStorage and TextExtractionStatus for full-text search (background task for text extraction).

- Storage Management — placing binary data in FileStorage (in the database) or on Volume with recording FilePath and FileStorageType; used when transferring files between volumes and the database.

- File Synchronization — comparison by UniversalModificationDate, binding Author to Catalog.FileSynchronizationAccounts.

5. Posting and Movements

The catalog is not posted and does not generate movements. It is a document-independent service catalog:

- there is no posting mode, no PostingProcessing handler;

- does not generate accounting entries and does not affect the chart of accounts of the RK (accounts 1210, 1030, 1330, 3310, 3130, 6010, 7010, etc. are not related to it);

- does not affect accumulation/information registers of the accounting contour;

- does not participate in the calculation of VAT (RK rate 2026 — 16%), individual income tax, pension contributions, social contributions, and social tax.

The only "movements" in a broad sense are changes to the file storage data themselves: writing binary data to FileStorage/on Volume and filling the registers of the full-text search subsystem during text extraction. They do not carry accounting significance.

Note. Attached files (including versions) are often attached to accounting documents — for example, to an invoice with VAT 16%, to an electronic invoice (ESF) (ESF information system) or to a tax return form. However, the catalog "FileVersions" only stores the content and history of the file, not the tax/sum data of the owner document.

6. Related Objects and Input on Basis

- File Owner — element of the catalog of attached files of a specific object (Catalog.<Object>AttachedFiles); through it, the version is linked to the document or element of the catalog.

- Catalog.FileStorageVolumes — attribute Volume (location of physical storage on disk).

- Catalog.Users / ExternalUsers / FileSynchronizationAccounts — attribute Author.

- Catalog.FileVersions (itself) — ParentVersion, chain of versions.

- Enumeration.FileStorageTypes, Enumeration.TextExtractionStatusFiles — service enumerations.

Input on Basis. The "Input on Basis" mechanism is not applied for this catalog. New versions are created automatically when the file is changed (uploading a new edition, editing through occupying/releasing the file), not by the command "Create on Basis".

7. Extension Points

- Configuration Extension — adding attributes (e.g., document classification labels) and form handlers without removing from support; permissible for service catalogs, but requires caution during BSP updates.

- BSP Programming Interfaces — working with versions through common modules of the "File Management" subsystem (creating, obtaining, rolling back versions) instead of direct object recording; preferred method of integration.

- Volumes and Storage Rules — configuring FileStorageVolumes and version storage policies (limiting quantity/storage duration) — standard way to manage volume without changing structure.

- Full-Text Search — influence on the composition of indexed content through TextStorage/TextExtractionStatus.

Requires verification (version-specific): exact names of module procedures and composition of service enumerations may differ depending on the version of BSP within the release 3.0.74.2.

---
_BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_