Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0).
The counterparty sent an act for 2,320,000 ₸, but your records show 2,088,000 ₸. It's hard to resolve over the phone — an in-person reconciliation is needed. You call, agree to meet on Tuesday at the office, and to ensure the meeting doesn't get lost among calls and emails, you enter it into the database. This is why the document "Meeting" is needed.
First, it's important that you don't look for something that doesn't exist. "Meeting" is a document of the "Interaction" subsystem (CRM block), not an accounting document. It does not create accounting entries, does not calculate VAT, does not generate electronic invoices (ESF) or tax returns (FNO), and does not affect the balance, trial balance, or taxes. Its purpose is to record the fact of communication: with whom, when, and what was agreed upon. Below, we will analyze it as thoroughly as accounting documents, but without invented entries — they simply do not exist here.
1. Purpose
"Meeting" records a planned or held personal meeting with the contact person of the counterparty (or a colleague). It stores participants, the topic, time, place, and outcomes, linking all correspondence and calls on a single issue into a unified chain ("Subject of Interaction").
2. Where to find
The document resides in the "Interaction" subsystem. The exact location of the item depends on the interface settings, most often:
- CRM and Sales → Interactions (or the section Sales → Interactions) → interaction journal → button Create → Meeting.
- From the counterparty or contact person card — button Create based on → Meeting.
The quickest way to open the list directly. Copy the navigation link and paste it into 1C: Service (Main Menu) → Go to navigation link (or using the menu combination "More"):
e1cib/list/Document.Meeting
Requires verification in your database: the "Interactions" item appears in the menu only when the functional option "Interactions" is enabled (Administration → Interaction Settings / CRM settings section). If the section is missing — the option is disabled, enable it or open the list using the navigation link above.
2a. How to know your release
Main menu (icon at the top left) → Help → About the program. In the opened window:
- Platform version — for example, "1C:Enterprise 8.3.24.x".
- Configuration — "Accounting for Kazakhstan", version 3.0, release (for example, 3.0.74.2).
If your release differs — the composition of fields may change slightly; the overall logic of the document remains the same.
3. How to fill in — by fields
You opened a blank form. Let's go from top to bottom.
| Field | What to write and why | What will happen if you make a mistake |
|---|---|---|
| Date | Date and time of document creation. Usually set to the current date. | Affects only sorting in the journal. Does not affect accounting. |
| Topic (mandatory) | A brief essence of the meeting: "Reconciliation of calculations according to act No. 145". This is what you will see in the list in a month. | The system will not allow an empty topic; an unclear topic — you will lose the meeting among dozens of others. |
| Start / End | Planned time of the meeting. Based on this, the meeting appears in the calendar and reminders. | If not filled in — the meeting will not appear in the calendar, you will forget about it. |
| Location | Address, conference room, "online, Zoom". Text field. | Technically does not affect anything, but participants will not understand where to go. |
| Participants (key) | Table part. Add the counterparty and their contact person (or colleague-users). Also include the participant's phone/email here. | Without participants, the meeting will not link to the counterparty and will not appear in their interaction history. |
| Description | Agenda before the meeting and outcomes after. Here you write what was agreed upon. | If you do not fill in the outcomes — you will lose the essence of the agreements. |
| Importance | Low / Normal / High. For sorting and filters. | Not critical. |
| Responsible | The user responsible for the meeting. The current user is set by default. | This is used to filter "my interactions". A different responsible person — the meeting will disappear from your lists. |
| Reviewed (checkbox) | Check when the meeting has been completed and no further actions are required. | If not checked — the meeting remains in "unreviewed". |
| Subject of Interaction | The object around which the communication revolves: counterparty, contract, transaction. Links emails/calls/meetings into one chain. | If not specified — the meeting will not pull into the history on this issue. |
After filling in — Post and Close (Ctrl+Enter).
4. Analyzed example
Situation. LLP "Astana-Snab" sent a reconciliation act for 2,320,000 ₸, including VAT 16% — 320,000 ₸ (base 2,000,000 ₸). Your records show 2,088,000 ₸, including VAT 16% — 288,000 ₸ (base 1,800,000 ₸). The discrepancy is 232,000 ₸ (one invoice for 200,000 ₸ base + 32,000 ₸ VAT not recorded on your side). You agreed to meet and reconcile.
Filling in the "Meeting":
- Date: 06.09.2026 09:15
- Topic: Reconciliation of calculations, discrepancy 232,000 ₸ according to act No. 145
- Start: 10.09.2026 11:00 · End: 10.09.2026 12:00
- Location: office, Astana, Abay Ave, 10, conference room 2
- Participants: LLP "Astana-Snab", contact person — Ivanov I.I., +7 701 000 00 00
- Subject of Interaction: Supply contract No. 7 dated 15.01.2026
- Description (agenda): reconcile turnovers for Q2 2026, find the missing invoice for 232,000 ₸
- Responsible: you
Posted. What happened:
| What we expect | What actually happened | Comment |
|---|---|---|
| Entries Dr/Cr | No | "Meeting" does not create accounting movements |
| Movements in the VAT register | No | VAT is not calculated here |
| ESF / FNO | No | Electronic documents generate invoices and waybills, not meetings |
| Movements in interaction registers | Yes | The meeting appeared in the history of LLP "Astana-Snab" and in your calendar |
After the meeting you open the document again, in Description you add the outcome: "Invoice No. 312 dated 20.05.2026 for 232,000 ₸ (base 200,000 + VAT 32,000) found. We will record it on our side, the act will be signed for 2,320,000 ₸." You check the Reviewed checkbox. The missing invoice is then entered as a separate accounting document (for example, "Receipt of goods and services") — and that will provide the entries Dr 1330 / Cr 3310 and VAT Dr 1420 / Cr 3310.
This is how "Meeting" works: it records the agreement, while money and VAT are moved by other documents.
5. "Types of operations" — that do not exist
Accounting documents have a "Type of operation" that changes entries. The "Meeting" does not have such a switch — there is only one operation. Instead, the document exists in states:
- Planned — the meeting is in the future, listed in the calendar.
- Conducted / Held — the meeting has taken place, outcomes have been recorded.
- Reviewed (checkbox) — the issue is closed, no further actions are required.
You manage the state manually: fill in the outcomes and check "Reviewed".
6. What is formed when posting
There are no accounting entries. The document writes movements to the interaction subsystem registers — it is due to these that the meeting is visible in the counterparty's history and in task lists:
- Interactions — the record of the meeting itself (topic, date, type).
- Subjects of interactions — the link of the meeting with the counterparty/contract.
- Responsible for interactions — who is leading.
- States of interactions — reviewed / not reviewed.
- Participants of interactions — list of participants for history and filters.
No ESF, FNO, or movements in the VAT and mutual settlements registers are created by the "Meeting".
7. Printed forms
Like accounting documents (invoice, waybill) — there are no printed forms for "Meeting". This is an internal working document. What is available in practice:
- Print out the list of interactions from the journal (button Print → table or More → Print list).
- Copy the text of the agenda/outcomes from the Description field into an email to participants (button to create an email based on).
8. Frequent errors
"The field 'Topic' is not filled in" — when trying to save an empty topic. Write a brief essence of the meeting and save again.
There is no "Interactions"/"CRM" section in the menu. The functional option is disabled. Go to Administration → Interaction Settings (or the CRM settings section) and enable "Interactions". Until then, open the list using the link e1cib/list/Document.Meeting.
"The meeting is not visible in the counterparty's history". The Subject of Interaction is not filled in or the Participants do not include the counterparty (only the contact person without the organization). Add the counterparty to the participants and specify the subject.
"The meeting has disappeared from my lists". A different user is set in the Responsible field. Set yourself (or use the filter "All").
Looking for entries/influence on the trial balance — they do not exist. This is not an error. If an entry is needed (receipt, payment, sale) — enter the relevant accounting document, "Meeting" is not intended for this.
9. FAQ
Questions and answers are presented in a structured block below.
10. Related documents
Based on what "Meeting" is entered:
- from the card of Counterparty or Contact Person (Create based on → Meeting);
- from another interaction — Planned Interaction, Phone Call, Email (on the same topic/subject).
What is entered based on "Meeting":
- the next interaction on the issue — Email, Phone Call, a new Meeting;
- based on the outcomes of agreements — already accounting documents separately: Invoice, Receipt of goods and services, Sale of goods and services, and based on them — ESF and if necessary FNO (the VAT rate in the RK in 2026 is 16%).
How to know your release
Main menu → Help → About the program — there you will find the platform version "1C:Enterprise" and the release of the configuration "Accounting for Kazakhstan". This instruction is compiled for release 3.0.74.2.
The manual has been checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0).