--- title: "Report \"Information on Acts of Completed Works\" (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/otchet-svedeniya-po-aktam-vypolnennyh-rabot-buhgalteriya--en source: BuhGPT --- # Report "Information on Acts of Completed Works" (Accounting for Kazakhstan 3.0.74.2) > **TL;DR:** 1. Identification Parameter Value Object Type Report Name InformationOnCompletedWorkActs Full Name Report.InformationOnCompletedWorkActs Synonym Information on completed work acts Configuration Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) Mechanism Basis Data comp --- 1. Identification Parameter Value Object Type Report Name InformationOnCompletedWorkActs Full Name Report.InformationOnCompletedWorkActs Synonym Information on completed work acts Configuration Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) Mechanism Basis Data composition scheme (DCS) Navigation Link e1cib/list/Report.InformationOnCompletedWorkActs Purpose. The report is intended for the analysis and control of completed work (services) by organizations, departments, counterparties, contracts, and nomenclature for the specified period. It is used by accountants and managers to obtain summarized information on completed work acts with flexible grouping and selection. It is generated based on the data composition scheme and prints the signatures of the manager and chief accountant. It is used regularly (monthly, quarterly) for management and regulatory accounting purposes. Where to find in 1C: section “Sales” → “Information on completed work acts”. Direct transition — via the navigation link e1cib/list/Report.InformationOnCompletedWorkActs. Important: this is a reporting object. It does not create entries or movements in the registers — it only reads accounting data and outputs it in a tabular document (see section 5). 2. Attributes and Table Parts The report is based on the DCS, so the “header attributes” are parameters and settings of the composition scheme, not attributes of the document object. Below are the fields from evidence. 2.1 Header Attributes (Parameter Settings) Name Type Mandatory Purpose StartPeriod xs:dateTime Not checked (DontCheck) Start date of the reporting period, lower limit of the selection of completed work acts EndPeriod xs:dateTime Not checked (DontCheck) End date of the reporting period, upper limit of the selection of acts OrganizationListRepresentation xs:string Not checked Text representation of selected organizations for the report header DepartmentListRepresentation xs:string Not checked Text representation of selected departments for report settings AdditionalFieldsPlacement xs:decimal Not checked Numeric code for the placement of additional fields in the layout (horizontal/vertical) DetailingMode xs:boolean Not checked Flag for generating the report with the possibility of detailing (breakdown) of data 2.2 Table Parts Grouping Stores settings for data grouping (hierarchy of analytical cuts). Name Type Purpose Usage xs:boolean Whether the field is used for grouping in the current report variant Field xs:string System name of the grouping field (e.g., “Organization”, “Department”, “Counterparty”) Representation xs:string User representation of the grouping field GroupingType EnumRef.GroupingDetailingTypes Type of detailing (Only totals, With detailed records, Without totals, etc.) AdditionalFields Optional fields displayed in the report in addition to the standard set of indicators. Name Type Purpose Usage xs:boolean Whether the field is displayed in the report Field xs:string System name of the additional field (e.g., “ActNumber”, “ActDate”, “Comment”) Representation xs:string User representation of the report column Indicators Stores a list of displayed numerical indicators (summative and quantitative measures). According to the standard logic of reports of this class, it includes indicators such as the total amount of completed work excluding VAT, VAT amount, total amount including VAT; each indicator has a Usage flag, a system Field, and Representation. VAT amounts are calculated at a rate of 16% (VAT rate of the RK, effective from 2026), currency — tenge (₸). 3. Forms For reports on DCS, custom forms are usually minimal — the interface is built dynamically based on the composition settings. Form Purpose Main Report Form (ReportForm / Form) Setting the period, selections (organization, department, counterparty), choosing the variant, starting the generation and outputting the result in the tabular document field. If a custom form is not specified — an automatically generated DCS form is used. Settings Form (if available) Extended editing of the structure, selections, conditional formatting, and user fields of the composition. Report Variants Predefined composition variants (sets of groupings and indicators) selected by the user. The printed form is generated by the DCS into a tabular document; the signatures of the manager and chief accountant of the organization are displayed in the footer. 4. Key Module Procedures The program code (BSL) of the modules is not attached in evidence, so below are typical report handlers for this configuration: - OnResultComposition(ReportResult, BreakdownData, StandardProcessing) — object module. Main intervention point: intercepting output, programmatically filling parameters (StartPeriod, EndPeriod, list representations), adjusting the layout, substituting signatures of the manager and chief accountant. - OnResultCompositionStart / OnResultCompositionEnd — when using the library wrapper for report generation (BSP): preparation and post-processing of the result. - OnCreateOnServer(Failure, StandardProcessing) — report form: initializing default settings, setting the period, selection by organization from session parameters. - OnPeriodChange / OnSelectionChange — form handlers: rebuilding representations of lists of organizations and departments (OrganizationListRepresentation, DepartmentListRepresentation). - SetDetailing / ToggleDetailingMode — managing the DetailingMode flag, enabling detailing in the composition structure. Requires verification in a specific build: the exact composition of handlers and module procedure names may differ between releases 3.0.7x. 5. Data Sources (analog of “Postings and Movements”) The report does not create postings or movements — it selects already formed accounting data. The sources are documents for the provision of work/services (“Sale of goods and services”, “Act of completed work”) and the corresponding registers of accounting and accumulation. According to the standard chart of accounts of the RK, the data reflected in the report is formed by source documents with the following postings (for reference, VAT rate 16%): Operation Debit Credit Comment Revenue from the sale of work (services) 1210 — short-term receivables from customers 6010 — revenue from sales Amount excluding VAT Accrual of VAT on sales 1210 3130 — VAT payable VAT 16% of the sales amount Cost of goods sold (if applicable) 7010 — cost of sales 1330 — goods May be absent for services Receipt of payment 1030 — cash in current accounts 1210 Repayment of customer debt Example of VAT calculation. The cost of work according to the act is 1,000,000 ₸ excluding VAT. VAT = 1,000,000 × 16% = 160,000 ₸. Total amount payable — 1,160,000 ₸. In the report by indicators: “Excluding VAT” = 1,000,000 ₸, “VAT” = 160,000 ₸, “Including VAT” = 1,160,000 ₸. The report primarily reads data from the accounting register “Cost Accounting” (turnovers on accounts 6010, 1210) and/or from the accumulation registers for sales; the specific set of data sets is determined by the report composition scheme. 6. Related Objects and Input on the Basis The report is a data consumer, so “input on the basis” is not provided for it. Related objects: - Source Documents: “Sale of goods and services”, “Act of completed work”, service provision documents. - Analytical Directories: “Organizations”, “Departments”, “Counterparties”, “Counterparty Contracts”, “Nomenclature”. - Electronic Documents of the RK: for the sale documents included in the report, ESF (electronic invoice, ESF IS) are issued and if necessary SNT (accompanying invoice for goods). The report itself does not generate ESF/SNT but serves as a tool for reconciling sales volumes with issued ESF. - Drill-down: from the report cells with DetailingMode enabled, you can access detailed records and source documents. 7. Extension Points - DCS Settings / User Variants — adding groupings, selections, conditional formatting, and user fields without changing the configuration. - Handler OnResultComposition (configuration extension) — programmatic adjustment of the result, adding columns, changing signatures. - Table Part “AdditionalFields” — standard mechanism for outputting optional fields (“ActNumber”, “ActDate”, “Comment”) with management via AdditionalFieldsPlacement. - Configuration Extension — overriding the form, adding custom data sets to the composition scheme, new parameters. - Additional Reports (external) — connecting a modified copy through the subsystem of additional reports and processing without removing from support. Requires verification in a specific build: the list of predefined report variants and the composition of fields in the composition scheme may differ between releases 3.0.7x. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_