Directory "History of Audits and Data Adjustments Attached Files" (Accounting for Kazakhstan 3.0.74.2)

1. Identification

Purpose. Technical catalog for storing files attached to records of the catalog “DataVerificationAndCorrectionHistory” (scans, PDF reports, exports, audit documents for corrections). The object implements the standard mechanism of the “File Management” subsystem: storage of metadata, versioning, file locking during editing (the “occupation” mechanism), electronic signature, and encryption. The user interacts with it indirectly — through the “Attached Files” command in the owner’s card; it is not presented in the main menu of the catalog.

Where to find in 1C: section “Service Technology” → “Attached Files (Data Verification and Correction History)”. Navigation link: e1cib/list/Catalog.DataVerificationAndCorrectionHistoryAttachedFiles

Note. The catalog is infrastructural (file storage) and does not participate in tax/accounting — it does not generate entries and does not operate with amounts. VAT rate 16%, MRP 4,325 ₸, MSP 85,000 ₸, chart of accounts of the RK (1210/1030/1330/3310/3130/6010/7010) and electronic documents (ESF, CNT) are not involved in this object; they are provided as context of the configuration for related objects.

2. Header Attributes and Table Parts

2.1 Header Attributes

Additionally, the standard object of attached files typically includes attributes TextStorage (extracted text for full-text search), FileStorageVolume (reference to the volume when stored in volumes) and the attribute FileStorage/TextExtractionStatus — the set depends on the file storage mode in the specific database.

2.2 Table Parts

Table parts are absent. The content of the file itself is stored:

• in the value storage of the object attribute (when stored “in the information base”), or
• in the volume of the file system (attributes FilePath / FileStorageVolume).

File versions and electronic signature data are stored in separate service objects of the subsystem (information register with versions/signatures), not in the table parts of the catalog itself.

3. Forms

Service catalogs of attached files typically do not contain their own forms — work is conducted through the common forms of the “File Management” subsystem. Standard set:

Specialized dialogs (adding a file, viewing versions, signing/verifying EP, encryption/decryption) are provided by the common BSP forms CommonForm.AttachedFiles, CommonForm.FileVersions, CommonForm.ElectronicSignatureForm.

4. Key Procedures of Modules

No separate application evidence for the object modules is attached. For the catalog of attached files, a standard set of handlers of the “File Management” subsystem applies:

• ObjectModule → BeforeWriting — control of mandatory attributes filling (Author, CreationDate), recording UniversalModificationDate, updating the attribute ModifiedBy.
• ObjectModule → BeforeDeleting — clearing related versions/signatures and freeing space in the storage volume.
• Content Management is not conducted in the object module, but through the server APIs of BSP:
  • FileManagement.AddFile(...) / AttachedFiles.AddFile(...) — creating an element and recording content;
  • FileManagementService — occupying/releasing a file (LoanDate, EditingUser), recording versions;
  • ElectronicSignature/Encryption — setting attributes SignedEP, Encrypted.
• Catalog Manager — procedures for forming representation and selecting an icon (ImageIndex) by file extension.

Requires verification (version-specific): exact names and signatures of BSP procedures may differ within the release 3.0.74.x — check against the common modules FileManagementService, AttachedFilesService of the specific database.

5. Posting and Movements

The catalog is not posted and does not generate movements in the accounting/accumulation/information registers in terms of accounting. This is a reference (infrastructural) object.

• Entries according to the chart of accounts of the RK (1210, 1030, 1330, 3310, 3130, 6010, 7010) are not generated.
• Records in tax registers (VAT 16%, PIT, UAPF, etc.) are not created.
• The only “movements” are service records in the information registers of the “File Management” subsystem (file versions, electronic signatures, encryption indicators), performed by BSP mechanisms, not by the document posting logic.

6. Related Objects and Input Based On

Input Based On is not provided for this catalog: elements are created exclusively by the file attachment command from the owner’s card (DataVerificationAndCorrectionHistory), not by the “Input Based On” mechanism.

7. Extension Points

• Configuration Extension: overriding common forms AttachedFiles / ElementForm, adding attributes/commands in the file card.
• Event Subscriptions BeforeWriting / OnWriting of the object — for additional control (e.g., limiting extensions or size of attached files).
• BSP Program Interfaces: FileManagement, AttachedFiles, ElectronicSignature — standard points for adding/reading files, working with versions and signatures from custom code.
• Additional Attributes/Information through the “Properties” subsystem (if enabled) — extending file metadata without changing the structure of the catalog.
• Storage Settings — switching “in database / in volumes” and rules for text extraction for full-text search.