1. Identification
| Parameter | Value |
|---|---|
| Object Type | Catalog |
| Name | SupplierInvoiceAttachedFiles |
| Full Name | Catalog.SupplierInvoiceAttachedFiles |
| Synonym | “Attached files (Supplier invoices)” |
| Configuration | Accounting for Kazakhstan, ed. 3.0 (version 3.0.74.2) |
| File Owner | Document.SupplierInvoice |
Purpose. The catalog stores files attached to “Supplier Invoice” documents (scanned copies of invoices, PDFs, images, contracts). It is one of the standard objects of the BSP subsystem “File Management” (FileManagement), implementing the “Attached Files” pattern for a specific document owner. The user interacts with it indirectly — through the “Attached Files,” “Attach File,” “Open” commands in the document owner form. In the command interface of the sections, the catalog is not displayed directly; a service list is available to the developer via a navigation link.
Where to find (for development/debugging):
e1cib/list/Catalog.SupplierInvoiceAttachedFiles
2. Attributes and Table Parts
2.1 Header Attributes (from evidence)
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| Author | CatalogReference.Users | Mandatory (ShowError) | User who first uploaded the file. Audit and rights segregation |
| FileOwner | DocumentReference.SupplierInvoice | Optional | Reference to the document owner. The main attribute linking the file to the business object |
| UniversalModificationDate | Date and time | Optional | Date/time of the last modification of the file (UTC). Synchronization and tracking changes |
| CreationDate | Date and time | Mandatory (ShowError) | Date/time of the initial file upload. Document flow chronology |
| Encrypted | Boolean | Optional | Indicates whether the file is encrypted with certificates. Working with confidential documents |
| ModifiedBy | CatalogReference.Users | Optional | Last user who modified the file/its properties. Audit of changes |
| ImageIndex | Number | Optional | Index of the icon for display in the interface by extension. Technical UI field |
| Description | String | Optional | Text description of the file provided by the user |
| SignedByEP | Boolean | Optional | Indicates the presence of an electronic signature. Legally significant document flow |
| FilePath | String | Optional | Path when stored on the volume (in the file system). Filled when the storage type is “On disk volume” |
| Size | Number | Optional | Size of the file in bytes. Control of volume and upload limits |
| Extension | String | Optional | File extension (pdf, jpg, docx…). Icon and available operations |
| EditingUser | CatalogReference.Users | Optional | User who has taken the file for editing (“locked”) |
| TextExtractionStatus | Enumeration.TextExtractionStatus | Optional | Status of text extraction for full-text search (not extracted / extracting / extracted / error) |
Standard attributes of the file management subsystem (present in objects of this type, complementing the list above): StorageVolume (CatalogReference.FileStorageVolumes), DisallowEditing/DisallowFileModification, FileHashSum, TextStorage/FullText (extracted text for search), as well as standard attributes Name, Code, DeletionMark, Predefined.
2.2 Storage (attributes-StorageValues)
| Attribute | Purpose |
|---|---|
FileStorage / FileStorage |
Binary data of the file when stored in the IB (storage type “In the information base”). Empty when stored on the volume — then FilePath + StorageVolume is used |
2.3 Table Parts
The object does not have its own table parts — it is a flat catalog-storage. Multiplicity is ensured by the fact that multiple catalog items relate to one FileOwner (many files for one invoice).
3. Forms
| Form | Purpose |
|---|---|
ElementForm (FileForm) |
Card of the attached file: description, author, dates, size, EP/encryption indicators, commands “Open,” “Save As,” “Edit,” “Finish Editing,” “Sign EP,” “Encrypt” |
| ListForm | Service list of all files in the catalog (for administration/debugging; available via navigation link) |
| SelectForm | Selecting a file from the attached ones (used in auxiliary scenarios) |
The main user scenario does not go through the catalog's own forms but through the common BSP form AttachedFiles (list of files of the document owner), opened by the “Attached Files” command in the Document.SupplierInvoice form.
4. Key Module Procedures
The specific application code of evidence does not contain module-specific logic — the logic is standard and inherited from the BSP subsystem “File Management.” Characteristic handlers of objects of this type:
Object Module:
OnWrite/BeforeWrite— recording the author of the first upload, updatingModifiedBy,UniversalModificationDate, recalculatingSize,Extension,ImageIndex.BeforeDeletion— clearing data on the storage volume (deleting the physical file when the storage type is “On disk volume”).CheckFillingProcessing— control of mandatoryAuthorandCreationDate(ShowError mode).
Common BSP modules servicing the object (called instead of code in the catalog itself):
FileManagement/FileManagementService— adding, opening, saving, locking/unlocking for editing.FileManagementInWorkingDirectory— unloading to a temporary/working directory for viewing and editing.UpdateIndexInSearch/ text extraction — fillingTextExtractionStatusand full-text index.ElectronicSignature— processingSignedByEP,Encrypted(signing/encryption with certificates).
Requires verification (version-specific): the exact composition of internal procedures and names of common modules depend on the version of the built-in BSP in 3.0.74.2.
5. Posting and Movements
The object is a catalog, therefore it is not posted and does not generate movements in accumulation/summary registers and accounting entries. The file itself does not create business transactions or impact accounting for VAT/taxes.
Accounting movements are generated by the document owner SupplierInvoice, to which the file is attached (the invoice in the RK is generally a document of managerial/operational purpose, movements are generated by the receipt and payment documents). For reference — standard accounts of the RK Chart of Accounts involved in the chain “invoice → receipt → payment to supplier”:
| Account | Name |
|---|---|
| 3310 | Short-term payables to suppliers and contractors |
| 1330 | Goods |
| 1030 | Cash on current bank accounts |
| 1210 | Short-term receivables from customers |
| 3130 | VAT payable (RK VAT rate 2026 — 16%) |
| 6010 | Revenue from sales |
| 7010 | Cost of sales |
Electronic document flow in the chain (ESF in IS ESF, SNT) is also conducted at the level of document owners and primary documents, not at the level of the attached file.
6. Related Objects and Input on Basis
- Owner:
Document.SupplierInvoice— the only document owner of the files in this catalog. - Users:
Catalog.Users— attributesAuthor,ModifiedBy,EditingUser. - Storage Volumes:
Catalog.FileStorageVolumes— when the storage type is “On disk volume.” - Enumeration:
Enumeration.TextExtractionStatus. - Subsystem: BSP “File Management” (common forms, commands, service data registers).
Input on basis is not applicable for this object — elements are created exclusively through the file attachment mechanism from the document owner form, not through “Create on basis” commands.
7. Extension Points
- Configuration Extension: adding attributes (for example, category/type of attachment, storage period) and overriding handlers
OnWrite/BeforeDeletionthrough annotations&Instead/&After. - Programmatic File Attachment: API of the
FileManagementsubsystem (AddFile, working withFileStorage/ volumes) — for uploading scanned copies of invoices from external sources (email, exchange, integrations). - Full-text Search: subscription to text extraction and filling
TextExtractionStatus— for searching the content of invoices. - EDO and EDS: handlers of the “Electronic Signature” subsystem (
SignedByEP,Encrypted) — for legally significant storage of invoices and linking with ESF/SNT. - Access Rights: segregation through RLS by
Author/FileOwnerand roles for file management. - Storage Regulation: processing of the storage volume, transfer “IB ↔ volume,” clearing outdated attachments.