Directory "Counterparties" (Catalogs.Контрагенты) — Accounting for Kazakhstan 3.0

1. Identification

Purpose. The “Counterparties” catalog is the central element for accounting mutual settlements in the configuration. It stores complete registration and contact data of partner organizations (buyers, suppliers), individual entrepreneurs, and individuals with whom business activities are conducted. The catalog is a mandatory attribute (analytics) in sales, purchase, and mutual settlement documents; it is used when calculating accounts receivable/payable, generating ESF and SNT, and preparing VAT tax reporting. Frequency of use is daily; it is accessed by all accounting staff and sales/purchasing departments.

Where to find it in 1C:

• Section “Purchase” → “Counterparties”, section “Sales” → “Counterparties”, as well as “Catalogs” → “Counterparties”.
• Navigation link: e1cib/list/Справочник.Контрагенты

2. Attributes and tabular sections

2.1 Header attributes

In addition to those listed, the catalog also has the standard common attributes (Код, Наименование, Родитель, ПометкаУдаления), as well as activity-type attributes and the “Buyer”/“Supplier”/“Other relations” indicators — used for quick filtering in lists.

2.2 Tabular sections (standard composition)

Subordinate objects (БанковскиеСчета, ДоговорыКонтрагентов, КонтактныеЛица) are physically separate catalogs with the owner Контрагенты, but from the user's perspective they are edited on the counterparty's forms.

3. Forms

4. Key module procedures

The evidence does not contain the BSL code of the modules, so below are typical handlers for a catalog of this kind in BK 3.0. The specific procedure names should be verified in the Configurator.

Object module (ОбработкаЗаполнения, ПередЗаписью, ОбработкаПроверкиЗаполнения):

• ОбработкаПроверкиЗаполнения — checks that ЮрФизЛицо is filled in (ShowError reaction), controls the correctness of BIN/IIN (12 digits, check digit), and the uniqueness of the identification code.
• ПередЗаписью — control of circular references via ГоловнойКонтрагент, normalization of RNN/BIN/IIN (removing spaces).
• ОбработкаЗаполнения — when entering on the basis of another object, sets СтранаРезидентства = Kazakhstan by default.

Item form module (ПриСозданииНаСервере, ЮрФизЛицоПриИзменении, ИдентификационныйКодЛичностиПриИзменении):

• ПриСозданииНаСервере / УстановитьВидимостьДоступность — toggles field visibility (for an individual, the VAT certificate details and KBE are hidden and SIK/IIN are shown; for a legal entity — vice versa).
• ЮрФизЛицоПриИзменении — recalculates the visibility and labels of fields (BIN↔IIN).
• ИдентификационныйКодЛичностиПриИзменении — control of length and checksum, checking for duplicates against the SRC.
• Contact information handlers (КонтактнаяИнформация…) — the standard SSL subsystem “Contact information”.

The catalog does not generate records — it has no posting procedures (it is not a document).

5. Posting and records

The “Counterparties” catalog does not create register records on its own. It acts as analytics (subconto) in the postings generated by mutual settlement documents. Below are typical postings under the RK chart of accounts, where the Counterparty is an object of analytics (RK VAT rate as of 2026 — 16%, currency — tenge ₸).

Sale to a buyer (account 1210 “Short-term accounts receivable from buyers”):

Example: a sale of 116,000 ₸ including VAT → 1210/6010 = 100,000 ₸, 1210/3130 = 16,000 ₸ (16%).

Payment from a buyer:

Receipt from a supplier (account 3310 “Short-term accounts payable to suppliers”):

Payment to a supplier:

Registers where the Counterparty is a dimension: “Mutual settlements with counterparties”, “Settlements with buyers”, “Settlements with suppliers”, VAT accounting registers (for matching with ESF).

6. Related objects and entry on the basis

Subordinate objects (owner — Counterparties):

• Справочник.ДоговорыКонтрагентов
• Справочник.БанковскиеСчета
• Справочник.КонтактныеЛица

Documents using the Counterparty as an attribute/analytics:

• Sales: “Sales of goods and services”, “Invoice for payment to buyer”, “Invoice (issued)” / ESF (ESF IS), “SNT” (accompanying waybill for goods).
• Purchases: “Receipt of goods and services”, “Invoice (received)” / incoming ESF.
• Money: “Payment order”, “Receipt to the settlement account”, “Write-off from the settlement account”, cash orders.
• Mutual settlements: “Debt adjustment”, “Mutual settlement reconciliation report”.

Entry on the basis (typical): from a catalog item you can create an “Invoice for payment to buyer”, “Sale”, “Receipt”, “Contract”, as well as request a reconciliation. The Counterparty is substituted into the owner attribute and into the mutual settlement analytics.

Integration: the Counterparty data (BIN/IIN, VAT certificate, address) is exported to the electronic documents ESF and SNT; the identifiers are used when exchanging data with the SRC and verifying the counterparty.

7. Extension points

• Event subscriptions (ПередЗаписью, ПриЗаписи) of the catalog — for additional BIN/IIN validation, auto-fill from external services.
• Configuration extension: adding attributes (e.g., customer segment, manager), overriding the item form without removing it from support.
• Additional attributes and information (SSL subsystem “Properties”) — custom characteristics without changing metadata.
• Integration rules (Enterprise Data / CD 3) — synchronization of counterparties with UT/ZUP.
• Catalog manager modules — for programmatic search/creation of a counterparty by BIN from external data processors.
• Counterparty verification — connecting a service for checking VAT payer status and registration status with the SRC.

Reference RK norms for 2026 (context for related calculations)

These norms are applied in calculation documents (payroll, tax liabilities), not in the catalog itself; they are provided for consistency of the numerical examples in postings and reporting.