--- title: "Directory \"Data Area Messages\" in \"Accounting for Kazakhstan\" 3.0: Service Object for Data Exchange Between Areas" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-07 canonical: https://buhgpt.kz/suraqtar/spravochnik-soobshcheniyaoblasteydannyh-v-buhgalterii-dly-en source: BuhGPT --- # Directory "Data Area Messages" in "Accounting for Kazakhstan" 3.0: Service Object for Data Exchange Between Areas > **TL;DR:** Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0). Let's get straight to the point to save time. "DataAreaMessages" is not an accounting document . There are no VAT amounts, no debit/credit entries, no electronic invoices (ESF), no tax returns. This is a se --- Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0). Let's get straight to the point to save time. "DataAreaMessages" is not an accounting document. There are no VAT amounts, no debit/credit entries, no electronic invoices (ESF), no tax returns. This is a service (technical) directory of the data separation mechanism, which works only in a cloud (service) model — for example, when you are working in "1C:Fresh" or in your corporate service model. If you were looking for where to enter an act or invoice, this is not the object; close it and return to the "Purchases" or "Sales" section. Below is an honest guide for those who really need this directory: service administrators and technical support specialists. Real Situation You are the administrator of a cloud database. A user calls: "The program shows a message that the subscription limit has been exceeded, although the tariff is paid." Or conversely — the new tariff has been paid, but the working database does not "see" it: access has not been opened. Information about the subscription, limits, and rights does not come to the working data area instantly, but as a message from the service area manager. If such a message is stuck in the queue or has not been processed — this is exactly where, in the "DataAreaMessages" directory, you will see it. You open the list, find the untransmitted message, check the status — and understand whether to fix the queue or wait for the scheduled task. 1. Purpose The directory stores messages exchanged between data areas within a single information database operating in a service model (multi-tenant database: one database — many independent organizations-"areas"). Through these messages, service data is transmitted: information about subscriptions and limits, changes to users and rights, administration commands. This is part of the "Message Exchange Between Data Areas" subsystem from the Library of Standard Subsystems (LSS). In a file or regular client-server database without data separation (that is, in the locally installed "Accounting for Kazakhstan"), the directory is usually empty and not used — there is simply nowhere for messages to go. 2. Where to Find In the interface of a regular accountant, there is no menu item for this directory — it is a service directory and is intentionally hidden. You can open it in two ways: - Through the navigation link. The menu (main menu, icon ≡ in the upper left corner) → "File" → "Open" is not available for links; use "Service" → "Go to Navigation Link" (in some interfaces — by keyboard shortcut) and paste: e1cib/list/Directory.DataAreaMessages - Through the functions of a technical specialist. Section "Administration" → "Maintenance" or "All Functions" (if enabled: "Service" → "Settings" → "Show 'All Functions' Command") → branch "Directories" → "DataAreaMessages". Direct work with it is usually carried out by the service administrator or a partner servicing the cloud. 2a. How to Know Your Release Main menu (≡) → "Help" → "About the Program". In the opened window: - "Platform Version" — version of "1C:Enterprise" (technological platform); - "Configuration" — here you will see "Accounting for Kazakhstan, version 3.0" and release number (for example, 3.0.74.2). The release number is important: the composition of service subsystems and the behavior of exchanges between areas change from version to version, and this instruction describes the behavior of release 3.0.74.2. 3. What Fields Are There and What Do They Mean Records in this directory are created and filled by the program itself — through scheduled tasks and the exchange mechanism. You usually do not create them manually; you read them for diagnostics. Therefore, it is more important here to understand what each field means than whether it is "mandatory or not". Field What it Means and What It Affects Code Internal record number. Service, does not carry any semantic load for the user. Name Brief description of the message — usually the type of operation or identifier. You navigate in the list by it. Message Identifier (GUID) Unique key of the message. It matches the message on the sender's and recipient's side. If you are looking for "that specific" message in the logs — search by it. Type / Kind of Message What exactly is being transmitted: subscription/limits data, user change, service command, etc. Determines which handler will process the message. Sender Area / Recipient Area Codes of data areas: who sent it, to whom it is addressed. An error in addressing will cause the message to "hang". Message Body The actual payload (usually XML/serialized data) in the value storage. It is opened for reading only technically; it is not edited manually. Date (Creation / Sending) When the message was placed in the queue. By the date, you can see whether it is a "fresh" jam or old garbage. Status / Processing Indicator Sent, delivered, processed, with error. A key field for diagnostics: it shows whether the message is stuck or not. If you open a record and do not understand the meaning — do not change anything manually. Incorrect editing of the body or status of the message will disrupt data consistency between areas. 4. Analyzed Example (Diagnostics, Not Entries) This object does not generate debit/credit entries — therefore, the example here is diagnostic, not accounting. Situation. The organization extended the subscription. In the working area, upon entry, there is still a warning about the limit. As the administrator, you check the exchange. - Open the list: e1cib/list/Directory.DataAreaMessages. - Sort by date, find the latest message of type "subscription/limits data", sender area — service manager, recipient area — code of the problematic organization. - Check the status: "Sent, not processed". This means the message has arrived, but the handler in the working area has not yet processed it. - Check the scheduled task for processing the message queue: "Administration" → "Maintenance" → "Scheduled and Background Tasks" — the task for message exchange between areas. You see that it is disabled/error. - Enable the task (or run it manually). After execution, the status of the message changes to "Processed", the warning about the limit in the working area disappears. Result. No accounting movements — only a change in the message status and an update of service data about the subscription in the recipient area. This is the "fix for detecting the subscription limit": not manual editing of numbers, but restoring normal queue operation. 5. Types of Operations (Message Types) Through the message exchange mechanism between areas, the following usually pass: - Subscription and limit data — how many users/services are available to the area, until what date (this is often the reason for inquiries). - User management — creation, blocking, changing user rights in the area. - Service commands — updating settings, initializing the area, maintenance. - Notifications to the service manager — reverse messages from the working area to the area manager. The specific list of types depends on which subsystems are included in your service model. 6. What Happens When Recording - No entries — this object does not create accounting movements in the registers (accounts 1210, 1030, 3310, 3130, 6010, 7010, etc.). - No electronic documents — this directory does not issue electronic invoices (ESF) in the ESF IS and tax returns. - Movements — only service: recording/reading from the message queue of the exchange subsystem, changing the processing status. The real "work" (application of the received data) is done by message handlers and scheduled tasks, not by the directory record itself. 7. Printed Forms No printed forms. This is a service directory — you cannot print an invoice, act, or statement from it. For analysis, use the standard list and opening of records, if necessary — the registration journal (log) and results of scheduled tasks. 8. Common Errors What You See / Symptom Reason How to Fix "Object not found: Directory.DataAreaMessages" when following the link The database operates without data separation (local installation), the subsystem is inactive This is normal for a local database. The object is only needed in the service model. Messages are piling up, status "Sent, not processed" The scheduled task for processing the queue is disabled or failing "Administration" → "Maintenance" → "Scheduled and Background Tasks" — enable/restart the message exchange task, check its log "Limit exceeded...", although the tariff is paid The message with new limits has not yet been processed in the working area Wait for the scheduled task to complete or manually start the queue processing (see example in p. 4) Message with status "Error" Handler failure, corrupted body, or inaccessible recipient area Check the error text in the registration log; retry processing. Do not edit the message body manually No rights to open the directory The user does not have an administrative role Open under a user with service administrator rights Manual editing of records in this directory should only be done in agreement with service support or a partner — it can disrupt the integrity of the exchange between areas. 9. FAQ Do they fill out invoices or acts here? No. This is a service directory for exchanging between data areas. Sales and purchase documents are maintained in the "Sales" and "Purchases" sections, not here. Does this object generate entries and VAT? No. It does not create accounting entries, movements in accounts, or VAT calculations (in the RK from 2026 the rate is 16%) — this is not an accounting document. Are ESF or tax returns issued from it? No. Electronic invoices (ESF) and tax returns are issued from sales/movement documents, not from the service message directory. Why is the directory empty? Most likely, your database is local (without data separation). Message exchange between areas works only in the service model (cloud), where records appear. Can old messages be deleted to "clean" the database? Processed messages are usually deleted on a schedule. It is not advisable to delete them manually in bulk — you might remove unprocessed messages. If cleaning is necessary — do it through service support. Is a message hanging "not processed" dangerous? Not by itself — but the related function (for example, updating subscription limits) will not work until the message is processed. Check the scheduled task for processing the queue. Where to find the object if it is not in the menu? Through "Go to Navigation Link": e1cib/list/Directory.DataAreaMessages, or "All Functions" → "Directories". Can the message body be edited manually? No. The body is serialized and intended for the handler. Manual editing will disrupt data integrity between areas. Work with the status/queue, not with the content. How to understand which release this behavior relates to? "Help" → "About the Program": there you will find the release number of the configuration. This instruction is for "Accounting for Kazakhstan" 3.0.74.2. 10. Related Objects - Scheduled and Background Tasks ("Administration" → "Maintenance") — they are the ones that take messages from the queue and apply them. - Data Separation Subsystem / Data Areas — the context in which the directory makes sense at all (service model, 1C:Fresh). - User and Rights Management — part of the messages concerns users of the area. - Subscription/Tariff Settings of the Area — data that is transferred by these messages. This directory is not introduced separately "on the basis of" and no documents are created based on it — it lives within the service exchange mechanism. How to Know Your Release Main menu (≡) → "Help" → "About the Program" — there you will find the version of the "1C:Enterprise" platform and the release number of the configuration. The material was prepared based on the configuration "Accounting for Kazakhstan". --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_