RUKKENZH
Задать вопрос AI
SectionsОбъекты конфигурации 1С
Report "Debt Structure of Organizations on OPRV" — Accounting for Kazakhstan 3.0.74.2
Язык статьи:🇷🇺 RU🇰🇿 KK🇬🇧 EN🇨🇳 ZH
Версия статьи:📘 Для бухгалтера⚙️ Для тех-специалиста

Report "Debt Structure of Organizations on OPRV" — Accounting for Kazakhstan 3.0.74.2

Applies to: 1С:Бухгалтерия для Казахстана, release 3.0.74.2 · by 1C-Sapa Group, 1C partner
СТ
Сапа Т.И. — Эксперт по 1С и бухгалтерскому учёту, преподаватель-практик

1. Identification

Parameter Value
Object Type Report
Name DebtStructureOfOrganizationsByPensionContributions
Full Name Report.DebtStructureOfOrganizationsByPensionContributions
Alias not set (the name "Debt Structure of Organizations by Pension Contributions" is used in the interface)
Configuration Accounting for Kazakhstan, edition 3.0, version 3.0.74.2
Mechanism Data Composition System (DCS)
Country of Accounting Republic of Kazakhstan, currency — tenge (₸)

Purpose. The report is intended for analyzing the debt structure of organizations for mandatory pension contributions of the employer (MPC) within the framework of the cumulative pension system of the Republic of Kazakhstan. MPC is the employer's contribution from its own funds at a rate of 3.5% of the employee's income (as opposed to the 10% pension contributions withheld from the employee's income). The report is used by accountants and financial controllers to monitor the status of calculations for MPC, plan payments to the Unified Pension Fund/budget, and generate management and control reporting.

The report is built on DCS with support for flexible grouping settings, indicators, selections, and conditional formatting, supports the breakdown mode and integration with the report distribution subsystem.

Where to find in 1C: section "Payroll""Debt Structure of Organizations by MPC".

Navigation link:

e1cib/list/Report.DebtStructureOfOrganizationsByPensionContributions

2. Attributes and Table Parts

The report in DCS does not have posting attributes; the attributes and table parts listed below relate to user-defined composition settings (saved output parameters). For dates, the type xs:dateTime is used, with the requirement DontCheck (unfilled values are allowed and interpreted as "without boundary restrictions").

2.1 Header Attributes

Name Type Mandatory Purpose
StartPeriod xs:dateTime DontCheck The start date of the report generation period. The lower boundary of the time range for analyzing debt.
EndPeriod xs:dateTime DontCheck The end date of the report generation period. The upper boundary of the range.
OrganizationListRepresentation xs:string DontCheck Text representation of the selected organizations for the report header. Automatically generated based on the organizations selected in the settings.
BreakdownMode xs:boolean DontCheck Flag for special breakdown mode. When activated, user settings are disabled, and preset breakdown parameters from the calling context are applied.

2.2 Table Parts

Grouping

Stores settings for data grouping (rows and columns). The user selects an arbitrary number of grouping fields specifying the type of detail.

Name Type Purpose
Usage xs:boolean Flag for the activity of grouping; only marked rows are included in the report.
Field xs:string Technical name of the field from the DCS schema (for example, Organization, TypeOfWorkServices).
Representation xs:string User display name of the field (for example, "Organization", "Type of Work/Services").
GroupingType cfg:EnumRef.StandardReportDetailingType Level of detail: "Only totals", "Detailed", "Without totals". Controls the output of total rows.

Indicators

Stores settings for numerical columns of the report — which summary and quantitative indicators to display.

Name Type Purpose
Usage xs:boolean Flag for the activity of the indicator; only marked indicators are displayed.
Field xs:string Technical name of the indicator from the DCS schema (for example, DebtAmount, PaymentAmount).
Representation xs:string User name of the indicator for the column header.

3. Forms

The standard set of report forms in DCS for the typical configuration:

Form Purpose
Main Report Form (MainReportForm / Form) The main launch form. Contains the table document field of the result, the DCS settings panel (quick selections, groupings, indicators, period), commands "Generate", "Settings", save/select options, output and print.
Settings Form (SettingsForm) Extended form for editing user composition settings: selections, grouping fields, order, conditional formatting. Called from the main form.
Report Variant Form (VariantForm) Management of saved variants (predefined and user-defined) through the "Report Variants" subsystem of the BSP.

In the absence of explicitly defined forms, the platform uses an auto-generated report form based on the composition schema and default settings.


4. Key Module Procedures

In the attached evidence, the texts of BSL modules are not provided, so below are typical report handlers in DCS for the BSP configuration. Specific procedure names in version 3.0.74.2 may differ — requires verification in the configurator for exact signatures.

Report Object Module (ReportObject.ObjectModule):

  • OnResultComposition(DocumentResult, BreakdownData, StandardProcessing) — overrides/complements the output: substitutes values for OrganizationListRepresentation, processes the flag BreakdownMode, programmatically forms the header with the period and list of organizations.
  • OnLoadVariantFromSettings(Settings) / OnSaveVariantInSettings(Settings) — synchronization of user settings (period, groupings, indicators) with the variant storage.
  • HeaderFormationSettings() — assembly of the header text from the selected period (StartPeriodEndPeriod) and list of organizations.

Form Module (Form.FormModule):

  • OnCreateOnServer(Failure, StandardProcessing) — initialization of the default period (current period), setting visibility of panels, connecting the distribution/variant subsystems.
  • Generate(Command)ComposerSettings, OutputReport() — start of composition.
  • Breakdown handler — on double-click sets BreakdownMode = True, disables user settings, and opens detail for the selected cell.

Data Composition Schema (MainDataCompositionSchema):

  • Set of data queries to budget/fund calculation registers (see section 5), parameters StartPeriod, EndPeriod, selection by organizations, calculated fields for debt and payment indicators.

5. Data Sources (for the report — instead of posting)

The report does not perform posting and does not generate movements — it is a read-only object. It builds a selection based on data previously recorded by payroll and tax calculation documents, and by budget calculation registers.

Main Sources (accumulation registers/information of the RK):

  • budget calculation register by types of taxes/contributions (turnovers and balances for MPC) — accrued, transferred, debt at the end of the period;
  • employee accrual register — the basis for calculating MPC.

Logic of MPC Indicators (Kazakhstan, 2026). MPC is calculated by the employer at a rate of 3.5% of the employee's income, from its own funds. The debt indicator of the report = "Accrued MPC − Transferred MPC" broken down by organizations and periods.

Entries that the accrual of MPC creates in accounting (for context; formed by payroll documents, not by the report):

  • Debit of expense account (for example, 7210 "Administrative Expenses" or 8110/8410 — by type of employee engagement) — Credit 3220 "Liabilities for Pension Contributions" (sub-account for MPC) — accrual of MPC;
  • Debit 3220 — Credit 1030 "Cash on Current Bank Accounts" — transfer of MPC to the Unified Pension Fund.

For reference — current calculation parameters of the RK for 2026 (used by related documents affecting the base):

Parameter Value 2026
MPR 4,325 ₸
MSP 85,000 ₸
VAT Rate 16%
Individual Income Tax 10% up to 8,500 MPR annual income, 15% above
Basic Deduction for Individual Income Tax 30 MPR/month, not more than 360 MPR/year
Pension Contribution 10%, ceiling base 50 MSP
MPC 3.5%
Social Health Insurance 2%
Obligatory Social Health Insurance 3%
Social Tax 5%
Social Tax 6%

Typical accounts of the RK plan encountered in related operations: 1210 (short-term receivables from customers), 1030 (cash on current accounts), 1330 (goods), 3310 (payables to suppliers), 3130 (VAT payable), 6010 (revenue from sales), 7010 (cost of sales).


The report is a read-only object, therefore input based on and creation based on it are not applicable (it is not possible to input based on the report, and the report is not input based on a document).

Related objects:

  • Payroll and Contribution Calculation Documents ("Payroll Accrual", "Reflection of Payroll in Accounting", tax/contribution payment documents) — generate data read by the report;
  • Registers of Calculations with the Budget and Funds — the actual source of the selection;
  • Directory "Organizations" — selection and grouping breakdown;
  • Subsystem "Report Variants" (BSP) — storage and selection of settings;
  • Subsystem "Report Distribution" (BSP) — scheduled sending of the generated report;
  • Related reports on budget calculations (for example, reports on pension contributions, social tax, social health insurance) — a common control framework for obligations.

7. Extension Points

  • Report Variants — creation of user-defined variants with saved groupings, selections, and formatting through the standard DCS mechanism, without changing the configuration.
  • Configuration Extensions — overriding the composition schema, adding new fields/indicators, borrowing the object module for refinement of OnResultComposition.
  • Handler OnResultComposition — point for programmatic adjustment of the header, additional formatting, and substitution of OrganizationListRepresentation.
  • External Data Sources / Additional DCS Sets — expanding the selection during refinements.
  • Report Distribution Subsystem — regulatory formation and sending without manual initiation.
  • Breakdown Mode (BreakdownMode) — integration of report calls from other forms in a preset detail context.

Electronic documents of the RK (ESF through IS ESF, SST) are not directly related to this report — the report operates within the framework of calculations for pension contributions, not for sales/VAT.

Частые вопросы

Does this report generate accounting entries?
No. This report is a management accounting report — a read-only object. It does not create entries or movements, but builds a selection based on the registers of calculations with the budget and funds. Entries for mandatory pension contributions (Debit expense account — Credit 3220, then Debit 3220 — Credit 1030 upon payment) are generated by the documents for calculating and paying salaries, not by the report.
What rate is used to calculate mandatory pension contributions in 2026?
Mandatory pension contributions (employer's mandatory pension contributions) are calculated at a rate of 3.5% of the employee's income from the employer's own funds. This is a separate contribution from the mandatory pension contributions (10%, withheld from the employee's income, with a base ceiling of 50 MZP).
What does the flag DetailMode do?
When enabled, user settings are disabled and preset detail parameters from the calling context are applied. It is used when opening the report in detail mode (for example, by double-clicking on a cell or when called from another form).
Where can I find the report in the interface?
Section "Payroll" → "Structure of Organizations' Debt on Mandatory Pension Contributions". Direct navigation link: e1cib/list/Report.StructureOfOrganizationsDebtOnMandatoryPensionContributions.
Can the report be modified without changing the standard configuration?
Yes. For output settings, use user report variants (management accounting). To change the logic or data schema, apply a configuration extension by borrowing the layout schema and object module (handler OnResultLayout).

Read also

Источники

Была ли статья полезна?
💼 Нужна помощь с 1С или учётом? Слава КВЦ — многолетняя практика в 1С в Казахстане. Изучите разложенный НК РК 2026 или спросите в чате BuhGPT — ответит за секунды.