--- title: "Document \"PlannedInteraction\" - Technical Description (Accounting for Kazakhstan 3.0.74.2)" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-07 canonical: https://buhgpt.kz/suraqtar/dokument-zaplanirovannoevzaimodeystvie-tehnicheskoe-opisa-en source: BuhGPT --- # Document "PlannedInteraction" - Technical Description (Accounting for Kazakhstan 3.0.74.2) > **TL;DR:** 1. Identification of the Object Parameter Value Object Type Document (Documents) Name PlannedInteraction Full Name Document.PlannedInteraction Synonym “Planned Interaction” Configuration Accounting for Kazakhstan, edition 3.0 (release 3.0.74.2) Subsystem Standard Subsystems (C --- 1. Identification of the Object Parameter Value Object Type Document (Documents) Name PlannedInteraction Full Name Document.PlannedInteraction Synonym “Planned Interaction” Configuration Accounting for Kazakhstan, edition 3.0 (release 3.0.74.2) Subsystem Standard Subsystems (CRM / Interactions) Numbering String, length 11 characters, periodicity — within a year Posting The document is not posted in the accounting sense (see section 5) Purpose. The document is intended for planning future business contacts with counterparties and partners — meetings, phone calls, preparation of outgoing letters. It is used by sales managers, marketers, and customer service staff to structure the schedule of interactions. This is a reference-organizational tool of the relationship management subsystem; it does not affect accounting and tax records. Based on it, real interaction documents (Meeting, Phone Call, Outgoing Email) are created. Where to find in 1C. Section “Standard Subsystems” → “Planned Interaction”. Navigation link: e1cib/list/Document.PlannedInteraction 2. Attributes of the Header and Table Parts 2.1 Header Attributes Attribute Purpose Mandatory Number Auto-numbering, string 11 characters Filled by the system Date Date of registration of the interaction plan Filled by the system Subject Brief subject of the planned interaction Mandatory Description Detailed description of the planned contact Mandatory Responsible Employee responsible for executing the plan (used in the scenario of group transfer of responsibilities) By standard logic Start Date / End Date (planned) Time frame of the planned interaction By standard logic If the attributes Subject or Description are not filled, the system will not allow saving/posting the document and will issue an error of the type “Field … is not filled”. 2.2 Table Part “Participants” Column Purpose Mandatory ContactRepresentation String representation of the interaction participant (contact/counterparty) Mandatory Contact Reference to the contact/counterparty directory item By standard logic If the ContactRepresentation column is empty, the document will not be saved — an error “Field … is not filled” will be issued. 3. Forms Form Purpose Document Form (DocumentForm) Main form for entering and editing the plan: subject, description, participants, deadlines List Form (ListForm) View and selection of planned interactions; entry point via navigation link Selection Form Selecting a document from the list when entering references in other objects Processing of Group Change of Responsibilities Mass transfer of plans from one employee to another (scenario 3.5) 4. Key Module Procedures According to evidence, individual BSL lines are not attached; below are standard handlers for this type of object in the standard configuration. Object Module: - FillingProcessing — filling in attributes when entering based on (incoming letter, counterparty). - FillingCheckProcessing — control of mandatory fields (Subject, Description, ContactRepresentation). This is where messages “Field … is not filled” are generated. - PostingProcessing — absent (the document does not generate postings). Form Module: - Handlers for adding a participant, including creating a new contact directly from the form (scenario 3.4). - Commands for creating actual interactions based on the plan. Typical error from the code (release 3.0.68.1): “Invalid object call on the client.” — occurs in the object module when attempting to call a server method from the client context. Requires checking a specific condition in the current release 3.0.74.2 (version-specific). 5. Posting and Movements The document does not generate accounting postings and movements in the accounting registers. The modules do not contain PostingProcessing. This is a reference-organizational document of the interaction subsystem, it does not affect accounting and tax records. Accordingly, this document does not apply to: - postings to RK accounts (for example, 1210, 1030, 1330, 3310, 3130, 6010, 7010); - calculations of VAT (rate 16% in 2026), PIT, pension contributions, social health insurance, etc.; - formation of electronic documents ESF (ESF IS) and STS. These mechanisms are involved in real accounting documents (sales, receipts, payroll), which may arise as a result of effective interaction, but not in the plan itself. 6. Related Objects and Input Based On Input based on — based on this document, the following are created: - Document.Meeting - Document.PhoneCall - Document.OutgoingEmail This document can be input based on: - incoming email (scenario 3.2 — planning a response/meeting); - contact/counterparty (initiated contact, scenario 3.1). Data source directories: contacts, counterparties, partners, employees (Responsible). Typical Scenarios No. Scenario When Applied 3.1 Creating a new interaction plan Request from a client or initiated contact 3.2 Creating based on an incoming letter The letter requires a planned response/meeting 3.3 Implementing the plan — creating actual interaction It is time for execution 3.4 Adding a contact directly from the form The participant is not in the contact directory 3.5 Group change of responsibilities Transfer of plans during employee leave/termination 7. Extension Points - Additional attributes and information (properties subsystem) — adding user characteristics to the plan without changing the configuration. - Configuration extensions — overriding FillingCheckProcessing, adding custom commands for creating interactions to the form. - Event subscriptions — response to document recording (notifications to the responsible person, integration with the calendar). - Input based on — expanding the list of created interaction objects. - Group processing — using the mechanism for changing responsibilities for integration with HR processes. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_