1. Identification
| Parameter | Value |
|---|---|
| Object Type | Report |
| Name | EmployeeListsOfOrganizations |
| Full Identifier | Reports.EmployeeListsOfOrganizations / Report.EmployeeListsOfOrganizations |
| Synonym | Lists of employees of organizations (in the interface — "Lists of organization employees") |
| Configuration | 1C:Accounting for Kazakhstan, edition 3.0 (3.0.74.2) |
| Implementation Basis | Data Composition System (DCS) |
Purpose. The report is intended for generating personnel lists of employees by organizations and structural subdivisions. It is used by the HR department and payroll accountants to obtain current summaries on the number and composition of personnel with flexible settings for groupings, selections, additional fields, and conditional formatting. It can be generated for a specific date or for a period — for analyzing the current and historical composition of organizations. The report can be included in the automatic mailing mechanism.
Where to find in 1C: section "Personnel Accounting" → "Lists of organization employees".
Navigation link: e1cib/list/Report.EmployeeListsOfOrganizations
2. Header Attributes and Table Parts
2.1 Header Attributes (Report Settings)
These are not document attributes, but saved report settings parameters. All are optional (mode DontCheck).
| Name | Type | Purpose |
|---|---|---|
| Period | dateTime |
Date or period for which the employee list report is generated |
| OrganizationListRepresentation | string |
Text representation of selected organizations for the report header and settings |
| SubdivisionListRepresentation | string |
Text representation of selected structural subdivisions for display to the user |
| AdditionalFieldsPlacement | decimal |
Method of placing additional fields in the layout (in columns, in rows, or separately) |
| DetailingMode | boolean |
Indicator of detailing mode when opening the report from another report/processing (detailing) |
2.2 Table Part "Grouping"
Configuration of the hierarchical structure of data output indicating the type of detailing at each level.
| Name | Type | Purpose |
|---|---|---|
| Usage | boolean |
Enabling/disabling a specific grouping in the generated report |
| Field | string |
Identifier of the composition scheme field by which grouping is performed |
| Representation | string |
User-defined name of the grouping in the settings interface |
| GroupingType | EnumRef.GroupingDetailingTypes |
Method of detailing: only grouping / only detailed records / grouping and detailed records |
2.3 Table Part "AdditionalFields"
Management of additional columns displayed alongside the standard set of indicators.
| Name | Type | Purpose |
|---|---|---|
| Usage | boolean |
Inclusion of an additional field in the report result |
| Field | string |
Identifier of the field from the available data set of the composition scheme |
| Representation | string |
Name of the field for the column header |
3. Forms
| Form | Volume | Purpose |
|---|---|---|
| ReportForm | ~377 elements | Main (only) report form: setting the period and parameters, selecting groupings and additional fields, selections, sorting, conditional formatting, generating and viewing the result |
There are no separate settings forms, variants, or subordinate forms for the object — all work is done from ReportForm, which relies on the standard data composition mechanism.
4. Key Procedures of Modules
The attached evidence text of BSL modules is not provided, so below are typical report handlers for DCS for this configuration. The paths indicate the modules where these procedures are located in reports of this type.
Report Object Module (Report.EmployeeListsOfOrganizations.ObjectModule)
OnResultComposition(DocumentResult, DataDetailing, StandardProcessing)— interception of composition: substitution of period/selections by organizations and subdivisions, layout reconfiguration, processingAdditionalFieldsPlacement.SettingsForDataAnalysisTechnology()/ service methods for forming the scheme — when using a dynamic composition scheme.
Form Module (Report.EmployeeListsOfOrganizations.Form.ReportForm.Form)
OnServerCreation(Refusal, StandardProcessing)— form initialization, restoration of saved settings, setting the period.OnOpening(Refusal)— reconfiguration of commands, auto-filling the period with the current date.- Handlers for selecting organizations/subdivisions — forming
OrganizationListRepresentationandSubdivisionListRepresentation. - Standard handlers of the composition mechanism (
Generate, updating quick settings, conditional formatting).
Since the report inherits the basic functionality of BCP (subsystem "Report Variants"), the main logic of composition, saving variants, and detailing is performed by the common BCP modules, not by the object's own code.
5. Posting and Movements
The report is not posted and does not generate movements. An object of type "Report" does not write to accumulation registers, accounting registers, or information registers and does not create accounting entries. It only reads data.
The data sources of the report are the registers of personnel and payroll accounting (information on hiring/termination, personnel movements, current composition of organizations and subdivisions). The report does not generate financial movements on accounts ("1210", "1030", "3310", "6010", "7010", etc.) — these accounts of the standard chart of accounts of the RK relate to accounting operations of other configuration objects and are not involved here. Similarly, the report does not participate in the calculation of individual income tax (IIT), mandatory pension contributions (MPC), social health insurance (SHI), and social tax — it outputs reference-personnel information about the employee list.
If it is necessary to obtain data with monetary/tax indicators for employees, specialized payroll reports of the configuration are used; settings relevant for 2026 parameters of the RK (VAT rate 16%, MRP 4,325 ₸, MZP 85,000 ₸, deduction for IIT 30 MRP/month and no more than 360 MRP/year, IIT 10%/15%, MPC 10% with a base cap of 50 MZP, MPCR 3.5%, SHI 2%, OSHI 3%, social tax 5%, social tax 6%) are set in the accounting policy and constant registers, not in this report.
6. Related Objects and Input on Basis
- Input on basis — absent. Reports do not participate in the input on basis mechanism.
- Data Sources: directories "Organizations", "Subdivisions", "Employees", registers of personnel accounting and payroll calculations.
- Adjacent Objects: other personnel reports of the "Personnel Accounting" and "Payroll" subsystems, report mailing mechanism (BCP), "Report Variants" subsystem.
- Electronic Document Management (ESF/IS ESF, STS): has no relation to this report — it is a personnel list, not a primary/tax document.
7. Extension Points
- Report Variants (DCS): adding user variants through the "Report Variants" subsystem of BCP without changing the configuration.
- Additional Fields: through the table part
AdditionalFieldsand attributeAdditionalFieldsPlacement— expanding the composition of displayed columns from the available set of the composition scheme. - Configuration Extensions: overriding
OnResultCompositionin the object module and handlers ofReportFormto add custom selections, fields, and formatting. - Data Composition Scheme: refinement of the main DCS (adding data sets, calculated fields, resources) — preferably through extension to maintain support for the standard.
- Automatic Mailing: inclusion of the report in the scheduled mailing using BCP tools.
Version-specific (requires verification when transferring to another release): the exact composition of elements of
ReportFormand internal names of fields in the composition scheme may differ between sub-releases 3.0.7x.
