--- title: "Guide \"Outgoing Payment Order Attached Files\" — Technical Description" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-07 canonical: https://buhgpt.kz/suraqtar/spravochnik-platezhnoeporuchenieishodyashcheeprisoedinenn-en source: BuhGPT --- # Guide "Outgoing Payment Order Attached Files" — Technical Description > **TL;DR:** 1. Identification Parameter Value Object Type Catalog Name OutgoingPaymentOrderAttachedFiles Full Name Catalog.OutgoingPaymentOrderAttachedFiles Synonym Attached Files (Outgoing Payment Orders) Configuration Accounting for Kazakhstan, edition 3.0 (3.0.74.2) File Owner Document --- 1. Identification Parameter Value Object Type Catalog Name OutgoingPaymentOrderAttachedFiles Full Name Catalog.OutgoingPaymentOrderAttachedFiles Synonym Attached Files (Outgoing Payment Orders) Configuration Accounting for Kazakhstan, edition 3.0 (3.0.74.2) File Owner Document.OutgoingPaymentOrder Navigation Link e1cib/list/Catalog.OutgoingPaymentOrderAttachedFiles Purpose. This service catalog is a specialized storage for files attached to the "Outgoing Payment Order" documents. It allows attaching scans of payment orders, bank statements, correspondence with the bank, contracts, and other accompanying materials to the payment document, forming an electronic archive of payment documentation. The catalog is part of the standard subsystem "File Management" (BSP) and is automatically created by the attached file constructor for the owner document. The user does not work directly with the list of items — access to the files is provided from the "Outgoing Payment Order" document form via the "Attached Files" command/hyperlink on the navigation panel of the form. Feature of the RK: the attribute SignedByEP and the associated digital signature mechanism are important for legally significant document flow — bank payment documents are often certified with an electronic signature (including when exchanged with the bank via "Client-Bank" / DirectBank). 2. Header Attributes and Table Parts The catalog does not have a hierarchy and does not contain table parts (except for the service table part for storing digital signatures, added by the platform/BSP file mechanism). The main content — binary data of the file — is stored not in the catalog attribute, but in the information register of the storage (see section 5). 2.1 Header Attributes Name Type Mandatory Purpose Author CatalogReference.Users Mandatory (ShowError) The user who initially attached the file to the payment order. Audit and control of authorship FileOwner DocumentReference.OutgoingPaymentOrder Optional The owner document to which the file is attached. Ensures the connection of the file with a specific payment order UniversalModificationDate Date (DateTime) Optional Date/time of the last modification of the file in UTC. Synchronization and version control CreationDate Date (DateTime) Mandatory (ShowError) The moment of creation of the file record in the system. Chronology of document flow Encrypted Boolean Optional Indicates that the content of the file is encrypted (mechanism for protecting confidential data) ModifiedBy CatalogReference.Users Optional The last user who modified the file or its attributes. Audit of changes ImageIndex Number Optional Index of the file type icon for display in the interface (PDF, Word, Excel, etc.) Description String Optional User comment/description of the file content SignedByEP Boolean Optional Indicates the presence of an electronic signature on the file. Critical for electronic document flow in the RK FilePath String Optional Path to the file in the file system (when stored "In the disk volume") Size Number Optional Size of the file in bytes. Control of volume and upload limits Extension String Optional File extension without a dot (pdf, doc, jpg…). Determines the file type and application for opening EditingUser CatalogReference.Users Optional The user currently editing the file (mechanism for conflict blocking) Standard naming code. The "Name" field (Name) stores the name of the file without the extension — it is used as the representation of the item. 2.2 Service Table Part Table Part Purpose ElectronicSignatures (added by the BSP mechanism) Stores an array of electronic signatures of the file: certificate, signing date, comment. Used when SignedByEP = True 3. Forms Form Type Purpose ElementForm Element form View and edit the attached file card: description, author, date, signature/encryption indicators, commands for opening, saving, signing, and editing the file ListForm List form Service list of all attached files of the document. Opens from the "Outgoing Payment Order" form; supports adding, viewing, and comparing versions SelectForm Select form Select an existing attached file in dialogs (for example, when inserting a link) In the standard BSP, the forms for attached files are usually inherited from the common forms of the "File Management" subsystem (CommonForm.AttachedFiles, CommonForm.AttachedFileForm). The presence of custom overridden forms for a specific object is version-specific and requires verification in a specific delivery. 4. Key Module Procedures The object module of such a catalog usually contains almost no direct application code — all logic is moved to the common modules of the "File Management" BSP subsystem. In evidence, the original BSL for this object is not attached, so below are the typical handlers/call points of this type of object. - ObjectModule.BeforeWrite — control of filling mandatory attributes Author, CreationDate; if absent — raises an exception (ShowError behavior). - ManagerModule / common module FileManagement — procedures for creating an item when attaching a file: AddFile, writing binary data to storage, setting Size, Extension, ImageIndex. - FileManagementService.UpdateFileVersion — updating the file and attributes UniversalModificationDate, ModifiedBy when editing. - FileManagementServerCall / FileFunctionsServiceClient — opening, saving, locking (EditingUser) and unlocking the file. - ElectronicSignatureManagement.SignFile — applying a digital signature, filling the signatures table part and setting SignedByEP = True; similarly, encryption sets Encrypted. - List form handler OnCreateOnServer — setting the filter by FileOwner to show files only for the current payment order. 5. Posting and Movements The catalog is not a document and is not posted — it does not generate direct accounting entries and movements in accumulation registers. The storage of the file content is ensured by service information registers of the "File Management" subsystem: Storage What it stores InformationRegister.BinaryFileData (or AttachedFilesStorage) The actual binary content of the file when stored "In the information base" Disk volume (Catalog.FileStorageVolumes + FilePath) The content when stored "In the disk volume" The posting is generated by the owner document OutgoingPaymentOrder (more precisely — the withdrawal from the settlement account, entered based on it), not the file. For the configuration "Accounting for Kazakhstan 3.0", when executing a payment according to the standard chart of accounts of the RK, the following entries are generated, for example: Operation Debit Credit Payment to the supplier 3310 "Short-term liabilities to suppliers" 1030 "Cash in current bank accounts" Transfer of VAT to the budget 3130 "VAT payable" 1030 Return/payment to the customer 1210 "Short-term receivables from customers" 1030 Reference values of the RK for 2026 (for the context of payment documents of the configuration): VAT rate — 16%; MRP — 4,325 ₸; MSP — 85,000 ₸; social tax rate — 6%; OPE — 10% (ceiling base 50 MSP), OPEA — 3.5%, VOSMS — 2%, OSMS — 3%, SO — 5%; PIT — 10% up to 8,500 MRP annual income and 15% above; basic tax deduction for PIT — 30 MRP per month, but not more than 360 MRP per year. Currency — tenge (₸). The file catalog does not use these values — they relate to the calculation part of the owner documents. 6. Related Objects and Input Based On - Owner Document: Document.OutgoingPaymentOrder — the only source of catalog items (through the attribute FileOwner). - Catalog.Users — attributes Author, ModifiedBy, EditingUser. - Catalog.FileStorageVolumes — when storing files on disk. - EDO RK Subsystem: files can accompany electronic documents — electronic invoices (ESF) and tax invoices; the catalog itself stores their scans/attachments, but the exchange is conducted with specialized EDO objects. - Input based on is not provided for the file catalog — items are created exclusively by the file attachment command from the document form. 7. Extension Points - Configuration extension: adding attributes (for example, "Bank document type", "Number in external system") and subscribing to record events for additional verification/classification of files. - Overridable BSP modules: FileManagementOverridable, FileManagementClientOverridable — setting restrictions on size/extensions, storage directories, version cleanup rules. - Roles and RLS: restricting access to files by owner/organization through record-level restrictions. - Event subscriptions: control of mandatory digital signature (SignedByEP) before posting the owner document. - Additional attributes/information: through the characteristic types plan of the "Properties" subsystem, if the corresponding option is enabled for the object (requires verification in a specific delivery). --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_