--- title: "Report on Obligations for Offsetting Electronic Invoices (ESF)" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-07 canonical: https://buhgpt.kz/suraqtar/otchet-obyazatelstva-po-zachetu-is-esf-reports-obyazatels-en source: BuhGPT --- # Report on Obligations for Offsetting Electronic Invoices (ESF) > **TL;DR:** 1. Identification Parameter Value Object Type Report Name ObligationsForSetoffInESF Full Name Report.ObligationsForSetoffInESF Synonym — (not recorded in the card; displayed in the interface as “Obligations for setoff in ESF”) Configuration Accounting for Kazakhstan, edition 3 --- 1. Identification Parameter Value Object Type Report Name ObligationsForSetoffInESF Full Name Report.ObligationsForSetoffInESF Synonym — (not recorded in the card; displayed in the interface as “Obligations for setoff in ESF”) Configuration Accounting for Kazakhstan, edition 3.0, version 3.0.74.2 First Appeared release 3.0.73 Construction Mechanism Data composition system (DCS) Records Movements No. The report is a read-only object Purpose. A control and analytical report that supports work with the Electronic Invoice Information System (ESF). It shows the organization's obligations related to setoff in the ESF — items that still need to be matched/closed in the interaction of accounting data with the electronic invoice system. The main users are accountants and chief accountants working with ESF and virtual warehouses. The report is used when reconciling accounting data with the ESF, usually before closing the period or submitting tax returns. It does not post or record anything — it helps to see outstanding obligations and address them in a timely manner. Where to find. Navigation link in 1C: e1cib/list/Report.ObligationsForSetoffInESF Typically available from the section dedicated to electronic documents / ESF (invoices, virtual warehouses, accompanying documents). 2. Attributes and Table Parts The report is built on DCS, so "attributes" and "table parts" are not fields of the metadata object (attributes and tabular_sections in the object card are empty), but parameters and settings of the data composition scheme displayed on the form. 2.1 Parameters (attributes of the form header) The exact names of the parameters are not recorded in the object card — they should be read from the report form. According to the standard template of the analytical report in DCS in "Accounting for Kazakhstan," the following are present: Field (standard) Purpose Organization Legal entity for which obligations to the ESF are analyzed. Mandatory selection in a multi-company database Period / Start of Period / End of Period Analysis boundaries. For reconciliation before closing, the tax period (month/quarter) is taken DCS Settings (groupings, selections, indicators) Management of detail: by counterparties, by ESF/SNT documents, by nomenclature of the virtual warehouse The exact names of the parameters are version-specific; check against the form of the specific release. 2.2 Table Parts (configuration tables of the report) The metadata object does not have its own table parts. The configuration tables of DCS (usually "Grouping," "Additional Fields," "Indicators," "Selections") are formed by the composition scheme and are available through user settings. Their composition is determined by the layout of the DCS report, not by the structure of the object. 3. Forms The object card has an empty list of forms (forms not filled). For the report in DCS, the platform uses a self-generated main report form (standard name ReportForm), if a custom form has not been created. It provides: - settings panel (period, organization, selections, groupings); - button “Generate”; - tabular document of the result; - saving/selecting options and user settings. The exact name and composition of the form should be read from the interface of the specific release. 4. Key Module Procedures Evidence with BSL code (path:string) to this object is not attached — metadata card is empty. Below is a standard set of handlers for the report in DCS (implemented in the report object's module and/or in the form module): Procedure / Handler Where What it does (standard logic) OnResultComposition(...) Report object module Programmatic intervention in composition: fine-tuning the layout, selections, formatting before outputting the result OnCreationOnServer(...) Form module Form initialization: setting default period, substituting organization, pre-setting selections OnOpening(...) Form module Fine-tuning the interface upon opening Handler for the “Generate” command Form module Launching composition and outputting the result in a tabular document SetDefaultSettings() (or similar) Form module Initial values of user settings The main business logic of such a report is usually implemented declaratively — in the data composition scheme (query to the registers of the ESF subsystem), rather than in procedural code. 5. Posting and Movements The report is not posted and does not generate movements — it has no entries in the accounting register, movements in accumulation/summary registers, or records in the information base. This is a read-only object (Reports) that performs selection and aggregation of already existing data. The data source for the report is the registers of the ESF and virtual warehouses, filled with documents ESF and SNT: - GoodsInVirtualWarehouses — balances/movements of goods in the ESF information system's virtual warehouses; - GoodsInVirtualWarehouseInReserve — reserved items of the virtual warehouse; - registers of matching/setoff of ESF (data on issued/received ESF requiring setoff). For context — what entries generate the data that the report then analyzes (standard chart of accounts of the RK, VAT rate 16% for 2026): Operation Debit Credit Sale of goods to the customer 1210 (short-term receivables from customers) 6010 (revenue from sales) VAT accrued on sales (16%) 1210 3130 (VAT payable) Cost of goods sold written off 7010 (cost of sales) 1330 (goods) Receipt of goods from the supplier 1330 3310 (payables to suppliers) Payment from the customer 1030 (cash in current accounts) 1210 Example: sale of 1,000,000 ₸ without VAT → VAT = 1,000,000 × 16% = 160,000 ₸ (Debit 1210 Credit 3130), total receivable 1,160,000 ₸. The report does not make these entries — it shows which ESF (of the virtual warehouse) positions remain uncredited concerning accounting movements. 6. Related Objects and Input Based On - ESF Document (electronic invoice) — the main data source of the ESF information subsystem. - SNT Document (accompanying invoice for goods) — movement of goods in virtual warehouses. - Registers "GoodsInVirtualWarehouses," "GoodsInVirtualWarehouseInReserve," and ESF setoff registers — actual sources of selection. - Primary documents of sales/receipts (sale of goods, receipt of goods), forming receivables/payables and VAT. Input based on is not provided for the report (reports do not participate in the "input based on" mechanism). Navigation (drill-down) to source documents is possible from the report form using standard DCS tools. 7. Extension Points - Report variants and user settings — standard configuration of groupings, selections, conditional formatting without changing the configuration. - Configuration extension — adding a custom form/variant, intercepting OnResultComposition, changing the composition scheme (adding fields, resources, data sets). - Modification of the DCS layout — including additional registers/indicators of the ESF subsystem. - Form handlers (OnCreationOnServer, "Generate" command) — for programmatic pre-setting of selections and integration with external checks of the ESF information system. The exact composition of indicators and the composition algorithm in the object card are not disclosed (metadata is empty) — when modifying, rely on the DCS layout and the query of the specific release 3.0.74.2. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_