Verified on release 3.0.74.2 "Accounting for Kazakhstan" (edition 3.0).
Monday morning. You sent three payment orders to the bank via "DirectBank," clicked "Exchange with bank," but the money didn't appear at the counterparty. In the payment orders journal there is a status of "Sent," but not "Executed." Where to look, what went wrong? This is exactly where "Bank Exchange Message" comes in — it's the "black box" of your exchange. It shows which package went to the bank, what the bank responded, which document was rejected and for what reason. Without this document you guess; with it — you know exactly where the payment got stuck.
1. Purpose
"Bank Exchange Message" is a service (transport) document. It records one exchange session with the bank using direct exchange technology (1C:DirectBank): what you sent to the bank and what the bank sent in response. By itself it does not make accounting entries — the entries are created by the payment documents and statements that "ride" inside this message.
2. Where to find it
Three ways — choose the convenient one.
- Via the document list: section "Bank and cash desk" → "Bank" block → "Bank Exchange Messages" (sometimes via "More" → "All documents" → "Bank Exchange Messages").
- From the payment order: in the "Payment Orders" list form the "Exchange with bank" button — each session creates its own message.
- Directly via the 1C navigation link. Main menu → "Tools" → "Follow navigation link" (or the "asterisk/link" icon in the header) and paste:
e1cib/list/Документ.СообщениеОбменСБанками
The full journal of all exchange sessions will open.
2a. How to find out your release
"Help" → "About" (or the "i" icon in the top right corner). There are two lines: platform version (for example, 8.3.24.x) and configuration release — "Accounting for Kazakhstan, edition 3.0 (3.0.74.2)". If your release is lower — some DirectBank buttons and fields may look different. This guide is for 3.0.74.2.
3. How to fill it in
Usually the document is created automatically when you click "Exchange with bank." You almost never create it manually. But you need to understand the fields — you use them to analyze incidents.
| Field | Why it is needed | What happens if it is wrong |
|---|---|---|
| Organization (required) | On whose behalf the exchange goes. Links the session to your legal entity and its bank settings. | The exchange will go with the wrong settings — the bank will reject the package or accept it from a "foreign" organization. |
| Bank account / Exchange settings (required) | The specific account and contract with the bank under which direct exchange goes. Determines the service address and certificate. | The message will go "into nowhere" or a service authorization error will be returned. |
| Date, session time | The timestamp of the exchange moment. By it you find the needed session among dozens. | Confusion during analysis: you won't understand which package is for which day. |
| Direction (Outgoing / Incoming) | Outgoing — you sent payment orders to the bank; Incoming — the bank sent statements/statuses. | Wrong direction — you'll be looking for a statement among the sent ones. |
| Session status | The result: "Sent," "Accepted by bank," "Error," "Confirmation required." | The "Error" status is precisely the signal to investigate. |
| "Documents" table section | List of payment orders/statements in this session, each with its own status from the bank. | Here you can see which specific document was rejected. |
| Message identifier / package number | Unique session code for reconciliation with the bank by phone. | Without it, the bank won't find your package in its system. |
| Bank response text / Comment | The verbatim reason for the bank's refusal. | Ignore it — you won't learn the reason for rejection. |
The practical order of work (not filling in fields):
- Post the needed Payment Orders.
- In the payment orders list, mark them with checkboxes → "Exchange with bank".
- Sign the package with a digital signature (with the director's/accountant's certificate).
- Wait for the bank's response — statuses will update.
- When you click "Load statement," the bank will return an Incoming message with statements.
4. Worked example with figures and entries
Situation. LLP "Astana-Trade" (VAT payer, rate 16%), account 1030 at the bank. On September 6, 2026, you send three payments:
| No. | Recipient | Purpose | Amount, ₸ |
|---|---|---|---|
| 1 | LLP "Snab" | Payment for goods (invoice with VAT 16%) | 1,160,000 |
| 2 | Budget | IIT for August | 250,000 |
| 3 | LLP "Snab" | Erroneous — account closed | 500,000 |
You mark all three → "Exchange with bank" → sign with digital signature. An outgoing "Bank Exchange Message" with three lines is created. The bank responds:
- Payment No. 1 — "Executed";
- Payment No. 2 — "Executed";
- Payment No. 3 — "Rejected: recipient's account closed".
The message itself makes no entries. The entries are created by the payment documents (in 3.0 these are "Outgoing Payment Order" / "Debit from current account") when the bank has confirmed the payment.
Payment No. 1 (payment to supplier LLP "Snab," 1,160,000 ₸ = 1,000,000 goods + 160,000 VAT 16%). The entry is generated upon actual debit:
| Dr | Cr | Amount, ₸ | Content |
|---|---|---|---|
| 3310 | 1030 | 1,160,000 | Paid to supplier from the current account |
The input VAT is offset by the receipt document (Dr 1420 Cr 3310), and the payment settles the accounts payable 3310.
Payment No. 2 (IIT to the budget):
| Dr | Cr | Amount, ₸ | Content |
|---|---|---|---|
| 3120 | 1030 | 250,000 | IIT transferred to the budget |
Payment No. 3 (rejected) — there are no entries. The money did not leave account 1030. In the exchange message, line No. 3 has the status "Rejected" and the bank's text. You correct the details in the payment order and send it in a new session.
Session result: 1,410,000 ₸ debited (1,160,000 + 250,000), one payment order returned. All this is visible in one "Bank Exchange Message" — no need to run around the payment orders journal.
Reminder on KZ-2026 figures: VAT 16%, MCI 4,325 ₸, minimum wage 85,000 ₸, OPV 10% (base cap 50 minimum wages), OPVR 3.5%, VOSMS 2%, OSMS 3%, SO 5%, social tax 6%. Basic IIT deduction — 30 MCI per month.
5. Types of operation
The document serves two exchange operations:
- Outgoing message — sending payment orders to the bank (individually or as a package), requesting statuses, revoking a payment.
- Incoming message — receiving from the bank: bank statements, statuses of previously sent documents, service notifications.
Separately, within a session, the following are supported: signing the package with a digital signature, resending, updating statuses, and loading the statement.
6. What is generated upon posting
- The document itself creates no entries. It is transport. The accounting movements (Dr/Cr for 1030, 3310, 3120, etc.) are made by the related payment orders and bank statements.
- Movements in exchange registers: the status of each document is recorded (sent / accepted / executed / rejected), the package identifier, the link to the DirectBank setting.
- Updating payment order statuses: based on the bank's response, payment orders move to "Executed."
- Electronic documents. This is an exchange with the bank, not with the ESF IS. Therefore ESF and SNT are not generated here — they are created by sales/receipt documents via "1C-EDO"/ESF and SNT IS, this is a separate circuit.
7. Printed forms
The transport document has few of its own "nice" printed forms:
- Exchange protocol (session log) — what was sent/received, statuses, error texts.
- Printing a payment order — called from the related payment order (PO form according to the NB RK standard).
- Register of sent documents — a list of the package's payment orders with amounts.
The main printed forms (payment order, statement) are printed from the payment documents themselves, not from the exchange message.
8. Common mistakes
"Electronic signature certificate not found / expired." The director's digital signature has expired or is not installed in the store. Reissue the certificate, install it in the personal store, and specify it in the exchange setting (section "Bank and cash desk" → "Bank exchange settings").
"Bank service authorization error (401/403)." The DirectBank login didn't match, the account is not connected to direct exchange, or the bank hasn't yet activated the service. Check the exchange setting and the connection status on the bank's side.
"Document rejected by the bank: incorrect recipient details." An error in the IIK/BIK/name of the payment order recipient. Correct the payment order and send it in a new session — a rejected one won't "come alive" by itself.
"Message not signed, sending impossible." The package is assembled but not signed with a digital signature. Open the message → "Sign and send."
"Exchange setting not filled in for the bank account." Direct exchange is not enabled for this account. Set up DirectBank for the account or send payment orders via the "Client-Bank" file.
"Document status is not updating, stuck on 'Sent'." The bank hasn't processed the package yet or the connection dropped. Click "Update statuses" / a repeat session of an incoming message. Do not create the payment anew — you'll get a double debit.
9. FAQ
1. Do I need to create this document manually? No. It is born automatically when you click "Exchange with bank." Manually you mostly just read it, analyzing incidents.
2. Does "Bank Exchange Message" make entries? No. The entries (for example, Dr 3310 Cr 1030) are made by payment orders and bank statements. The message is only transport and statuses.
3. How is DirectBank different from "Client-Bank" with files?
DirectBank exchanges directly over a secure channel without uploading files. "Client-Bank" is a manual upload of 1c_to_kl.txt and loading of kl_to_1c.txt. The exchange message relates to direct exchange.
4. I sent a payment, but there's no money. Where do I look for the reason?
Open the needed session in the journal (e1cib/list/Документ.СообщениеОбменСБанками), find the line for this payment and read the status and the text of the bank's response.
5. Are ESF or SNT generated here? No. ESF (ESF IS) and SNT are an exchange with tax information systems, a separate EDO circuit. Bank exchange does not create them.
6. Can I send several payment orders at once? Yes. Mark the needed payment orders with checkboxes in the list and click "Exchange with bank" — they will go as one package, each with its own status.
7. A payment was rejected by the bank. What to do? Correct the details in the payment order and send it again in a new session. A rejected line does not resend itself.
8. How do I delete an unnecessary exchange message? Mark it for deletion as an ordinary document (right-click → "Mark for deletion"). But remember: the message is the exchange history, it's better to keep it for reconciliation with the bank by package identifier.
9. Can I revoke an already sent payment? If the bank hasn't executed it yet, send an outgoing message with the "Revoke" operation. After execution, revocation via 1C is impossible — contact the bank.
10. Where do I get the package identifier to call the bank? In the exchange message itself, the "Message identifier / package number" field. You give it to the bank operator for the search.
10. Related documents
- On the basis of what it appears: posted Payment Orders (outgoing payments) — they are exactly what is assembled into the outgoing package.
- What it generates / updates: payment order statuses ("Executed"), and an incoming message — Bank Statements (receipts to the account, Dr 1030 Cr 1210 upon payment from a buyer).
- Settings: "Bank exchange settings (DirectBank)" — the "Bank and cash desk" section.
- Adjacent circuit: for electronic invoices, use sales/receipt documents and the ESF/SNT module — this is not about the bank.
How to find out your release: "Help" → "About" — there you'll find the platform and configuration release.
This guide was prepared for "Accounting for Kazakhstan," edition 3.0, release 3.0.74.2.