Directory "ETDAttachedFiles" — Technical Description

1. Identification

The catalog is a standard object of the BSP mechanism “File Management” (ServiceFiles, FileStorage), allocated for the ETD subsystem. Access is strictly inherited: the user sees and edits only those files to which they have rights for the owning document (Document.ETD).

Where to find in 1C:

• Interface: section “HR Accounting” → “Attached Files (ETD)”.
• Navigation link: e1cib/list/Catalog.ETDAttachedFiles

2. Attributes and Table Parts

2.1 Header Attributes

In addition to the listed attributes, the standard BSP object usually contains service attributes DeletionMark, Code, Name (corresponds to “Description”), and when stored in the information base — an attribute with file data (ValueStorage) or a reference to the register BinaryFileData. The exact composition of the binary data storage is version-specific — please clarify with the configurator 3.0.74.2.

2.2 Table Parts

For the catalog of attached files, BSP table parts are generally not used — the storage of content and versions is allocated to separate information registers (FileVersions/BinaryFileData). If table parts are present in a specific build, they are service-related and are not filled in the application logic.

3. Forms

Some visual forms for working with files are provided by the common BSP forms (for example, CommonForm.AttachedFiles, “Attached Files” on the ETD document owner form). Custom forms of the catalog may be absent and replaced by common ones — this is normal for this type of object.

4. Key Module Procedures

No application BSL code is attached in evidence, so below are the typical handlers for this type of object (BSP mechanism “File Management”). Specific paths module:string should be verified with the configurator.

Object Module (BeforeWriting, BeforeDeletion):

• BeforeWriting — control of mandatory attributes (Author, CreationDate, FileStorageType), updating UniversalModificationDate, ModifiedBy.
• BeforeDeletion — deletion of related versions and binary data, freeing space on the volume (when FileStorageType = OnVolume).

Manager Module / Common BSP Modules:

• FileManagement, ServiceFileManagement — adding a file (AddFile), retrieving (GetFile), updating from a file, working with versions.
• ServiceFileServerCall — server operations for reading/writing binary data, text extraction for full-text search (filling TextStorage, TextExtractionStatus).
• ServiceElectronicSignature / UserSupportFileManagement — signing/verifying ES, setting the flag SignedByES.
• File “loan” mechanism: setting/removing EditingBy — blocking simultaneous editing.

Form Modules:

• ElementForm.OnOpen/OnCreateOnServer — filling attributes from file data, configuring command availability based on rights and indicators (Encrypted, SignedByES).
• Commands Open, Edit, FinishEditing, SignWithES, Encrypt — calls to corresponding BSP procedures.

5. Posting and Movements

The catalog is not posted and does not generate accounting movements. It is a file storage object, not an accounting document — it has no table part of postings and does not participate in period closing.

Business operations (sales, receipts, payroll, and taxes) are generated by documents to which files can be attached. For reference — standard posting logic of related accounting documents in the configuration “Accounting for Kazakhstan” with RK parameters for 2026:

• Sale of goods:
  • Dr 1210 “Short-term Accounts Receivable” — Cr 6010 “Revenue from Sales” (cost excluding VAT);
  • Dr 1210 — Cr 3130 “VAT Payable” (VAT at 16 %);
  • Dr 7010 “Cost of Sales” — Cr 1330 “Goods”.
• Receipt of goods: Dr 1330 — Cr 3310 “Accounts Payable to Suppliers”; VAT to be credited — to the corresponding sub-account with Cr 3310.
• Payment: Dr 3310 — Cr 1030 “Cash in Current Accounts” / Dr 1030 — Cr 1210.

Electronic documents (ESF via IS ESF, CNT) are generated based on accounting documents, and scans/copies of accompanying documents can be stored in the attached files subsystem.

Current RK parameters for 2026 (for accounting documents, not for this catalog): VAT 16 %; MRP 4,325 ₸; MSP 85,000 ₸; basic deduction for PIT 30 MRP/month (not more than 360 MRP/year); PIT 10 % up to 8,500 MRP annual income and 15 % above; OPE 10 % (base ceiling 50 MSP); OPEA 3.5 %; VOSMS 2 %; OSMS 3 %; SO 5 %; social tax 6 %.

6. Related Objects and Input on Basis

• Document.ETD — file owner (FileOwner); source of access rights. Files are attached from the ETD document form.
• Catalog.FileSynchronizationAccounts, Catalog.Users — types of attributes Author, ModifiedBy, EditingBy.
• Enumeration.FileStorageTypes — defines the storage location (in IB / on volume).
• Enumeration.TextExtractionStatuses — status of content indexing.
• Catalog.FileStorageVolumes — when FileStorageType = OnVolume, content is stored on the volume, path is in FilePath.
• BSP version/binary data registers (FileVersions, BinaryFileData) — storage of content and version history.

Input on basis: files are created by adding to the owning document (drag-and-drop, “Add → From File / From Scanner”), not through “Input on Basis”. The catalog does not serve as an independent basis for other objects.

7. Extension Points

• Configuration Extension: adding attributes to the catalog (for example, document category, storage period), adding columns/commands to the common form of attached files through form borrowing.
• Event Subscriptions: BeforeWriting/BeforeDeletion of the object for custom validation (checking the mandatory nature of ES for certain types of ETD documents) and logging.
• BSP Programming Interfaces: FileManagement, ClientFileManagement, ServiceFileServerCall — for programmatic addition/retrieval of files and versions.
• Access Rights Mechanism (RLS): record-level restrictions are inherited from Document.ETD; customization — through access restriction templates of the ETD subsystem.
• Electronic Signature: integration with cryptographic providers through the “Electronic Signature” BSP subsystem; handlers for verification/overlay of ES.
• Full-text Search: overriding text extraction (TextExtractionStatus, TextStorage) for non-standard formats.