Document "Meeting" (Documents.Встреча) — Technical Description

1. Identification

Purpose. "Meeting" is an element of the interactions subsystem (CRM): the document plans and records a meeting with a client or partner — start and end date, participants, subject, venue, and outcome. It is used to maintain the history of communications with a counterparty. The main user is a sales manager; path: "CRM and Marketing" section → "Interactions".

Important for the KZ-2026 configuration context: tax accounting parameters (VAT rate 16%, MCI 4,325 ₸, minimum wage 85,000 ₸, basic IIT deduction 30 MCI/month, etc.) relate to the financial documents of the configuration. The "Meeting" document is an organizational CRM object and does not generate any tax, inventory, or cash movements by itself (see Section 5). These figures are provided as a reference point for the KZ corporate standard and are not involved in posting this object.

2. Header attributes and tabular sections

2.1 Header attributes

2.2 Tabular section Участники (Participants)

2.3 Service tabular sections (SSL mechanisms)

3. Forms

No separate list form is defined in the export — the list is opened via the standard link e1cib/list/Document.Meeting.

4. Key module procedures

Below are the handlers based on BSL static analysis data (names verbatim from the export).

Object module (ObjectModule)

Manager module (ManagerModule)

Dependencies on common modules

Calls: Пользователи (Users) (2), ОбщегоНазначения (Common) (1), СозданиеНаОсновании (CreateOnBasis) (1) — working with the current user/rights, common service functions, and the create-on-basis mechanism.

5. Posting and movements

According to RegisterRecords static analysis data, the object is empty — the document does not generate any movements.

• "Meeting" is a CRM document of the "Interactions" subsystem. It does not create accumulation register movements (goods, settlements, cash, prices) and does not generate Dr/Cr accounting entries.
• Accordingly, the standard KZ chart of accounts (1210 — short-term receivables from customers, 1030 — cash in current accounts, 1330 — inventory, 3310 — payables to suppliers, 3130 — VAT payable, 6010 — sales revenue, 7010 — cost of sales), as well as VAT calculation at the 16% rate and electronic documents (ESF in the ESF IS, waybills), do not apply to this object — they relate to the configuration's inventory/financial documents (sales, receipts, invoices).
• The effect of writing the document is limited to the interactions subsystem: recording the fact of the meeting in the counterparty's communication history, updating interaction subjects/chains and access value sets (RLS). The "posted" flag on the document reflects the completeness/relevance of the interaction, not financial movements.

Requires verification (version-dependent): the exact set of service information registers of the "Interactions" subsystem (e.g., interaction subject and folder registers) that the SSL mechanism may write to when the object is recorded — this is determined by the SSL implementation in a specific release, not by the document's own module.

6. Related objects and create-on-basis

• Interaction chain. Via the ВзаимодействиеОснование attribute, a meeting is linked to other interaction documents: Meeting, PlannedInteraction, PhoneCall, SMSMessage, IncomingEmail, OutgoingEmail. This allows different contacts to be gathered into a single subject/correspondence thread.
• Create on basis. The presence of a call to the common module СозданиеНаОсновании (CreateOnBasis) indicates the document's participation in the create-on-basis mechanism — both as a basis (creating another interaction/task from a meeting) and as a result (creating a meeting based on another interaction). ОбработкаЗаполнения transfers data from the basis.
• Participants and contacts. The Участники tabular section and the service form pages link the document to contact catalogs (partners, contact persons, users).
• Users. Автор (Author) and Ответственный (Responsible) are references to the Users catalog.
• Additional attributes/information. Linked to the AdditionalAttributesAndInfo chart of characteristic types.

7. Extension points

• Object module. Overridable/extendable handlers: ОбработкаПроверкиЗаполнения (add custom agenda/participant checks), ПередЗаписью and ПриЗаписи (integrations, auto-tasks, notifications), ОбработкаЗаполнения (fill-in rules from basis objects), ПриКопировании.
• Configuration extension (SSL-compatible). Adding attributes via the "Additional Attributes and Information" mechanism without removing support; subscriptions to ПередЗаписью/ПриЗаписи events.
• Forms. Extending ФормаДокумента (additional tabs, command bar, response to switching between "Contacts filled/not filled" pages) and ФормаВыбора (additional filters) via form extensions.
• Manager. ОбработкаПолученияДанныхВыбора — a point for custom filtering when selecting meetings.
• Create on basis. Via СозданиеНаОсновании — registering new create-on-basis scenarios (e.g., creating a task/assignment based on meeting outcomes).
• RLS. The НаборыЗначенийДоступа tabular section — integration with record-level access restriction; extended by configuring profiles and access rules rather than editing the document.