--- title: "Types of Contact Information in 1C:Accounting for Kazakhstan 3.0 — Setting Up Addresses, Phone Numbers, and Emails" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-07 canonical: https://buhgpt.kz/suraqtar/vidy-kontaktnoy-informacii-v-1s-buhgalterii-dlya-kazahsta-en source: BuhGPT --- # Types of Contact Information in 1C:Accounting for Kazakhstan 3.0 — Setting Up Addresses, Phone Numbers, and Emails > **TL;DR:** ```html Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0). You are issuing an electronic invoice (ESF), and the "Address of location" field for the buyer is empty — and the ESF system operator rejects the document. Or you need to enter a second phone number --- ```html Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0). You are issuing an electronic invoice (ESF), and the "Address of location" field for the buyer is empty — and the ESF system operator rejects the document. Or you need to enter a second phone number and delivery address for the counterparty, but the form only allows adding one. Or the reconciliation act prints the wrong address of the organization. All of this can be fixed in one place — in the directory "Types of Contact Information". Here you set which fields (address, phone, email) are available for counterparties, organizations, individuals, and warehouses, which of them are mandatory, whether multiple entries are allowed, and whether to check for correctness. This is not an accounting directory but a service configuration directory, yet it directly affects whether your ESF will pass and what will be printed in the primary document. 1. Purpose The directory stores a list of types of contact information — "Legal Address," "Phone," "Email," etc. — grouped by owner objects (counterparties, organizations, individuals, warehouses, banks). It manages the composition of contact fields, their mandatory status, and validation rules in all cards where there is a "Contact Information" block. 2. Where to find The directory is hidden in the settings because it is filled out once during implementation: Main → Settings → Types of Contact Information. If the item is not visible — enable it through Main → Functions for Technical Specialist (mode for experienced users) or open it directly via the navigation link. 1C Navigation Link (Service → "Go to navigation link" or Ctrl+click on the address bar): e1cib/list/Directory.TypesOfContactInformation The directory itself is hierarchical: the top level consists of "sets" (groups) such as "Counterparties," "Organizations," "Individuals," "Warehouses," "Banks," "Bank Accounts." Inside each set are specific types: "Legal Address," "Actual Address," "Phone," "Email," etc. 2a. How to find out your release Help → About the Program (or the "i" icon in the upper right corner). In the opened window, you will see the platform version ("1C:Enterprise 8.3.24.…") and the configuration release ("Accounting for Kazakhstan, version 3.0 (3.0.74.2)"). Focus specifically on the configuration release — it determines the composition of predefined types and address validation settings. 3. How to fill out Open the set (for example, "Counterparties") and click Create — a contact information type card will open. Let's break down each field and what happens if you make a mistake. Field Purpose What happens in case of an error Name (mandatory) The label of the field in the card (for example, "Delivery Address"). An empty name cannot be saved. A duplicate name in one set will confuse the user — they won't understand where to write. Type (mandatory) Determines the behavior of the field: Address, Phone, Fax, Email, Web Page, Skype, Other. If you choose the type "Other" for the address, the breakdown into region/city/street will disappear, and it won't be substituted in the ESF. A phone of type "Other" will not be formatted. Group (set) (mandatory) Indicates to which object the field belongs — counterparties, organizations, etc. It is set by the group in which you clicked "Create". A type created in the wrong set will appear in other cards or not appear anywhere. Mandatory filling Requires the field to be filled before saving the owner card. Set for BIN-address if you want guaranteed clean ESFs. If removed — counterparties will be saved without an address, and the ESF will be rejected by the operator. If set unnecessarily — you won't be able to quickly create a counterparty "on the fly". Check for correctness Validates the format: for email — presence of "@", for address — filling in mandatory elements, for phone — mask. Without validation, an "email" without "@" or an address without a city will enter the database — and this is an error in the invoice. Allow multiple values Allows adding multiple lines of the same type (two phones, shipping warehouse + return warehouse). If turned off — you won't be able to enter a second phone, and you'll have to write everything in one line separated by commas. National address only For addresses in the RK, restricts input to the Kazakhstan address classifier. For a foreign counterparty, this flag will prevent entering a foreign address — remove it for "Address (foreign)". Store change history Makes the field periodic (relevant for the legal address of an organization when it changes). Available for the sets "Organizations," "Individuals". Without history, when changing the address "retroactively," the old primary document will also change. Display in list form Outputs a column with the contact directly in the list of counterparties/warehouses. Nothing critical — just convenience. Order (arrows ↑↓ in the list) The order of fields displayed in the card. Does not affect the data, only the appearance of the form. After configuring, click Save and Close. Changes are immediately applied to all cards of the corresponding set. 4. Analyzed Example Task. The logistics manager asked to store two addresses for purchasing counterparties — the legal one (used in the ESF) and the delivery address — and a second, "warehouse" phone. Currently, the counterparty card has only one address and one phone. Steps. - I open e1cib/list/Directory.TypesOfContactInformation, go to the set "Counterparties". - I check the type "Legal Address": type — Address, "National address only" — yes, "Check for correctness" — yes, "Mandatory filling" — yes (to ensure ESFs are not rejected). - I click Create. Name — "Delivery Address", type — Address, "Allow multiple values" — yes, "Mandatory" — no, "Check for correctness" — yes. I save. - I create another type: name "Warehouse Phone", type — Phone, "Allow multiple values" — yes. I save. - I open the buyer's card LLP "Astana Trade" (BIN 010203400567). In the "Contact Information" block, new fields appeared. I fill in: - Legal address: Astana, Kunaev St., 12/1, office 305; - Delivery address: Karaganda, Warehouse St., 4; - Phone: +7 (7172) 55-11-22; Warehouse phone: +7 (7212) 44-33-77. What this achieved. Now when issuing an ESF for sales to this buyer, the legal address is automatically pulled into the "Buyer Details" section. I sell goods for 1,160,000 ₸ excluding VAT, VAT at a rate of 16% = 185,600 ₸, total 1,345,600 ₸. The ESF passes validation in the ESF system because the address is filled in correctly. The sale itself generates standard entries (this is done by the "Sale" document, not our directory): Debit Credit Amount, ₸ Content 1210 6010 1,160,000 Revenue from sales (excluding VAT) 1210 3130 185,600 VAT payable, 16% 7010 1330 cost Cost of goods written off It is important to understand: the directory "Types of Contact Information" does not create entries. It only ensures that the address and phone correctly enter the ESF and primary document. However, it is precisely due to an unfilled address that the sending of the ESF is most often "failed" — therefore, setting the address as mandatory saves you time on redoing documents. 5. Types of Operations (Types of Contact Information) Through the Type field, the directory supports the following types: - Address — with breakdown into country/region/city/street/house, supporting the RK address classifier. - Phone — with formatting for country and city codes. - Fax — like phone, as a separate field. - Email (email address) — with checks for "@" and domain. - Web Page — the website of the counterparty/organization. - Skype — for the messenger. - Other — a free text string without format checks. Each set (counterparties, organizations, individuals, warehouses, banks, bank accounts) can have its own composition of these types. 6. What is generated This is a configuration directory, so it does not create accounting entries or electronic documents. The result of its work: - Records in the information register "Contact Information" — actual addresses, phones, and emails of all objects are stored there; the directory determines which specific fields can be recorded there. - Change in the composition of forms — the set and order of fields in the cards of counterparties, organizations, individuals, warehouses, banks. - Indirect influence on electronic documents: address and BIN/IIN from the cards enter the ESF (ESF system) and SNT; with an empty or incorrect address, these documents will not pass validation by the operator. 7. Printed Forms The directory does not have its own printed form — there is no need to print a list of contact types. However, the data, the composition of which it determines, is printed in: - ESF and invoice (address, BIN/IIN, phone of the buyer and supplier); - SNT (addresses of shipping/receiving points); - acts of completed work, waybills, invoices (details of the parties); - reconciliation acts (address and contacts of the organization/counterparty). 8. Common Errors "The field 'Legal Address' is not filled" (when saving a counterparty or processing an ESF). → The type has "Mandatory filling" enabled. Fill in the address in the card. If the field is not needed for a specific counterparty — remove the mandatory flag from the type, but remember: then the ESF may be rejected later. "The email address is incorrect" / "Could not recognize the address". → Validation is enabled. For email, check for "@" and domain; for the address, fill in the region and locality. For foreign addresses, remove the "National address only" flag on the corresponding type. "Cannot add more than one value of this type of contact information". → The type has "Allow multiple values" disabled. Enable the flag if you need, for example, two phones. The new type did not appear in the card. → The type was created in the wrong set (for example, "Delivery Address" ended up in "Organizations" instead of "Counterparties"). Open the type and check the owner group; if necessary, recreate it in the correct set. After changing the address, the old primary document was altered. → The type does not have "Store change history" enabled. For organizations, enable periodic storage, then old documents will retain the previous address on their date. The item "Types of Contact Information" is missing from the menu. → Enable Functions for Technical Specialist or open via the navigation link e1cib/list/Directory.TypesOfContactInformation. 9. FAQ How to add a second phone to a counterparty? Open the set "Counterparties," find the type "Phone," enable the flag "Allow multiple values" (or create a separate type, for example, "Accounting Phone"). After that, the card will have the option to add a line. Can a predefined type, such as "Legal Address," be deleted? It is not recommended to delete predefined types — they are tied to the export to ESF and reporting. If the field is not used, remove its mandatory status and hide it in the form, but do not delete it. Why is the buyer's address not populated in the ESF? The address is not filled in the counterparty's card or is filled in as a type "Other" (without breakdown into elements). Check that the type "Legal Address" is of type Address and fill in the field correctly. How to make the address mandatory for all counterparties? In the set "Counterparties," open the type "Legal Address" and enable "Mandatory filling." New cards without an address will not be allowed to be saved. What is the difference between a set (group) and a type? A set is the owner (counterparties, organizations, warehouses, etc.), the top level of the hierarchy. A type is a specific field within a set (address, phone). Types are always created within a set. How to enter a foreign address for a counterparty? Create (or open) the address type and remove the "National address only" flag — then the class ``` --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_