--- title: "Document \"Input of Information on Planned Employee Deductions of Organizations\" - Technical Description" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-07 canonical: https://buhgpt.kz/suraqtar/dokument-vvodsvedeniyoplanovyhuderzhaniyahrabotnikovorgan-en source: BuhGPT --- # Document "Input of Information on Planned Employee Deductions of Organizations" - Technical Description > **TL;DR:** 1. Identification Parameter Value Object Type Document (Documents) Name InputInformationOnPlannedDeductionsOfEmployeesOfOrganizations Full Name Document.InputInformationOnPlannedDeductionsOfEmployeesOfOrganizations Synonym Input information on planned deductions of employees o --- 1. Identification Parameter Value Object Type Document (Documents) Name InputInformationOnPlannedDeductionsOfEmployeesOfOrganizations Full Name Document.InputInformationOnPlannedDeductionsOfEmployeesOfOrganizations Synonym Input information on planned deductions of employees of organizations Configuration Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) Interface Section Payroll Calculation Navigation Link e1cib/list/Document.InputInformationOnPlannedDeductionsOfEmployeesOfOrganizations 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 Attribute Type Required Purpose Number String auto Document number, assigned automatically Date Date yes Date of document registration Organization ReferenceLink.Organizations yes Organization to which the deductions relate Responsible ReferenceLink.Users no User responsible for the document Comment String no Arbitrary comment 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). Column Type Required Purpose Individual / Employee ReferenceLink (Employees / Individuals) yes Employee to whom the deduction applies Calculation Type PlanCalculationTypesLink.OrganizationDeductions yes Type of planned deduction (alimony, loan, union fee, etc.) Action Enumeration (TypesOfActionsWithDeduction) yes "Start of action", "Change of parameters", "Termination of action" Amount Number conditional Amount or percentage of deduction depending on the calculation type Indicator / CalculationMethod — conditional Method of calculation (fixed amount, percentage of base, etc.) ActionDate / StartDate Date conditional Date from which the deduction starts/terminates EndDate Date no Planned end date of the deduction (if known) Mandatory columns: Individual, Calculation Type, Action. If not filled — error "Field ... is not filled", processing is blocked. 3. Forms Form Purpose DocumentForm Main form for entering and editing the header and table part "Deductions". Contains input control (one row per employee) and logic for selecting calculation types. ListForm List of documents of the type "Input information on planned deductions" filtered by organization, period, and responsible person. Opens via navigation link. SelectForm Selecting a document from other configuration objects (if necessary for linking). 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: - Temporary tables are created: - AttributesTable — document attributes (date, organization, document reference); - DeductionsTable — data of the table part "Deductions" with additional fields for processing. - 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. - 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: Register Type What it records InformationRegister.PlannedDeductionsOfEmployeesOfOrganizations Information register Active planned deductions: Individual, Calculation Type, Amount, period of action, termination indicator 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: Economic Operation Debit Credit Salary accrual (expense) 7010 / 8110, etc. 3350 (short-term debt for labor payment) Withholding from salary (alimony, loan, union fee) 3350 3390 / 3520 (other KZ for withholdings) Transfer of withheld amount to the recipient 3390 / 3520 1030 (money in current accounts) 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 Object Role PlanCalculationTypes.OrganizationDeductions Defines types of planned deductions and the procedure for their calculation InformationRegister.PlannedDeductionsOfEmployeesOfOrganizations Receiver of movements of the document Reference.Employees / Reference.Individuals Employees — subjects of deductions Payroll documents (for example, "Salary Accrual for Employees of Organizations") Consumer of the register data: apply deductions during calculation Reference.Organizations Employer organization 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). --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_