1. Identification
| Parameter | Value |
|---|---|
| Object Type | Catalog |
| Name | FundsOfOrganizations |
| Full Name | Catalog.FundsOfOrganizations / Catalogs.FundsOfOrganizations |
| Synonym | not specified (—) |
| Configuration | Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) |
| Hierarchy | Supported (hierarchy of groups and elements) |
| Owners | None (non-subordinate catalog) |
Purpose. The catalog is intended for the classification and accounting of various funds of payments formed by the organization for the purposes of payroll calculation and other employee payments. It is used in the payroll calculation subsystem for grouping and analytics of payments by funds (wage fund, social payments, compensation funds, etc.). It is applied by accountants and HR specialists when configuring the payroll calculation system and generating reports on funds. Working with the catalog is periodic — at the initial setup stage and when changing the structure of the organization's funds.
Where to find in 1C: section “Regulated Reporting” → “Funds of Organizations”.
Navigation link: e1cib/list/Catalog.FundsOfOrganizations
2. Attributes and Table Parts
2.1 Header Attributes
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| WageFund | Boolean (xs:boolean) |
Optional (DontCheck) |
Flag indicating the fund's affiliation to the wage fund (WF). Used for filtering and grouping funds when generating reports on WF, to highlight main payments from other social and compensation funds. |
Standard (system) attributes of the catalog:
| Name | Purpose |
|---|---|
| Name | Name of the payment fund (main representation of the element). |
| Code | Unique code of the catalog element. |
| Parent | Reference to the parent group (hierarchy of groups and elements). |
| DeletionMark | Standard mark for deletion. |
| Predefined | Indicator of a predefined element (standard). |
2.2 Table Parts
Table parts are absent. The catalog has a simple structure — attributes are stored only in the header of the element.
3. Forms
The catalog contains three standard forms:
| Form | Purpose |
|---|---|
| ElementForm | Main form for creating and editing an individual element. Contains fields: Parent, Name, Code, and the WageFund flag (as a CheckBoxField). Key form for user interaction with a specific payment fund. |
| SelectionForm | Form for selecting an element from the catalog when filling in attributes in other system objects. Contains a list with search and filtering. |
| ListForm | Form listing all payment funds. Contains the command EditSelected (FormEditSelected and ListContextMenuEditSelected) for bulk editing of several elements. Used for viewing, navigation, and mass editing. |
4. Key Procedures of Modules
In the attached evidence, the software modules (object module, form modules) do not contain non-standard procedures — no specific code has been identified. Below are the typical handlers characteristic of a catalog of this type; they are present in the object only if the corresponding business logic exists.
Object Module (ObjectModule):
FillProcessing(FillingData, ...)— filling in attributes when creating a new element (including when entering based on).BeforeSaving(Refusal)— control of data correctness before saving (for example, prohibiting the setting of the WageFund flag for a group).OnCopying(CopyingObject)— adjustment of attributes when copying an element.
Element Form Module (ElementForm):
OnServerCreation(Refusal, StandardProcessing)— initial setup of field availability/visibility in the form, including the WageFund flag field.WageFundOnChange(Element)— typical handler for reacting to the change of the flag (if dependent logic exists).
List Form Module (ListForm):
- Handlers for the command
EditSelected— calling typical processing for bulk changes of attributes of selected elements.
Requires verification on a specific build: the presence and exact content of handlers
BeforeSaving/FillProcessingis version-dependent; in the base delivery, the object module may be empty.
5. Posting and Movements
The catalog is not a document and is not posted — it does not generate its own postings and movements in registers. It is an element of normative and reference information (analytics).
The value of the catalog is used as analytical dimension (subaccount) in the payroll calculation subsystem: the payment fund element participates in the grouping of accruals and in the formation of reports on funds (in particular, on WF when the WageFund flag is set).
Postings are generated by payroll calculation and payroll reflection documents that reference this catalog. According to the typical chart of accounts of the RK (Accounting for Kazakhstan), such documents involve, in particular:
| Account | Name |
|---|---|
| 3350 | Short-term liabilities for labor payment |
| 7210 / 8110 / 7010 | Expenses (including 7010 — cost of sales) related to labor payment |
| 3120–3160 | Liabilities for taxes and deductions from payroll |
Rates and bases for calculations with payroll for 2026 (Kazakhstan), applied in related documents:
- OPV — 10% (base ceiling 50 MZP);
- OPVR — 3.5%;
- VOSMS — 2%;
- OSMS — 3%;
- SO — 5%;
- Social tax — 6%;
- IPN — 10% up to 8,500 MRP annual income and 15% above; basic tax deduction — 30 MRP per month (not more than 360 MRP per year);
- MRP = 4,325 ₸, MZP = 85,000 ₸;
- Currency of calculations — tenge (₸).
The catalog itself does not generate records in these movements, but serves as a measure of analytics.
6. Related Objects and Input Based on
- Payroll calculation and reflection documents — use catalog elements as analytics of payment funds.
- Reports on WF and payment funds — group and filter data by the WageFund attribute.
- Other catalogs and settings of the “Payroll and HR” subsystem — reference payment funds when configuring types of accruals.
Input based on: for this catalog, typical mechanisms are not provided (the catalog is a receiver of references, not a source of documents). Filling is performed manually or through bulk change (EditSelected).
7. Extension Points
- Configuration extension: adding custom attributes (for example, additional classification of the fund), connecting handlers
BeforeSaving/FillProcessingthrough the object module of the extension. - Additional attributes and information: when the properties subsystem is connected — through characteristic types plans (without changing the configuration).
- Forms: extending
ElementForm/ListFormto add fields and commands; overriding handlersOnServerCreation. - Event subscriptions: processing
BeforeSaving/OnSavingof the catalog through subscription for external business logic without modifying the standard module. - Bulk change: the mechanism
EditSelectedis available for mass adjustment of attributes, including the WageFund flag.
