Document "Employee Salary Refunds for Organizations" - Technical Description (Accounting for Kazakhstan 3.0.74.2)

1. Identification

Purpose. The document registers the fact of an employee refunding previously paid salary in cash or non-cash form. It is used by the payroll accountant and HR specialist when processing refunds of overpaid amounts. Typical cases include:

• refund of overpayment after recalculation of accruals;
• refund of advance payment upon termination;
• refund of funds for unused days of previously granted leave.

The document is usually created based on the document “Salary Payable to Organizations” and serves to adjust the liabilities for settlements with personnel. The usage register is irregular (as needed).

2. Header Attributes and Table Parts

2.1 Header Attributes

2.2 Table Part “Salary”

Contains a line-by-line list of individuals and amounts to be refunded.

Control of filling during processing: if a mandatory field is not filled, the platform does not process the document and issues an error of the type “Field … is not filled”.

Currency. All amounts are in tenge (₸).

3. Forms

The specific composition of forms and the presence of additional managed forms are version-dependent; checked in the configurator for assembly 3.0.74.2.

4. Key Module Procedures

The provided evidence does not include the source code of modules (BSL) with the indication path:string. Below is a typical set of handlers for documents of this type in “Accounting for Kazakhstan” 3.0; actual signatures should be verified in the configurator.

Object Module:

• FillProcessing(FillingData, StandardProcessing) — filling in attributes when inputting based on “Salary Payable to Organizations”: substitution of Organization, basis document, and transfer of individuals/amounts to the table part “Salary”.
• FillCheckProcessing(Refusal, CheckedAttributes) — control of mandatory fields (Organization; Individual in the rows of the table part).
• Processing(Refusal, ProcessingMode) — the document lacks substantive processing for posting (see section 5): the array of recorded registers is empty, movements are not formed.

Document Form Module:

• OnCreateOnServer(...) — initial setup of the form, visibility, and availability of attributes.
• Handlers for selection and filling of the table part “Salary” (selection of individuals, auto-filling amounts from the basis document).
• Handlers for changes to the basis document (scenario of reassigning the refund, p. 3.3).

“Requires verification”: exact names of procedures and presence of server calls depend on assembly 3.0.74.2 and should be verified in the configurator.

5. Posting and Movements

Key Feature: in the document metadata, the list of recorded registers (register_records) is empty — the posting processing does not directly create movements in the registers.

The document performs an accounting and registration function: it records the fact of salary refund and serves as a source of data/basis for other objects. Economic movements (settlements with personnel, cash movements) in the typical methodology are reflected by related documents — cash receipt (cash refund) or incoming payment to the current account (non-cash refund), generated based on this document.

Approximate accounting logic for salary refund according to the typical chart of accounts of the RK (entries are formed by related cash/bank documents, not by the refund document itself):

The specific corresponding account for settlements with personnel (account group 33xx) is determined by the organization’s accounting settings and the nature of the refund. Numerical norms of the RK for 2026 relevant to salary calculation (used in related payroll documents, not in this one): VAT rate 16%, MRP 4,325 ₸, MSP 85,000 ₸, basic deduction of PIT 30 MRP/month (not more than 360 MRP/year), PIT 10% up to 8,500 MRP annual income and 15% above, OPE 10% (base ceiling 50 MSP), OPR 3.5%, VOSMS 2%, OSMS 3%, SO 5%, social tax 6%.

6. Related Objects and Input Based On

Input based on (the document is created based on):

• Document.SalaryPayableToOrganizations (“Salary Payable to Organizations”) — the main basis document; it transfers the organization, individuals, and amounts.

Related Objects and Typical Usage Scenarios:

• Attribute DocumentBasis — stores a reference to the payment document and allows reassignment (p. 3.3).
• Cash/bank documents for refunding money (cash receipt / incoming payment) — create actual cash and settlement movements based on the fact recorded by this document.

User Scenarios (from evidence):

1. Creating a refund based on the payment statement (after discovering an overpayment during the processing of the statement).
2. Manual creation of a refund with selection of employees (overpayment not linked to a specific accrual).
3. Changing the basis document in an existing refund (reassignment).
4. Copying the refund document (quick creation with the same individuals and amounts).
5. Group modification of refund documents (mass editing of attributes Responsible, Comment).

7. Extension Points

• Configuration Extension (without removal from support): adding handlers Processing, FillProcessing, FillCheckProcessing through borrowing the object module; adding header attributes/columns of the table part “Salary”.
• Forms: adding custom elements and commands to the document/list form through extension, additional event handlers for the form.
• Input based on: extending the filling procedure when inputting based on other payroll documents.
• Event Subscriptions: subscriptions BeforeSaving/OnSaving/Processing for the document, if it is necessary to add custom movements to the registers (considering that the typical posting does not create movements).
• Additional reports and processing (BSP): assigning external processing for group modification and printing of refund documents.

When making modifications, consider that the document by typical logic does not create movements: if automatic reflection of cash/settlement operations is required, it is more appropriate to modify related cash/bank documents or add movements through extension with conscious control of the accounting methodology.