Report "Invoice Availability Report" — Technical Description (Accounting for Kazakhstan 3.0.74.2)

1. Identification

Purpose. The report is intended for monitoring and analyzing the availability and movement of invoices issued by the organization to customers and clients. It is used by accountants and financial specialists to verify the completeness of issued invoices, track their statuses (accepted/not accepted in the ESF information system), and ensure compliance with the tax legislation of the Republic of Kazakhstan. It is generated regularly — when preparing for VAT reporting (rate 16% from 2026), during the inventory of accounts with customers (account 1210), and also at the request of management. It is a regulated analytical report with flexible settings for grouping, filtering, and detailing.

Where to find in 1C: section "Sales" → "Report on the availability of issued invoices". Also available through the "Reports" section → "VAT and tax accounting" and via the command from the invoice interface.

2. Attributes and Table Parts

The report is implemented on the DCS, so "attributes" are the parameters and settings of the composition scheme that define the period, filters, and formatting; "table parts" are the tables that set the structure (groupings).

2.1 Header Attributes (Settings Parameters)

2.2 Table Parts

Grouping

Purpose: manages the structure of data grouping — defines the dimensions by which totals and subtotals are formed.

Typical selection and grouping fields characteristic of the report: Organization, Department, Counterparty (buyer), Contract, Invoice (issued), Document basis (sale), Document date, ESF Status (in the ESF information system), Amount without VAT, VAT amount (at a rate of 16%), Amount with VAT, Currency (tenge, ₸).

3. Forms

For reports on DCS, custom forms are generally not created — the platform's auto-generated form system is used:

If there is a custom form in the configuration (e.g., "ReportForm" with an enhanced command panel or additional fields for selecting organizations/departments), it replaces the auto-generated one — this is the source of the attributes OrganizationListRepresentation / DepartmentListRepresentation.

4. Key Module Procedures

The attached evidence does not contain BSL fragments with paths/strings, so below is a typical set of handlers for the report on DCS in BK 3.0. Specific implementations should be viewed in the object modules of this version.

Object module / report manager module:

• OnResultComposition(ReportResult, BreakdownData, StandardProcessing) — manages the composition process: disables standard processing, programmatically generates the result, substitutes representations of organizations/departments in the header, applies the ReportType parameter.
• OnFormSettingsDetermination(Form, VariantKey, Settings) — configures the behavior of the report form, availability of control elements, breakdown mode (DetailingMode).

Form module:

• OnCreationOnServer(Error, StandardProcessing) — initializes the default period, restores saved user settings, fills in the representations of filters.
• Handlers for selection fields of organizations/departments — generates text representations (OrganizationListRepresentation, DepartmentListRepresentation) when multiple selections are made.
• OnBreakdownProcessing / DCS breakdown handler — transitions from the aggregated row to the primary document (issued invoice, sale).

DCS Composer (main scheme): text query to data sources, parameters StartPeriod/EndPeriod, data sets, calculated and user fields, resources (amounts), predefined variants.

5. Posting and Movements

The report is not a document and does not perform posting — it does not generate accounting entries and movements in registers. The report only reads already generated data.

Data sources of the report (by standard logic):

• Documents "Invoice (issued)" and their electronic forms (ESF in the ESF information system), accompanying invoices (SNT);
• Documents of sale;
• VAT accounting registers and the register of information on the statuses of electronic documents (accepted/not accepted, rejected).

Entries generated by the basis documents (for understanding the source of the report amounts; typical chart of accounts of the RK):

The report aggregates amounts without VAT, VAT (at a rate of 16%), and with VAT across selected groupings; all amounts are in tenge (₸).

6. Related Objects and Input on Basis

Reports do not participate in the "input on basis" mechanism (there is no input on the basis of a report and a report on the basis of another object). Functionally, the report is related to:

• Document "Invoice (issued)" — the main analyzed object; supports breakdown to the document.
• Sale documents (sale of goods and services) — basis documents for invoices.
• ESF / ESF Information System, SNT — electronic documents and their statuses reflected in the report columns.
• Directories "Organizations", "Departments", "Counterparties", "Contracts" — dimensions of filters and groupings.
• VAT accounting registers — source of amounts at a rate of 16%.
• Related reports of the VAT block (register of invoices, VAT declaration form 300.00) — use overlapping data.

7. Extension Points

• User report variants — saving configured groupings/filters without changing the configuration; distribution through "Additional reports".
• Configuration extensions — overriding handlers OnResultComposition, OnCreationOnServer, adding form attributes and selection elements without removing from support.
• Enhancement of the DCS scheme — adding data sets, calculated/user fields, resources, and conditional formatting (e.g., highlighting unaccepted ESFs).
• Additional fields — managed by the attribute AdditionalFieldsPlacement; a convenient point for displaying ESF/SNT attributes.
• Functional options — managing the visibility of the report in interface sections.

Requires verification for version 3.0.74.2: the exact composition of predefined values for the parameter ReportType and the presence of a custom report form — depend on the specific build of the configuration.