1. Identification
| Parameter | Value |
|---|---|
| Object Type | Document (Documents) |
| Name | EnforcementOrder |
| Full Path | Document.EnforcementOrder |
| Synonym | “Enforcement Order” |
| Configuration | Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) |
| Where to find in 1C | Section “Payroll Calculation” → “Enforcement Order” |
| Navigation Link | e1cib/list/Document.EnforcementOrder |
Purpose. The document is intended for registering judicial and administrative enforcement documents (enforcement orders, court orders, resolutions of private bailiffs, etc.), based on which the employer is obliged to withhold part of the employee's salary and transfer it to the claimant (alimony, repayment of debts on loans, compensation for damages, etc.). The document is maintained by the HR department and the accounting department for payroll settlements. After processing, a planned withholding is formed, which is automatically applied during each payroll calculation for the employee during the specified period of validity.
All monetary norms are provided for the RK for the year 2026: MRP = 4,325 ₸, MSP = 85,000 ₸. These amounts are used as a basis for limiting the maximum amount of withholding and for calculating alimony in multiples of MRP/MSP.
2. Attributes of Header and Table Parts
2.1 Mandatory Header Attributes
From the evidence of the configuration — fields without which the document cannot be processed (1C gives an error “Field … is not filled”):
| Attribute | Type (standard) | Purpose |
|---|---|---|
EffectiveDate |
Date | The date from which the enforcement order comes into effect and begins to be applied in payroll calculations. Determines the start of the validity period of the planned withholding. |
Organization |
ReferenceLink.Organizations | The legal entity (employer) that is obliged to make the withholding. Measurement of the planned withholdings register. |
Individual |
ReferenceLink.Individuals | The employee from whose income the withholding is made (debtor). Key measurement of the register. |
Recipient |
ReferenceLink.Counterparties / Individuals | The claimant — the person or organization to whom the withheld amount is transferred (for example, the recipient of alimony, bank, government agency). |
TransferMethod |
ReferenceLink / Enumeration | The procedure for transferring withheld amounts to the recipient (to a bank account, by postal transfer, in cash through the cash desk, etc.). |
2.2 Other Standard Header Attributes
In addition to the mandatory ones, for documents of this type in the configuration, there are attributes that set the rule for calculating the withholding and the period of its validity:
| Attribute | Purpose |
|---|---|
EndDate / ValidityPeriod |
The date of completion of the withholding (if known). An empty value means the withholding is indefinite, until fully paid or termination of employment. |
CalculationMethod / TypeOfCalculation |
The method of determining the amount: fixed amount, percentage of earnings (shares), multiple of MRP/MSP. |
Amount |
Numerical value of the withholding: amount in ₸, percentage (share), or number of MRP — depending on the calculation method. |
Number, IssueDate of the enforcement document |
Attributes of the external judicial document basis. |
Comment |
Arbitrary text note. |
Limitation on the amount of withholding. According to labor and enforcement legislation of the RK, the total amount of withholdings generally does not exceed 50% of the salary after taxation (for certain categories — up to several withholdings, but with the established minimum retained for the employee). Control of the maximum share is performed at the payroll calculation stage, not at the processing of this document.
2.3 Table Parts
Documents of this type, as a rule, do not have table parts — all information about one enforcement proceeding is placed in the header. One enforcement order = one document = one record of planned withholding for the pair “Organization + Individual”.
3. Forms
| Form | Purpose |
|---|---|
| Document Form (DocumentForm) | Main form for input/editing: filling in the attributes of the enforcement order, selecting the individual, recipient, transfer method, and amount of withholding. |
| List Form (ListForm) | Viewing all registered enforcement orders, filtering by organization and individual, navigation (e1cib/list/Document.EnforcementOrder). |
| Selection Form (SelectionForm) | Selecting an enforcement order from other objects (for example, when entering related documents or in reports on withholdings). |
4. Key Module Procedures
According to the evidence, the specific logic of calculation is encapsulated in the common modules PayrollCalculationServer and ProcessingServer; standard handlers are involved in the object itself.
Manager Module (ManagerModule):
PrepareProcessingParameters(...)— preparation for processing: creates a temporary tables manager and forms a request to load the document attributes (≈81 lines of SQL text). The request selects all header attributes of the document and places them in a temporary table for subsequent movement formation.
Object Module (ObjectModule) — standard handlers for this type of document:
FillProcessing(DataFilling, ...)— filling in attributes when entering based on/copying (scenario “Copying the enforcement order upon extension”).CheckFillingProcessing(Refusal, CheckedAttributes)— control of filling mandatory fieldsEffectiveDate,Organization,Recipient,TransferMethod,Individual.Processing(Refusal, ProcessingMode)— calls the mechanics of forming movements in the planned withholdings register (throughProcessingServer/PayrollCalculationServer).RemoveProcessing(Refusal)— clears movements when canceling processing (suspension/completion of proceedings).
Processing Logic (in ProcessingServer / PayrollCalculationServer):
- Preparation of parameters — temporary tables, request for attributes.
- Formation of movements in the register
PlannedWithholdingsEmployeesOrganizations. - Integration with payroll calculation: when accruing, the system reads the register and, if a record is active on the calculation date, forms the withholding according to the amount and calculation method.
5. Processing and Movements
5.1 Information Register
The document forms movements in the information register PlannedWithholdingsEmployeesOrganizations:
| Role | Fields (standard) |
|---|---|
| Dimensions | Organization, Individual, validity period (StartDate/EndDate) |
| Resources | Amount of withholding, TransferMethod, Recipient, parameters of the calculation method |
The record is valid for the specified period and is read during the payroll calculation of the employee.
5.2 Accounting Entries
The document “Enforcement Order” does not generate accounting entries — it only registers the planned withholding (information register). Actual entries arise later, during the payroll accrual/payment document, when the withholding is calculated and recognized. According to the standard chart of accounts of the RK, the movement of the withheld amount looks like this:
| Operation | Debit | Credit | Comment |
|---|---|---|---|
| Withholding from employee's salary | 3350 “Short-term debt for labor payment” | 3390 “Other short-term creditor debt” (obligation to the claimant) | Reduction of the amount payable to the employee by the amount of withholding |
| Transfer of withholding to the claimant | 3390 | 1030 “Cash on current bank accounts” | According to TransferMethod (cashless / cash 1010) |
The withholding under the enforcement order is made from income after taxes and mandatory contributions. The procedure for calculating the base: accrued income → OPP 10% (base ceiling 50 MSP = 4,250,000 ₸/month), VOSMS 2% → tax deduction for PIT (basic 30 MRP = 129,750 ₸/month, but not more than 360 MRP per year) → PIT 10% (15% on annual income over 8,500 MRP). The withholding under the enforcement order is calculated from the amount remaining after the specified withholdings.
6. Related Objects and Input Based On
- Information Register
PlannedWithholdingsEmployeesOrganizations— receiver of movements of the document. - Common modules
PayrollCalculationServer,ProcessingServer— consumers of the register data during payroll accrual. - Payroll accrual documents — read the planned withholding and form the actual amount of withholding and entries.
- Payment statements / payment documents — transfer of the withheld amount to the claimant (
TransferMethod, account 1030/1010). - Directories
Organizations,Individuals,Counterparties— sources of attribute values.
Input Based On / Copying. According to the configuration scenarios, the following are provided:
- copying the enforcement order upon extension of obligations (the same employee, similar attributes);
- bulk change of organization for a batch of orders during reorganization;
- registration of suspension/change of amount/completion of proceedings as separate actions (reprocessing or cancellation of processing).
7. Extension Points
Processing(ProcessingServer / PayrollCalculationServer) — adding custom checks for the maximum share of withholding (control of 50% of net income), prioritization of multiple orders for one employee.FillProcessing/ copying — auto-filling attributes when extending and inputting based on.CheckFillingProcessing— additional business rules (for example, mandatory number and date of the external enforcement document).- Extension of the register
PlannedWithholdingsEmployeesOrganizationsthrough subscriptions to record events for integration with external withholding registers. - External processing/extensions of the configuration for bulk change of organization for a batch of orders.
Requires verification (version-specific): the exact composition of optional header attributes (
EndDate,CalculationMethod,Amount) and the presence of subscriptions to events may differ between releases of branch 3.0.74.x — clarify with the configurator of the specific installation.