Verified on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4).
A manager visited a client, spent an hour discussing the delivery of office furniture worth 3,500,000 ₸, agreed on a discount and deadlines — and a week later went on vacation. The client calls, asks "where did we leave off," and no one in the company can answer. Sounds familiar? To prevent this, every meeting with a client is recorded with a "Meeting" document. This is not an accounting document or a "paper for the sake of it" — it's your memory of the negotiations: who was there, what was agreed, what was promised, and what the next step is.
An important note right away, so you don't go looking for postings where there are none: "Meeting" is a document of the CRM (interactions) subsystem. It does not create accounting postings, does not generate electronic invoices (ESF) or waybills (SNT), and does not move money, goods, or VAT. It lives in the CRM registers and in the client interaction history. Below is how to work with it so it brings value rather than just taking up space in the database.
1. Purpose
The "Meeting" document records the fact of in-person negotiations with a counterparty: participants, topic, agreements, and next steps. The document is linked to the client and to the deal, so the entire negotiation history is collected in one place — by client, by deal, by manager.
2. Where to find it
Interface path:
- Section "CRM and Marketing" → "Interactions" — opens a general list of all interactions (emails, calls, meetings, scheduled events). The "Create" → "Meeting" button.
- The second common entry point is from the client's card or from a deal: on the interactions tab, the "Create" → "Meeting" button. This way the document is immediately linked to the correct deal, and you won't need to fill in "Basis" manually.
To open the list directly in 1C: menu "Service" / "Functions for the technical specialist" → "Go by navigation link" and paste:
e1cib/list/Документ.Встреча
2a. How to find out your release
"Help" → "About the program" (or the "i" icon in the top right corner). In the window that opens you will see two lines: the platform version ("1C:Enterprise 8.3.24…") and the configuration release ("Trade Management for Kazakhstan", edition 3.4, version 3.4.5.21). If your version differs, individual fields and buttons may look different.
3. How to fill it in — field by field
You've opened a new "Meeting". Let's go through each field and what happens if you make a mistake.
| Field | Why it's needed and what happens if you make a mistake |
|---|---|
| Subject (required) | A short title for the meeting, by which you'll find it in the list. Leave it blank — the document won't post, and the list will turn into a mess of nameless rows. Write to the point: "Negotiations on furniture delivery, discount and deadlines". |
| Held / Scheduled (status) | A status toggle. "Scheduled" — the meeting is still ahead, it will appear in the calendar and reminders. "Held" — the negotiations have taken place, you're recording the outcome. Forget to switch to "Held" — the meeting will keep hanging in plans and nagging with reminders. |
| Start date and Duration / End date (required) | When and how long the negotiations lasted. The document's place in the timeline and calendar depends on the date. Set the wrong date — the meeting will "move" to the wrong day, and the negotiation timeline will fall apart. |
| Location | Text: office address, meeting room, city. Doesn't affect accounting, but helps restore the context. |
| Participants (key) | Two sides: our employees and the counterparty's contact persons. Add everyone who was actually there. If you don't specify a contact person, the meeting won't be "filed" into their card, and it won't be visible in that person's history. |
| Basis (Deal / Client) (key) | Link to a deal with the client or to the partner itself. This is the most important field after the subject: it's what pulls the meeting into the sales funnel and the client's history. Leave it blank — the meeting will "hang" on its own, outside the deal. |
| Importance | Low / Normal / High. Affects sorting and highlighting in the list. |
| Description (minutes) (key in practice) | Free text: what was agreed, what prices and discounts were discussed, who promised what. Not formally required, but it's the main reason the document exists at all. An empty description = a meeting with no content. |
| Responsible (required) | The employee responsible for this meeting and further actions. Defaults to the current user. Reports on manager workload are built based on the responsible person. |
| Basis interaction / In reply to | If the meeting is a continuation of a call or email, specify it. Then the entire negotiation chain will be visible. |
After filling it in — "Post and close". I also recommend right then, using the "Create based on" button, scheduling the next step (a call or meeting) and/or setting a task — otherwise the agreement will be forgotten.
4. Worked example
Situation. On September 23, 2026, manager Assel Nurlanovna held a meeting at the office of the client "Astana Office" LLP. They discussed the delivery of 20 office desks. They agreed on a price of 3,500,000 ₸ including VAT at a rate of 16% and a 5% discount. The client asked for an invoice by the end of the week.
How to record the meeting:
- Subject: "Negotiations on the delivery of 20 office desks, 5% discount".
- Status: Held.
- Start date: 23.09.2026 14:00, duration: 1 hour.
- Location: office of "Astana Office" LLP, Astana.
- Participants (ours): Nurlanova A. N.; client's contact person: Ivanov I. (procurement).
- Basis: Deal "Furniture delivery to Astana Office LLP".
- Description: "Agreed on 20 desks, price 3,500,000 ₸ including 16% VAT, 5% discount. The client is waiting for an invoice by 26.09. Payment upon delivery."
- Responsible: Nurlanova A. N.
No postings. Let me repeat this directly, because it's the main question about this document: when the "Meeting" is posted, no accounting Dr/Cr postings are generated. The amount of 3,500,000 ₸, the 16% VAT rate, and the discount live in the text as an agreement — they will enter the accounting later, when you create an "Invoice for Payment" based on this deal, and then a "Sale (act, waybill)". That's where the familiar postings of the Kazakh chart of accounts will appear:
| Event (in the sales document, not in the "Meeting") | Dr | Cr |
|---|---|---|
| Revenue from sale | 1210 "Short-term accounts receivable from buyers" | 6010 "Sales income" |
| 16% VAT on sale | 1210 | 3130 "VAT payable" |
| Write-off of cost of goods sold | 7010 "Cost of sales" | 1330 "Inventory" |
| Receipt of payment | 1030 "Cash in current accounts" | 1210 |
In other words, the "Meeting" is a step before accounting. Its value is that the figures and terms from the example won't be lost and will form the basis of the invoice.
5. Transaction types
The "Meeting" does not have a separate "Transaction type" field. Functionally, the document works in two states:
- Scheduled meeting — an event in the future. Appears in the calendar and in the responsible person's reminders.
- Held meeting — a record of the fact and results of negotiations that have already taken place.
Additionally, a meeting can be standalone (just tied to a client) or part of a deal — this determines which sales funnel it falls into.
6. What is generated upon posting
Once again, to manage expectations: this document does not create accounting postings, movements of money, goods, or VAT, nor does it generate ESF or SNT. ESF and SNT are generated from sales/transfer documents, not from a CRM meeting.
When posted, the "Meeting" makes movements in the registers of the "Interactions" subsystem:
- Interactions — the fact of the interaction itself, date, type "Meeting", responsible person.
- Interaction participants — the list of our employees and the client's contact persons.
- Interaction subjects — the link to the deal/client (that very "Basis"), thanks to which the meeting is visible in the client's history and in the deal.
- Interaction states — marks "reviewed / under control", processing status.
It is precisely these movements that ensure the meeting is visible in the calendar, in the list of interactions, and in the client's card.
7. Printed forms
"Meeting" is an internal CRM document, and it has no dedicated regulated printed form (you don't print an invoice or waybill from it — other documents do that). In practice, the results of a meeting are used as follows:
- the text from the "Description" field is copied into a letter to the client or into internal minutes;
- if needed, the on-screen form is printed using platform tools ("More" → "Print list" or the system's form printing) — for internal use.
8. Common errors
"The 'Subject' field is not filled in" — when trying to post an empty meeting. Fill in a meaningful subject for the negotiations and post again.
"The 'Responsible' field is not filled in" — remove the auto-fill flag or select the employee manually. Without a responsible person, the meeting won't appear in manager workload reports.
The meeting is not visible in the deal / in the client's history. The cause is almost always the same — the "Basis" (deal or partner) is not filled in. Open the document, specify the basis, and re-post.
The meeting "hangs" in reminders after the negotiations. You forgot to switch the status from "Scheduled" to "Held". Open it and change the status.
"Start date is later than the end date" / illogical duration. Check the start time and duration — mixed-up fields send the meeting to the wrong day on the calendar.
9. FAQ
Q: Does "Meeting" create accounting postings? A: No. It's a CRM document. Postings, 16% VAT, and the write-off of cost of goods sold appear later — in the invoice and sale that you create based on the deal.
Q: Does "Meeting" generate ESF or SNT? A: No. Electronic invoices (ESF system) and SNT are issued from sales and transfer documents, not from a meeting.
Q: Where can I find all meetings for a specific client? A: On the partner/client's card, on the interactions tab, or in the "CRM and Marketing → Interactions" list, filtered by subject. The key is that the meeting has "Basis" filled in.
Q: How do I link a meeting to a deal? A: Fill in the "Basis" field by selecting the deal. It's more convenient to create the meeting directly from the deal — then the link is filled in automatically.
Q: Can I schedule a meeting for the future? A: Yes. Set the status to "Scheduled" and a future date — it will appear in the calendar and in the responsible person's reminders.
Q: How do I schedule the next step from a meeting? A: The "Create based on" button → scheduled interaction / call / meeting, or set a task for the responsible person.
Q: Where do I record the amount and terms of the deal that were agreed upon? A: In the "Description" field as text. Record the amount, the 16% VAT rate, and the discount there; they will enter the accounting figures later through the invoice and sale.
Q: Can I add several contact persons from the client? A: Yes, in the "Participants" block add everyone who was present — both your employees and the counterparty's contact persons.
Q: Why doesn't "Meeting" have a printed waybill or invoice? A: Because it's a negotiation document, not a shipping one. Printed forms for invoices, waybills, and ESF belong to sales documents.
Q: How do I mark a meeting as processed and remove it from control? A: Through the interaction state status ("reviewed"/remove "under control") — this removes it from active tasks.
10. Related documents
What a meeting can be based on:
- Client deal — most often the meeting is created directly from the deal.
- Another interaction (call, email, scheduled interaction) — as a continuation of the negotiation chain.
What is created based on a meeting:
- Scheduled interaction / Call / Meeting — the next step in working with the client.
- Task / assignment for the responsible person.
- Further down the funnel (already outside of CRM interactions) — Invoice for payment and Sale (act, waybill) for the deal, where postings, ESF, and SNT arise.
How to find out your release: "Help" → "About the program" — this shows the "1C:Enterprise" platform version and the configuration release.
This guide was prepared for "Trade Management for Kazakhstan", edition 3.4, release 3.4.5.21.