Checked on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4).
The supplier sent you a certificate of conformity and technical passport for a new product group — for example, "household appliances." You created an item type for it, set up the unit of measure, a 16% VAT rate, and accounting rules. And then the thought occurs: let the scanned certificate always stay next to this setting, so the manager doesn't have to search for it in email. You click "Attached files," drag the PDF in — and it lands in this service catalog. Opening it directly (or following a link to it), you'll see not a "document" in the accounting sense, but a file card: name, author, size, date, digital signature flag. Let's figure out how to work with it correctly.
1. Purpose
Catalog.ItemTypesAttachedFiles is a service storage catalog. It holds files (scans, PDFs, images, Word/Excel documents) attached to elements of the "Item Types" catalog. It is created automatically by the "File Management" subsystem and is usually not filled in separately "by hand via the menu" — you work with it from the item type card.
2. Where to find it
The standard path is from the file's owner:
- Master data and administration → Items → Item Types (or via "All functions" / search "Item Types").
- Open the needed item type.
- On the card, click the navigation panel "Attached files" (or More → Attached files).
You can open the storage itself as a list via "Main menu → File → Open" → "Go to navigation link", entering:
e1cib/list/Справочник.ВидыНоменклатурыПрисоединенныеФайлы
If there is no "Attached files" item — enable the functionality: Master data and administration → Master data and section settings → General settings → Attached files (or the "File Management" section). Without the enabled subsystem, the button will not appear.
2a. How to find out your release
"Help" (or the "i" icon) → "About the program". The window that opens shows the "1C:Enterprise" platform version (e.g., 8.3.24) and the configuration release: "Trade Management for Kazakhstan, edition 3.4 (3.4.5.21)." Check the instructions against this exact line — field locations may shift slightly between releases.
3. How to fill it in
You almost always get an individual file card automatically when uploading. But it's worth understanding each field.
| Field | Why it's needed / what happens if it's wrong |
|---|---|
| File owner (mandatory, filled automatically) | Reference to the item type the file is attached to. If you could change it manually incorrectly, the file would "drift" to the wrong group and get lost. That's why 1C fills it in automatically when uploading from the card. |
| Name (mandatory) | File name without extension. Search and sorting are based on it. Give it a vague name like "Scan1" and a month later you won't find the right certificate. Write it clearly: "Certificate of conformity household appliances 2026." |
| Extension | File type (pdf, jpg, docx). Filled in from the source file. Cannot be changed manually — otherwise the file won't open in the right program. |
| Author | The user who uploaded the file. Filled in automatically with the current user — this is your "trail" for auditing: it shows who attached it. |
| Creation date / Modification date | Service timestamps. They show relevance: if the certificate has "expired," the date tells you it's time to update it. |
| Size | File volume. Large scans (tens of MB), when stored "in the database," bloat it — see the storage option below. |
| File storage option | "In the information base" or "in volumes on disk." Affects database size and backup speed. By default — in the database; for large volumes, the administrator configures volumes. |
| Digitally signed | Flag indicating a digital signature is attached to the file. Set when signing via "More → Sign with digital signature." Not editable manually. |
| Encrypted | File encryption flag. An encrypted file cannot be opened without a certificate — don't encrypt something all managers need to read. |
| Being edited by | Who currently has the file open "for editing" (checked out). While a user holds it, others can only edit a copy. Forget to "Finish editing" — a colleague won't be able to save changes. |
Practical procedure: from the item type card → "Attached files" → "Add" → "File from disk" (or drag it with the mouse). 1C will create the catalog element itself, filling in the owner, author, date, and size. All you need to do is fix the name.
4. Worked example
Task. You have the item type "Household appliances." The supplier sent a certificate of conformity (PDF, 2.4 MB). The file needs to be stored in the database and signed with your digital signature for internal control.
Steps:
- Open the item type "Household appliances."
- Panel "Attached files" → "Add" → "File from disk", select
sert_teh_2026.pdf. - On the file card, change the name to "Certificate of conformity — household appliances (2026)".
- More → Sign with digital signature, select your certificate. A checkmark appears in the "Digitally signed" field.
Result (card values):
| Attribute | Value |
|---|---|
| File owner | Household appliances |
| Name | Certificate of conformity — household appliances (2026) |
| Extension | |
| Size | 2.4 MB |
| Author | Saparbayev A. |
| Creation date | 09/23/2026 |
| Digitally signed | Yes |
| Storage option | In the information base |
Dr/Cr entries: none — and that's correct. An attached file is not a business transaction. It does not affect any accounts in the standard chart of accounts for Kazakhstan: it doesn't touch 1330 "Goods," 6010 "Revenue," 3130 "VAT payable," and it doesn't generate an ESF or SNT. Attaching a certificate to an item type doesn't change the 16% VAT rate, cost price, or tax calculations. If you need actual accounting entries, work with sales/receipt documents — use this catalog as an "attached folder" next to the setting.
5. Operation types
The service catalog has no "operation types" in the sense of a document. Available actions on the file:
- Add — from disk, from scanner, from template, create blank.
- Open / Open card — view the file or its properties.
- Edit / Finish editing — check out the file for editing and return it.
- Save as — export a copy to disk.
- Sign with digital signature / Verify signature / Save together with digital signature.
- Encrypt / Decrypt.
- Store versions — on re-upload, the file's version history is preserved.
- Mark for deletion.
6. What gets generated during operation
- No entries. No movements in accounts, cost registers, VAT, or mutual settlements.
- No electronic documents (ESF, SNT) are created. This is a file storage, not a statement.
- Service-level movements (version-dependent): records in the file subsystem registers — binary file data; when stored in volumes, information about the file path and a deletion queue from the volume; when signing — digital signature data; when versioning — records in the versions catalog. These mechanisms work "under the hood" and are not directly visible to the user. The exact set of registers depends on the standard subsystems library version in your release — check in the configurator if needed.
7. Printed forms
The file card has no "printed forms" of its own (like TORG-12, invoice, act) — there's nothing to print, only an attachment. What's available instead:
- Open the file in the associated program and print from there (PDF, Word, Excel).
- Save as — export the file to disk.
- Save together with digital signature — export the file with the signature container (for submission to auditors).
8. Common errors
"File is checked out for editing by user …" Someone (sometimes you yourself in another session) has opened the file for editing. Wait until they click "Finish editing", or, if you have the rights, release the lock via "More → Release file".
"Insufficient rights to perform the operation on the data." The profile lacks rights for attached files. Contact your administrator — this is enabled in access group rights/profile settings.
"Failed to create/save file in volume." Storage is configured "in volumes," and the volume directory is unavailable (no rights to the network folder, disk full). Check the file storage volume settings with your administrator.
"File size exceeds the allowed limit." There's a restriction on the maximum uploaded file size. Reduce the size (compress the PDF/scan) or ask the administrator to raise the limit in the file management settings.
File attached "to the wrong place." You added the file while standing in the wrong item type. The file's owner is the object from whose card you clicked "Add." Mark the mistaken file for deletion and add it again from the correct card.
9. FAQ
(see faq block)
10. Related objects
- File owner —
Catalog.ItemTypes. It's from this card that you create elements of this storage; deleting an item type turns its attached files into "orphans." - Similar storages — most key objects have their own "…AttachedFiles" (for items, counterparties, contracts, receipt/sales documents). They work the same way.
- File versions catalog — if versioning is enabled, the file's change history is stored in a subordinate versions catalog.
- Digital signature mechanism — certificates and digital signature settings are used when signing a file (the same mechanism as for signing an ESF, but the file itself does not go to the ESF information system).
How to find out your release: "Help" → "About the program" — shows the platform version and configuration release.
Material prepared for "Trade Management for Kazakhstan," edition 3.4, release 3.4.5.21. When updating the configuration, check against your own release number.