1. Identification
| Parameter | Value |
|---|---|
| Object Type | Report (Reports) |
| Name | ObligationsByNotificationsAndESF |
| Full Name | Reports.ObligationsByNotificationsAndESF (Report.ObligationsByNotificationsAndESF) |
| Synonym | — (not specified in the object card) |
| Configuration | Accounting for Kazakhstan, edition 3.0, version 3.0.74.2 |
| Introduced in Release | 3.0.73 |
| Construction Mechanism | Data Composition System (DCS) |
| Usage Type | Read-only (analytical report, does not generate movements) |
Purpose. Control and analytical report for working with the Electronic Invoice Information System (ESF). Shows the organization's obligations related to notifications in the ESF — notifications that still need to be processed, confirmed, or matched when reconciling accounting data with the electronic system. Notifications in the ESF are generally related to the movement of goods (import and/or sale of specific categories of goods requiring notifications). The report is used by accountants and chief accountants when reconciling accounting with the ESF, usually before closing the period or submitting reports, as a self-control tool for the completeness of notifications.
The exact subject area (specific categories of goods and the complete set of indicators of this report) is not disclosed in the object card — requires verification for the specific release. Below, the structure of forms, fields, and procedures is described according to the typical report template in DCS, as
metadata.attributes,metadata.tabular_sections, andmetadata.formsin the original card are empty.
2. Attributes of Header and Tabular Parts
In the object card, the composition of attributes and tabular parts is not recorded (metadata.attributes and metadata.tabular_sections are empty). For a report in DCS, this is normal: parameters and settings are stored in the data composition scheme (template MainDataCompositionScheme) and in report variants, not in the attributes of the metadata object.
2.1 Standard Parameters (Header of Report Form)
| Parameter | Purpose |
|---|---|
Period / StartPeriod, EndPeriod |
Boundaries of the analyzed interval (date/period of receiving notifications) |
Organization |
The organization for which obligations for notifications in the ESF are monitored |
| Filters | By counterparty, nomenclature/category of goods, type/status of notification |
2.2 Configuration Tables (in DCS)
| DCS Element | Purpose |
|---|---|
| Groupings | Order and levels of grouping rows (by organization, counterparty, supporting document) |
| Indicators / resources | Numerical totals (quantity, amount of obligations for notifications) |
| Filters | Conditions for limiting the sample |
| Conditional formatting | Highlighting overdue/unclosed obligations |
The exact names of parameters, fields, and resources should be read from the form and from the data composition scheme of the specific version — they are not invented in the card.
3. Forms
| Form | Purpose |
|---|---|
ReportForm (standard) |
The only standard report form in DCS: settings panel (period, organization, filters, groupings) + area of the tabular document with results. Formed by the platform's DCS mechanism |
In the object card, the list of forms is empty (metadata.forms is empty). For a report in DCS without its own forms, the platform automatically generates the report form; if there is a custom form, its name is usually ReportForm. The exact composition of the form should be viewed in the configurator of the specific release.
4. Key Procedures of Modules
No own BSL code (evidence) is attached in the object card. For a report in DCS, the following handlers are typical (object module / form module):
| Handler | Module | What it does |
|---|---|---|
OnResultComposition(...) |
Report object module | Programmatic intervention in the composition process: fine-tuning the layout, outputting results, processing fields before output |
OnVariantUploadToServer / OnUserSettingsUploadToServer |
Form module | Initialization of variant settings and user settings upon opening |
OnCreationOnServer |
Form module | Setting default parameter values (current organization, working period) |
| Command handlers for formation | Form module | Launching composition and outputting to the tabular document |
If the report has its own module in a specific release — procedures and their purposes should be taken from the code of that release. The provided list is a typical framework for a report in DCS.
5. Posting and Movements
The report is not posted and does not record anything — it is a read-only object. It does not generate postings and movements in registers, but only reads data from accounting registers and the ESF subsystem and displays them.
The data sources for such a report in "Accounting for Kazakhstan" are usually:
- Registers of the ESF subsystem (data of ESF documents, SNT, movements in virtual warehouses of the ESF);
- Accounting register according to the typical chart of accounts of the RK — when reconciling obligations with accounting data.
References to relevant accounts of the typical chart of accounts of the RK (for the context of related operations of sale/purchase of goods for which notifications in the ESF are generated):
| Account | Purpose |
|---|---|
| 1210 | Short-term receivables from customers |
| 1030 | Cash on current bank accounts |
| 1330 | Goods |
| 3310 | Short-term payables to suppliers |
| 3130 | VAT payable (VAT rate in the RK from 2026 — 16%) |
| 6010 | Revenue from sales of products and services |
| 7010 | Cost of goods sold and services |
The report itself does not make movements on these accounts — the accounts are provided as the context of operations for which it monitors obligations.
6. Related Objects and Input Based On
- Document "ESF" (electronic invoice) — the main related object; the report monitors the completeness and status of notifications for the ESF.
- Document "SNT" (accompanying invoice for goods) — notifications in the ESF are related to the movement of goods documented by the SNT.
- Virtual warehouses of the ESF — registers of movements of goods requiring notifications.
- Documents of sale/purchase of goods — basis operations for which obligations for notifications arise.
Input based on the report is not applicable: reports do not participate in the input based on mechanism and are not themselves the basis for documents.
7. Extension Points
- Report Variants (DCS) — adding user/additional variants with different groupings, filters, and formatting without changing the configuration.
- Configuration Extensions — overriding/adding the handler
OnResultComposition, adding attributes and elements to the report form, refining the composition scheme. - User Settings — saving filters and groupings at the user level.
- Roles and Rights — managing access to the report through the rights subsystem (viewing ESF data).
Where to Find
Navigation link 1C:
e1cib/list/Report.ObligationsByNotificationsAndESF
Opened from the subsystem for working with ESF / electronic documents of the "Accounting for Kazakhstan" configuration.