Directory "Files" (Catalogs.Files) — Technical Description

1. Identification

Purpose. The catalog stores files attached to accounting objects (documents, catalogs, registers). It provides versioning, electronic signature, encryption, and synchronization of files. Users attach scanned copies of primary documents (invoices/ESF, waybills, СНТ, contracts), images, external reports, and other files to the cards of accounting objects. Access to each file is restricted by the rights to the owner object (RLS).

Where to find in 1C:

• Direct list: e1cib/list/Catalog.Files
• Through the interface: section “Administration” → “Files”, or the “Files” command / the attached files panel in document and catalog forms.

This is a service (technical) catalog of the BSP infrastructure. It does not participate in accounting/tax accounting, does not generate entries and movements, and is not related to the chart of accounts, tax rates, or MRP/MZP. The national specifics of the RK are manifested only indirectly — through the types of attached documents (ESF, СНТ, etc.).

2. Attributes of the Header and Table Parts

2.1 Attributes of the Header

Additionally, standard attributes of the catalog are inherited: Code, Name (file name), DeletionMark, PredefinedElement. Binary data and text of the versions themselves are stored not in this catalog, but in the subordinate Catalog.FileVersions and/or the information storage register (depending on the mode — in the information base or on disk volumes).

2.2 Table Parts

The catalog does not have its own user-defined table parts. Data multiplicity (version history, access rights) is implemented through related objects, not through table parts:

• file versions — subordinate Catalog.FileVersions;
• access rights — registers of the “Access Management” subsystem (RLS by FileOwner).

3. Forms

Forms are largely standard and are managed programmatically from the common BSP modules “File Management client/server”.

4. Key Module Procedures

BSL-evidence for this object is not attached. Below are typical handlers and mechanisms characteristic of the file catalog of BSP in this configuration:

• BeforeWriting (object module) — control of filling Author and FileOwner, updating UniversalModificationDate, ModifiedBy; prohibition of modifying a file occupied by another user.
• FillingProcessing — setting Author, CreationDate, ImageIndex (by extension) when created from an external file.
• BeforeDeletion — cascading processing of subordinate versions (FileVersions) and clearing storage/data volumes.
• File operation commands (implemented in common modules FileManagement, FileManagementService, FileManagementClient):
  • “Borrow” / “Release” — setting/removing EditedBy, BorrowDate;
  • “Create new version” — recording a new FileVersions, resetting CurrentVersion;
  • “Sign EP” / “Check signature” — setting SignedEP, working with signatures through the “Electronic Signature” subsystem;
  • “Encrypt” / “Decrypt” — setting Encrypted, working with certificates;
  • “Save as…”, “Open”, “Refresh from file”.
• Text Extraction — asynchronous scheduled filling of TextStorage for full-text search.
• File Synchronization — exchange by UniversalModificationDate and FileSynchronizationAccounts.

Specific paths path:string should be indicated after unloading the object modules and common BSP modules of the corresponding version.

5. Posting and Movements

The catalog is not a posted document — it has no posting mechanism, and it does not generate accounting and accumulation registers. This object does not create any entries according to the typical chart of accounts of the RK (for example, 1210, 1030, 1330, 3310, 3130, 6010, 7010).

File data is reflected not in accounting, but in service structures:

• Catalog.FileVersions — versions and binary data (or volumes on disk);
• information registers of the “File Management” subsystem — texts for search, service data of the storage;
• registers of the “Access Management” subsystem — rights (RLS) by the attribute FileOwner.

National indicators of the RK for 2026 (for reference when working with related accounting documents, and not with this catalog): VAT rate 16 %, MRP 4,325 ₸, MZP 85,000 ₸, basic deduction for individual income tax 30 MRP/month (not more than 360 MRP/year), individual income tax 10 % up to 8,500 MRP annual income and 15 % above, OPE 10 % (ceiling base 50 MZP), OPR 3.5 %, VOSMS 2 %, OSMS 3 %, CO 5 %, social tax 6 %. These values are applied in accounting documents to which files are attached, but the catalog “Files” itself is not used.

6. Related Objects and Input on the Basis

• Catalog.FileVersions — subordinate object, stores versions and content; connection through CurrentVersion.
• Owner Object (FileOwner) — any document/catalog to which a file is attached. The most common owners in RK accounting: sales/purchase documents, invoices and ESF, СНТ, counterparty contracts, advance reports.
• Catalogs Users / ExternalUsers / FileSynchronizationAccounts — authorship, editing, synchronization.
• Subsystem “Electronic Signature” — certificates and signatures (SignedEP, Encrypted).

Input on the Basis. The classic “Input on the Basis” is not used by the catalog. Record creation occurs:

• when attaching a file to an object (uploading from disk, scanning, drag-and-drop);
• when synchronizing files between nodes/services;
• programmatically through the BSP API “File Management”.

7. Extension Points

• Common BSP modules FileManagement, FileManagementClient, FileManagementService — overridden procedures for creation, versioning, signing, encryption (extend through *Overridable).
• Configuration Extensions — adding attributes/commands to ElementForm and the attached files form without removing from support.
• Subsystem “Access Management” — configuration/improvement of RLS profiles by FileOwner for access restriction to files.
• Scheduled Tasks — text extraction (TextStorage), clearing unused versions, antivirus check.
• Synchronization — connecting external storages through FileSynchronizationAccounts.
• Integration with EDO/ESF — attaching printed forms and XML electronic documents (ESF, СНТ) to accounting documents as owner files.

Version-specific (requires verification under 3.0.74.2) is the file storage mode — in the information base or on disk volumes — and the exact composition of common modules/BSP API; this affects the method of access to binary data in modifications.