Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0).
You have set up direct exchange with the bank (DirectBank) or uploaded a statement via "Client-Bank". The bank sent a message — a statement file, a payment status receipt, sometimes a PDF confirmation. A day passes, and you need to understand: what exactly did the bank send that time? Which file was the basis for the upload? This is where you open this directory. It stores the files you exchanged with the bank, linked to specific exchange messages. This is not a statement or a payment document — it is an "attachment archive," a technical storage where 1C keeps everything that has come and gone through the "bank ↔ 1C" channel.
Let's be clear: this is a service (subordinate) directory. It does not make accounting entries, does not generate electronic invoices (ESF) or tax returns (SNT), and does not participate in tax calculations. Its task is to store files and allow you to open, export, or delete them. Below is how to work with it and where the line is drawn between a "file" and a "real statement with entries".
1. Purpose
The directory stores attached files (attachments) to messages from the bank exchange service: payment export files, uploaded statements, receipts, and status confirmations from the bank. This is an archive of attachments from the exchange channel, not an accounting document.
2. Where to find
Directly in the interface, the list of this directory is usually not included in the menu — 1C opens it from the exchange message card. Practical routes:
- Section "Bank and Cash" → "Exchange with Bank" (Client-Bank / DirectBank) → open the required exchange message → command "Attached Files".
- From the exchange processing journal — by clicking the "Open File" or "Show Attachments" button on a specific line.
To open the list directly in 1C: Main Menu → "File" → "Open" is not needed. Use the navigation mechanism: Service → "Go to Navigation Link" and paste:
e1cib/list/Directory.ExchangeMessageWithBanksAttachedFiles
This way you will go directly to the general list of all exchange attachments.
2a. How to find out your release
"Help" (icon ?) → "About the Program". In the opened window, you will see two lines: the platform version (for example, 8.3.24.xxxx) and the configuration release — "Accounting for Kazakhstan, version 3.0 (3.0.74.2)". It is the second line (3.0.74.x) that determines whether your interface matches this instruction. If your release is older — check the location of the exchange commands, as they have moved between sections.
3. How to fill
You almost do not fill this directory manually — records are created by the exchange mechanism when you send payments or upload a statement. But you need to know how to read the file card. Key fields:
| Field | Purpose | What happens if incorrect |
|---|---|---|
| Name (mandatory) | The name of the file — you find the attachment in the list by it. By default, it takes the name of the original file (statement_20260907.txt). |
An empty name — the file will "get lost" in a list of dozens of similar attachments. |
| Owner (mandatory, service) | A link to the exchange message to which the file is attached. It is filled automatically. | Loss of connection with the message — the file will become "orphaned," it will not be visible from the exchange card. |
| Stored File / File Data | The binary content itself (the file itself). | An empty storage — nothing to open or export. |
| Extension | File type (txt, xml, pdf, kkm). Determines what 1C will suggest to open. | Incorrect extension — the file will open with the "wrong" program. |
| Size, Creation Date, Modification Date | Technical labels. Help distinguish a fresh receipt from an old one. | Not critical, but by date you can distinguish the current attachment. |
| Author | The user during whose session the file appeared. | Reference for audit: who uploaded the statement. |
Practically, your work comes down to three buttons in the card: "Open", "Save As..." (export to disk), "Edit" (replace content if it is an allowed service file).
4. Disassembled example
This directory does not make entries — and it is important to understand this to avoid searching for them in vain. Entries are formed not by the file, but by the document you create based on this file. Let's show the entire chain with numbers.
Situation. On September 7, 2026, a payment from the buyer LLP "Astana-Trade" arrived at the current account — 1,160,000 ₸ (including VAT 16% = 160,000 ₸) for previously shipped goods.
- The bank sends the statement file
kz_out_20260907.txt. The exchange mechanism saves it here — in the directory of attached files. No entries. - You click "Upload Statement". 1C reads the file and creates the document "Receipt to Current Account".
- The document of receipt is already processed:
| Dr | Cr | Amount, ₸ | Description |
|---|---|---|---|
| 1030 | 1210 | 1,160,000 | Payment received from the buyer to the current account |
VAT in this operation was already accrued upon sale (Dr 1210 Cr 6010 for 1,000,000 and Dr 1210 Cr 3130 for 160,000), so only 1030 ↔ 1210 moves during payment.
Conclusion of the example: the file in the directory is the "primary document of the communication channel". Accounting entries live in the receipt/disbursement document, not in the attachment. In the directory, you store proof: what exactly the bank sent, on the basis of which the statement was created.
5. Types of operations
The directory does not have a separate attribute "Type of Operation", but in essence, attachments are divided as follows:
- Outgoing file — what you exported to the bank (register of payment orders).
- Incoming statement file — export of operations on the account for the day/period.
- Receipt / Status — the bank's response regarding the acceptance or rejection of the payment (accepted, processed, rejected).
- Confirmatory document — PDF payment order with the bank's stamp, when using DirectBank.
6. What is formed during processing
The directory is not a document, so there are no postings, movements in registers, entries, electronic invoices (ESF), or tax returns (SNT). It only stores files. All "movement" occurs around it:
- when uploading a statement, documents "Receipt to Current Account" and "Disbursement from Current Account" are created (these already provide entries for 1030, 1210, 3310, etc.);
- ESF and SNT are formed from sales/purchase documents, not from exchanges with the bank, and are not related to this directory.
7. Print forms
The directory does not have its own print forms. You have access to actions with the file itself:
- "Open" — view the attachment (txt/xml/pdf) with the standard OS program.
- "Save As..." — export the file to disk for transfer to the auditor or for archiving.
- Print — only through an external program that opened the file (for example, print the PDF payment order from the PDF viewer).
Print forms for payment orders and statements should be taken from the corresponding banking documents, not from here.
8. Common mistakes
"File contains no data" / "Storage value is empty" — the attachment was created, but the content did not upload (channel failure). Delete the empty record and repeat the statement upload again.
"File format not supported" when uploading a statement — the bank sent a file in the wrong format (for example, PDF instead of txt/1C format). Open the attachment, ensure it is a text exchange, and upload the statement from the correct file, not from the receipt.
"Exchange message not found (owner)" — the file was left without a parent message (the message was deleted, but the attachment was not). Such an "orphaned" file can be safely deleted; it contains no accounting data.
Duplicate statements — you uploaded the same file twice, resulting in duplicated receipts. Refer to the date and file name in the directory: if such an attachment already exists, do not initiate a repeat upload.
9. FAQ
Does this directory make accounting entries? No. This is a service storage for exchange files. Entries are formed by the documents "Receipt to Current Account" and "Disbursement from Current Account," which are created based on the uploaded statement.
Can old files be deleted to save space? Yes, attachments can be deleted without harming the accounting — entries and statement documents will remain. But it is better to keep them until the end of the primary storage period: this is proof of what and when the bank sent.
Where to see from which file the statement was uploaded?
Open the exchange message in the "Bank and Cash → Exchange with Bank" section and go to its attached files, or open the list via the link e1cib/list/Directory.ExchangeMessageWithBanksAttachedFiles.
Does this directory affect VAT (16%) or tax calculations? No. The VAT rate of 16%, individual income tax (IIT), social tax (ST), and other taxes are calculated in accounting documents and regulatory operations. The exchange file does not participate in calculations.
Why can't the file be opened within 1C? 1C sends the content to an external program based on the extension. Txt/xml will open in a text editor, PDF — in a PDF viewer. If the extension is incorrectly specified, indicate the correct one or save the file to disk and open it manually.
Can the content of the file be replaced manually? Technically — yes, through "Edit," but this breaks the correspondence of "what the bank actually sent." For accounting, this is meaningless and risky: edit not the file, but the statement document itself.
There is a file, but no statement in accounting — what to do? This means you saved the attachment but did not initiate the upload. Return to the exchange with the bank and click "Upload Statement," specifying this file.
Do I need to fill this directory manually when entering the statement by hand? No. If you are entering a receipt/disbursement manually, the exchange with the bank and attachments are not involved at all — the directory will remain empty, and this is normal.
How to distinguish an incoming statement from a receipt of status? By the name and size of the file: a statement is usually larger and contains operations on the account, while a receipt is a short response about the acceptance/rejection of a specific payment.
10. Related documents
- Based on what it appears: the service message "Exchange with Bank" (DirectBank / Client-Bank) — this is the owner of the record.
- What is created from the file: documents "Receipt to Current Account" and "Disbursement from Current Account" (uploading the statement), as well as the outgoing register for "Payment Order".
- What it is linked to in the chain: payment order ← invoice ← sale/receipt; but the directory of attachments stands "aside" from this chain and only stores files of the channel.
How to find out your release
"Help" → "About the Program": the top line is the platform version, the bottom line is the configuration release. This manual is written for "Accounting for Kazakhstan", version 3.0, release 3.0.74.2. If you have a different release, the location of the exchange commands with the bank may differ — check with the "Bank and Cash" section.
Prepared for release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0).