Document "Salary to be Paid by Organizations" - Technical Description

1. Identification

Purpose. The document is intended for generating payroll lists for salary payments for a specific period. It is used by accountants and HR specialists to calculate amounts to be paid (taking into account payment percentage and rounding), choose the method of payment (through cash or bank), reflect the status of payments (paid, deposited, unpaid), and print regulated forms (T-2, payroll). The document is used monthly or as salary is accrued.

Important: this is an information-management document. It records the intention of payment and the amounts to be issued, but does not generate accounting entries — the actual movement of money and settlement closure are reflected in payment documents (RKO, payment order) entered based on it (see sections 5–6).

Where to find in 1C: section “Salary Calculation” → “Salary to be paid by organizations”. Navigation link: e1cib/list/Document.SalaryToBePaidOrganizations

2. Header and Table Part Attributes

2.1 Header Attributes

The attributes Organization, SalaryAccrualPeriod, CalculationType, PaymentCalculationMethod, Bank are marked as mandatory — without their completion, the system will not process the document and will issue an error “Field … is not filled in”.

2.2 Table Part “Salary”

The main table part containing the list of employees and amounts to be paid.

All monetary amounts are stored in tenge (₸).

3. Forms

The specific composition of forms depends on the version; in 3.0.74.2 the document form contains commands “Fill”, “Calculate amounts” and employee selection. Requires verification in the specific delivery: presence of a separate form for selecting card accounts.

4. Key Module Procedures

According to evidence, the document does not contain the handler ProcessingConduct. Below are the typical handlers of this type of document in BK configurations 3.0:

• FillingProcessing(FillingData) (object module) — fills the table part “Salary” with employees and amounts. Reads balances of mutual settlements from registers MutualSettlementsWithEmployeesOfOrganizations and MutualSettlementsWithDepositorsOfOrganizations for the specified accrual period.
• FillingCheckProcessing(Refusal, CheckedAttributes) — control of mandatory fields (Organization, SalaryAccrualPeriod, CalculationType, PaymentCalculationMethod, Bank, Individual in rows).
• Procedure for calculating amounts to be paid (form/general module) — implements scenario 3.2: applies payment percentage to the accrued amount and rounds the result to the specified precision (for example, to 10 ₸).
• Filling card accounts (form) — for PaymentMethod = "ThroughBank" substitutes card accounts from the directory CardAccountsIndividuals (scenario 3.3).
• Employee selection (form) — manual addition of individual employees (scenario 3.6).
• Setting payment status — marking “Paid / Deposited / Unpaid” for rows (scenario 3.4).

Integration of the object (according to evidence):

• Directory CardAccountsIndividuals — binding of card accounts for bank payments.
• Information register InformationOnPaymentsToEmployeesOfOrganizationsByPayrolls — indirectly, through payment documents.
• Accumulation registers MutualSettlementsWithEmployeesOfOrganizations, MutualSettlementsWithDepositorsOfOrganizations — reading balances during filling.

5. Conducting and Movements

The document does not generate its own accounting entries — the conducting handler is absent. The document records the list of amounts to be issued, while the movements for accounting are performed by related payment documents.

The standard scheme for reflecting payment (entries are generated by RKO / payment order entered based on the payroll), according to the typical chart of accounts of the RK:

When making payments, movements also affect mutual settlement registers (MutualSettlementsWithEmployeesOfOrganizations, when depositing — MutualSettlementsWithDepositorsOfOrganizations), closing the debt to the employee.

The payroll “Salary to be paid” does not directly affect VAT and tax calculations — withholdings (individual income tax 10%, social tax 10%, social health insurance 2%, etc.) and employer contributions are calculated by salary accrual documents. Current norms for 2026 (MPR = 4,325 ₸, MZP = 85,000 ₸, basic deduction for individual income tax = 30 MPR/month) are applied at the accrual stage, not at the payment stage.

6. Related Objects and Input Based On

Source document (entered based on it):

• Cash expenditure order (RKO) — salary payment through cash (scenario 3.5).
• Outgoing payment order — transfer of salary through bank.

Objects related to the document:

• Directory Organizations — paying organization.
• Directory Individuals — recipients.
• Directory CardAccountsIndividuals — bank card accounts of employees.
• Accumulation registers MutualSettlementsWithEmployeesOfOrganizations, MutualSettlementsWithDepositorsOfOrganizations — source of data on liabilities.
• Information register InformationOnPaymentsToEmployeesOfOrganizationsByPayrolls.
• Salary accrual documents — source of amounts for SalaryAccrualPeriod.

Electronic documents (ESF in the ESF IS, SNT) with the payroll for salary payment are not related — they pertain to the realization/movement of goods.

7. Extension Points

• Configuration extension (EF): adding header attributes and columns of the table part “Salary” without removing from support; overriding form procedures (FillingProcessing, amount calculation).
• Event subscriptions: processing BeforeSaving / OnSaving of the document for additional validation or integration with external bank-client systems.
• Additional conducting handlers through extension: if necessary, to reflect management movements (the typical document does not have its own entries).
• Additional printed forms through the mechanism “Additional reports and processing” (BSP).
• Rules for calculating amounts to be paid: customization of rounding and percentage algorithm (scenario 3.2) in the general module of the extension.

Requires verification in the specific delivery 3.0.74.2: exact list of event subscriptions and presence of predefined extension points BSP for this document.