Report "Report on the Availability of Received Invoices" (Accounting for Kazakhstan 3.0.74.2)

1. Identification

Purpose. The report is intended for monitoring and analyzing the availability of invoices received from suppliers within the framework of regulated accounting in the RK. It is used by accountants and tax specialists to monitor the status of receiving electronic invoices (ESF) from the ESF information system, check the completeness of document flow with counterparties, and prepare for reconciliations with VAT tax reporting. The report allows filtering data by periods, organizations, departments, document reception statuses, and cumulative registers. It is generated at the user's request and is used regularly — at the end of the period, before submitting tax reports (form 300.00 and VAT appendices), and during reconciliations with counterparties.

Where to find in 1C: section “Purchasing” → “Report on the availability of received invoices”. Navigation link: e1cib/list/Report.ReportOnAvailabilityOfReceivedInvoices.

The report is relevant for the conditions of the RK in 2026: the basic VAT rate is 16%, electronic invoices are issued and received through the ESF information system, accompanied by accompanying documents for goods if necessary. VAT indicators in the report are derived from the data of documents and VAT accounting registers, not calculated by the report itself.

2. Settings Attributes and Table Parts

The report is built on the basis of a data composition scheme (DCS). The attributes listed below are parameters and elements of the report settings structure (settings storage) that define the selection and formatting, not the document attributes.

2.1 Header Attributes (Report Parameters)

2.2 Table Parts

Grouping

Defines the levels of data grouping in the report (by counterparties, documents, dates, etc.).

AdditionalFields

List of additional fields for output besides standard indicators.

Indicators

Numerical indicators (sums, quantities) displayed in the report.

Standard set of indicators: amount excluding VAT, VAT amount (at a rate of 16%), amount including VAT, number of documents, status of invoice reception (received / not received / absent), invoice number and date.

3. Forms

The forms section in the evidence is not disclosed. For the report on DCS, the standard composition is:

If user forms are not defined, the report uses the auto-generated system data composition form.

4. Key Module Procedures

The evidence by modules (path: line) is not attached. For the report on DCS, the following typical handlers are characteristic.

Report object module:

• OnResultComposition(ReportDocument, DetailData, StandardProcessing) — interception point of composition; here the layout is usually fine-tuned, period parameters from StartPeriod/EndPeriod are substituted, an external data source is formed or the result is programmatically supplemented.
• SettingsForDataSetSelection() / initialization of report type parameters (ReportType) — setting the selection structure depending on “received / issued”.

Report form module:

• OnCreateOnServer(Error, StandardProcessing) — setting the default period, restoring user settings, filling in representations of organization/department lists.
• Generate(Command) → ComposeResult() — starting composition.
• StartPeriodChange / EndPeriodChange — handlers for changing period boundaries with re-filling parameters.
• Detail processing handler (ReportDocumentDetailProcessing) — transition from a report cell to the underlying document (Received Invoice, Receipt) when DetailingMode is enabled.

5. Data Source, Movements, and Entries

The report is not a posting object: it does not perform postings and does not generate records in accounting registers or accumulation registers. The report only reads already formed data.

Data sources for the report:

• VAT accounting register(s) and data of documents “Invoice (received)”, “Receipt of goods and services”;
• data from the electronic document management subsystem ESF (status of reception/issuance of ESF in the ESF information system, binding of accompanying documents);
• attributes of counterparties, organizations, departments for groupings and selections.

Entries are formed not by the report, but by the underlying documents. For context, typical movements of the receipt document with VAT in the chart of accounts of the RK:

VAT payable is accumulated in account 3130 “VAT payable”; sales are reflected through 1210 / 6010 and cost 7010 / 1330. The report on the availability of received invoices works with “incoming” VAT and statuses of ESF reception.

The calculated indicator in the report (VAT amount) is taken from documents at the actual rate; for 2026, the basic rate is 16%.

6. Related Objects and Input on the Basis

The report is a data consumer; input on the basis from it is not performed. Related objects included in the selection and details:

• Documents: “Invoice (received)”, “Receipt of goods and services”, “Advance report” (in terms of incoming invoices), corrective/adjusted invoices.
• Electronic documents: ESF (ESF information system), accompanying documents — based on the status of reception and matching.
• Directories: Organizations, Departments, Counterparties, Contracts.
• Registers: VAT accounting registers, registers of information on electronic documents (statuses of ESF).
• Related reports: registers of received/issued invoices, VAT reporting (form 300.00 and appendices).

Detailing a cell opens the underlying document or related ESF.

7. Extension Points

• Configuration extension (adopt/annotate): overriding OnResultComposition in the object module to add custom columns/indicators or an alternative data source.
• Additional report variants (DCS): adding custom layout variants without changing the code — new groupings, selections, conditional formatting.
• Additional fields and indicators through table parts AdditionalFields / Indicators — a standard mechanism for extending the composition of output data.
• External reports / additional processing (BSP): connecting a similar report without removing the configuration from support.
• Subscriptions and common modules of EDM: extending the logic of determining the status of ESF reception (integration with the ESF information system) through common modules of the electronic documents subsystem.
• Selection by cumulative registers and reception statuses — parameterizable points allowing to adapt the selection for the reconciliation regulations of a specific organization.