Verified on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4).
You are creating a record for an individual — for example, a client's director — and want to indicate that his spouse is also a contact person of the same partner. You open the "Relations" tab, click "Add", and in the "Relation type" field search for "Spouse". But it's not in the list. There's "Relative", "Colleague", "Manager", but not the one you need. To avoid using a vague "Other", you open the "Types of relations between individuals" catalog and add the needed type. That's exactly what it does: it stores the list of types of family and business relations that you then select in people's records.
1. Purpose
This is a classifier catalog. It stores the names of types of relations between individuals (spouse, child, parent, manager, assistant, authorized person, etc.). You record the actual relations in individuals' records; the catalog just provides a ready-made list of values so that relations are filled in consistently rather than as free-form text.
2. Where to find it
This is a service catalog, without a separate item in the section panel. You can open it in three ways:
- From an individual's record: Master Data and Administration → Individuals → open a person → the "Relations" tab/section → "Add" → the "Relation type" field → "Show all" / "+". From there you go straight into this catalog.
- Via "All functions": Main menu (☰) → "All functions" → "Catalogs" → "Types of relations between individuals". If "All functions" is missing, enable it in "Tools and Settings" → "Settings" → "Parameters" → "Display the 'All functions' command".
- Via a navigation link: "Tools and Settings" → "Go to navigation link" and paste:
e1cib/list/Справочник.ВидыСвязейМеждуФизЛицами
This is the fastest way — it opens the catalog list directly.
2a. How to check your release
"Help" (or ☰ → "About the program") → the "About the program" window. The top line is the platform version (e.g., 8.3.24.x), below is the configuration release ("Trade Management for Kazakhstan, edition 3.4 (3.4.5.21)"). The instructions below are verified specifically on 3.4.5.21; in other releases the set of attributes may differ slightly.
3. How to fill it in
The item is simple — essentially it's one line of a list. But it needs to be filled in carefully, because you will see this value in all people's records.
| Field | Required | Purpose and what happens if filled incorrectly |
|---|---|---|
| Name | Yes | The text of the relation type as you will see it in the individual's record: "Spouse", "Child", "Manager". Write it from the perspective of the record's subject. Cannot be saved empty. If written ambiguously ("Relation", "Other"), no one will later understand the meaning of the entry. |
| Code | Filled automatically | Assigned automatically upon recording. No need to change it manually — it's used to order the catalog, and people's relations reference it. |
| Reverse relation name | No | What this same relation is called "from the other side". For "Parent" the reverse is "Child", for "Manager" it's "Subordinate". For "Spouse", "Colleague", "Relative" the reverse matches the direct one. By filling it in, you get a correct two-way relation: when you enter a relation in one person's record, it's correctly reflected for the second one too. The presence and exact name of this attribute is version-dependent — if your release doesn't have the field, the reverse side simply duplicates the name. |
Procedure:
- Open the catalog via the navigation link.
- Click "Create".
- Fill in the Name — briefly and unambiguously.
- If there's a reverse relation field — specify the reverse name.
- "Save and close".
Tip: create the relations once as a list at the start of your work (spouse, child, parent, sibling, manager, subordinate, assistant, authorized person) — and you won't need to return to the catalog again.
4. Worked example
Task. The partner "Ak-Zhol LLP" sent two powers of attorney: contracts are signed by director Asanov A.A., while payment orders and acts are brought by accountant Asanova G.M. — his spouse. You want to see this relation in the CRM so the manager understands they are dealing with a family, not two independent contacts.
Step 1. Open the catalog and create two types:
- Name: "Spouse", reverse relation: "Spouse".
- Name: "Manager", reverse relation: "Subordinate".
Step 2. Open the individual's record Asanov A.A. → "Relations" → "Add":
- Individual: Asanova G.M.
- Relation type: Spouse
Save. In Asanova G.M.'s record, the relation is reflected mirror-wise — "Spouse: Asanov A.A.".
Important note on postings. This is a classifier, not a document. Recording a catalog item generates no accounting entries (Dr/Cr) whatsoever, and no money or goods move. So Kazakhstan accounts (1210, 1030, 1330, 3310, 3130, 6010, 7010), the 16% VAT rate, the MCI of 4,325 ₸, and other amounts are irrelevant here — the catalog is not involved in tax or cost calculations. It only affects how relations between people are filled in within the CRM and the individuals catalog.
Where this "fires" in terms of money. Relations matter indirectly — for controlling related parties. If a counterparty's director and accountant are spouses, and you sell to that same counterparty at a preferential price, such transactions are reviewed separately during a transfer pricing audit. The classifier helps record this connection in advance, but it doesn't calculate the tax itself.
5. Operation types
The catalog has no "operation types" in the sense of a document. Available actions on an item:
- Create — add a new relation type.
- Create by copying (F9) — quickly create a similar one.
- Mark for deletion / unmark (Del) — remove an unused type from circulation.
- Save and close — save the changes.
6. What is generated upon recording
| What | Generated? |
|---|---|
| Accounting entries (Dr/Cr) | No |
| Accumulation/information register movements | No — when recording the catalog itself |
| ESF (Electronic Invoice System) | No |
| SNT (Goods Shipment Note) | No |
| Printed forms | No |
The only result of recording is that the new item becomes available for selection in the "Relation type" field of individuals' records. Actual relations between people are stored in individuals' records and the service relations mechanism; the catalog, unlike documents, has no posting.
7. Printed forms
The catalog has no printed forms of its own — there's nothing to print for a classifier. If you need to print the list, use the standard "More" → "Print list" command (Ctrl+P from the list form) — it exports the names to a spreadsheet document or Excel.
8. Common mistakes
"The 'Name' field is not filled in" You clicked "Save" with an empty name. Enter the relation type text and save.
"Could not delete 'Spouse'. The object is in use…" (when deleting) The relation type is already assigned in people's records. Direct deletion is prohibited. Correct approach: mark the item for deletion (Del), then Master Data and Administration → "Delete marked objects". The program will show where it's referenced and offer to either replace the relation with another type or remove it.
Duplicates in meaning: "Husband", "Wife", "Spouse (m)", "Spouse (f)" The program doesn't prohibit similar entries, and the list gets cluttered. Keep one neutral type "Spouse". Mark the extras for deletion and remove them via the processing tool.
The relation is visible for only one person You didn't fill in the reverse relation (or it doesn't exist in this release). Check the reverse name attribute, or also enter the relation in the second individual's record.
The needed type is missing from the record's dropdown list The item is marked for deletion — marked items aren't shown in selection. Unmark it in the catalog.
9. FAQ
Is this a document or a catalog? A catalog (classifier). It's not posted, doesn't create accounting entries, ESF, or SNT — it only stores a list of relation types for selection.
Why doesn't it have a synonym and isn't on the section panel?
This is a service catalog. It's accessed through an individual's record, "All functions", or the navigation link e1cib/list/Справочник.ВидыСвязейМеждуФизЛицами.
Does the relation type affect taxes — 16% VAT, IIT, interdependence? Directly — no, it doesn't calculate taxes. Indirectly, relations are used to analyze transactions with related parties; the actual amounts and rates come from sales/purchase documents, not from here.
How do I set up a "manager — subordinate" relation? Create the type "Manager" with the reverse "Subordinate", then in the employee's record on the "Relations" tab specify the second individual and this type.
Can an unnecessary relation type be deleted? Only if it isn't selected anywhere. Otherwise mark it for deletion and remove it via "Delete marked objects" with reference replacement.
Are dependents for the IIT deduction configured here? No. IIT calculation (basic deduction of 30 MCI per month, no more than 360 MCI per year; rates of 10% and 15%) and dependent tracking are handled in the payroll configuration, not in Trade Management. In Trade Management, this catalog serves the CRM and the individuals catalog.
Is it mandatory to fill in the "Reverse relation name"? No, but with it the relation is correctly visible from both sides. For symmetric relations (spouse, colleague, relative) the reverse matches the direct one.
How can I quickly print all relation types? From the list form: "More" → "Print list" → to a spreadsheet document or Excel.
Why are there duplicates "Wife" and "Spouse (f)" in the list? They were created manually at different times. The program doesn't block similar names. Keep one type, mark the rest for deletion.
Where did the relation type disappear from selection in the record? It's marked for deletion — such items are hidden from the selection list. Unmark it in the catalog.
10. Related objects
- "Individuals" catalog — the main "consumer": it's in the individual's record (the "Relations" tab) that you select values from this catalog.
- "Contact persons" / "Partners" catalog — through individuals, relations extend to partners' contacts and help maintain a relationship history in the CRM.
- CRM reports and lists — use the filled-in relations to group contacts; the classifier has no separate "based on" document — it's entered manually and exists independently.
How to check your release
"Help" → "About the program" (or ☰ → "About the program"): the window that opens shows the 1C:Enterprise platform version and the configuration release. Check against it — attributes and form behavior depend on the version.
This guide was prepared for "Trade Management for Kazakhstan", edition 3.4, release 3.4.5.21.