--- title: "Document \"Report on the Availability of Issued and Received VAT Invoices\" — Accounting for Kazakhstan 3.0.74.2" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-07 canonical: https://buhgpt.kz/suraqtar/dokument-otchetponalichiyusntvydannyhpoluchennyh-buhgalte-en source: BuhGPT --- # Document "Report on the Availability of Issued and Received VAT Invoices" — Accounting for Kazakhstan 3.0.74.2 > **TL;DR:** 1. Identification Parameter Value Full Name Document.ReportOnAvailabilityOfIssuedReceivedSNT Metadata Type (declared) Document (Documents) Synonym — (not set) Configuration Accounting for Kazakhstan, edition 3.0, version 3.0.74.2 Country of Accounting Republic of Kazakhstan Na --- 1. Identification Parameter Value Full Name Document.ReportOnAvailabilityOfIssuedReceivedSNT Metadata Type (declared) Document (Documents) Synonym — (not set) Configuration Accounting for Kazakhstan, edition 3.0, version 3.0.74.2 Country of Accounting Republic of Kazakhstan Navigation Link e1cib/list/Document.ReportOnAvailabilityOfIssuedReceivedSNT Purpose. The object is intended for monitoring the availability of issued (outgoing) and received (incoming) SNT — accompanying invoices for goods — in the electronic document management system of Kazakhstan. It is used by accountants and tax specialists to reconcile data on SNT, control the timeliness of issuing/receiving documents, and prepare for tax audits. It supports two modes of operation: analysis of issued SNT and analysis of received SNT (attribute ReportType). It is generated regularly — usually before submitting VAT tax returns and during reconciliations with counterparties. Terminological Clarification. SNT (accompanying invoice for goods) and ESF (electronic invoice) are different electronic documents of the ESF information system/module "Virtual Warehouse". This object works specifically with SNT; the original description contains a mix-up with "invoices" — when using the material, focus on SNT. Note on Type. By declaration, this is a Document, however, the composition of attributes (StartPeriod, EndPeriod, ReportType, table parts Grouping, AdditionalFields, Indicators, flags DetailingMode, PlacementOfAdditionalFields) fully corresponds to reporting object / data layout settings storage. Functionally, the object behaves like a report: it generates a tabular document based on accounting data, rather than registering a business transaction. Practical implications of this are in section 5. Where to find in 1C: section “Sales” → “Report on the availability of issued and received SNT”. 2. Attributes and Table Parts 2.1 Header Attributes Name Type Mandatory Purpose StartPeriod Date (dateTime) ShowError Start date of the report generation period. Limits the selection of documents from below. EndPeriod Date (dateTime) ShowError End date of the report generation period. Limits the selection of documents from above. OrganizationListRepresentation String DontCheck Text representation of the list of selected organizations for display in the report form. DepartmentListRepresentation String DontCheck Text representation of the list of selected departments for display in the report form. PlacementOfAdditionalFields Number (decimal) DontCheck Setting the layout of additional fields in the layout (vertically/horizontally). DetailingMode Boolean DontCheck Flag for including detailed data breakdown when double-clicking on a cell. ReportType String ShowError Mode of operation: "AvailabilityOfIssuedSNT" or "AvailabilityOfReceivedSNT". Key parameter determining the direction of analysis. 2.2 Table Parts Grouping — settings for grouping report data (by counterparties, dates, organizations, etc.). Name Type Purpose Usage Boolean Flag for the activity of this grouping. Field String System name of the grouping field (e.g., Counterparty, Organization). Representation String User-defined name of the grouping field. GroupingType EnumRef.StandardReportDetailingType Detailing type: grouping / detailed records / totals only. AdditionalFields — list of additional output fields (beyond the standard set). Name Type Purpose Usage Boolean Flag for including the field in the report. Field String System name of the additional field. Representation String User-defined name of the field. Indicators — numerical output indicators (sums, quantities, etc.). Name Type Purpose Usage Boolean Flag for including the indicator. Field String System name of the indicator (e.g., Sum, Quantity). Representation String User-defined name of the indicator. 3. Forms The composition of forms in evidence is not complete (section 2.3 is truncated). By purpose and composition of attributes, the object uses the following standard set of forms: Form Purpose ReportForm (main) Input of parameters (StartPeriod, EndPeriod, ReportType, selection by organizations/departments), launching the generation and outputting the result in a tabular document. Switching between the modes “issued”/“received” SNT. SettingsForm (layout settings) Management of the composition of groupings, additional fields, and indicators (table parts Grouping, AdditionalFields, Indicators), selection of PlacementOfAdditionalFields and DetailingMode. SelectionForm / ListForm Standard forms for selecting and listing saved report settings options. The specific list of forms and their names are version-specific — clarify the composition of metadata 3.0.74.2 (requires verification only regarding the exact names of forms). 4. Key Procedures of Modules BSL code in evidence is not attached, so below are typical handlers for objects of this type (report/layout settings storage in the form of a document). Paths and strings are indicated when source codes are available; here is the expected composition. Report Form Module: - OnCreateOnServer — initialization of the default period, restoration of settings, setting ReportType and filling OrganizationListRepresentation / DepartmentListRepresentation. - GenerateReport / Formulate — building the result: preparing the data layout scheme (DLS), applying selection by period and organizations, outputting to a tabular document. - OnChangeReportType — restructuring the layout and set of available fields when switching “AvailabilityOfIssuedSNT” ↔ “AvailabilityOfReceivedSNT”. - DetailingProcessing (TabularDocumentDetailingProcessing) — detailing the value of a cell to the source document of SNT when DetailingMode is enabled. - SetDefaultSettings / LoadSettings / SaveSettings — working with the composition of groupings, indicators, and additional fields. Object Module (as with the document): - FillingProcessing — filling in default parameters when creating a new settings element. - FillingCheckProcessing — control of filling mandatory attributes (StartPeriod, EndPeriod, ReportType have ShowError). Handlers ConductProcessing / RemoveConductProcessing for this object do not carry substantive load — see section 5. 5. Conducting and Movements Although the object is declared as a Document, by the composition of attributes and purpose it is a report (layout settings storage) and: - does not generate accounting entries in the chart of accounts of the RK; - does not create movements in accumulation/summary registers (SNT accounting register, VAT, mutual settlements); - works only in read mode: reads already conducted documents of sales/purchases and related SNT for the period StartPeriod … EndPeriod and outputs the reconciliation result. In other words, conducting as such is absent; the result of the object is a generated tabular document. The data analyzed by it relates to the following typical accounting areas of the RK (these accounts appear in the source documents of SNT, not in the report itself): Area RK Account Goods (movement by SNT) 1330 “Goods” Revenue from sales 6010 “Revenue from sales of goods and services” Cost of sales 7010 “Cost of sold goods and services” VAT payable (rate 16 %) 3130 “VAT” Settlements with customers 1210 “Short-term accounts receivable from customers” Settlements with suppliers 3310 “Short-term accounts payable to suppliers” Cash 1030 “Cash in current bank accounts” The VAT rate for transactions reflected in related ESF/SNT is 16 % (Kazakhstan, 2026). 6. Related Objects and Input on the Basis The object has a control-analytical nature, so "input on the basis" is atypical for it. Related objects: - Electronic documents: SNT (accompanying invoice for goods), ESF (electronic invoice) — sources of analyzed data from the ESF information system / "Virtual Warehouse" module. - Source documents for SNT: sale of goods and services, receipt of goods and services, transfers — based on them, SNT are issued/received, the availability of which is checked by the report. - Selection directories: “Organizations”, “Departments”, “Counterparties” (used in selection and groupings). - SNT and VAT accounting registers — sources for sampling when generating the report. - From the report cells (when DetailingMode = True) a transition-detailing to the specific SNT document / source document is available. 7. Extension Points - Configuration extension: adding custom selection attributes in ReportForm and new elements in table parts Grouping / AdditionalFields / Indicators without removing from support. - Interception of form handlers: &Around/&After on GenerateReport, OnChangeReportType, DetailingProcessing — for refining the composition of data and detailing rules. - Additional values of ReportType: introducing new analysis modes (e.g., separate control of canceled/rejected SNT) with expanding the logic of layout construction. - Additional indicators: expanding the list in the table part Indicators for custom reconciliation metrics. - Integration: programmatic generation of the report from external processing/scheduled tasks for automatic reconciliation of SNT before submitting VAT reports. - BSF mechanisms: saving/loading settings options through the standard settings storage subsystem. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_