1. Identification
| Parameter | Value |
|---|---|
| Object Type | Catalog |
| Name | CommonDataInformationCenter |
| Full Name | Catalog.CommonDataInformationCenter / Catalogs.CommonDataInformationCenter |
| Synonym | — (not specified) |
| Configuration | “Accounting for Kazakhstan”, edition 3.0, version 3.0.74.2 |
| Object Class | Service (infrastructure), non-accounting |
| Where to find | Section “Service Technology” → “Common Data of the Information Center”. Navigation link: e1cib/list/Catalog.CommonDataInformationCenter |
Purpose. The catalog stores centralized informational messages (news, announcements, warnings, update notifications) that are displayed in the system's information center — usually on the home page or in a separate interface panel. Each item carries content in HTML format and/or an external link, has a type and a validity period during which the message is shown to users. The catalog is managed by administrators and responsible staff for informational content; in a typical scenario, data is fed into it from the information service (internet support) and is not filled in manually by regular users.
The object belongs to the service subsystem and does not participate in accounting/tax accounting: it does not generate entries and movements in accounting registers. Tax parameters of the RK (VAT, PIT, etc.) are not applicable to it — see section 5.
2. Attributes and Table Parts
2.1 Header Attributes
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
Attachments |
ValueStorage | Not checked | Storage for binary data attached to the message — images, files, documents |
ExternalLink |
String | Not checked | URL of the external resource for additional information on the message |
Date |
Date (dateTime) | Not checked | Date and time of creation/publication of the message |
StartDateValidity |
Date (dateTime) | Mandatory (ShowError) | The moment from which the message starts to be displayed in the information center |
EndDateValidity |
Date (dateTime) | Mandatory (ShowError) | The moment after which the message ceases to be relevant and is hidden |
Identifier |
UUID | Not checked | Unique identifier of the record; used for synchronization and matching when exchanging data with the service |
Criticality |
Number (decimal) | Not checked | Priority/importance of the message; affects the order of output (the higher, the more important) |
HTMLText |
String | Not checked | Body of the message in HTML format (formatting, lists, links) |
InformationType |
CatalogReference.InformationTypesInformationCenter |
Not checked | Classifier of the message (news, warning, update, etc.) |
Standard catalog attributes: Code, Name, DeletionMark, Predefined, Reference. The hierarchy and subordination to the owner in the typical delivery for this catalog are not used (flat list).
2.2 Table Parts
Table parts are absent.
3. Forms
| Form | Purpose |
|---|---|
ElementForm |
Main and only form of the element: viewing and editing a single record — validity period, type, criticality, HTML text, external link, attachments. Key form for the user. |
The list form, selection, and others are generated automatically by the platform. The display of messages to the end user is not done by the catalog form, but by the information center mechanism (general modules/forms of the home page), which reads current records by period and criticality.
4. Key Module Procedures
In the catalog evidence, software modules (object module, manager module, form module) are not attached. Below is a typical set of handlers for a service catalog of this kind; check for presence and exact content in the configurator of the specific build.
Object Module (ObjectModule):
CheckFilling(Refusal, CheckedAttributes)— control of mandatory filling ofStartDateValidityandEndDateValidity(the ShowError flag for the attributes raises an error when the value is empty). A logical additional check is that the start date is not later than the end date.BeforeSaving(Refusal)— service initialization: ifIdentifieris empty — assign a new UUID; ifDateis not filled — set the current date.
Manager Module (ManagerModule):
- Functions for selecting relevant messages for the information center: filtering records where
StartDateValidity ≤ CurrentDate ≤ EndDateValidity, sorted byCriticality(in descending order). Used by the mechanism for output on the home page. - Procedures for loading/updating data from the information service (matching by
Identifier, creating/updating elements).
Element Form Module:
OnOpen/OnCreateOnServer— preparation of the HTML document field for displayingHTMLText, output of the content ofAttachments.- Handlers for navigation by
ExternalLink(opening URL) and working with attached files.
Requires verification (version-specific): the actual composition of the general modules of the information center and the exact names of loading procedures from the service may differ between releases of the 3.0 line.
5. Posting and Movements
The catalog is not posted and does not generate movements in accumulation registers, information or accounting registers. This is a service object of the interface subsystem, not an accounting document.
Accordingly, no postings and tax calculations of the RK apply to it. For completeness, we will provide reference values of Kazakhstan for 2026 — they relate to accounting documents of the configuration, not to this catalog:
- VAT rate — 16 % (VAT register, account 3130 “VAT payable”).
- MPR — 4,325 ₸, MZP — 85,000 ₸.
- Basic tax deduction for PIT — 30 MPR/month, but not more than 360 MPR per year.
- PIT — 10 % up to 8,500 MPR of annual income and 15 % above.
- OPV — 10 % (base ceiling 50 MZP), OPVR — 3.5 %, VOSMS — 2 %, OSMS — 3 %, SO — 5 %, social tax — 6 %.
- Typical accounts of accounting documents: 1210 (short-term receivables from customers), 1030 (money in current accounts), 1330 (goods), 3310 (payables to suppliers), 6010 (revenue from sales), 7010 (cost of sales).
These indicators are set and used in accounting objects (sales/purchase documents, payroll calculation, etc.), not in the information center catalog.
6. Related Objects and Input Based On
Catalog.InformationTypesInformationCenter— parent classifier referenced by the attributeInformationType.- Subsystem “Service Technology” / internet support — source of filling the catalog when receiving messages from the information service.
- Information center mechanism (home page, notification panel) — consumer of catalog data.
- Electronic documents of the RK (ESF through IS ESF, SNT) are not linked to this catalog — they relate to the accounting part of the configuration.
Input based on: not provided (not applicable for service catalog).
7. Extension Points
- Configuration extension (without removing from support): adding custom attributes (e.g., “RegionDisplay”, “TargetUserGroup”) and logic for filtering messages through the form/manager module.
- Handler
CheckFilling— point for additional validation of the validity period and correctness of HTML/URL. - Subscriptions to events (
BeforeSaving,OnSavingof the catalog) — for auditing changes to informational messages or integration with external notification channels. - General modules of the information center — overriding rules for selecting relevant messages (by criticality, type, date) for customizing output on the home page.
- Attachment mechanism — extending the processing of
Attachmentsto support additional formats of attached materials.
When making modifications, maintain the service nature of the object: do not attach accounting logic or movements to it — documents are intended for this in the configuration.
