Document "Employee Transfer of Organizations" (Accounting for Kazakhstan 3.0)

1. Identification of the Object

Purpose. The document formalizes the transfer of one or more employees between separate and structural divisions within one organization. In addition to the fact of the transfer, the document records changes in the planned accruals of employees and supports the indexing of earnings. It is used by HR specialists and payroll accountants during the reorganization of the company's structure and personnel rotation.

⚠️ This is a personnel-accounting document. It does not generate accounting entries for accounts (1210, 6010, 3130, etc. are not involved — these are accounts for trade and financial operations) and is not related to VAT, electronic invoices (ESF), individual income tax, or calculations in tenge for sales. All its movements are records in periodic registers of personnel and payroll accounting.

2. Header Attributes and Table Parts

2.1 Header Attributes

Date and number are standard attributes of the document. The document date is used as the period of movements for planned accruals and indexation coefficients.

2.2 Table Part “EmployeesOfOrganization”

List of transferred employees and their new organizational affiliation.

2.3 Table Part “MainAccruals”

Change of planned accruals during the transfer (regional coefficient, allowances, bonuses, etc.).

If any of the mandatory fields are not filled, the platform will not process the document and will issue an error of the type “Field ... is not filled”.

3. Forms

4. Key Module Procedures

No separate BSL code with the binding path:string in evidence is attached, so below is a typical set of handlers for documents of this type in BK 3.0:

• ProcessPosting(Refusal, PostingMode) — main handler. Forms sets of records for information registers (see section 5), performs filling checks, and calls access preparation.
• FillAccessValueSets — before recording movements, PayrollServer.FillAccessValueSets is called: the RLS system restricts visibility of records at the level of subdivisions and organizations.
• FillData(CompletionData, ...) — filling in attributes when entering based on / from the employee directory.
• CheckFilling — control of mandatory header attributes and columns of table parts.
• Form handlers: OnCreateOnServer, ProcessSelection, handlers for events of table part fields (substitution of position/subdivision, recalculation of amount during indexing).

5. Posting and Movements

When posting, the document operates in “Replacement” mode (sets of records are pre-cleared by the registrar selection) and generates movements in three information registers. The document does not create accounting entries according to the chart of accounts.

5.1 Information Register EmployeesOfOrganizations (periodic, subordinate to the registrar)

Logic: for each employee, a record is created that fixes their new affiliation to the subdivision from the specified date.

5.2 Information Register PlannedAccrualsOfEmployeesOfOrganizations (periodic)

Logic for the column Action:

• Add — a new record of planned accrual is created.
• Change — the amount of the existing record is updated.
• Delete — the period of action of the accrual ends on the document date.

5.3 Information Register IndexationCoefficientsOfEarnings (only when IndexationOfEarnings = True)

Logic: for each employee, the indexation coefficient applied in subsequent payroll calculations is recorded.

The amounts of planned accruals are stored and calculated in tenge (₸) — the currency for payroll calculations in the RK.

6. Related Objects and Input Based On

• Directory Employees / Individuals — source of rows for the table part; typical scenario — creating a transfer document directly from the employee directory.
• Directories OrganizationSubdivisions and separate subdivisions — values for the “To”/“From” fields and the subdivision column.
• Planned types of calculation (types of accruals) — fills the CalculationType column in the table part “MainAccruals”.
• Receiving registers (EmployeesOfOrganizations, PlannedAccrualsOfEmployeesOfOrganizations, IndexationCoefficientsOfEarnings) — used by subsequent payroll calculation documents.
• Documents of hiring/termination/personnel accounting form a common contour of the employee's personnel history.

7. Typical Usage Scenarios

1. Creating a transfer from the employee directory — transferring one/multiple employees to another subdivision on a permanent basis.
2. Mass transfer with indexing of earnings — reorganization with simultaneous salary increases (for example, transferring a department to a new branch with a regional allowance): the flag IndexationOfEarnings and coefficient are set.
3. Correction of a posted transfer — correcting the date, composition of employees, or accruals with reposting (the “Replacement” mode correctly recreates movements).
4. Printing the order of transfer — formalizing the official order after posting.
5. Adding accruals during the transfer — assigning new types of accruals (regional coefficient, bonus) through the table part “MainAccruals” with the action “Add”.

8. Extension Points

• Subscriptions to events / extensions of handlers ProcessPosting and FillData — for adding custom movements or checks.
• Additional attributes and information — through the properties mechanism for storing non-standard attributes of the transfer.
• Extension of printed forms — adding custom versions of the order.
• Payroll calculation — customization of the application of the indexation coefficient in the module PayrollServer during subsequent accruals.

⚠️ Requires verification in a specific version: the exact composition of the resources of the registers and the presence of the column CalculateMandatoryPensionContributions may differ between releases of the 3.0.7x branch — check with the configurator of the target database.

Where to Find

Navigation link 1C:

e1cib/list/Document.PersonnelTransferOrganizations