RUKKENZH
Задать вопрос AI
SectionsОбъекты конфигурации 1С
Document "Termination from Organizations" - Technical Description (Accounting for Kazakhstan 3.0.74.2)
Язык статьи:🇷🇺 RU🇰🇿 KK🇬🇧 EN🇨🇳 ZH

Document "Termination from Organizations" - Technical Description (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 Document (Documents.TerminationFromOrganizations)
Name TerminationFromOrganizations
Synonym “Termination from organization”
Configuration 1C:Accounting for Kazakhstan, edition 3.0 (release 3.0.74.2)
Numbering string, length of the number 11 characters, numbering frequency — within the year
Where to find section “Personnel Management” → “Termination from organization”
Navigation link e1cib/list/Document.TerminationFromOrganizations

Purpose. The document registers the fact of termination of employment relations with one or more employees. When processed, it:

  • fixes the status “terminated” in personnel accounting;
  • closes (terminates from the date of termination) planned accruals and planned deductions of the employee;
  • terminates the application of standard and other tax deductions for individual income tax (IIT);
  • serves as the basis for printing the termination order.

The document does not generate accounting entries by itself — the final calculation upon termination (accrual of compensations, withholding of IIT, OIW, VOSMS, etc.) is performed by the document “Salary Calculation” and related calculation documents. Main users: HR specialists and payroll accountants.

2. Header Attributes and Table Parts

Header Attributes

Attribute Type (standard) Purpose Mandatory
Number String(11) Document number auto-assigned
Date Date Date of document registration yes
Organization ReferenceLink.Organizations Employer organization from which employees are terminated mandatory
Responsible ReferenceLink.Users User responsible for the document no
Comment String Arbitrary comment no

The flag TerminateStandardDeductions controls whether the document will terminate the application of standard tax deductions for IIT (see section “Movements”). It is set at the document/line level depending on the version of the form.

Table Part “EmployeesOfOrganization”

The main table part is the list of terminating employees.

Column Type (standard) Purpose Mandatory
Employee ReferenceLink.Employees Terminating employee mandatory
TerminationDate Date Date of termination of employment relations; used as the movement period and the closing point of planned records mandatory
TerminationBasis / ArticleLaborCode ReferenceLink / Enumeration Basis (article of the Tax Code of the RK) for the order no
TerminateStandardDeductions Boolean Terminate the application of standard deductions for IIT for the employee no

Integrity constraint: only one line per employee is allowed in the document. When attempting to add a duplicate, the message is displayed: “Only one line can be entered for one employee in this document!” (check in the document form / selection handler: Object.EmployeesOfOrganization.FindRows(New Structure("Employee", ArrayString)).Count() = 0).

3. Forms

Form Purpose
DocumentForm Main input form: header (organization), filling the table part with employees, setting termination dates and bases. Contains client logic for checking employee duplicates and a selection handler.
ListForm Journal of termination documents: filtering, searching, bulk editing of attributes (for example, changing the responsible person). Opens via the link e1cib/list/Document.TerminationFromOrganizations.
Printed Forms Termination order (generated after processing the document).

4. Key Procedures of Modules

Below are the procedures and functions confirmed by the evidence of the configuration.

Manager Module (ManagerModule):

  • PrepareProcessingParameters (≈59 lines) — prepares data for processing: collects temporary tables TableEmployees, TablePlannedAccruals, TablePlannedDeductions, TableIITPlannedDeductions, ApplicationDeductionsIIT, StandardDeductionsIIT, OtherDeductionsIIT. In total, there are 4 data selection queries in the manager module.
  • GetTaxpayerForApplicationDeductionsIIT (≈32 lines) — determines the taxpayer (individual) for the correct termination of the application of IIT deductions for the employee.

Server Common Module:

  • SalaryCalculationServer — implements the logic of closing planned accruals and deductions from the date of termination (in the context of the document — 5 calls). It is here that planned records are “cut off” by the termination date.

Document Form:

  • Form handlers contain 2 queries and client checks for the uniqueness of the employee in the table part (selection handler / SelectionHandler).

If specific printing/filling procedures in a particular release are absent in the evidence, standard document handlers are used: ProcessingConducting, ProcessingFilling, OnSettingNewNumber, FillByEmployeerequires verification in the specific release 3.0.74.2.

5. Processing and Movements

When processed, the document generates records in information registers (the document does not create accounting entries according to the chart of accounts):

# Register (InformationRegister) What Happens
1 EmployeesOfOrganizations Registers the termination of employment relations. Dimensions: Organization, Employee; period = TerminationDate; resource status → Employed = False.
2 PlannedAccrualsEmployeesOfOrganizations Closes planned accruals (salary, allowances) from the date of termination. Logic — through SalaryCalculationServer.
3 PlannedDeductionsEmployeesOfOrganizations Closes planned deductions (alimony, loans, professional contributions) from the date of termination.
4 DeductionsIndividualsIIT When TerminateStandardDeductions = True terminates the application of standard deductions for IIT.
5 ApplicationDeductionsIIT Registers the termination of the application of deductions from the date of termination.
6 IITPlannedTaxDeductionsIndividuals Closes planned records of IIT deductions.
7 OtherDeductionsIndividualsIIT Closes other deductions (if applicable).

How it relates to calculation. The calculation upon termination and its entries are generated by the document “Salary Calculation” (and, if necessary, “Vacation Compensation”, “Payment”). The termination document only correctly closes planned records and deductions so that the subsequent calculation is performed according to the norms of the RK for 2026:

  • Basic deduction IIT — 30 MRP per month (not more than 360 MRP per year). MRP = 4,325 ₸, thus the monthly deduction = 30 × 4,325 = 129,750 ₸.
  • IIT: 10% up to 8,500 MRP of annual income, 15% on the amount exceeding the threshold.
  • OIW 10% (ceiling base — 50 MZP; MZP = 85,000 ₸, that is 4,250,000 ₸), OIW 3.5%, VOSMS 2%, OSMS 3%, SO 5%, social tax 6%.

Example of entries for subsequent calculation/payment (accounts of the standard chart of the RK; generated not by the termination document, but by calculation documents):

Operation Debit Credit
Payment of calculation from current account 3350 “Short-term liabilities for wages” 1030 “Cash on current accounts”
Withholding IIT 3350 3120 “IIT”
Accrual of social tax 7210/8410 3150 “Social tax”

For operations of realization/calculations with counterparties in the RK, the following accounts are used: 1210 (short-term receivables from buyers), 1330 (goods), 3310 (payables to suppliers), 3130 (VAT payable, rate 16%), 6010 (income from realization), 7010 (cost of realization). They are not related to the termination document, provided as a reference for the chart of accounts of the configuration. Electronic documents of the configuration — ESF (IS ESF) and SNT — are not related to termination.

  • Input Based On: the document can be created from the card of the reference Employees (scenario “Creating based on the employee reference”) for quick processing of the termination of one employee.
  • Related Calculation Documents: “Salary Calculation”, “Vacation Compensation upon Termination”, payment documents — use planned records closed by the termination document.
  • Related Registers: listed in section 5 (personnel statuses and IIT deductions).
  • Source References: Organizations, Employees, articles/bases for termination (Tax Code of the RK).

Standard Usage Scenarios

  1. Termination of one employee — single processing.
  2. Mass termination — group of employees (staff reduction, reorganization, project completion) in one table part.
  3. Input from employee card — quick processing based on.
  4. Printing the termination order — after processing.
  5. Manual adjustment after processing — editing attributes without reprocessing movements (for example, typo in the basis).
  6. Bulk editing — mass change of attributes (for example, responsible person) from the list form.

7. Expansion Points

  • Subscriptions to events / extensions of ProcessingConducting — adding custom movements (for example, to additional personnel registers) without removing the configuration from support.
  • Form Extensions (DocumentForm, ListForm) — additional attributes, buttons, additional checks during processing.
  • PrepareProcessingParameters (ManagerModule) — point for overriding the set of closed planned records/deductions.
  • SalaryCalculationServer — common module, the logic of closing planned accruals/deductions is advisable to expand here, rather than in the document module.
  • Additional printed forms of the order — through the mechanism of external/additional printed forms of BCP.
  • Additional attributes and information — through the subsystem of properties (without changing metadata).

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

Does the document "Termination from the Organization" generate accounting entries?
No. The document only creates records in information registers (employment status in Employees of Organizations, closing of planned accruals/deductions and individual income tax deductions). Accounting entries for the final settlement upon termination are generated by settlement documents — "Salary Accrual", "Vacation Compensation", payment documents.
Why can't an employee be added to the document twice?
The configuration includes a uniqueness check: only one line is allowed per employee. If a duplicate is found, a message is displayed: "Only one line can be entered for one employee in this document!" (the condition FindRows by the structure "Employee" = 0). A separate document is issued for repeated termination.
What does the flag "TerminateStandardDeductions" do?
When set to True, the document stops the application of standard tax deductions for individual income tax from the date of termination (movements in the registers IndividualIncomeTaxDeductions and ApplicationOfDeductions). This is important so that in subsequent calculations, the basic deduction — for 2026, 30 MRP per month (129,750 ₸ at MRP 4,325 ₸), not more than 360 MRP per year — is no longer applied to the terminated employee.
What tax norms of the RK 2026 are considered in the related calculation?
The basic deduction for individual income tax — 30 MRP/month (not more than 360 MRP/year); individual income tax 10% up to 8,500 MRP of annual income and 15% above; OPE 10% (base ceiling 50 MZP, MZP = 85,000 ₸), OPER 3.5%, VOSMS 2%, OSMS 3%, CO 5%, social tax 6%. The termination document does not calculate these amounts, but correctly closes planned records and deductions for subsequent calculations.

Read also

Источники

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