--- title: "Document \"MessageExchangeWithBanks\" - Technical Description" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-07 canonical: https://buhgpt.kz/suraqtar/dokument-soobshchenieobmensbankami-tehnicheskoe-opisanie-en source: BuhGPT --- # Document "MessageExchangeWithBanks" - Technical Description > **TL;DR:** 1. Identification of the Object Parameter Value Object Type Document (Documents) Name MessageExchangeWithBanks Full Name Document.MessageExchangeWithBanks Synonym “Message exchange with banks” Configuration Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) Conducted No --- 1. Identification of the Object Parameter Value Object Type Document (Documents) Name MessageExchangeWithBanks Full Name Document.MessageExchangeWithBanks Synonym “Message exchange with banks” Configuration Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) Conducted No — the document does not contain ProcessingConduct and does not generate movements Where to find Section “Electronic Interaction” → “Message exchange with banks” Navigation Link e1cib/list/Document.MessageExchangeWithBanks Purpose. The document is the central object of the electronic document management (EDM) subsystem with banks. It registers, stores, and manages the lifecycle of electronic documents (ED) exchanged between the organization and credit institutions: payment orders, bank statements, receipts, status requests, etc. The document is created automatically during synchronization with the bank (client-bank / direct exchange) or manually when generating an outgoing ED. The main users are accountants and treasury staff who work with payments and statements daily. By its nature, the object is informational-reference (transport) in nature: it records the fact and status of the exchange but does not itself reflect a business transaction in accounting or tax accounting. Accounting movements (for cash on account 1030, settlements with counterparties 1210/3310, etc.) are formed by related accounting documents (“Payment Order,” “Withdrawal from Current Account,” “Receipt to Current Account”), not by the “MessageExchangeWithBanks” itself. 2. Attributes and Table Parts Below is the typical composition of an object of this type in the configuration. The specific list of attributes may vary slightly within the release (version-specific). Header Attributes Attribute Purpose Date Date/time of message exchange formation Number Document number Organization The organization on behalf of which the exchange is conducted BankAccount / Account The organization's account in the bank to which the exchange relates TypeOfExchange / MessageType Type of ED: payment order, statement, receipt, status request, etc. Direction Outgoing / incoming document Status / EDState Current state of the lifecycle (prepared, signed, sent, accepted by the bank, rejected, executed) EDIdentifier Unique identifier of the ED in the exchange system / at the bank SendingDate, ReceivingDate Timestamps of transport events Responsible User responsible for the document Comment Arbitrary text note Stored Data / Composition Attributes Element Purpose Storage (ValueStorage) of the ED body The body of the electronic document (XML/binary container) as it is transmitted to the bank/received from the bank Electronic signatures (ES) Attached certificates and signatures to the ED Table part of statement/payment register lines Lines parsed from the ED body (for example, movements in the statement or register of payment documents) — filled during the parsing of the incoming message Table parts are used as a transport container for parsing: based on them, accounting documents are formed or matched, but the lines do not generate independent accounting movements. 3. Forms Form Purpose List Form View the message exchange log, filter by organization, account, status, and direction Document Form View the attributes of a specific message exchange Form ElectronicDocument Key working form of EDM: signing the ED with a certificate, sending to the bank, status request, processing bank responses (see procedures in section 4) Form for selecting/printing statements Generating and printing a statement for an arbitrary period (scenario 3.5) 4. Key Module Procedures From the evidence of the configuration, the form handlers ElectronicDocument related to signing and transport of ED are confirmed: Procedure / Point What it does Diagnostic Message OpenCertificate Selects the ES certificate from the list of installed signatures before signing the ED. Controls Elements.ES.CurrentData <> Undefined “Select a certificate from the list of installed signatures.” AfterSendingPaymentStatusRequestSberbank Processes the bank's response to the payment status request; checks the flag AdditionalParameters.AuthenticationPerformed “Authentication error on the bank server” The texts of the messages are quoted verbatim from the code (recorded in release 3.0.68.1). If the user sees such a message — check the condition from the corresponding line. Other typical handlers of an object of this type (general logic of the EDM document): - OnCreationOnServer of the form — initialization of state, availability of signing/sending commands based on the current status of the ED. - Form commands Sign, Send, RequestStatus, Reject — manage the lifecycle (status transitions). - ProcessingFilling — filling in attributes during automatic creation during synchronization with the bank. - Module procedures for parsing the body of incoming ED and filling table parts (statement/register). Important: the procedure ProcessingConduct in the object is not present. 5. Conducting and Movements The document is non-conductive. In the metadata register_records = [] — the object does not generate movements in either accounting registers or accumulation/tax accounting registers. Accordingly, no entries of the type “Dr/Cr” are made by the “MessageExchangeWithBanks” itself. All accounting records are generated by related payment and statement documents. For reference — typical correspondence according to the chart of accounts of the RK, which is made by these related documents (and not the described object): Operation (related document) Dr Cr Payment to the supplier (withdrawal from the current account) 3310 “Payables to suppliers” 1030 “Cash in current accounts” Receipt of payment from the buyer 1030 “Cash in current accounts” 1210 “Short-term receivables from buyers” The currency of settlements is tenge (₸). Rates and standards of the RK for 2026 (VAT 16%, MRP 4,325 ₸, MSP 85,000 ₸, etc.) do not apply directly to this object, as it does not participate in tax calculations — they are provided as context for the configuration. 6. Related Objects and Input Based On - Accounting documents of payments: “Payment Order,” “Withdrawal from Current Account,” “Receipt to Current Account” — are the source/receiver of ED data. The outgoing message exchange is formed based on payment documents; when parsing the incoming statement, the lines are matched with these documents or create them. - Bank account (reference) and Organization — determine the exchange channel and EDM settings. - ES certificates / signatures — are attached to the ED during signing. - Profile/exchange settings with the bank (client-bank, direct exchange) — set transport and authentication data. Input based on an accounting document for this object is not typical: exchange messages are usually created automatically by the EDM subsystem or by commands of the ElectronicDocument form, not through “Input Based On.” 7. Extension Points - Extension of the form ElectronicDocument — adding custom checks before signing/sending, integration with additional banks (similarly to ...Sberbank branch of status processing). - Subscriptions to events of the object (BeforeWriting, OnWriting) — for logging exchanges or notifying responsible parties. - Processing the parsing of the ED body — refining the matching of statement lines with accounting documents to the specifics of a particular bank/format. - Additional attributes/information — extending the composition of message attributes without interfering with the standard code. Since the object is non-conductive, extension points related to conducting and movements are absent — do not attempt to add logic to the non-existent ProcessingConduct; refine accounting movements in related payment documents. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_