Verified on release 3.0.74.2 "Accounting for Kazakhstan" (edition 3.0).
Friday, end of the day. You need to pay five supplier invoices, and the accountant usually exported the payment orders to a 1c_to_kl.txt file, manually uploaded it into the internet bank, signed it there, then downloaded the statement and loaded it back into 1C. Half an hour of clicking. But today the bank has enabled direct exchange (DirectBank), and all your payment orders went to the bank with a single button — no files, no flash drive, no second window. Behind this "single button" stands the document "Bank Exchange Package". It collects payment orders into a batch, sends them to the bank over a secure channel, and receives statements and statuses back. Let's break it down piece by piece.
1. Purpose
The "Bank Exchange Package" is a service document that packs payment orders and statement requests into a single package and exchanges it with the bank directly (DirectBank / direct exchange technology). It stores exactly what was sent to the bank, in what status, and what came back in response. The 1c_to_kl.txt / kl_to_1c.txt files are no longer needed with direct exchange.
2. Where to find it
The document is usually generated automatically from the payments form, but you can reach the list like this:
- Section "Bank and Cash Desk" → "Bank" → "Exchange with Bank" command (DirectBank) — from there sending and receiving packages is launched.
- The package list itself: "All Functions" → "Documents" → "Bank Exchange Package" (if the "All Functions" mode is enabled).
- Direct 1C navigation link:
e1cib/list/Документ.ПакетОбменСБанками
To open the list directly: menu "Tools" (or the ▾ icon in the header) → "Go to navigation link", paste the string above, click "Go".
Direct exchange works only after DirectBank is configured and connected for your account in "Bank and Cash Desk" → "Bank Accounts" (the "Connect DirectBank" / "Configure exchange with bank" button). Without a connected service, you won't be able to create the document.
2a. How to find out your release
Open "Help" → "About the program" (or the "?" icon in the top right corner). In the window you will see two lines: the platform version (for example, 8.3.24.x) and the configuration release — "Accounting for Kazakhstan, edition 3.0 (3.0.74.2)". If your release differs, individual fields and buttons may be named differently — check by meaning.
3. How to fill it in
In most cases you don't fill in this document by hand — it's created by the exchange mechanism. But you need to understand the fields in order to read what was sent and what came back.
| Field | What it's for and what happens if you make a mistake |
|---|---|
| Organization (req.) | On whose behalf the exchange takes place. If you select the wrong organization, the bank won't find the service agreement and will reject the package. |
| Bank account (req.) | The account for which DirectBank is connected. Choose the wrong account and the package will go "into the void", the bank will return an authorization error. |
| Date (req.) | The moment the package is formed. It determines which payment orders are selected for sending and how the exchange log is built. |
| Package type / Direction | "Send to bank" (payment orders, statement request) or "Receive from bank" (statement, statuses). Determines what the program does with the contents. |
| Package contents (tabular section) | The list of payment orders and requests that were sent/received. Here you can see each document and its status. |
| Exchange status | "Prepared", "Sent", "Accepted by bank", "Executed", "Rejected". The main field for control: from it you understand whether the money went through. |
| Date and time of communication session | When the session with the bank actually took place. Helps to sort things out if a payment is "stuck". |
| Comment | Your note. It doesn't affect postings but helps when analyzing disputed situations. |
Order of work (typical scenario):
- You create payment orders ("Bank and Cash Desk" → "Payment Orders"), check the amounts and recipient details.
- You click "Exchange with Bank (DirectBank)" — the program collects unsent payment orders into a package and offers to send them.
- You send them. A signature window appears (SMS code, token, or digital signature, as configured in the bank). You sign.
- The bank accepts the package, the status changes to "Accepted / Executed". The package records this.
- Later you request a statement — a new package "Receive from bank" arrives, and based on it the documents "Receipt to account" / "Debit from current account" are created.
4. Worked example with postings
Situation. LLP "Astra" (VAT payer, rate 16%) pays supplier LLP "Bars" for goods in the amount of 1,160,000 ₸, including VAT of 16%. The exchange goes through DirectBank.
VAT calculation within the payment amount: VAT = 1,160,000 × 16 / 116 = 160,000 ₸, cost excluding VAT = 1,000,000 ₸.
Step 1. Payment order for 1,160,000 ₸ to supplier LLP "Bars", account 1030.
Step 2. Clicked "Exchange with Bank", the payment order went into the package, sent it, signed with an SMS code. Package status — "Executed".
Step 3. Requested the statement. A "Receive from bank" package arrived, and based on it the document "Debit from current account" for 1,160,000 ₸ was created.
The posting is formed precisely by the debit (the package is transport, it doesn't make postings itself):
| Dr | Cr | Amount, ₸ | Description |
|---|---|---|---|
| 3310 | 1030 | 1,160,000 | Payment to supplier LLP "Bars" from current account |
When the goods arrive (the "Receipt of Inventory" document), the postings will be as follows:
| Dr | Cr | Amount, ₸ | Description |
|---|---|---|---|
| 1330 | 3310 | 1,000,000 | Goods received (excluding VAT) |
| 1420 | 3310 | 160,000 | VAT recoverable (16%) |
If this were a sale rather than a purchase, and you received from LLP "Bars" a receipt to the account of 1,160,000 ₸ for shipped goods with a cost of 700,000 ₸:
| Dr | Cr | Amount, ₸ | Description |
|---|---|---|---|
| 1030 | 1210 | 1,160,000 | Money received from the buyer |
| 1210 | 6010 | 1,000,000 | Revenue from sales |
| 1210 | 3130 | 160,000 | VAT payable (16%) |
| 7010 | 1330 | 700,000 | Cost of goods written off |
Thus the exchange package links the movement of money on account 1030 with settlements (1210 / 3310) and VAT (3130 / 1420), and for a sale an ESF is also added on top.
5. Types of operation (package directions)
| Type | What it does |
|---|---|
| Sending payment orders | The package collects signed payment orders and transmits them to the bank for execution. |
| Statement request | The package sends a request to the bank for account movements over a period. |
| Receiving a statement | The package receives the statement from the bank; based on it, receipts/debits are created. |
| Receiving statuses | The package updates the statuses of previously sent payment orders (accepted / executed / rejected). |
| Payment recall | For a number of banks — sending a request to recall a payment order that has not yet been executed. |
6. What is generated upon posting
- The package makes no accounting postings of its own. It's a communication channel. Postings are created by the documents it carries: payment orders (after execution), "Debit from current account", "Receipt to account".
- Movements in exchange registers: the log of communication sessions, statuses of payment documents, the signature log.
- Electronic documents. The package itself is a banking exchange and has nothing to do with ESF/SNT. But the sale/receipt it pays for requires issuing an ESF in the ESF IS and, when moving goods, an SNT. They are issued separately from the sale/receipt documents, not from the package.
- Statuses are set on the related payment orders: "Sent", "Executed", "Rejected".
7. Printable forms
The exchange package is a technical document; it doesn't have a rich set of printable forms. Available are:
- Exchange protocol (session log) — what was sent, what was received, communication time, result.
- Register of the package's payment documents — a list of payment orders with amounts and statuses.
The main printable forms (the "Payment Order" itself, as well as the "Bank Statement") are printed from the corresponding documents — the payment orders and statements, not from the package.
8. Common mistakes
"Failed to establish connection with the bank (DirectBank). Check the exchange settings." The service is not connected or the access credentials have changed. Go to "Bank and Cash Desk" → "Bank Accounts" → account card → "Configure exchange with bank" and reconnect DirectBank.
"Package rejected by the bank: invalid signature." The digital signature certificate has expired or you entered an incorrect SMS code. Renew the certificate / request the code again and re-sign the package.
"The document cannot be sent: the recipient's bank account / BIC is not filled in." An error in the payment order details. Open the payment order, check the recipient's IIC, BIC, KBe, and Knp — the bank won't accept a payment with empty fields.
"The payment amount exceeds the account balance." There are insufficient funds on account 1030. Wait for a receipt or reduce the payment; the package will go out only after the bank confirms the available balance.
"The payment has already been sent in this package." Re-sending the same payment order. Don't create a new package for an already executed order — check the status in the existing package.
9. FAQ
1. How does direct exchange (DirectBank) differ from file exchange?
With file exchange, you export 1c_to_kl.txt, manually load it into the client-bank, and download the statement back. Direct exchange via a package does this over a secure channel with a single button — no files.
2. Does the package make postings? No. Postings are formed by payment orders, "Debit from current account", and "Receipt to account". The package only transmits them to the bank and returns statuses.
3. How do I know that a payment went through? By the status of the package and the related payment order: "Executed" — the money has been debited, "Rejected" — the bank did not process it, "Sent" — awaiting processing.
4. Do I need to issue an ESF for the package? The package itself doesn't require an ESF. An ESF is issued for the sale/receipt that this payment closes — separately, in the ESF IS.
5. Can I send several payment orders in one package? Yes. That's the whole point: the package collects all unsent signed payment orders and goes out in a single session.
6. How do I recall a sent payment? If the payment has not yet been executed, some banks support recall through a separate package. If the status is already "Executed" — only through the bank by application.
7. What is the VAT rate within the payment amount in 2026? For settlements in the RK, a rate of 16% applies. In the example with 1,160,000 ₸, VAT = 160,000 ₸ (1,160,000 × 16 / 116).
8. Why is a payment "stuck" in the "Sent" status? The bank has not yet processed the package or the session was interrupted. Request the statuses again via DirectBank — the status will update to "Executed" or "Rejected".
9. Which account is the money debited from? From account 1030 "Money in current bank accounts" — it's credited when paying a supplier (Dr 3310 Cr 1030) and debited when receiving from a buyer (Dr 1030 Cr 1210).
10. What to do if DirectBank won't connect? Check whether the service is enabled at the bank itself, whether the login/password and certificate are current, and whether there is internet access. Reconnect the exchange in the bank account card.
10. Related documents
- On what basis the package appears: "Payment Order" (for sending), a statement request from the exchange form.
- What is entered based on the statement in the package: "Debit from current account", "Receipt to current account".
- Related by chain: "Invoice for Payment", "Receipt of Inventory and Services", "Sale of Inventory and Services", ESF (in the ESF IS), SNT.
The guide was prepared and verified on release 3.0.74.2 of the "Accounting for Kazakhstan" configuration (edition 3.0). Check your release via "Help" → "About the program": it shows the platform version and the configuration release.