1. Identification
| Parameter | Value |
|---|---|
| Object Type | Catalog |
| Name | GoodsMovementAttachedFiles |
| Full Path | Catalog.GoodsMovementAttachedFiles |
| Synonym | “Attached files (Goods Movement)” |
| Navigation Link | e1cib/list/Catalog.GoodsMovementAttachedFiles |
| Configuration | Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) |
| Subsystem | File Management (BSP — “Attached Files”) |
Purpose. A service (technical) catalog for storing metadata about files attached to “Goods Movement” documents: scanned invoices, photographs, electronic invoices (ESF)/SNT, accompanying documents for the movement of goods between warehouses. The catalog is created and filled automatically by the BSP's attached files mechanism and is not intended for direct manual editing by the user. Interaction with it is done through the “Attached Files” command in the “Goods Movement” document form. Each record in the catalog represents one attached file; the binary content of the file is stored separately (in the information base or on disk volumes), while the catalog itself stores the attributes.
This is an owner catalog subordinate to the owner document through the attribute
FileOwner. It is not a document, does not conduct itself, and does not generate movements in registers/accounts.
2. Attributes
2.1 Header Attributes (from evidence)
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| Author | CatalogReference.Users | Mandatory (ShowError) | The user who initially attached the file. Audit and control of authorship. |
| FileOwner | DocumentReference.GoodsMovement | Optional | Reference to the goods movement document to which the file is attached. Provides a link between the file and the accounting object. |
| UniversalModificationDate | Date (DateTime) | Optional | Universal time (UTC) of the last modification of the file. Synchronization, tracking the relevance of versions. |
| CreationDate | Date (DateTime) | Mandatory (ShowError) | Date and time of the creation of the file record. Chronology of work with the document. |
| Encrypted | Boolean | Optional | Indicates whether the file is encrypted. Manages access/decryption logic before opening. |
| ModifiedBy | CatalogReference.Users | Optional | The user who last modified the file or its properties. Audit of changes. |
| ImageIndex | Number | Optional | Index of the file icon in the image collection. Visual representation of the file type in lists/forms. |
| Description | String | Optional | User's arbitrary comment on the file. |
| SignedByEP | Boolean | Optional | Indicates the presence of an electronic signature. Important for legally significant document flow (ESF, SNT). |
| FilePath | String | Optional | Path to the file on the disk volume (for the storage mode “On disk volumes”). |
| Size | Number | Optional | Size of the file in bytes. Disk space control. |
| Extension | String | Optional | File extension (pdf, jpg, xlsx, etc.). Determines the type and program for opening. |
| EditingBy | CatalogReference.Users | Optional | The user currently editing the file (“file is in use”). Blocking against conflicts of simultaneous editing. |
2.2 Standard Attributes and Service Fields of BSP
In addition to those listed, the object uses standard fields of the BSP attached files catalog (which may be present as object attributes):
- Name (standard) — the name of the file without the extension.
- FileStorage / StorageVolume / FileStorage — method and location of storing binary content (in IB or on disk volume).
- TextStorage / ExtractedText — extracted text for full-text search.
- DeletionMark, Reference, Code — standard attributes of the catalog.
2.3 Table Parts
This catalog does not have table parts — it is a flat metadata object “one file = one record”. File versions (history of changes to binary content) when versioning is enabled are stored in a separate information register “AttachedFileVersions”, not in a table part.
3. Forms
For the service catalog of attached files, the configuration uses common (standard) BSP forms, not individual object forms:
| Form | Purpose |
|---|---|
Element Form (ElementForm / common AttachedFile) |
View and edit the file card: name, description, author, dates, signature/encryption indicators, commands “Open”, “Edit”, “Finish Editing”, “Save As…”. |
List Form (ListForm / common AttachedFiles) |
List of all files attached to the owner document. Called by the “Attached Files” command from the “Goods Movement” form. Commands for adding, viewing, editing, EP, deleting. |
| Selection Form | Service file selection (used by BSP mechanisms). |
Opening the list is also possible directly via the navigation link e1cib/list/Catalog.GoodsMovementAttachedFiles, but the standard scenario is through the document's attached files panel.
4. Key Module Procedures
There are no BSL exports by lines in the attached evidence, so below are standard handlers for this type of object (implemented in the common modules of the “FileManagement” / “ServiceFileManagement” BSP; the catalog module itself is usually minimal):
- ObjectModule → BeforeWriting — fixing service fields: filling
UniversalModificationDate,ModifiedBy, control of the mandatoryAuthorandCreationDate(ShowError). - ObjectModule → BeforeDeleting — clearing binary content in storage/volume, deleting versions and records of extracted text.
- ServiceFileManagement.AddFile / WriteFileToInformationBase — creating a catalog record when attaching a file to the “Goods Movement” document, calculating
Size,Extension,ImageIndex. - ServiceFileManagement.OccupyFileForEditing / ReleaseFile — setting/removing the
EditingByattribute (blocking against simultaneous editing). - ServiceFileManagement.AddVersion — when versioning is enabled, recording a new version of the binary content.
- EP Handlers — setting the
SignedByEPindicator, signature verification; when encrypted — settingEncrypted. - TextExtractionServer — background text extraction for full-text search.
Specific names and signatures of procedures are version-dependent (BSP edition within 3.0.74.2) — this is the only place where the content should be checked against the module of the specific delivery.
5. Posting and Movements
The catalog is not posted and does not generate movements. As a metadata object about files, it does not participate in accounting and tax accounting, does not create records in accumulation/information registers of the accounting circuit, and does not generate accounting entries.
The accounting movements are generated by the owner document “Goods Movement”, to which files are attached. For context (these are the movements of the document, not the catalog) in the RK chart of accounts, the movement of goods between warehouses/MOL is reflected as an internal turnover on the inventory account:
- Debit 1330 “Goods” (receiving warehouse) — Credit 1330 “Goods” (sending warehouse) — at the cost of the moved goods.
- Accumulation registers: “GoodsInWarehouses”, “GoodsOfOrganizations” (expense for the sending warehouse, income for the receiving warehouse).
Movement between own warehouses is an internal turnover within one account, therefore:
- income (6010), cost of sales (7010), settlements with the customer (1210) or supplier (3310) do not arise;
- VAT on internal movement is not charged (account 3130 “VAT Payable” is not involved); in the RK context, the applicable VAT rate for 2026 is 16%, which is applied in sales/income documents, not in movement.
Attached files (scans of SNT/ESF, invoices) serve only as documentary attachments to this movement and do not affect the entries.
6. Related Objects and Input Based On
- Owner Document:
Document.GoodsMovement(attributeFileOwner). Key link “file → document”. - Catalog.Users: attributes
Author,ModifiedBy,EditingBy. - Content Storage: volumes for file storage (
Catalog.FileStorageVolumes) in “On disk volumes” mode or storage in IB. - Versions: information register of versions of attached files (when versioning is enabled).
- EP: electronic signature and encryption mechanism of BSP (
SignedByEP,Encrypted).
Input Based On: for the service catalog of attached files is not provided and does not make sense — records are created exclusively by the file attachment mechanism from the “Goods Movement” document form. The file itself may, in turn, be the result of printing/exporting electronic documents (ESF from the ESF IS, SNT), attached to the document.
7. Extension Points
- Configuration Extensions: adding attributes (for example, category/type of attachment), additional commands in the common list form of attached files; overriding handlers via
&Instead/&Afterin the object module or common BSP modules. - Additional Attributes and Information (subsystem “Properties”) — if necessary, expand file classification without changing metadata.
- BSP Programming API:
FileManagement,ClientFileManagement,ServiceFileManagement— standard points for programmatically adding, retrieving, and processing files. - Event Subscriptions
BeforeWriting/BeforeDeletingof the object — for integrations (external storage, antivirus checks, logging). - Handler for filling ESF/SNT — automatic attachment of exported electronic documents to the movement.
Version-specific: the exact composition of common modules and names of export procedures of BSP depends on the version of the library within the delivery 3.0.74.2 — when developing an extension, method names should be taken from the specific configuration.