--- title: "Document \"Meeting\" (Documents.Встреча) — Technical Description" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-24 canonical: https://buhgpt.kz/suraqtar/dokument-vstrecha-documents-vstrecha-tehnicheskoe-opisani-en source: BuhGPT --- # Document "Meeting" (Documents.Встреча) — Technical Description > **TL;DR:** 1. Identification Parameter Value Object type Document ( Document.Meeting ) Name Meeting Synonym "Meeting" (no separate synonym specified in the export) Configuration Trade Management for Kazakhstan, edition 3.4.5.21 Subsystem CRM and Marketing → Interactions (implemented via --- 1. Identification Parameter Value Object type Document (Document.Meeting) Name Meeting Synonym "Meeting" (no separate synonym specified in the export) Configuration Trade Management for Kazakhstan, edition 3.4.5.21 Subsystem CRM and Marketing → Interactions (implemented via the SSL "Interactions" library) Numbering Type String, length 11, periodicity — Year Navigation (list) e1cib/list/Document.Meeting Navigation (object) e1cib/data/Document.Meeting 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 Name Type Required Purpose Тема (Subject) String Yes Brief subject of the meeting. Описание (Description) String Yes Detailed description / agenda. ДатаНачала (StartDate) Date Yes Date and time the meeting starts. ДатаОкончания (EndDate) Date No Date and time the meeting ends; cannot be earlier than ДатаНачала (checked during fill-in validation). МестоПроведенияВстречи (MeetingVenue) String No Address/venue of the meeting. СписокУчастников (ParticipantsList) String No Free-text list of participants (duplicates the tabular section for printing/display purposes). Важность (Importance) EnumRef.InteractionImportanceOptions No Interaction priority (low/normal/high). Автор (Author) CatalogRef.Users No The user who created the document. Ответственный (Responsible) CatalogRef.Users Yes Person responsible for the document and its outcome. ВзаимодействиеОснование (BasisInteraction) DocumentRef (Meeting, PlannedInteraction, PhoneCall, SMSMessage, IncomingEmail, OutgoingEmail) No Reference to the basis interaction; links the meeting into an interaction/correspondence chain. Комментарий (Comment) String No Free-form comment. 2.2 Tabular section Участники (Participants) Name Type Purpose Контакт (Contact) Reference (composite contact type) A meeting participant (partner, contact person, user, etc.). ПредставлениеКонтакта (ContactPresentation) String Text representation of the participant (display cache). КакСвязаться (HowToContact) String Contact method (phone, e-mail, etc.). 2.3 Service tabular sections (SSL mechanisms) Tabular section Columns Purpose НаборыЗначенийДоступа (AccessValueSets) НомерНабора (SetNumber, Number), ЗначениеДоступа (AccessValue), Уточнение (Refinement, CatalogRef.MetadataObjectIDs), Чтение (Read, Boolean), Изменение (Update, Boolean) Service tabular section of the RLS subsystem: stores access value sets for record-level access restriction. Populated by the mechanism, not edited manually. ДополнительныеРеквизиты (AdditionalAttributes) Свойство (Property, ChartOfCharacteristicTypesRef.AdditionalAttributesAndInfo), Значение (Value), ТекстоваяСтрока (TextString, String) Standard "Properties" mechanism: additional attributes configurable without changing the configuration. 3. Forms Form Role Features ФормаДокумента (DocumentForm) Main document form 166 elements, 14 input fields, 6 buttons, 1 table (Участники). Tabs: СтраницаОписание (DescriptionPage), СтраницаУчастники (ParticipantsPage), СтраницаКонтактыНеЗаполнены (ContactsNotFilledPage), СтраницаКонтактыЗаполнены (ContactsFilledPage), СтраницаДополнительныеРеквизиты (AdditionalAttributesPage), СтраницаКомментарий (CommentPage). The two "Contacts…" pages switch depending on whether the participants tabular section is filled in. ФормаВыбора (SelectionForm) Selection/list form for picking 35 elements, Список (List) table. Used when a meeting is selected as a value (e.g., when specifying an interaction basis). 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) Procedure Size Purpose ОбработкаПроверкиЗаполнения (FillCheckProcessing) ~12 lines Validation of required attributes (Тема, Описание, ДатаНачала, Ответственный) and business rule: ДатаОкончания not earlier than ДатаНачала. ПередЗаписью (BeforeWrite) ~7 lines Pre-write preparation: data normalization, calls to the interactions SSL before writing. ПриЗаписи (OnWrite) ~7 lines Actions performed on write (updating interaction links, participants, access values). ОбработкаЗаполнения (FillingProcessing) ~4 lines Default attribute filling on creation (Author/Responsible — current user) and when entered based on another object. ПриКопировании (OnCopy) ~5 lines Clearing/recalculating fields not subject to copying (dates, outcome) when created by copying. Manager module (ManagerModule) Procedure Size Purpose ОбработкаПолученияДанныхВыбора (ChoiceDataGetProcessing) ~4 lines Configuring data for document selection (filtering/presentation in selection forms). 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. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_