1. Identification
| Parameter | Value |
|---|---|
| Object Type | Catalog |
| Name | EmployeesOfOrganizations |
| Full Name | Catalog.EmployeesOfOrganizations |
| Alias | “Employees” |
| Hierarchy | Hierarchy of groups and elements (folders for classification) |
| Configuration | Accounting for Kazakhstan, edition 3.0.74.2 |
| Where to find (interface) | Section “Personnel Accounting” → “Employees” (also accessible from the “Payroll” section) |
| Navigation Link | e1cib/list/Catalog.EmployeesOfOrganizations |
Purpose. The catalog is the central element of personnel accounting. It stores a record of the employment relationship of a specific individual with the organization and links the individual’s card with the organizational structure (organization, branch, structural unit, position). The same person (one Individual) can be represented in the catalog by multiple entries — according to the number of workplaces (main, external, and internal part-time jobs). The catalog is used in all personnel documents (hiring, personnel transfer, dismissal), in payroll documents, calculation of individual income tax (IIT), mandatory pension contributions (MPC), social medical insurance (SMI), and social tax, as well as in regulated labor reporting.
The key difference from the catalog
Individuals:Individualsdescribes a person (full name, identification number, documents, date of birth), whileEmployeesOfOrganizationsdescribes the workplace of that person in a specific organization.
2. Header Attributes and Table Parts
2.1 Header Attributes
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| Organization | CatalogReference.Organizations |
Not checked | Main organization where the employee works (head organization if branches exist) |
| StructuralUnit | CatalogReference.Organizations |
Not checked | Branch of actual work; may coincide with Organization |
| StructuralSubdivision | CatalogReference.SubdivisionsOfOrganizations |
Not checked | Structural subdivision within the organization (department, workshop, etc.) |
| Individual | CatalogReference.Individuals |
Mandatory (ShowError) | Link to the individual’s card with personal data (full name, identification number, date of birth, documents) |
| Relevance | Boolean |
Not checked | Indicator of the relevance of the employment relationship (True = employed, False = dismissed/archived) |
| EmploymentType | EnumerationReference.TypesOfEmploymentInOrganization |
Not checked | Type of employment relationship: main job, external or internal part-time job |
| NamePostfix | String |
Not checked | Additional text for distinguishing namesakes or clarifying the name of the element |
| CurrentStructuralUnit | CatalogReference.Organizations |
Not checked | Current branch at the moment (cache for quick access without querying registers) |
| CurrentStructuralSubdivision | CatalogReference.SubdivisionsOfOrganizations |
Not checked | Current structural subdivision at the moment |
| CurrentSubdivisionOfOrganization | CatalogReference.SubdivisionsOfOrganizations |
Not checked | Duplicate field of the current subdivision (compatibility) |
| CurrentPositionOfOrganization | CatalogReference.PositionsOfOrganizations |
Not checked | Current position of the employee at the moment |
| DateOfHiring | Date |
Not checked | Date of the start of the employment relationship in this organization |
| DateOfDismissal | Date |
Not checked | Date of termination of the employment relationship (filled in upon dismissal) |
Attributes with the prefix “Current” are denormalized cache. The primary source of information about the subdivision, position, and employment status remains personnel documents and subordinate information registers (
EmployeesOfOrganizations, personnel history). Cache fields are updated when processing personnel documents and serve to speed up the display of lists and filling in new documents.
2.2 Table Parts
AdditionalAttributes
Purpose: storage of user-defined customizable attributes (additional characteristics of the employee), defined through the “Properties” subsystem.
| Name | Type | Purpose |
|---|---|---|
| Property | PlanOfTypesOfCharacteristicsReference.AdditionalAttributesAndInformation |
Type of additional attribute |
| Value | Characteristic.AdditionalAttributesAndInformation |
Value of the attribute (type defined by the property) |
| TextString | String |
Text representation of the value (for types with long text) |
Additional information (as opposed to attributes) is stored outside the object — in the information register
AdditionalInformationand is not reflected in the table part itself.
3. Forms
| Form | Purpose |
|---|---|
| ElementForm | Employee card: input/view of individual, organization, subdivision, position, type of employment, dates of hiring/dismissal; transitions to personnel documents and calculations |
| ListForm | Main list with filtering by organization, subdivision, relevance; group work with employees |
| SelectionForm | Selection of an employee when filling out personnel and payroll documents (considering filtering by organization and relevance) |
| GroupForm | Editing a group (folder) of the hierarchical catalog |
| Hiring Assistant Form (if included in the delivery) | Step-by-step creation of an employee with simultaneous input of the document “Hiring” |
The exact composition of forms is version-specific; in 3.0.74.2, the main input is conducted through
ElementFormand the hiring assistant.
4. Key Module Procedures
Evidence for BSL modules (ObjectModule, ManagerModule, form modules) is not attached to the object. Below are typical handlers characteristic of a catalog of this type in BK 3.0. Specific lines cannot be indicated — marked as a guideline.
Object Module (FillProcessing, BeforeWriting, WhenSettingNewCode):
FillCheckProcessing— control of the mandatory attributeIndividual(ShowError rule); if the individual is not filled, the record is blocked.BeforeWriting— formation/update of the element name (full name of the individual +NamePostfix), control of the uniqueness of the combination “Individual + Organization + EmploymentType”.- Filling cache attributes “Current…” from subordinate personnel data upon writing.
Manager Module (ManagerModule):
- Procedures for forming the representation of the employee, obtaining the current position/subdivision as of the date, obtaining a list of employees of the organization for documents.
Element Form Module:
OnCreatingOnServer/OnReadingOnServer— setting visibility and availability of fields depending onRelevanceand the presence of hiring documents.- Handlers for commands to transition to personnel documents, calculations, references.
Since the object is a catalog, it does not participate in processing and does not have its own
ProcessingProcedure.
5. Processing and Movements
The catalog is not a document and does not generate entries/movements itself. Records in accounting and accumulation registers are created by personnel and payroll documents, in which the employee acts as a measurement/attribute. The role of the catalog is to serve as the analytics (subaccount/measurement) of these movements.
Registers where the employee acts as a measurement/analytics:
- Information register
EmployeesOfOrganizations(personnel history: organization, subdivision, position, type of employment, status) — filled by the documents “Hiring”, “Personnel Transfer”, “Dismissal”. - Accumulation registers for labor accounting, worked time, settlements with the employee, contributions, and deductions.
Where amounts go when calculating salaries (typical entries BK 3.0, chart of accounts RK):
| Operation | Debit | Credit |
|---|---|---|
| Salary accrual (production/expenses) | cost accounting accounts (7210, 8110, etc.) | 3350 “Short-term liabilities for labor payment” |
| Withholding IIT | 3350 | 3120 “IIT” |
| Withholding MPC | 3350 | 3220 “Liabilities for MPC” |
| Accrual of SMI (employee contribution) | 3350 | 3210 “Liabilities for social medical insurance” |
| Social tax, CO, SMI, MPC (at the employer's expense) | cost accounts | 3150/3210/3160, etc. |
| Salary payment | 3350 | 1010/1030 “Cash in hand / on current accounts” |
Numerical norms of RK for 2026 (for calculations involving the employee):
- VAT rate — 16 % (applied in sales/purchases, not in salaries).
- MPR = 4,325 ₸, MSP = 85,000 ₸.
- Basic tax deduction for IIT — 30 MPR per month (= 129,750 ₸), but not more than 360 MPR per year.
- IIT: 10 % on annual taxable income up to 8,500 MPR and 15 % on the excess amount.
- MPC — 10 % (ceiling of the base — 50 MSP = 4,250,000 ₸).
- MPCR — 3.5 %; SMI — 2 %; OSMI — 3 %; CO — 5 %; social tax — 6 %.
The specific accounts for payroll entries and the composition of contributions are configured in the organization's accounting policy and in the catalogs of accruals/deductions; accounts 1030, 1210, 1330, 3310, 3130, 6010, 7010 from the typical chart of accounts RK relate to trade and monetary operations and are not directly linked to the employee catalog.
6. Related Objects and Input Based On
Catalogs:
Individuals— owner of personal data (mandatory link).Organizations,SubdivisionsOfOrganizations,PositionsOfOrganizations— organizational structure.
Documents using the employee:
- “Hiring”, “Personnel Transfer”, “Dismissal” — form the personnel history.
- “Salary Accrual”, “Accrual of Other Income”, “Payroll List”, “Accrual of Leave”, “Sick Leave”.
- Calculation documents for IIT, MPC, MPCR, SMI, OSMI, CO, and social tax.
Input based on (typical scenario): from the employee card, personnel documents (hiring/transfer/dismissal) and payroll accruals are created with auto-filling of organization, subdivision, position, and individual.
Information registers: EmployeesOfOrganizations (relevance and employment parameters), registers of personnel history and accounting of worked time.
Electronic document flow: the catalog does not participate directly in EDO; electronic invoices (ESF) and tax invoices (TI) in the ESF system are generated based on sales/purchase documents and are not related to employees.
7. Extension Points
- Additional attributes and information — through the “Properties” subsystem (table part
AdditionalAttributes+ register ```