1. Identification
| Parameter | Value |
|---|---|
| Object Type | Report |
| Name | TaxAccountingStatusAnalysisByVAT |
| Full Name | Report.TaxAccountingStatusAnalysisByVAT |
| Synonym | Tax accounting status analysis by VAT |
| Configuration | Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) |
| Currency of Indicators | tenge (₸) |
Purpose. The report is designed for a comprehensive analysis of the VAT tax accounting status. It visualizes VAT flows in the form of a graphical diagram and allows accountants and tax specialists to verify the accuracy of accounting for sales, purchases (offsets), imports, exports, and VAT adjustments over any period. The report is analytical (read-only): it does not create documents or perform transactions, but aggregates previously formed accounting data.
The main scenario is to control the completeness and accuracy of data before submitting the VAT declaration (form 300.00) and before issuing/reconciling electronic invoices (ESF) in the ESF information system. Each block of the graphical diagram expands into a tabular breakdown with links to primary documents.
The current VAT rate in the RK for 2026 is 16% (standard). The report correctly processes preferential/zero rates (exempt transactions, export 0%), as well as transactions for imports with VAT paid at customs.
Where to find in 1C: section "Enterprise" → "Tax accounting status analysis by VAT".
Navigation link: e1cib/list/Report.TaxAccountingStatusAnalysisByVAT
2. Attributes and Table Parts
2.1. Attributes (report settings parameters)
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| StartPeriod | Date (xs:dateTime) |
ShowError (mandatory) | The start date of the analysis period. Determines from which date to collect data on VAT transactions. Participates in validation: must not exceed EndPeriod. |
| EndPeriod | Date (xs:dateTime) |
ShowError (mandatory) | The end date of the analysis period. Limits the selection by the upper boundary. Used when forming queries to VAT registers and VAT adjustments. |
| SettingsCollection | (type not defined / settings storage) | DontCheck (optional) | Saved user settings for the report. Allows loading and saving data display configurations. |
| OrganizationListView | String (xs:string) |
ShowError (mandatory) | String representation of the list of selected organizations (taxpayers) for filtering. Affects the formation of queries — the report selects data only for the specified organizations. |
| DepartmentListView | String (xs:string) |
DontCheck (optional) | Representation of the list of organizations' departments. Allows detailing the analysis by the company's structural divisions. |
2.2. Table Parts
Table parts are absent. The report is parameterized by the header attributes, and the results are generated "on the fly" based on the data from the VAT registers.
3. Forms
| Form | Role | Content |
|---|---|---|
| ReportForm | Main (key) user form | Contains ~110 control elements: input fields for the period (StartPeriod, EndPeriod), selection of organizations and departments, report generation button, area for the graphical diagram of VAT flows, and area for tabular breakdowns of individual blocks. It is the entry point when opening the report from the menu. |
Separate forms for settings/breakdowns as independent objects are not highlighted — breakdowns are opened programmatically based on ReportForm.
4. Key Module Procedures
The attached evidence does not provide the source code (BSL) of the modules, so below is a typical composition of handlers for this type of object (behavior of the BK configuration 3.0). Specific paths path:string will appear when there is a module export.
Form Module (ReportForm):
OnCreateOnServer— initialization of the default period (usually the current tax period/quarter), substitution of the main organization, restoration ofSettingsCollection, setting visibility of diagram elements.Generate(command) /GenerateOnServer— validation of the period (StartPeriod ≤ EndPeriod), data collection through queries and construction of the graphical diagram of VAT flows.- Handlers for selecting organizations/departments — form
OrganizationListViewandDepartmentListView, filtering for queries. - Breakdown handlers (
BreakdownHandlerarea of the diagram) — open tabular detailing of the selected block (sales, offsets, imports, adjustments) and transition to registering documents.
Report Object Module:
- Procedures for generating results (composition/query): building queries to VAT registers, calculating control totals by blocks, checking the "convergence" of the accrued and offset VAT transactions.
Requires verification (version-specific): the exact list and names of internal procedures for building the diagram may differ between releases 3.0.7x — clarified based on the specific module export.
5. Data Sources, Registers, and Accounting Accounts
The report does not perform postings and does not generate transactions — this is its fundamental feature as an object of the "Report" type. It reads already formed data and matches them. Sources:
Accumulation Registers for VAT (mentioned in evidence as sources for queries):
- turnover registers for VAT (accrued VAT on sales/advances);
- VATAdjustment registers (adjustments and reversals of transactions);
- registers for offsettable (to be offset) VAT, VAT on imports, and by the proportional/separate accounting method.
Checked Transactions and Accounting Accounts (typical chart of accounts of the RK):
| Operation | Dr | Cr | Comment |
|---|---|---|---|
| Sale of goods (income) | 1210 | 6010 | Short-term receivables from customers / income from sales |
| VAT on sales | 1210 | 3130 | VAT payable (16%) |
| Cost of goods sold | 7010 | 1330 | Cost of sales / goods |
| Receipt of goods | 1330 | 3310 | Goods / Payables to suppliers |
| VAT on purchases (to offset) | 1420 | 3310 | VAT to be offset |
| Payment to supplier / receipt from customer | 3310 / 1030 | 1030 / 1210 | Cash in current accounts |
Control Logic. The report matches:
- turnovers on account 3130 "VAT payable" with the turnover of accrued VAT in the registers and with data from ESF/SNT;
- the amount of offsettable VAT with incoming ESF;
- the correctness of applying the rate 16%, zero rate (export), and exempt transactions;
- the completeness of issuing ESF and processing SNT for taxable transactions.
Example: sale of 1,160,000 ₸ with VAT 16% → base 1,000,000 ₸, VAT 160,000 ₸ (Dr 1210 Cr 3130 — 160,000 ₸). The report will check that this VAT is reflected in the registers and confirmed by the issued ESF.
6. Related Objects and Input on the Basis
As a report, the object does not support input on the basis and is not a basis for other objects. Functionally related to:
- VAT registering documents: "Sale of goods and services", "Purchase of goods and services", "Invoice (ESF) issued/received", import documents, "VAT Adjustment", advance transactions — from the report breakdowns, there is a transition to these documents.
- Electronic documents: ESF (ESF information system) and SNT — the report is used for reconciliation before their issuance/submission.
- Regulated reporting: VAT declaration (form 300.00) — the report is used as a control tool before forming the declaration.
- VAT registers and VATAdjustment — as data sources.
7. Extension Points
- Configuration Extensions (BSL extensions): overriding/adding procedures of the form module (
OnCreateOnServer,GenerateOnServer) and the object module to add custom blocks to the diagram or additional checks. - Additional selections: through attributes
OrganizationListView/DepartmentListView— extending filtering logic by organizations/departments. SettingsCollection: saving and replacing user options for diagram formatting.- Subscriptions/general VAT accounting modules: influence on data sources (registers), which the report only reads; adjustments to the VAT offset methodology are reflected automatically.
- Breakdown processing: connecting custom forms for detailing individual blocks of VAT flows.
Requires verification: the availability of specific programming interfaces for extension depends on the compatibility mode and release of the 1C:Enterprise 8.3 platform on which the configuration is deployed.
