1. Identification
| Parameter | Value |
|---|---|
| Object Type | Document (Documents) |
| Name | Meeting |
| Full Name | Document.Meeting |
| Synonym | “Meeting” (no separate synonym specified in the task) |
| Configuration | Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) |
| Subsystem | “Interactions” (CRM / contact management) |
| Conducted | No — registry document without movements in accounting registers |
Purpose. The document is intended for registering and planning personal meetings with contacts (clients, partners) in the interaction management subsystem (CRM). It is used by sales managers, customer service specialists, and executives to record the fact of a conducted or planned meeting: its topic, participants, time, and place. It ensures control over the history of contacts with external and internal participants. The meeting is created manually or based on other interaction documents (calls, letters, planned interactions). Access to the meeting is restricted on the principle of “only the author and responsible person can see it.”
Where to find in 1C: section “Standard Subsystems” → “Meeting”.
Navigation link: e1cib/list/Document.Meeting
Note: this is a document of the CRM subsystem, not an accounting document. It does not affect accounting, tax, or inventory records and does not participate in the calculation of VAT (16% in the RK from 2026), individual income tax (IIT), social tax, and other taxes — these mechanisms do not apply to the “Meeting.”
2. Header Attributes and Table Parts
Header Attributes
| Attribute | Purpose | Mandatory |
|---|---|---|
Subject |
Brief subject/title of the meeting | Yes |
Description |
Detailed description, agenda, outcome of the meeting | Yes |
StartDate |
Date and time of the meeting start | Yes |
EndDate |
Date and time of the meeting end | No (controlled for consistency) |
Responsible |
User responsible for the meeting | Yes |
Importance |
Priority (Low / Normal / High) | No |
Location |
Meeting place (address, conference room, etc.) | No |
Author |
User who created the document (for access control) | Automatically filled |
Attributes
StartDate,Description,Responsible,Subjectare declared mandatory in the configuration — if not filled, 1C will not allow saving the document and will display “Field … is not filled.”
Table Part “Participants”
| Column | Purpose | Mandatory |
|---|---|---|
ContactRepresentation |
String representation of the participant (contact) | Yes |
Contact |
Reference to the contact person / counterparty / user | No |
HowToContact |
Method of contact (phone, e-mail, etc.) | No |
Role / Type |
Role of the participant in the meeting | No |
3. Forms
| Form | Purpose |
|---|---|
DocumentForm |
Main form for creating/editing a meeting: header (subject, description, dates, responsible, importance, location) and table “Participants”. Contains handlers for time/date control. |
ListForm |
List of meetings (opens via e1cib/list/Document.Meeting), filtering by responsible, date, importance. |
SelectForm |
Selecting a meeting when picking from other interaction objects. |
| Group Change Form | Mass editing of attributes (responsible, importance) for a set of meetings (scenario 3.6). |
4. Key Module Procedures
From evidence, the following handlers are recorded (release 3.0.68.1, also relevant in 3.0.74.2):
Form DocumentForm:
EndTimeOnChange— control of the correctness of the end time. Error condition:StartOfDay(Object.EndDate) + SelectTime(EndTime) < Object.StartDate→ message “End time cannot be less than start time.”EndDateOnChange— control of the correctness of the end date. Error condition:StartOfDay(EndDate) < StartOfDay(StartDate)→ message “End date cannot be less than start date.”
Object Module (ObjectModule):
- Processing of server logic for recording; if an invalid client call to the server method occurs, it results in “Invalid object call on the client.”
Standard handlers of this type of object (general logic of CRM documents, not confirmed line by line):
CheckFilling(object module) — checks mandatory attributes (Subject, Description, StartDate, Responsible) and the columnContactRepresentationin “Participants.”BeforeRecording(object module) — setsAuthor, synchronizes with the registers of the “Interactions” subsystem (subject of interaction, status, responsible).OnCreateOnServer(form) — initializes the responsible/author with the current user, setsStartDate = CurrentDate().
Typical Errors
| 1C Message | Where it Occurs | Condition in Code |
|---|---|---|
| Invalid object call on the client. | ObjectModule | calling a server procedure from a client context |
| End time cannot be less than start time. | DocumentForm / EndTimeOnChange | StartOfDay(Object.EndDate) + SelectTime(EndTime) < Object.StartDate |
| End date cannot be less than start date. | DocumentForm / EndDateOnChange | StartOfDay(EndDate) < StartOfDay(StartDate) |
5. Conducting and Movements
The document is not conducted. In the metadata register_records is empty — “Meeting” is a registry document of the CRM subsystem “Interactions” and does not generate movements in accounting registers (accounting entries, accumulation registers of balances/turnovers, tax registers).
Practical implications:
- No entries in the standard chart of accounts of the RK (for example,
1210,1030,1330,3310,3130,6010,7010) — the meeting is not an economic operation. - No calculation and accrual of VAT (RK rate 16% from 2026), IIT, social tax, social tax for the self-employed, and other taxes — the document is of an organizational and informational nature.
- Does not generate or link to electronic documents ESF (ESF IS) and STS — these mechanisms apply to sales/purchase documents, not to interactions.
- Recording the “result” of the meeting is done through attributes (
Description, status) and links of the “Interactions” subsystem, not through movements.
6. Related Objects and Input Based On
Input based on (incoming):
- Based on the document “Letter” (scenario 3.2 — during correspondence, it was decided to hold a face-to-face meeting).
- Based on documents “Phone Call”, “Planned Interaction”, and other objects of the “Interactions” subsystem.
Related objects:
- Meeting contacts refer to directories of counterparties, contact persons, users (through the column
Contactof the “Participants” table). - The meeting is included in the overall history (feed) of interactions by subject/counterparty.
Copying (scenario 3.5): creating a new meeting by copying an existing one with a date change — convenient for planning regular meetings.
7. Extension Points
- Extension of the form
DocumentForm— adding attributes (for example, a reference to a deal/project), additional validation inEndTimeOnChange/EndDateOnChange. - Event subscriptions (
BeforeRecording,OnRecordingof the document) — integration with external calendars, notifications to the responsible person, auto-filling fields. - Additional attributes and information (PVC mechanism) — expanding the composition without modifying metadata.
- Additional processing/commands — printed forms (meeting protocol), mass change commands (scenario 3.6).
- Access control (RLS) — the rule “only the author and responsible can see” is configured through profiles/access restrictions.
- BSM mechanisms — versioning of objects, prohibition of editing by date, additional states of interaction.
Version-specific (requires verification on 3.0.74.2): the exact composition of the columns in the “Participants” table and the presence of the attribute
Location— the literal handlers from release 3.0.68.1 are provided; in a specific build, the set of form attributes may have been expanded.