“UserNotifications” in 1C:Accounting for Kazakhstan 3.0 is a service directory for storing system messages addressed to infobase users. In 2026, messages from this directory must be distinguished from informational, warning, and mandatory tax authority notifications stipulated by the Tax Code (Articles 82 and 83 of the Tax Code of the RK). When reviewing taxation warnings, note that the standard VAT rate in the RK is 16%. This description was prepared for release 3.0.74.2.
You log into the infobase in the morning and see a red number beside the bell icon at the top. You open it and find a message about an event requiring attention. You did not create it manually: the program mechanism generated the entry and saved it in the “UserNotifications” directory. Below, we explain how this directory is structured, what its fields mean, how to identify the source of a specific notification, and how to remove entries that have already been processed.
The main point from the outset: this is a service directory, not an accounting document. It is intended to store system notifications addressed to infobase users. Program messages should not be confused with official tax authority notifications: their types and content are defined by the Tax Code (Articles 82 and 83 of the Tax Code of the RK).
1. Purpose
The directory stores notifications displayed to users by the program: reminders about actions and events, data warnings, and service messages from the mechanisms being used. An entry may contain text, information about the recipient, and data required to display the message or navigate to the related object.
The directory is used by the configuration’s internal mechanisms. Entries may appear automatically when conditions specified in the program are met: for example, when a user needs to pay attention to a related object, read an important message, perform a required action, or check whether data is up to date.
2. Where to Find It
In the interface of the release described here, active messages can be viewed using the bell icon in the upper-right corner. Clicking it opens the notification panel.
You can try to open the complete list of directory entries in the following ways:
- “Service Tools” → “User Notifications”, if this command is provided and displayed in the interface.
- “Functions for Technical Specialist” → “Directories” → “UserNotifications”, if the technical specialist functions are available to the user and the object is present in the list.
- Using the navigation link e1cib/list/Справочник.ОповещенияПользователей: copy it and paste it into the navigation-link field. This method will work if this internal name is used in the configuration and the user has access.
These methods are intended to open the list of entries, not only the active-message panel. The availability of commands, form contents, and ability to view the directory depend on the release, interface, and user permissions.
2a. How to Find Your Release
Main menu, the ≡ icon in the upper-left corner → Help → About. The window that opens usually shows:
- the platform version, for example, 8.3.24.xxxx;
- the configuration release — a line such as “Accounting for Kazakhstan, edition 3.0 (3.0.74.2)”.
The second line is important for this guide: the set of fields, command availability, and notification behavior may change between releases. This description applies to 3.0.74.2, which is part of the current 3.0.74.x release line.
3. How to Fill It In and Why This Is Usually Unnecessary
Directory entries are intended primarily for service use and are created by program mechanisms. Manual entry is usually unnecessary. However, it is useful to understand the attributes of an entry available to the user in order to read the notification, identify its recipient, and find the related object.
| Field | Purpose |
|---|---|
| Name | Briefly identifies the entry. If the field is present on the form, it can be used to find the notification in the list and identify its subject. |
| User / Recipient | Specifies the message recipient. Whether the notification is displayed to a particular user is determined by the recipient data and the logic of the mechanism that created the entry. |
| Date / Creation Date | If provided, this field shows when the entry was created and helps associate the message with the corresponding event. |
| Validity Date / Display Until | If the form provides this attribute, it defines the period during which the message remains valid or is displayed. |
| Importance | Contains a value provided by the configuration that may be used to present the message in the interface. |
| Notification Text | Describes the event and the action expected from the user. |
| Navigation Link / Navigation Object | May be used to navigate to a related document, report, data processor, or other object. If the object has been deleted, the link is outdated, or the user lacks the necessary permissions, navigation may fail. |
| Source / Reason | If this attribute is displayed on the form, it contains information that can be used to associate the entry with a program object or mechanism. |
| Read / Dismissed | If these indicators are provided, they reflect the notification’s processing status. Available statuses and commands depend on the mechanism that created the message. |
Practical conclusion: the complete directory list is useful for analyzing recurring messages and accumulated entries. The names, purposes, and set of attributes should be checked directly on the form in the release being used.
4. Worked Example
Situation: in September 2026, an accountant posts a sale, and a warning appears beside the bell asking them to check the VAT rate.
If such a notification is generated by the mechanism being used, the available entry may contain:
- Name: “Check the VAT rate in the sales document”.
- User: the accountant to whom the message is addressed.
- Date: the notification creation date.
- Importance: warning.
- Text: a message stating that the VAT rate must be checked.
- Navigation Link: navigation to the “Sales of Goods and Services” document.
- Source: the mechanism or object associated with the warning.
Since 2026, the standard VAT rate in the Republic of Kazakhstan has been 16%. The accountant should open the document using the link, check the turnover date, the nature of the transaction, and the specified rate, and make any necessary changes in the sales document.
Calculation example: if the sales value excluding VAT is 1 000 000 ₸ and the standard rate applies, the VAT amount is 1 000 000 × 16% = 160 000 ₸. The value including VAT will be 1 160 000 ₸.
What should be checked in the accounts? From the notification, navigate to the sales document and check the recorded business transaction:
| Debit | Credit | Amount, ₸ | Description |
|---|---|---|---|
| 1210 | 6010 | 1 000 000 | Sales revenue |
| 1210 | 3130 | 160 000 | VAT at the rate of 16% |
| 7010 | 1330 | — | Write-off of the cost of goods |
The account correspondence, amounts, and analytics should be checked with regard to the type of sale, accounting settings, and data in the specific document. In this scenario, the notification is used to navigate to the object in which the accountant performs the check and corrects the data if necessary.
5. Types of Notifications: What Is Included
The composition of messages is determined by the mechanisms and settings of the specific configuration. For the purpose of working with the list, entries can be provisionally grouped by content and presumed source:
- Event reminders — messages about upcoming actions and events set by the user.
- Data checks — warnings about attributes or other circumstances to which the program suggests paying attention.
- Electronic documents — messages related to processing E-invoices and Goods Accompanying Notes (SNT), if the corresponding mechanism is used in the infobase.
- Exchange and synchronization — service information from the data import, export, or exchange mechanisms being used.
- Updates and service — messages related to infobase maintenance, if they are saved by this mechanism.
- User reminders — notifications created through the reminder mechanism available in the configuration.
This is a working grouping for analyzing the list, not a list of values for a particular directory attribute. The specific source is determined from the entry’s contents, available attributes, and related object.
6. What Is Generated When an Entry Is Saved
When the notification mechanism operates, a service entry is created or modified in the directory. Depending on its data, status, and settings, the message may be displayed in the panel beside the bell. After the specified processing command is performed, it may disappear from the list of active messages.
Service logic varies between mechanisms and releases. Therefore, when analyzing a particular entry, refer to the attributes actually available on the form, the message text, the recipient, and the navigation object in the configuration version being used.
7. Print Forms
No separate print form is provided for the notification directory in the scenario described. If the information needs to be recorded, you can copy the message text or use the data output and saving commands available on the list form.
8. Common Errors
“Notifications keep popping up and interfere with my work.” Open the message and review its text, recipient, related object, and source information, if available. Then check the settings of the mechanism to which the message relates. The available notification-management commands are determined by the notification type, user permissions, and release.
“The notification is still displayed, but the object no longer exists.” If navigation results in an “Object not found” message, check the entry attributes and user permissions. This may be caused by deletion of the object, a change to the link, or restricted access. After checking, process the notification using an available command.
“A user does not receive notifications, although other users do.” Check the “User / Recipient” attribute, if available, as well as permissions and personal settings. Also compare the source and parameters of messages visible to other users.
“The list has grown to thousands of entries, and the bell opens slowly.” Open the complete list, apply the available filters, and analyze old entries. If the form allows them to be marked for deletion, perform further processing using the standard deletion mechanism for marked objects. Create an infobase backup before bulk clearing.
“I deleted a notification—what happened to the related object?” Open the source document or other related object and check its status separately. Deleting a notification directory entry should not be used as a substitute for performing the required actions in the accounting document.
9. Step-by-Step Review of a Specific Notification
- Open the message beside the bell and read the full text.
- Check the recipient, creation date, and validity information, if available.
- Review the “Source / Reason” attribute or other available data indicating the origin of the message.
- If navigation is provided, open the related document, report, or data processor.
- Check and, if necessary, correct the data in the related object.
- After processing, use the available command to change the notification status.
- If the message reappears, return to the related object or the settings of the mechanism that creates it.
10. How to Safely Clear Old Notifications
It is better to clear entries after analyzing the list so that a message is not removed before its related object has been checked. Follow these steps:
- Create an infobase backup.
- Open the complete list through “Service Tools” → “User Notifications” or by another available method.
- Apply a filter by date, recipient, or entry status, if the corresponding fields are available.
- Open several entries from the selected group and make sure that the related events have already been processed.
- Mark unnecessary entries for deletion only if this command is available and you have the required permissions.
- Perform the standard deletion of marked objects in accordance with the organization’s established procedure.
- Check the operation of the panel beside the bell and make sure that the required active messages have been preserved.
If the source continues to create identical messages, clearing the list alone will not eliminate the cause of their recurrence. You need to check the related document, personal settings, or the mechanism generating the notification.
11. Related Objects
- Scheduled and background jobs — perform automatic operations and, in some mechanisms, may be associated with the appearance of service messages.
- Reminders — a user mechanism for messages associated with an object or event.
- Tasks and business processes — if available and used in the configuration, they may be associated with assignment messages.
- Accounting documents, including sales, receipt, and payment documents, may serve as navigation objects if the corresponding link is recorded in the notification.
- E-invoices and Goods Accompanying Notes (SNT) — electronic documents whose processing may be associated with certain service messages.
A notification should be regarded as a means of informing the user and, if a link is available, navigating to a program object. The main work is performed in the document, report, data processor, or other section specified in the message.
Frequently Asked Questions
Is this a document or a directory? — It is a service directory. To check a business transaction, navigate to the related accounting document.
Where does a specific notification come from? — Review the entry text, navigation object, and the “Source” or “Reason” attribute, if provided on the form. This information helps establish which document or mechanism is associated with the message.
Can entries be deleted without losing data? — Before processing an entry, check its date, recipient, text, and navigation object. For bulk clearing, use the standard commands and create an infobase backup beforehand. After deletion, check the status of the related object separately.
How can I disable annoying pop-up notifications? — First identify the source of the message. Then check the settings of the corresponding mechanism and the commands available in the notification panel.
I received a notification with an outdated standard VAT rate. What should I do? — Since 2026, the standard VAT rate has been 16%. Open the document using the link, check the turnover date and the nature of the transaction, and then correct the rate in the document itself if the standard rate applies to the transaction.
Why is a notification visible to one user but not another? — Check the “Recipient / User” attribute, if available, as well as permissions and personal settings. Also compare the source and message parameters for both users.
How can I open the complete list of all notifications rather than only the active ones beside the bell? — If you have the appropriate permissions, use “Service Tools” → “User Notifications”, the technical specialist functions, or the navigation link e1cib/list/Справочник.ОповещенияПользователей. The availability of each method is determined by the interface, release, and permissions.
What should I do with a notification about an E-invoice or Goods Accompanying Note (SNT)? — Open the related object and perform the required actions in the electronic documents section. Check the status of the E-invoice or Goods Accompanying Note (SNT) directly in the related object and the corresponding exchange mechanism.
Can a notification be printed as a document? — If there is no separate print form, the text can be copied, while the list can be output or saved using an available form command.
Notifications are accumulating, and the bell opens slowly. What should I do? — Filter entries by the available fields, analyze old notifications, and process unnecessary ones using standard tools. Create a backup before bulk clearing.
Why does a link in a notification produce the “Object not found” message? — Check the entry attributes and user permissions. The related object may have been deleted, the link may no longer be valid, or access may be unavailable. After checking, process the notification using an available command.
How do 1C messages differ from tax authority notifications? — A directory entry informs the user within the program. Tax authority notifications are informational, warning, or mandatory notifications stipulated by the Tax Code (Articles 82 and 83 of the Tax Code of the RK).
Sources
- Tax Code of the Republic of Kazakhstan, Article 82 “Informational and Warning Notifications of the Tax Authority”.
- Tax Code of the Republic of Kazakhstan, Article 83 “Mandatory Notifications of the Tax Authority”.
This guide was prepared for “Accounting for Kazakhstan”, edition 3.0, release 3.0.74.2. Field names, command locations, available actions, and message texts may differ in another release.