Verified on release 3.0.74.2 "Accounting for Kazakhstan" (edition 3.0).
A counterparty has sent you an incoming document via EDI — for example, an ESF for goods. You opened it, but what you need is not the object in 1C itself, but the attachment: a PDF to print and file, an XML to verify the details, or a signature file to prove that the document was signed with the supplier's digital signature. All these attachments are stored in the reference book "ElectronicDocumentIncomingEDIAttachedFiles". This is not a document you create manually — it is a "pocket" of files that arrived together with the incoming electronic document. Let's figure out how to navigate it, lose nothing, and quickly retrieve the needed attachment.
1. Purpose
The reference book stores files attached to a specific incoming electronic EDI document: the XML of the document itself (ESF, SNT, waybill, act), the PDF visualization, electronic signature files (.p7s/.sig), and sometimes accompanying attachments from the counterparty. Each entry is subordinate to its incoming document (owner) and lives together with it.
2. Where to find it
This service reference book is usually not opened directly through the menu — the files are visible right from the incoming document card. The practical path:
- Sales / Purchases → Electronic Document Management → Incoming electronic documents (depending on the setup — "Current EDI tasks" or "EDI Archive");
- open the needed incoming document → the block/hyperlink "Attached files" (or the paperclip icon) → before you is a list of files, and these are the items of this reference book.
You can open the full object list (for example, for searching or a technical check) via a navigation link. Tools → "Go to navigation link" and paste:
e1cib/list/Справочник.ЭлектронныйДокументВходящийЭДОКПрисоединенныеФайлы
2a. How to find out your release
Help → About the program (or the "i" icon in the top right corner). In the window that opens, you can see the version of the "1C:Enterprise" platform and the configuration release — a line like "Accounting for Kazakhstan, edition 3.0 (3.0.74.2)". Check the first three or four digits: the arrangement of buttons and the set of fields may differ slightly between releases.
3. How to fill it in
You do not fill in this reference book manually — entries are created automatically when 1C receives an incoming electronic document and sorts its attachments into files. Therefore, "filling in" here means reading and checking the fields. What is important to understand in each field:
| Field | Why it exists and what happens if it's wrong |
|---|---|
| Name (required) | The file name as it appears in the list. You use it to find the needed attachment (for example, ESF_...xml versus Print.pdf). If the name is empty or truncated, the file opens, but it's hard to find it in a list of a dozen attachments. |
| Owner (required) | A link to the incoming electronic document to which the file belongs. This is the "file ↔ document" connection. If you see a file "without an owner" — it has been orphaned, and when the document is deleted such a file will not be cleaned up. |
| Extension | xml, pdf, p7s, sig. Determines what the file opens with. It is precisely by the extension that you distinguish the machine-readable XML from the human-readable PDF. |
| Size | Volume in bytes. Zero size is an alarming sign: the file arrived "empty," there is nothing to open, and the document needs to be re-requested. |
| File storage (data) | The file content itself (in the database or in storage volumes). The "Open" and "Save" buttons work from here. If the storage is unavailable, the file is in the list but cannot be opened. |
| Signed with ES | An indicator that the file has an electronic signature. By it, you understand whether legal significance can be proven. |
| Encrypted | The file is encrypted — first decryption with a certificate, then opening. |
| Author / Creation date / Modification date | Service history: who added/modified the file and when. Useful when analyzing disputed situations. |
| Deletion mark | A file marked for deletion does not participate in work and is deleted by the standard deletion processing. |
The buttons you actually use: "Open" (viewing), "Save as…" (export to disk), "Verify signature"/"Show signature data", "Update from file on disk" (for your own attachments).
4. A worked example with figures and postings
A supplier sent you an incoming ESF via the ESF IS for a batch of goods. The amount is 1,160,000 ₸, including VAT at the rate of 16%. Three files were automatically attached to the incoming document (these are the items of our reference book):
| Name | Extension | What it is |
|---|---|---|
ESF_JSC_Supplier_2026-09-07.xml |
xml | Machine-readable ESF — details are pulled from it |
ESF_print.pdf |
Visualization for printing and filing | |
ESF_signature.p7s |
p7s | The supplier's electronic signature |
You open the PDF, verify the amount, check the signature (.p7s), and from the XML you fill in the "Receipt of goods and services" document. The file reference book itself does not make postings — the entries are formed by the receipt document, for which these files serve as the basis. On the given figures, the receipt produces:
| Dr | Cr | Amount, ₸ | Description |
|---|---|---|---|
| 1330 | 3310 | 1,000,000 | Goods received (excluding VAT) |
| 1420 | 3310 | 160,000 | VAT for offset (16% of 1,000,000) |
Total debt to the supplier on account 3310 — 1,160,000 ₸. Check: 1,000,000 × 16% = 160,000 ₸; 1,000,000 + 160,000 = 1,160,000 ₸.
When you sell this same product, say, for 1,740,000 ₸ including VAT (net 1,500,000, VAT 240,000), the sale produces: Dr 1210 Cr 6010 — 1,500,000; Dr 1210 Cr 3130 — 240,000 (VAT payable); Dr 7010 Cr 1330 — 1,000,000 (cost of goods sold written off). And the PDF and XML of the incoming ESF will remain attachments in our reference book — your proof of the right to offset input VAT.
5. Types of operations
The reference book does not have separate "types of operation" like a document does. In practice, files are divided by purpose:
- XML of the electronic document — the ESF/SNT/waybill/act itself in machine-readable form;
- PDF (visualization) — a printed form for a person;
- Signature file (
.p7s,.sig) — the sender's digital signature; - Accompanying attachments — additional files that the counterparty attached to the EDI package.
6. What is formed upon posting
The reference book is not posted and does not create register movements — it is a storage, not a document. When an incoming electronic document is received, the following happens:
- in the reference book, file items are created (XML, PDF, signatures), linked to the owner;
- the "Signed with ES"/"Encrypted" indicators are filled based on the package composition;
- accounting movements (postings, VAT registers, mutual settlements) are formed by the accounting document that you create on the basis of the incoming one (receipt, ESF received). The postings of such a document — see section 4.
7. Printed forms
The reference book has no printed form of its own — the content of the files is printed:
- PDF visualization of the ESF/SNT — opens and prints directly;
- Printing XML via the built-in visualization of the electronic document (the "Print" button in the incoming document form);
- Electronic signature protocol/card — signature information (who, when, certificate) via "Show signature data".
8. Common mistakes
"The file contains no data" / "Failed to open the file" — the file storage is empty (zero size) or the file did not finish downloading. Re-request the document from the counterparty or repeat the receipt from the ESF IS/EDI operator.
"Failed to verify the electronic signature" — cryptography is not set up on the workstation or the CA root certificate is missing. Install the cryptographic protection tool (NCALayer/CryptoPro), add the certificates, and repeat the check.
"A program for viewing files with the p7s extension is not installed" — you are trying to open the signature file as an ordinary document. A signature is not "read," it is verified with the "Verify signature" button, not opened.
"Owner is not filled in" — the file has lost its connection with the document (usually after an import failure). It is better to mark such a file for deletion and re-receive the document, otherwise it will not be cleaned up together with the owner.
"EDI subscription limit exceeded" — some incoming documents are not received, and attachments do not arrive. Check the state of the EDI operator's tariff and renew the subscription, then repeat the receipt.
9. FAQ
Q: Do I need to manually create entries in this reference book? A: No. Files appear automatically when an incoming electronic document is received. You only view them, save them, and verify the signature manually.
Q: Where do I get the original ESF to check the amount? A: Open the incoming document → "Attached files" → XML (machine-readable original) or PDF (visualization). The XML contains the exact details and amounts.
Q: How do I save the PDF or XML to disk? A: Select the file, "Save as…", specify the folder. This is convenient for filing documents or passing them to an auditor.
Q: The file opens empty, size 0 bytes. What should I do? A: The attachment arrived corrupted. Re-request the document from the counterparty or re-receive it from the ESF IS/EDI operator — the file will be recreated.
Q: How do I make sure the document was actually signed by the counterparty? A: The "Signed with ES" indicator and the "Verify signature"/"Show signature data" button — there you can see the certificate owner, the term, and the verification result.
Q: Can I delete an unnecessary file? A: Set a deletion mark and run "Deletion of marked objects". Remember: by deleting the original ESF file, you lose the proof of the operation — do this deliberately.
Q: Why did some incoming documents arrive without attachments? A: A common reason is that the EDI subscription limit with the operator has been exhausted. Renew the tariff and repeat the document receipt.
Q: Do these files affect VAT and postings? A: Not directly. The postings (Dr 1330/1420 Cr 3310 on receipt, VAT for offset on 1420 at the 16% rate) are made by the accounting document. But the ESF XML file is the basis of your right to offset input VAT, so it must not be lost.
Q: I can't open the .p7s file — what's wrong?
A: This is a signature file; it is not opened with a viewer but verified with the signature verification button. This requires cryptography set up on the workstation.
Q: How do I quickly find the needed attachment among many documents?
A: Open the list via the navigation link e1cib/list/Справочник.ЭлектронныйДокументВходящийЭДОКПрисоединенныеФайлы and filter by owner or by name/extension.
10. Related documents
- What it appears on the basis of: an incoming electronic EDI document (owner) — an incoming ESF from the ESF IS, an SNT, an electronic waybill/act from the EDI operator.
- What is created next: based on the received incoming document, you enter accounting documents — "Receipt of goods and services", "ESF received", receipt of services/inventory. It is precisely these that form the postings and movements in the VAT and mutual settlement registers, and the files from this reference book remain linked to them as primary confirmation.
How to find out your release: Help → About the program — there the version of the "1C:Enterprise" platform and the configuration release are indicated.
Prepared for "Accounting for Kazakhstan", edition 3.0, release 3.0.74.2.