1. Identification
| Parameter | Value |
|---|---|
| Type of metadata | Catalog |
| Name | WriteOffGoodsAttachedFiles |
| Full name | Catalog.WriteOffGoodsAttachedFiles |
| Synonym | “Attached files (Write-offs of inventory)” |
| Configuration | Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) |
| File owner | Document “Write-off of goods” (Document.WriteOffGoods) |
| Role in the system | Service (technological) catalog of the “File Management” subsystem |
Purpose. The catalog is a service storage for files attached to the “Write-off of goods” documents. It implements the subsystem of attached files in the BSL: it allows attaching scans of invoices, write-off acts, product photos, memos, and other supporting documents to inventory write-offs. Records are created automatically through the “File Management” mechanism (the “Attach file” command in the write-off document form), rather than being entered manually by the user. The catalog ensures versioning of files, electronic signature, encryption, and access control at the authorship level. It is not displayed in the main menu/section panel — access is through the attached files panel in the owner document form.
Where to find (for service opening of the list):
e1cib/list/Catalog.WriteOffGoodsAttachedFilesIn regular work, the list is not accessed directly, but through the hyperlink “Attached files” in the “Write-off of goods” document form.
2. Attributes of header and table parts
The catalog of table parts of applied purpose does not contain (except for the standard table part of versions/signatures, hidden in the interface). The main information is in the header attributes.
2.1 Header attributes
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| Author | CatalogReference.Users | Mandatory (ShowError) | The user who attached the file. Used for access control and file history. |
| FileOwner | DocumentReference.WriteOffGoods | Not mandatory | Reference to the write-off document to which the file is attached. The main attribute for linking to the owner. |
| UniversalModificationDate | Date (dateTime) | Not mandatory | Date and time of the last modification of the file in UTC. Used for synchronization and version comparison. |
| CreationDate | Date (dateTime) | Mandatory (ShowError) | The moment the file was attached to the system. Records the upload. |
| Encrypted | Boolean | Not mandatory | Indicates whether the file is encrypted with a certificate. If True, the content requires decryption for viewing. |
| ModifiedBy | CatalogReference.Users | Not mandatory | The user who last modified the file or its description. For auditing. |
| ImageIndex | Number | Not mandatory | Index of the file icon in the image collection for lists. Depends on the extension. |
| Description | String | Not mandatory | Text description of the file entered by the user (name in the file list). |
| SignedEP | Boolean | Not mandatory | Indicates the presence of an electronic signature (True if signed by at least one certificate). |
| FilePath | String | Not mandatory | Physical path to the file on the storage volume (when stored on server disks). Empty when stored in the IB. |
| Size | Number | Not mandatory | Size of the file in bytes. For quota control and user display. |
| Extension | String | Not mandatory | File extension without a dot (pdf, xlsx, jpg). Determines the type and opening program. |
| EditingUser | CatalogReference.Users | Not mandatory | The user who has locked the file for editing. Prevents simultaneous editing. |
| TextExtractionStatus | EnumerationReference.TextExtractionStatuses | Not mandatory | Status of text extraction for full-text search (not extracted / extracted / error). |
2.2 Standard attributes and storage
- Code — service code of the catalog item (usually not shown to the user).
- Name — usually synchronized with the “Description” attribute; filled with the file name without the extension.
- Stored file / version data — binary data of the file is stored either in the value storage attribute (
ValueStorage) when stored in the IB, or on the volume (thenFilePathis filled). Versions, signatures, and encryption certificates are stored in related BSL mechanisms (see section 6).
3. Forms
The set of forms is typical for attached files in BSL:
| Form | Purpose |
|---|---|
| ElementForm | File card: description, author, date, size, signature/encryption indicators; commands “Open”, “Edit”, “Save as”, “Sign EP”, “Encrypt”, work with versions. |
| ListForm | List of all attached files of the catalog (service, called by navigation link). Not intended for everyday use. |
| SelectForm | Selecting a file from the list in subsystem dialogs. |
In the form of the document “Write-off of goods”, files are displayed not as a separate form of this catalog, but through the common managed form of the “File Management” subsystem (panel/field of attached files), which works with this catalog as a storage.
4. Key procedures of modules
The applied BSL code in evidence is not attached — below are listed typical handlers that the BSL forms for attached files (the “File Management” subsystem). Specific procedure bodies are version-dependent.
Object module (ObjectModule):
BeforeWriting(Refusal)— control of filling mandatory attributes (Author,CreationDate), updatingUniversalModificationDate, checking editing lock (EditingUser).OnCopying(CopyingObject)— clearing signature/encryption indicators and service fields during file copying.BeforeDeletion(Refusal)— deletion of version data/binary data from the volume when the file is stored outside the IB.
Catalog manager / common modules of the subsystem:
ProcessGettingViewFields/ forming a view — output of the file name with extension and icon byImageIndex.- Service calls
FileManagement/FileManagementService— attaching a file, creating and retrieving versions, locking/releasing for editing, signing EP, encrypting, extracting text for full-text search (updatingTextExtractionStatus). - Access control handlers — checking rights by
Authorand by rights on the owner documentWriteOffGoods.
Requires verification (version-specific): the exact composition of common modules and procedure names depends on the version of BSL embedded in 3.0.74.2.
5. Posting and movements
The catalog is not posted and does not generate movements in registers — it is an object of the type “Catalog”, it has no posting mechanism. It only stores files. It does not create any accounting entries or records in accumulation/summary registers by itself.
Accounting movements are generated by the owner document “Write-off of goods”. For context, below is its standard logic according to the typical chart of accounts of the RK (numbers/rates — Kazakhstan, 2026):
Registers:
- Accumulation register “Goods in warehouses” (
GoodsInWarehouses) — expense of the written-off nomenclature. - Accounting register “Economic calculation” — write-off entries.
- Registers of batch accounting / cost — for calculating the write-off amount.
Typical write-off entries for inventory:
| Dr | Cr | Content |
|---|---|---|
| 7010 “Cost of goods sold and services rendered” (or expense account/losses due to write-off) | 1330 “Goods” | Write-off of the cost of goods from accounting |
When writing off for reasons unrelated to sales (damage, loss, defects), the corresponding expense account/other expenses according to the accounting policy is used as the debit; account 1330 on the credit remains the account for goods accounting.
VAT on write-off (RK, rate 16%). If previously accepted VAT on the written-off goods is subject to adjustment (for example, write-off exceeding the norms of natural loss), VAT recovery from the offset is performed; the calculation is made at the current rate of 16% and, if necessary, is formalized in the VAT accounting subsystem with the formation of corresponding electronic documents (ESF in the ESF IS; during the movement of goods — SNT). The currency of accounting is tenge (₸).
Other related accounts of the RK (for reference): 1210 (short-term receivables from buyers), 1030 (money in current accounts), 3310 (payables to suppliers), 3130 (VAT payable), 6010 (income from sales).
6. Related objects and input based on
- Document.WriteOffGoods — owner of the files (attribute
FileOwner). The catalog exists only as an attachment to this document. - Catalog.Users — attributes
Author,ModifiedBy,EditingUser. - Enumeration.TextExtractionStatuses — status of text extraction for full-text search.
- Subsystem “File Management” (BSL) — common modules, forms, and mechanisms: file versions, electronic signature, encryption, storage volumes, text extraction.
- Information registers of versions and signatures of BSL — storage of version history, EP, and encryption certificates.
Input based on for the service catalog of attached files is not provided: records are created exclusively through the file attachment mechanism from the owner document form, not by the “Create based on” command.
7. Extension points
- Configuration extensions: adding attributes/event subscriptions to the catalog; overriding handlers
BeforeWriting/BeforeDeletionfor additional control (for example, mandatory description or restriction of extensions). - Common modules of the “File Management” subsystem — programming interfaces for attaching, retrieving, and versioning files; use documented export methods, not direct writing to the catalog.
- Access restriction (RLS): setting rights on files through access group profiles and rights on the owner document
WriteOffGoods; the fieldAuthoris the basis for personal restriction. - Additional attributes/information — generally not applicable to service catalogs of files; expand the composition through extension attributes when there is a real need.
- Exchange/synchronization: consider
UniversalModificationDateand storage mode (IB or volume) when setting up exchange rules to correctly transfer binary data of files.
Requires verification (version-specific): the availability of specific extension points (event subscriptions, export procedures) in the BSL supplied with release 3.0.74.2.