Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0).
You sent payment orders to the bank via direct exchange (DirectBank / "Client-Bank"), and the operator says: "The file is unreadable, please send it again." You open the exchange package — and inside it are attached files: the export file itself, the bank's response, electronic signature files. These attachments are stored in the directory "BankExchangePackageAttachedFiles". Or another case: the auditor asks to show what exactly was sent to the bank on March 5 — you retrieve the original file from this directory instead of reconstructing the export again.
Let's figure out what this object is, where it is located, and what you can do with it.
1. Purpose
This is a service (technical) directory, subordinate to the bank exchange package. It stores files attached to a specific exchange package: the export file of payment documents, the import file of the statement, bank responses, electronic digital signature (EDS) files. You do not create it manually for entries — it is filled when you attach a file to the exchange package or when the exchange with the bank itself saves an attachment.
2. Where to find
There is no direct item in the main menu for this directory — it opens from the exchange package card:
- Section "Bank and Cash" → "Bank Exchange" (or "Bank Exchange (Direct)" / DirectBank) → open the required exchange package → in the package card, the command "Attached Files" (paperclip button on the panel or hyperlink "Files").
To open the list of all records directly (for searching, cleaning, diagnostics), use the navigation link in 1C:
e1cib/list/Directory.BankExchangePackageAttachedFiles
How to navigate: Main Menu (☰) → Service → "Go to Navigation Link" (or Ctrl+Shift+L in some builds), paste the line above and click "Go". A complete list of attached files for all packages will open.
Tip: working with the list "head-on" should be done rarely. The standard way is through the card of a specific exchange package, where files are filtered specifically for it.
2a. How to know your release
Main Menu (☰) → Help → "About the Program". In the opened window, you will see:
- platform version (for example, "1C:Enterprise 8.3.24.xxxx");
- configuration version — "Accounting for Kazakhstan, version 3.0 (3.0.74.2)".
Always check the release before repeating the steps: the location of the "Attached Files" button and the set of attributes may differ between versions.
3. How to fill
In 99% of cases, the record is created automatically or through the "Add" button in the attached files form of the package. When you open the file card, you will see the following fields.
| Field | Purpose and what happens in case of error |
|---|---|
| Name (mandatory) | The name of the file for searching in the list. By default, it is taken from the name of the original file. If left empty or named "Document1", you won't find the necessary attachment among dozens of packages in a month. |
| Owner (mandatory, filled automatically) | A link to the exchange package to which the file is attached. This is a key field: if the owner is not correct, the file will "go" to someone else's package and will not appear in the card of the required package. It is usually not changed manually. |
| File / File Storage (mandatory) | The actual file body (in volumes or in the database). Without it, the record is empty. If the volume storage is configured and the volume is unavailable, you will receive an opening error — the file physically resides on the server disk. |
| Extension | File type (txt, xml, p7s, pdf). Filled from the name. Incorrect extension → the file will not open with the required program. |
| Size (bytes) | Service, filled automatically. It shows whether the file is "zero" (0 bytes = corrupted export). |
| Author | Who attached the file. Filled with the current user. Useful for understanding who and when sent the payment orders. |
| Creation Date / Modification Date | Service timestamps. Help understand which submission the file relates to. |
| Signed by EDS | Flag indicating that the file contains an electronic signature (relevant for .p7s files/bank responses). If "Signed" is set, editing the file is prohibited — otherwise, the signature will be invalidated. |
| Encrypted | Encryption flag. An encrypted file cannot be opened without decryption — a certificate will be needed. |
| Comment / Description | Free text: "Re-export after bank refusal", "Bank response on crediting". Saves time when analyzing disputed submissions. |
Practical actions in the package file form:
- Add — attach a file from the disk.
- Save as... — export the original file from the database to the disk (what is needed when the bank asks to "send it again").
- Open — view the file.
- Edit → Finish editing — editing with saving a new version (for unsigned files).
- Delete (mark for deletion) — remove unnecessary attachment.
4. Analyzed example
Situation. On March 5, 2026, you exported three payment orders to the supplier LLP "Astana-Snab" for a total amount of 2,320,000 ₸ (including VAT 16% = 320,000 ₸ for one of the payments). The exchange is done through a direct channel with the bank.
What happens with this directory:
- 1C generates a bank exchange package dated 05.03.2026.
- The export file is automatically attached to the package, for example
to_bank_20260305.xml(extensionxml, size 8 KB), author — you, flag "Signed by EDS" — yes. - Later, the bank sends a response — you (or the exchange) attach
bank_response_20260305.p7swith the flag "Signed".
Now the key point. This directory does not create entries. It stores attachments. Accounting movements are made by payment documents that "went" in the package. When money is debited from the current account, the entry is formed by the document "Debit from Current Account":
| Dr | Cr | Amount, ₸ | Description |
|---|---|---|---|
| 3310 | 1030 | 2,320,000 | Payment to supplier LLP "Astana-Snab" from the current account |
If the payment was an advance, the advance account will replace 3310. VAT (320,000 ₸ at a rate of 16%) is taken for credit not at the time of payment, but upon receipt of goods/services and registration of the incoming electronic invoice (ESF).
The result for our directory: in the package card dated 05.03.2026, you see two files — the export and the bank response. In six months during an audit, you retrieve the original of what actually went to the bank in 10 seconds using the "Save as..." button.
5. Types of operations
The directory does not have "types of operations" in the accounting sense. Practically, it is used in three modes:
- Storage of the export file — what 1C sent to the bank.
- Storage of the import/response file — the bank statement or receipt.
- Storage of EDS files — detached signatures (
.p7s) for the transmitted data.
6. What is formed when posting
The directory is not posted — it is not a document, but a list of files. Accordingly:
- There are no accounting entries. Entries are made by related payment/revenue documents (see the example above).
- Electronic documents (ESF, CNT) are not formed by this directory. ESF is issued separately from sales/revenue documents in the "ESF (IS ESF)" subsystem; CNT — for commodity operations. Exchange files with the bank are not related to them.
- This directory does not perform movements in registers. It is only linked by owner to the exchange package register/directory and stores the binary data of the file (in the database or in the file storage volumes, if the file handling library is configured).
This is normal and expected: you are facing a technical container of attachments, not an accounting document.
7. Print forms
The directory does not have its own print forms (acts, invoices) — printing the "attachment file" as a form is not required. Available actions for the file:
- Open — view in an external program by extension.
- Save as... — export the original to disk (for sending to the bank, auditor, in the archive).
- Print content — only if the file itself (for example,
pdf) supports printing in its program.
8. Frequent errors
"File not found in the file storage volume" — the volume with files is unavailable (disk is disconnected, path has changed). Correction: check the volume settings in the section "Administration" → "File Handling Settings", restore access to the volume directory. The file physically resides on the server in this volume.
"File modification is prohibited as the file is signed by an electronic signature" — you are trying to edit an attachment with EDS. Correction: signed files cannot be changed — otherwise, the signature will become invalid. If editing is really needed, remove the signature/add a new version as a separate file.
"Insufficient rights to view attached files" — the user does not have a role to work with exchange files. Correction: the administrator adds the corresponding access profile in "Administration" → "User and Rights Settings".
File 0 bytes / bank "cannot read the file" — the export was interrupted. Correction: do not "fix" the attachment, but recreate the exchange package and export it again; mark the old corrupted attachment for deletion with a comment.
"File is locked by another user" — someone has opened the file for editing. Correction: ask to finish editing or remove the lock through the list of locked files.
9. FAQ
Is this a document or a directory? A directory, specifically a service one. It is subordinate to the bank exchange package and stores the files attached to it. It does not create entries or electronic documents itself.
Where to get the original file that went to the bank? Open the required exchange package → "Attached Files" → select the export file → "Save as...". You will get an exact copy of what was sent.
Are entries (for example, Dr 3310 Cr 1030) formed from it? No. Entries for payments are made by the "Debit from Current Account" document and others. The directory only stores files.
Is ESF or CNT issued from it? No. ESF is issued from sales/revenue documents in the ESF subsystem (IS ESF), CNT — for commodity operations. Exchange files with the bank are not related to them.
Why can't I edit the attachment? Most likely, the "Signed by EDS" or "Encrypted" flag is set. Such files are protected from modification to avoid breaking the signature. Open for viewing or save a copy.
Can I delete unnecessary files to prevent the database from "bloating"? Yes, mark unnecessary attachments for deletion and delete them through "Administration" → "Delete Marked Objects". It is better to keep relevant files of submissions and bank responses — they will be useful in disputes and audits.
Where are the files physically stored — in the database or on disk? It depends on the configuration. If file storage volumes are configured, the file body resides on the server disk, and only a link is in the database. If volumes are not configured — inside the database. See "Administration" → "File Handling Settings".
How to open the directory directly, bypassing the package?
Through "Service" → "Go to Navigation Link", line e1cib/list/Directory.BankExchangePackageAttachedFiles. This mode is for diagnostics; usually, work is done from the package card.
What to do if the bank did not accept the file? Do not edit the attachment. Recreate and re-export the exchange package, and mark the old file with a comment about the reason for refusal.
Does this directory affect the calculation of VAT (16%) or taxes? No. It does not participate in calculations. The VAT rate of 16%, individual income tax, social tax, and others are calculated in the relevant accounting documents and regulatory operations, not here.
10. Related documents
- Based on what it appears: records are created in the context of the bank exchange package (exchange via DirectBank / "Client-Bank"), to which the directory is subordinate. The owner of each record is a specific exchange package.
- Related documents: "Payment Order", "Debit from Current Account", "Credit to Current Account" — these are the documents that form the entries.