Verified on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4).
You are issuing an ESF for an individual buyer, click "Send to ESF IS", and the system returns a rejection: "Recipient document type not filled in" or "Invalid identity document code". You open the buyer's card — the document details are empty, or "Foreign passport" is selected, even though the person paid with a Kazakhstan identity card. To fix this, you go to the "Individual Document Types" catalog. This is exactly where the list of document types (identity card, passport, residence permit, birth certificate) is stored, from which you select a value in the individual's card. Below is how it is structured and how to maintain it so that ESFs go through on the first try, and forms 200.00 and 910.00 are generated without manual corrections.
1. Purpose
The catalog is a classifier of identity document types. Its value is substituted into the "Document" attribute of an individual's card (buyer, responsible person, sole-proprietor employee). The value itself does not generate journal entries: it is needed for ESFs, electronic documents, and tax reporting, where the law requires specifying the recipient's document type and code.
2. Where to find it
This is a service catalog with no separate item on the sections panel. Three working ways to open it:
From the individual's card.
Master Data and Administration→Individuals(orBuyers→ card →Documenttab) → in the "Document type" field, click the selection button and, at the bottom of the list —Show all/+ Create.Via "All functions". Main menu (☰) →
Functions for a technical specialist→Catalogs→ "Individual Document Types".Direct navigation by link. Main menu →
Tools→Open URL(orCtrl+Shift+Fin some builds) and paste:e1cib/list/Справочник.ВидыДокументовФизическихЛиц
It is convenient to save the link to "Favorites" — then the catalog is always at hand.
2a. How to find your release
Help (or the ☰ icon in the top right corner) → "About the program". The window that opens shows two lines: the platform version (e.g., 8.3.24.xxxx) and the configuration release — Trade Management for Kazakhstan, edition 3.4 (3.4.5.21). Everything described below applies to release 3.4.5.21. If you have a different release, individual field labels may differ by a word or two, but the logic will not.
3. How to fill it in
The catalog card is short. Let's go through each field.
| Field | Required | Why and what happens on error |
|---|---|---|
| Name | Yes | Text you see in the selection list and that is printed in documents. Write it as it appears in the law: "Identity card of a citizen of the Republic of Kazakhstan", not "ID card". An empty name cannot be saved — you'll get the error "Field 'Name' is not filled in". Duplicates with different wording ("Identity card" and "ID card") lead to inconsistencies in reports. |
| Code | Filled in automatically | Internal code of the catalog item. Rarely changed. If you manually set a code already taken by another item, you'll get "Value of field 'Code' is not unique". |
| Document type code (exchange code / ESF IS) | Yes, if the item is used in ESFs | This is the numeric document code per the classifier sent to the ESF IS and to tax forms. This is exactly how the government system identifies the recipient's document type. An incorrect code — ESF rejection. For standard preloaded items, it's already filled in; when creating your own item, fill it in strictly according to the classifier. |
| Use (Active / Deletion mark) | — | Do not delete unneeded exotic types if they already appear in documents — mark them for deletion instead, or leave them but don't select them. Deleting an item that is in use will be blocked by "Referential integrity control". |
Practical sequence of actions when creating a new type:
- Open the catalog via the navigation link.
- Check whether the needed type already exists in the list — standard types (RK identity card, RK passport, residence permit, birth certificate, foreign citizen's passport) are usually already set up.
- If not —
Create, enter the Name according to the law's wording. - Fill in the Document type code according to the ESF IS classifier (for resident individuals this is the identity card; for non-residents — a foreign country passport).
Save and close.
4. Worked example
It's important to understand: this catalog is a classifier — it does not generate accounting entries. Journal entries are generated by sales documents, not by a catalog record. That's why the example shows exactly where the value surfaces and what an error in it turns into.
Situation. A sole proprietor under the general tax regime, VAT rate 16%. A retail buyer — individual Akhmetov A. — paid for goods worth 116,000 ₸ (VAT included). Cost of goods 70,000 ₸. The buyer requests an ESF, so his card needs a correct document.
Step 1. In the "Akhmetov A." individual's card, on the Document tab, select from the catalog Document type = "Identity card of a citizen of the Republic of Kazakhstan", enter the series/number, date, and issuing authority.
Step 2. Issue a Sale of Goods and Services. It is this document that generates the entries (the catalog has nothing to do with it), using our figures:
| Dr | Cr | Amount, ₸ | Description |
|---|---|---|---|
| 1210 | 6010 | 100,000 | Sales revenue (excl. VAT) |
| 1210 | 3130 | 16,000 | VAT 16% payable |
| 7010 | 1330 | 70,000 | Cost of goods written off |
| 1030 | 1210 | 116,000 | Payment received to current account |
Step 3. Based on the sale, create an ESF. In the "Recipient" section, the document type and its code are automatically pulled from Akhmetov's card. The ESF is sent to the ESF IS and accepted.
But if the catalog/card had the wrong type set (e.g., "Foreign passport" with someone else's code), the ESF IS would return a rejection, the sale would be left "hanging" without an electronic document, and data for the individual in form 200.00 would be compiled incorrectly. The catalog value itself doesn't move money — but without it, legally significant electronic document workflow cannot be completed.
5. Operation types
The catalog has no "operation types" in the sense of a document. Functionally its items break down as follows:
- Documents of RK residents — identity card of an RK citizen, passport of an RK citizen.
- Documents of non-residents — foreign citizen's passport, stateless person's identity document.
- Permit documents — residence permit of a foreigner in the RK.
- Other — birth certificate (for minors), military ID, driver's license (where permitted).
6. What is generated upon saving
- No journal entries. Saving to the catalog is just a new classifier item.
- No register movements either: the catalog is not a source of movements.
- The effect is indirect. The selected value is stored in the individual's attributes and from there flows into: the ESF (recipient's document code), the SNT — when issuing goods waybills where the individual needs to be identified, and into tax forms 200.00 (personal income tax/social payments), 910.00 (simplified regime). If you changed a value in the catalog retroactively — reprocess/reissue the dependent electronic documents.
7. Printed forms
A catalog item has no printed form of its own — it's a classifier. The document type's name and code are printed as part of other forms where the individual's data appears:
- recipient details in the printed form of an invoice / ESF;
- goods waybill (SNT) — the person data block;
- questionnaire and contract printed forms, where the "Identity document" line is displayed.
The catalog list itself can be printed using the standard More → Print list button (for reconciling the classifier).
8. Common errors
- "Field 'Name' is not filled in". You are trying to save an empty item. Enter the name according to the law's wording.
- "Value of field 'Code' is not unique". You manually set a code that's already taken. Restore auto-numbering or specify a free code.
- ESF IS rejection: "Invalid recipient document code". The item's document type code is not filled in or is incorrect. Open the item, set the code per the ESF IS classifier, and reissue the ESF.
- "Could not delete, object is in use…" when trying to delete a type directly. Do not delete with the Delete button — mark it for deletion, then run
Administration→Deletion of marked objects. References will show where the type is still used. - Duplicate types in the list ("Identity card" and "RK ID card"). Different ones are selected in individuals' cards — reports diverge. Keep one correct one, unmark the second for use, and reassign references using the search-and-replace values processor.
9. FAQ
Q: Does this catalog generate journal entries? A: No. This is a classifier of document types. Journal entries are generated by sales, receipt, and payment documents — the catalog just stores the document type for the individual's card, ESF, and reporting.
Q: Where is the value from this catalog selected? A: In the individual's card (buyer, responsible person), on the "Document" tab, in the "Document type" field.
Q: Do I need to set up the RK identity card myself? A: Usually not — standard types are preloaded in the delivery. First check the list; only create a new item if the needed type is missing.
Q: The ESF isn't being accepted because of the recipient's document — what should I do? A: Open the needed type in the catalog, check and set the "Document type code" per the ESF IS classifier, then reissue the ESF. Also check that the correct type is selected in the individual's card.
Q: Can an unnecessary document type be deleted? A: Not directly, if it's in use. Mark it for deletion and run "Deletion of marked objects". The program will warn you if the item has references.
Q: What's the difference between "Code" and "Document type code"? A: "Code" is the internal code of the catalog item (for numbering in 1C). "Document type code" is the code per the external classifier that is sent to the ESF IS and tax forms. For exchange purposes, it's the latter that matters.
Q: What about a foreign buyer? A: Select the type "Foreign citizen's passport" (or "Residence permit of a foreigner in the RK", if they reside in the RK) with the corresponding code. This determines the correctness of the ESF and form 200.00.
Q: Does the document type affect the calculation of personal income tax and deductions? A: The type itself — no. Tax amounts are calculated by accrual documents. But the individual's document data flows into form 200.00, so an incorrect type/code distorts reporting. As a reminder of the 2026 benchmarks: personal income tax 10% (15% above 8,500 MCI of annual income), standard deduction 30 MCI per month with MCI at 4,325 ₸.
Q: I corrected the document type in the catalog — will old ESFs update automatically? A: No. Already issued electronic documents need to be reissued for the new value to take effect in them.
Q: Why doesn't the item have a printed form? A: This is a classifier catalog. Its name and code are printed as part of the ESF, SNT, and the individual's contract forms, but the item itself has no separate printed form.
10. Related documents
- Based on what it is filled in: catalog values are selected in the individual's card (
Individuals,Buyers) — this is the main "consumer" of the catalog. - What uses the value further: the ESF (created based on
Sale of Goods and Services), the SNT, tax forms 200.00 and 910.00, contract and questionnaire printed forms. - Service processors:
Search and Replace Values(merge duplicates),Deletion of Marked Objects(remove unnecessary types).
How to find your release
Help → "About the program": the window shows the platform version (8.3.x) and the configuration release. Compare it with the note below — if the release differs, the names of individual fields may differ slightly.
This material was prepared for "1C:Trade Management for Kazakhstan", edition 3.4, release 3.4.5.21.