1. Identification
| Parameter | Value |
|---|---|
| Object Type | Catalog |
| Name | TypesOfOtherPayments |
| Full Name | Catalog.TypesOfOtherPayments / Catalogs.TypesOfOtherPayments |
| Synonym | — (no separate synonym assigned; in the interface, "Types of other payments" is used) |
| Configuration | Accounting for Kazakhstan, edition 3.0.74.2 |
| Data Nature | Regulatory and reference information (RRI) |
| Purpose | Classification and accounting of types of payments to employees that are not related to salary on the main accrual (bonuses, compensations, material assistance, other one-time and periodic payments). Used in the payroll calculation module for categorizing payments, when setting up payroll schemes, and when entering documents for the accrual of other payments. |
The catalog is of an RRI nature: elements are created and edited infrequently — during the initial system setup or changes in accounting policy. Accountants and HR specialists refer to it.
Where to find in 1C: section "Payroll" → "Types of other payments".
Navigation link: e1cib/list/Catalog.TypesOfOtherPayments
2. Attributes and Table Parts
2.1 Header Attributes
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| FullName | String (unlimited length) | Optional (DontCheck) | Extended official name of the type of payment for printed forms, reports, and documents. Complements the short Name and allows specifying the full wording (for example, "Material assistance in connection with the birth of a child" instead of the short "Mat. assistance"). |
| ReflectionMethodInRegAccounting | CatalogReference.ReflectionMethodsOfPayrollInRegAccounting |
Optional (DontCheck) | Reference to the catalog that defines the rules for reflecting the payment in regulated accounting: expense accounts, departments, expense articles. Used for automatic generation of entries when accruing this type of payment. Critical for accurate accounting records and reporting. |
Standard attributes of the 1C catalog: Code, Name (short), Parent (when hierarchy is enabled), DeletionMark, Predefined, and service attributes.
2.2 Table Parts
Table parts are absent. The catalog has a flat structure — only the header attributes of the element.
3. Forms
The catalog contains three forms:
| Form | Elements | Purpose |
|---|---|---|
| ListForm | 29 | Main list form: viewing, searching, navigation, and selection of types of other payments from the general list. |
| ElementForm | 13 (including 3 input fields: Name, FullName, ReflectionMethodInRegAccounting) |
Key form for the user — creating and editing a separate element of the catalog. |
| SelectionForm | 29 | Selection of an element when filling in the attributes of documents and other objects. Structurally identical to ListForm, optimized for the value selection mode. |
4. Key Module Procedures
No evidence of separate non-standard module handlers (BSL with paths path:string) is recorded. For a catalog of this kind, typical platform handlers are characteristic:
- Object Module —
FillProcessing: filling in default attributes during interactive creation of a new element. - Object Module —
FillCheckProcessing: control of mandatory attributes before saving. Considering thatFullNameandReflectionMethodInRegAccountingare marked as DontCheck, automatic checking does not apply to them — control is added here if necessary. - Object Module —
BeforeSaving/OnSaving: service logic of saving (for example, updating related data). - Forms
ElementForm/ListForm—OnCreatingOnServer: setting visibility, availability, and conditional formatting of form elements.
Requires verification: the presence of overridden handlers specifically in 3.0.74.2 — clarified by the object module and form modules in the configurator.
5. Posting and Movements
The catalog is not a document and is not posted — it does not independently generate movements in registers and accounting entries.
The attribute ReflectionMethodInRegAccounting determines how the payment of this type will be reflected in the entries generated by accrual/payment documents (documents of the "Payroll" module) that reference the catalog element. Entries are built according to the typical Chart of Accounts of the RK based on the selected reflection method.
The typical scheme for reflecting other payments to employees (accounts — according to the chart of accounts of the RK):
| Operation | Debit | Credit |
|---|---|---|
| Accrual of payment (allocation to expenses according to the reflection method) | expense account from ReflectionMethodInRegAccounting (e.g., group 7xxx) |
3350 "Short-term liabilities for labor payment" |
| Withholding of PIT | 3350 |
3120 "Individual income tax" |
| Withholding of OPP (10%, base cap 50 MRP) | 3350 |
3220 |
| Payment to employee from current account | 3350 |
1030 "Cash on current bank accounts" |
Indicators of the RK 2026, applied in the calculation of taxes and contributions from payments:
- VAT — 16% (other payments to employees are not subject to VAT; the rate is provided as a current configuration parameter).
- MRP = 4,325 ₸, MZP = 85,000 ₸.
- Basic tax deduction for PIT = 30 MRP per month (not more than 360 MRP per year).
- PIT — 10% up to 8,500 MRP annual income, 15% above.
- OPP — 10% (base cap 50 MZP), OPPR — 3.5%, VOSMS — 2%, OSMS — 3%, CO — 5%, social tax — 6%.
The taxability of a specific type of payment for PIT, OPP, contributions, and social tax is determined by the settings of the corresponding type of accrual (not by the catalog itself) — verified according to the accounting policy.
6. Related Objects and Input Based On
CatalogReference.ReflectionMethodsOfPayrollInRegAccounting— used as the attributeReflectionMethodInRegAccounting; source of accounts and analytics for entries.- Documents for the accrual of other payments (Payroll module) — use the catalog element as the value of the "Type of payment" attribute, determining the calculation and reflection order.
- Payroll scheme / accrual type settings — refer to catalog elements when categorizing payments.
Input based on for the RRI catalog is not provided: it serves as a source of values for other objects, not as a basis for creating documents.
7. Extension Points
- Attribute
ReflectionMethodInRegAccounting— the main mechanism for configuring reflection without code modification: through it, accounts and analytics of entries are changed. FillCheckProcessing(object module) — a place to add custom control for the mandatoryFullNameorReflectionMethodInRegAccounting.- Form module
ElementForm(OnCreatingOnServer, field handlers) — for setting visibility/accessibility and hints according to the organization's accounting policy. - Configuration extension — adding custom attributes (for example, taxability indicator, code according to the payment classifier) without removing from support.
- Event subscriptions (
OnSaving,BeforeSaving) — for integration with external accounting mechanisms and synchronization of RRI.