Report "Invoice Accounting Journal" — Technical Description

1. Identification

Purpose. A specialized report for maintaining the journal (purchase book and sales book) of invoices for VAT in accordance with the requirements of the legislation of the Republic of Kazakhstan. Used by the accountant for controlling and analyzing invoices — both paper and electronic (ESF) — issued to customers and received from suppliers over a period. Supports:

• verification of the compliance of invoice amounts with primary documents of sales/purchases;
• mass refilling of invoice details;
• working with electronic invoices (ESF, ESF IS);
• data grouping by counterparties, contracts, and method of issuance (electronic/paper).

The VAT rate applied when generating turnover is 16% (Kazakhstan, 2026).

The report is an object not performing posting: it does not generate movements in registers and accounting entries, but only reads and aggregates already posted data (see section 5).

2. Attributes and Structure

2.1 Header Attributes (Parameters)

The report does not have attributes in the classical sense of a metadata object — the fields listed below are configuration parameters set by the user on the form and passed to the construction algorithm.

The key controlling parameter is InvoiceType: it is the only mandatory one (control ShowError) and determines whether the sales book (issued invoices) or the purchase book (received invoices) is constructed. It affects the set of data sources and result columns.

2.2 Table Parts

None. The report does not store its own data but accesses external sources — documents of issued and received invoices and related primary documents. The result is generated in the form of a tabular document.

3. Forms

No separate settings/variant forms are provided — all parameters are directly placed on ReportForm.

4. Key Module Procedures

Evidence with the source code BSL for this object is not attached. Below is a typical set of handlers for reports in BK 3.0; specific names and signatures should be clarified in the configurator.

Form Module (ReportForm):

• OnCreateOnServer — initialization of default parameters (period = current month/quarter, organization from user settings, InvoiceType), restoration of saved settings.
• OnOpen — adjustment of the visibility of panel elements depending on InvoiceType.
• Handlers OnChangeInvoiceType, OnChangeSelectByCounterparty, OnChangeGroupBy… — management of availability/visibility of related fields (for example, the field CounterpartyForSelection is available only when SelectByCounterparty = True).
• Generate (command) — collection of parameters, calling the server procedure for construction, and outputting the tabular document in the result field.
• Mass operation commands — “Check compliance of amounts” and “Refill invoices” (refilling invoice details based on primary documents).

Report Object Module:

• Procedure for compiling/building the result (GenerateReport or through the SDM CompileResult) — selection of invoices for the period by organizations, filtering by InvoiceType, applying counterparty filters, groupings, and excluding expired invoices, generating the tabular document.

Requires verification: whether the report is implemented on SDM or fully programmatically generating the tabular document — this is version-dependent and determines the exact structure of procedures.

5. Data Generation (Movements/Entries)

As a report, the object does not perform posting and does not create movements in registers and accounting entries. It reads already generated accounting data.

Data sources:

• documents of issued and received invoices (including ESF);
• related primary documents of sales and purchases;
• VAT accounting registers (purchase/sales books).

For context — the turnovers that the report analyzes are generated by primary documents and reflected in the accounts of the standard chart of accounts of the RK:

Sales (issued invoice), VAT 16%:

Receipt (received invoice), VAT 16%:

The VAT amount in each invoice is calculated at the rate of 16%; these amounts are what the report reconciles with primary documents when executing the compliance check command.

6. Related Objects and Input Based On

• Source Documents: Invoice (issued), Invoice (received), as well as documents of sales/purchases based on which invoices are issued.
• Electronic Documents: ESF (ESF IS), statuses and details of electronic invoices are taken into account when grouping by issuance method.
• Directories: Counterparties (CounterpartyForSelection), Organizations, Counterparty Contracts.
• Input Based On: not applicable for the report (the object is not a source for inputting documents). A breakdown is available from the report result — a transition to a specific invoice document.

7. Extension Points

• Configuration extension of the form ReportForm: adding custom selection parameters/columns, overriding handlers OnCreateOnServer, Generate through annotations &Before/&After/&Instead.
• Additional reports (external) through the BSP subsystem “Additional reports and processing” — as an alternative to editing the standard object.
• Report/SDM variant settings (if implemented on SDM) — user variants, conditional formatting, additional groupings without changing the code.
• Refilling invoice details — if customization of the mass operation logic is necessary, it is advisable to move the rules to a separate common module/extension, without affecting the standard procedure.

Requires verification (version-dependent): the presence of BSP extension points and the indication of configuration support being locked — this affects the permissible method of refinement in a specific database 3.0.74.2.