Verified on release 3.0.74.2 "Accounting for Kazakhstan" (edition 3.0).
A client called and claimed that the invoice you sent had "the wrong amount." The conversation was long: you agreed to reconcile the period, you promised to call back tomorrow. A week later a different manager calls — and you remember neither what was agreed nor who called. So that such conversations don't get lost, 1C has the document "Phone Call". You enter the essence of the conversation there, link it to a counterparty and a contract — and the entire history of correspondence and calls for this client is gathered in one place.
First, the main point, so you don't search in vain: this document does not create accounting entries and does not calculate taxes. It belongs to the "Interactions" subsystem, not to accounting. Below I'll go through it honestly and completely.
1. Purpose
"Phone Call" records the fact of a telephone conversation: direction (incoming/outgoing), the interlocutor, the subject, the content and the result. It is linked to a counterparty, a contract or a specific document and is placed into the general interaction feed for the client. This is a tool for memory and for monitoring performers, not for accounting.
2. Where to find it
There is no single "large" menu item for the call — it lives inside the general interactions journal and in counterparty cards:
- From the interactions journal. The section with CRM/interactions → the "Interactions" journal → the "Create" → "Phone Call" button.
- From the counterparty card. Open the counterparty → the "Interactions" command (or "More" → interactions) → "Create" → "Phone Call". This way the interlocutor and the subject are filled in automatically.
- Directly via a navigation link. Copy the line below, in 1C click "Tools" → "Go to navigation link" (or Shift+F11) and paste:
e1cib/list/Документ.ТелефонныйЗвонок
This way you'll get to the full list of all phone calls in the database.
2a. How to find out your release
The "Help" → "About" menu (or the "i" icon in the top right corner). In the window that opens you'll see two lines: the platform version (for example, 8.3.24.x) and the configuration release — "Accounting for Kazakhstan, edition 3.0 (3.0.74.2)". It is the second line that determines whether your interface matches this guide.
3. How to fill it in
Let's go through it field by field. Fields without which the document won't be posted or will lose its meaning I mark as MANDATORY.
| Field | What it's for and what happens if you make a mistake |
|---|---|
| Date and time (MANDATORY) | The moment of the conversation. The chronology in the feed is built on it. If you enter it "backdated" incorrectly — the call will end up in the wrong place in the history, and you'll decide you never agreed on anything. |
| Call type / direction (MANDATORY) | Incoming (they called you) or Outgoing (you called). This determines who the "Subscriber" is and how the feed is read. Mix it up — and you lose the meaning: it will seem that the initiative came from the wrong side. |
| Subscriber / interlocutor (MANDATORY) | Whom you spoke with: the counterparty and their contact person (or just a phone number). If you leave it empty, the call won't be linked to the client and won't appear in its history — effectively "hanging in the air". |
| Subject | A short heading line ("Discrepancy in the August act"). You use it to find the call in the list. An empty subject — and in a month you'll be opening a dozen "(No subject)" ones blindly. |
| Description / content | The essence of the conversation and the agreements. This is the main value of the document. Write specifically: "the client disputes the amount of 464,000 ₸, we promised a reconciliation by 10.09". |
| Subject item | The link to an object: contract, invoice, sale, task. It provides a jump "from the document to the call and back". If you don't fill it in — the conversation won't be linked to the deal. |
| Importance | Low / Normal / High. Affects sorting and filtering in the to-do list. |
| Responsible (MANDATORY) | The employee to whom the call is assigned. Monitoring is built on it: whose calls have not been reviewed. An empty responsible — and the call won't appear in anyone's task list. |
| Reviewed (flag) + Review date | A mark that the call has been handled. As long as the flag is cleared — the document hangs in the "not reviewed" list. This is your built-in to-do. |
| Group / folder | Optional sorting of calls by topics or projects. |
Once filled in → "Write", then "Post" (or "Post and close"). Posting here does not mean an accounting operation, but the recording of the call in the interaction registers.
4. A worked example
Situation. On September 6, 2026, the accountant of LLP "Astana-Snab" calls you and says that the amount in the act doesn't match: they have 464,000 ₸, you have 400,000 ₸ + VAT.
You create a Phone Call:
- Date:
06.09.2026 10:15 - Type: Incoming
- Subscriber: counterparty LLP "Astana-Snab", contact person — chief accountant
- Subject:
Discrepancy in the August act - Subject item: Contract No. 12 dated 01.02.2026
- Description:
The client sees 464,000 ₸ (400,000 + VAT 16% = 64,000). We have a sale posted for 348,000 ₸ (300,000 + 48,000). Discrepancy 116,000 ₸ — the second delivery note was not recorded. Promised a reconciliation and to reissue the electronic invoice by 10.09. - Importance: High; the "Reviewed" flag — cleared.
You post it. This document does not create Dr/Cr accounting entries — it only writes lines into the interaction registers (see section 6).
So where are the money and the VAT? They will appear not here, but in the documents you draw up as a result of the conversation. For example, by additionally recording the forgotten sale of 100,000 ₸ + VAT 16%, in the "Sale" document you'll get real entries at the Kazakhstan-2026 rates:
| Dr | Cr | Amount, ₸ | Meaning |
|---|---|---|---|
| 1210 | 6010 | 100 000 | Sales revenue (excluding VAT) |
| 1210 | 3130 | 16 000 | VAT payable, rate 16% |
| 7010 | 1330 | — | Write-off of the cost of goods |
That is, the call is the cause, and the entries are born in the linked accounting document. The call itself remains pure communication history.
5. Operation types
The document differs by call direction:
- Incoming — the initiator of the conversation is the client/supplier. The "Subscriber" is the one who called you.
- Outgoing — you make the call. The "Subscriber" is the one you got through to.
Additionally, the card is affected by the "Reviewed / Not reviewed" status — based on it the call is either hanging in tasks or considered handled.
6. What is generated upon posting
No entries, electronic invoices (ESF), electronic waybills (SNT) or account movements — because this is not a financial operation. Upon posting, the document makes records in the information registers of the "Interactions" subsystem:
- Interactions — the fact of the call itself enters the general feed.
- Interaction participants — the counterparty, the contact person, the interlocutor's number/address.
- Interaction subject items — the link to a contract, invoice or another object.
- Interaction states — the responsible person, importance, the "Reviewed" flag, the review date.
It is precisely these registers that make it possible to show the entire history for the counterparty and the list of unreviewed tasks.
7. Printable forms
The phone call has no separate regulated printable form — it is an internal document, not a source document. From the card you have available:
- printing the content of the conversation (description + details) — as a note for yourself or your manager;
- output to the feed/report on the counterparty's interactions.
No forms with signatures and stamps are provided here, because the document does not certify anything in external circulation.
8. Common mistakes
"The 'Subscriber' field is not filled in" (or "Participants are not filled in"). You did not specify whom you spoke with. Open the interlocutor field, select a counterparty and a contact person, or enter a phone number. Without this the call won't be linked to the client.
"The 'Responsible' field is not filled in". Enter an employee — monitoring of unreviewed calls is built on it. Usually the current user is substituted automatically, but when entering from the general list it must be specified manually.
"I'm looking for entries — there are none". This is not an error. The "Dr/Cr" button is empty because the document is by its nature not an accounting one. If you need entries — draw up a sale, receipt or task based on the call.
The call "disappeared" from the client's history. This means you didn't fill in the "Subject item" or specified the wrong counterparty. Open the document, correct the interlocutor/subject item and repost.
Duplicates for one conversation. Two employees created a call independently. Agree to record incoming calls only through the counterparty card and to mark "Reviewed" — this way duplicates are visible right away.
9. FAQ
Does "Phone Call" make entries to accounts 1210, 6010, 3130? No. This is a document of the "Interactions" subsystem. It writes only to the interaction registers. Entries and 16% VAT appear in accounting documents (sale, receipt) that you create as a result of the conversation.
Is an electronic invoice (ESF) or electronic waybill (SNT) generated from a call? No. Electronic invoices and SNT are issued from sale/transfer documents, not from a phone call.
How can I view all calls for one counterparty? Open the counterparty card → the "Interactions" command. There, in the feed, will be all calls, letters and meetings. The condition is that the interlocutor/subject item is correctly specified in the call.
How does "Incoming" differ from "Outgoing"? Only in direction: incoming — they called you, outgoing — you called. This does not affect accounting, but it sets the correct reading of the communication history.
What does the "Reviewed" flag mean? It is a mark of "the call has been handled". As long as it is cleared, the document hangs in the list of unreviewed interactions as a reminder. Set the flag and the date when you close the issue.
Can I draw up an invoice or a sale directly from the call? Yes — via "Create based on". This way the subject item and counterparty are transferred to the new document, and the link between the conversation and the deal is preserved.
Is it mandatory to post the document? Yes, it is advisable to post it — then the records enter the registers and the call appears in the feeds and reports. A merely "Written" call may not display correctly in the history.
Does a call affect VAT, individual income tax, social tax or reporting? Not at all. It does not participate in tax calculation and does not appear in any declarations or in the tax accounting registers. All the Kazakhstan-2026 rates (VAT 16%, individual income tax 10%, the 30 MCI deduction, etc.) concern other documents.
Should I delete or mark for deletion an erroneous call? Mark it for deletion and delete it via "Deletion of marked objects". Direct deletion of a posted document is blocked so as not to break the links in the registers.
Can I attach a file to the call (a recording of the conversation, a scan)? Yes, via the attached files panel in the document card — the recording or a photo of the act is stored together with the call.
10. Related documents
- Based on what it is created: usually from the card of a Counterparty or a Contact person, as well as from another interaction along the conversation chain. It can be opened from a Contract or an Invoice as a reaction to them.
- What is drawn up based on the call: a Planned interaction (call back/meet), a Task/Reminder, and by business results — an Invoice for payment, a Sale of goods and services, a Receipt — it is there that real entries, electronic invoices and 16% VAT are born.
How to find out your release
The "Help" → "About" menu: the top line is the 1C:Enterprise platform version, the line below is the configuration release. If yours is not 3.0.74.2, individual field labels and button locations may differ slightly, but the document's logic is the same.
This guide was prepared for "Accounting for Kazakhstan", edition 3.0, release 3.0.74.2.