1. Identification
| Parameter | Value |
|---|---|
| Object Type | Catalog |
| Name | ElectronicDocumentOutgoingEDOCAttachedFiles |
| Full Name | Catalog.ElectronicDocumentOutgoingEDOCAttachedFiles |
| Synonym | — (no synonym specified in the object card) |
| Configuration | Accounting for Kazakhstan, edition 3.0, version 3.0.74.2 |
| Introduced in Release | 3.0.73 (new service catalog of the outgoing electronic document subsystem of the RK) |
| Owner | Document.ElectronicDocumentOutgoingEDOC (via the attribute FileOwner) |
Purpose. The catalog is a file storage of the outgoing electronic document circulation subsystem of Kazakhstan. It stores metadata and content of files attached to the "Outgoing Electronic Document" documents. This includes files that the organization generates and sends to the counterparty via the "1C:EDO" service:
- XML of the outgoing electronic document;
- visualization of the document (PDF / print form);
- attached attachments;
- service files — containers for electronic signatures (
.p7s) and service XML.
The catalog is auxiliary (service): the user works with files through the outgoing EDO document form and general file handling mechanisms of the BSP, while the catalog list is rarely opened directly.
Where to find: e1cib/list/Catalog.ElectronicDocumentOutgoingEDOCAttachedFiles
2. Header Attributes and Table Parts
2.1 Header Attributes (from evidence)
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| Author | Catalog.Users | ShowError (mandatory) | The user who created/uploaded the file. Needed for auditing and access control. |
| FileOwner | Document.ElectronicDocumentOutgoingEDOC | DontCheck | Reference to the outgoing electronic document to which the file belongs. The main attribute for grouping files by document. |
| BorrowedDate | Date and time (xs:dateTime) | DontCheck | The moment when the file is "taken for editing" by the user. For monitoring the duration of editing. |
| UniversalModificationDate | Date and time (xs:dateTime) | DontCheck | Date of the last modification of the file in UTC. For synchronizing distributed databases and monitoring version relevance. |
| CreationDate | Date and time (xs:dateTime) | ShowError (mandatory) | Date of the initial creation/upload of the file. Chronology and sorting. |
| Encrypted | Boolean | DontCheck | Indicator of content encryption. If True, decryption is required before opening. |
| ModifiedBy | Catalog.Users | DontCheck | The user who last modified the file or its metadata. Audit of changes. |
| ImageIndex | Number | DontCheck | Index of the file icon in the platform's image collection (by type/extension). Visual representation in lists. |
| Description | String | DontCheck | Arbitrary description/comment for the file. Displayed in lists, participates in searches. |
| SignedByES | Boolean | DontCheck | Indicator of the presence of a valid electronic signature for the file. Important for the legal significance of the outgoing document. |
| FilePath | String | DontCheck | Path to the file on the disk when stored in volumes. Used together with the attribute Volume. |
| Size | Number | DontCheck | Size of the file in bytes. Control of storage volume and limits. |
| Extension | String | DontCheck | File extension (xml, pdf, p7s, jpg…). Determines the method of opening and processing. |
| EditingUser | Catalog.Users | DontCheck | The user who has taken the file for editing (blocking from simultaneous modification). |
| HashSum | String | DontCheck | Hash of the file content. Control of integrity and detection of duplicates. |
| FullFileName | String | DontCheck | Full name of the file with extension. |
| OriginalFile | Boolean | DontCheck | Indicator that the file is the original document (not a service/derivative copy). |
| ServiceFile | Boolean | DontCheck | Indicator of a service file (container for electronic signatures, service XML) — such files are hidden from the user in regular lists. |
| Volume | Catalog.FileStorageVolumes | DontCheck | Volume of storage when using file (in volumes) storage method. |
Standard attributes of the catalog: Code and Name (the name usually matches the file name), Owner — at the metadata level, DeletionMark.
2.2 Table Parts
For this type of service file storage catalog, custom table parts are generally absent. File versions and their binary content are stored not in a table part, but:
- in the value storage (attribute with binary data) — when stored "in the information base";
- or in the file storage volumes (
FilePath+Volume) — when stored "in volumes on disk".
Requires verification in the specific build 3.0.74.2: presence of the binary data storage attribute and subordinate version catalog — the composition depends on whether file versioning is implemented for this catalog.
3. Forms
| Form | Purpose |
|---|---|
| ElementForm | File card: viewing/editing metadata (description, author, dates, signature/encryption indicators). Opening and saving file content. |
| ListForm | List of files; in practice, it is used by filtering by FileOwner, embedded in the outgoing EDO document form as a list of attached files. |
| SelectForm | Selecting a file from the list when substituting into other objects/forms. |
The user does not directly open these forms in the standard scenario — work is done through the "Outgoing Electronic Document" form and general file handling forms of the BSP ("Attached Files").
4. Key Module Procedures
No separate application BSL code in evidence for this catalog is provided. For the service catalog of attached files, a standard set of handlers applies (integration with the "File Handling" subsystem of the BSP):
Object Module:
BeforeWriting(Refusal)— updatingUniversalModificationDate,ModifiedBy, recalculation/check ofHashSumandSize.OnCopying(CopyingObject)— resetting lock indicators (EditingUser,BorrowedDate) when copying an element.FillingProcessing(FillingData, ...)— settingAuthor,CreationDatefrom the current user and session.
Manager Module:
- Functions for obtaining/saving binary content of the file (working with value storage or volumes).
FormRetrievalProcessing— substituting forms if necessary.
Element Form Module:
OnOpening/OnCreatingOnServer— configuring field availability based on indicatorsEncrypted,SignedByES,ServiceFile,EditingUser.- Commands "Open", "Save As", "Finish Editing", "Check Signature" — redirecting to general file handling and cryptography modules.
Requires verification: exact names of procedures and presence of overriding handlers are specific to build 3.0.74.2 (a review of the configurator/export is needed).
5. Posting and Movements
The object is a catalog, therefore it does not perform postings and movements in registers and does not generate accounting entries. It only stores files attached to the outgoing EDO document.
Accounting consequences arise from the source document to which the outgoing electronic document is attached (sales, payment, etc.). Typical entries of these documents according to the chart of accounts of the RK (Kazakhstan, 2026), for reference:
- Sale of goods (with outgoing ESF/SNT):
- Dr 1210 "Short-term receivables from buyers" — Cr 6010 "Revenue from sales" — for the amount of revenue;
- Dr 1210 — Cr 3130 "VAT payable" — VAT at the rate of 16% (RK rate 2026);
- Dr 7010 "Cost of sales" — Cr 1330 "Goods" — write-off of cost.
- Receipt of money from the buyer: Dr 1030 "Money in current accounts" — Cr 1210.
- Settlements with the supplier (incoming direction, for comparison): Cr 3310 "Payables to suppliers".
Example of VAT calculation for the ESF line: with a product cost of 1,000,000 ₸, the VAT amount = 1,000,000 × 16% = 160,000 ₸, total payable 1,160,000 ₸.
The catalog itself interacts not with accounting registers, but with the file storage mechanism (value storage / file storage volumes) and with the registration journal during audit changes.
6. Related Objects and Input Based on
Owner / source of files:
Document.ElectronicDocumentOutgoingEDOC— outgoing electronic document (attributeFileOwner).
Reference objects in attributes:
Catalog.Users—Author,ModifiedBy,EditingUser;Catalog.FileStorageVolumes—Volume.
Adjacent subsystems:
- "1C:EDO" — generation and sending of XML of the outgoing document, receipt of receipts;
- IS ESF (electronic invoices) and SNT (accompanying invoices for goods) — sources of outgoing EDO RK;
- BSP subsystem "File Handling", "Electronic Signatures and Encryption".
Input based on: not applicable. The catalog is not a source/receiver for input based on; elements are created programmatically when attaching a file to the EDO document, not manually "based on".
7. Extension Points
- Event subscriptions
BeforeWriting/OnWritingof the catalog — for additional validation of files (checkingHashSum, limitsSize, mandatorySignedByESfor originals). - Configuration extension: adding attributes (for example, file classification tag), overriding element/list forms, adding commands without removing from support.
- Overridable general BSP modules for file handling and cryptography — points for customizing scenarios for opening/saving/checking signatures.
- Roles and RLS: restricting access to files by
Authorand by document owner (organization, counterparty of the source document). - Data exchange:
UniversalModificationDate— a reference attribute for correct synchronization of files in RIB/exchanges.
General rule: it is preferable to extend behavior through event subscriptions and configuration extensions, without removing the standard object from support, to maintain release updatability.
