Document "Input of Information on Planned Employee Deductions of Organizations" - Technical Description

1. Identification

Purpose. The document is intended for the centralized input and management of planned (regular) deductions from the salaries of employees of Kazakhstani organizations. It is used by HR specialists and payroll accountants to register union fees, alimony, loan repayments, voluntary insurance contributions, and other permanent deductions.

The document works in conjunction with the calculation type plan "Deductions of Organizations" and the information register "Planned Deductions of Employees of Organizations." The data entered by the document is automatically applied during payroll calculations. It is used as needed: when hiring new employees with existing deductions, changing conditions, or terminating actions.

Note: Planned deductions (alimony, loans, union fees) should not be confused with mandatory taxes and contributions, which are calculated automatically according to the RK norms for 2026: PIT 10% (15% over 8,500 MRP annual income), OPE 10% (base ceiling 50 MZP), OPEA 3.5%, VOSMS 2%, OSMS 3%, SO 5%, social tax 6%. The basic tax deduction for PIT is 30 MRP per month, but no more than 360 MRP per year. MRP = 4,325 ₸, MZP = 85,000 ₸.

Where to find in 1C: section "Payroll Calculation" → "Input information on planned deductions of employees of organizations".

2. Header Attributes and Table Parts

2.1 Header Attributes

Mandatory header attribute: Organization. If the field is not filled, 1C will not process the document and will issue an error "Field ... is not filled".

2.2 Table Part "Deductions"

The main table part of the document. Only one row is allowed per employee (controlled by the form).

Mandatory columns: Individual, Calculation Type, Action. If not filled — error "Field ... is not filled", processing is blocked.

3. Forms

4. Key Module Procedures

From evidence by configuration code:

• Document form — employee selection processing (Form.DocumentForm / handler OrganizationEmployeesEmployeeSelectionProcessing): ensures that there is only one row per employee. Condition in the code: EmployeeRows.Count() > 0 AND Elements.OrganizationEmployees.CurrentData.Individual <> SelectedValue → issues message “Only one row can be entered for one employee in this document!” (verbatim from release 3.0.68.1).

• Manager module (ManagerModule) — preparing movements:

  1. Temporary tables are created:
     • AttributesTable — document attributes (date, organization, document reference);
     • DeductionsTable — data of the table part "Deductions" with additional fields for processing.
  2. Queries form movements: extracts Individual, Calculation Type, Action, Amount, dates; for each row, a record is created in the register indicating the period of action of the deduction.
  3. Processing of action types:
     • “Start of action” — new record in the register with ActionDate as the start of the period;
     • “Change of parameters” — new version of the record with changed parameters (the old one is closed by date);
     • “Termination of action” — record is marked as terminated from the specified date.

Standard document handlers of this type (standard implementation of 1C):

• ProcessingConducting — calls manager module procedures to form movements in the information register;
• ProcessingFilling — pre-fills attributes (organization, date) when creating;
• ProcessingCheckFilling — controls mandatory fields (Organization, Individual, Calculation Type, Action);
• in the form — OnCreationOnServer, OnChange of row attributes for recalculating indicators.

5. Processing and Movements

The document does not generate accounting entries (it is not a financial and economic operation by itself) — it registers normative and reference information about planned deductions.

Movement Register:

Movements in the register are formed depending on the value of the "Action" column: start of action → new record; change → new version with closure of the previous one; termination → marking of completion.

Where entries occur. Actual accounting entries for deductions are generated by the payroll document, which reads data from the register PlannedDeductionsOfEmployeesOfOrganizations. When calculating and withholding, the standard chart of accounts of the RK is used, for example:

The specific credit accounts for deductions depend on the configuration of the calculation type "Deductions of Organizations" and are assigned in the organization's accounting policy. The document under consideration does not make entries in the accounts.

6. Related Objects and Input on Basis

Input on Basis. The document is usually entered independently. Typical scenarios for application:

• registration of a new deduction when hiring an employee with existing deductions (alimony, loan, union fees);
• change of the amount of an existing deduction (new enforcement order, employee's application);
• termination of a deduction (dismissal, loan repayment, expiration of the enforcement order);
• mass filling of a similar deduction for a group of employees (for example, union fees for all union members);
• manual adjustment of movements in the register in exceptional cases (error correction, data migration).

7. Extension Points

• Configuration extension: adding header/table part attributes (for example, reference to the enforcement order, attributes of the alimony recipient) through an extension without removing from support.
• Form handlers: overriding/adding OnCreationOnServer, BeforeRecording, employee selection handlers for custom validation.
• Manager module: refinement of movement formation (ProcessingConducting) for non-standard logic of versioning records in the register.
• Event subscriptions: subscribing to BeforeRecording/OnRecording of the document for integration with external HR/payroll accounting systems.
• Additional reports and processing (BSP): mechanism for external processing for mass filling of the table part "Deductions".
• Additional attributes and information (BSP): adding properties of the document without changing metadata.

Requires verification in a specific release: the exact composition of the enumeration "Action" and the set of columns in the table part "Deductions" may differ between versions (evidence by code refers to release 3.0.68.1; current — 3.0.74.2).