1. Identification
| Parameter | Value |
|---|---|
| Object Type | Catalog |
| Name | Subaccount |
| Full Name | Catalog.Subaccount (Catalogs.Subaccount) |
| Synonym | — (matches the name) |
| Configuration | Accounting for Kazakhstan, ed. 3.0 (3.0.74.2) |
| Hierarchy | Hierarchical (groups and elements) |
| Subordination | Can be used as a subordinate — the standard attribute "Owner" is present |
| Navigation Link | e1cib/list/Catalog.Subaccount |
Purpose. The catalog stores and systematizes analytical attributes (types of analytics) used in the chart of accounts for accounting. A subaccount is an additional dimension of analytical accounting (counterparties, contracts, nomenclature, divisions, etc.) linked to specific accounts for detailing accounting data. The catalog is used by accountants and administrators when setting up the chart of accounts and defining types of analytics. Work with it is mainly carried out at the initial setup stage of the system and rarely changes during operation.
Where to find in 1C: section "Analytical Information" → "Subaccount" (or directly via the navigation link e1cib/list/Catalog.Subaccount).
2. Attributes and Table Parts
2.1 Header Attributes
According to the metadata map, the catalog does not have additional user attributes beyond the standard attributes of the catalog.
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| Code | String | Yes | Unique code of the subaccount element |
| Name | String | Yes | Name of the type of analytics (subaccount) |
| Parent | CatalogReference.Subaccount | No | Reference to the parent group for hierarchical organization |
| Owner | (not explicitly defined) | No | Owner of the element, if the catalog is used as a subordinate |
2.2 Table Parts
Table parts are absent — the catalog is a simple hierarchical classifier of types of analytics.
3. Forms
The catalog contains 5 forms:
| Form | Purpose |
|---|---|
| ElementForm | Main form for creating and editing a subaccount element (key for the user) |
| GroupForm | Creating and editing a group of elements (node of the hierarchy) |
| GroupSelectionForm | Selecting a group from the hierarchy (for example, when moving an element) |
| ListForm | Main list form with support for bulk changes (key for viewing) |
| SelectionForm | Selecting a subaccount element when filling other objects |
4. Key Module Procedures
Specific application BSL code in evidence is not attached. For a catalog of this type (simple hierarchical classifier without user attributes and table parts), standard handlers are characteristic, which are listed below with the expected placement.
Object Module (ObjectModule):
FillProcessing(FillData, FillText, StandardProcessing)— filling attributes when entering based on / from fill data.BeforeSaving(Refusal)— control of correctness before saving (for example, prohibition of cyclic hierarchy, uniqueness check of the name within the owner/group).OnCopying(CopyingObject)— reset/correction of attributes when copying an element.
Element Form Module (ElementForm):
OnServerCreation(Refusal, StandardProcessing)— initial setup of field availability and visibility.OnOpening(Refusal)— final adjustment of the interface upon opening.
List Form Module (ListForm):
OnServerCreation(Refusal, StandardProcessing)— setup of conditional formatting, filters, availability of bulk changes.
Requires verification (version-specific): exact names and presence of application procedures in the specific build 3.0.74.2 — determined by the object 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. Its role in the accounting model is to serve as a source of analytical values (subaccount) for accounts in the chart of accounts and, consequently, for dimensions of the accounting register.
The mechanics of participation in accounting:
- Types/values of subaccounts from this catalog are substituted into subaccount dimensions of the accounting register ("Cost Accounting" and related) when posting documents that operate with the corresponding accounts.
- Analytics reveals turnovers and balances on accounts of the typical chart of accounts of the RK. Examples of accounts to which subaccounts are linked:
| Account | Name |
|---|---|
| 1210 | Short-term accounts receivable from customers |
| 1030 | Cash in current bank accounts |
| 1330 | Goods |
| 3310 | Short-term accounts payable to suppliers |
| 3130 | VAT payable (to the budget) |
| 6010 | Income from sales of goods and services |
| 7010 | Cost of goods sold and services rendered |
Example of postings for the sale of goods (numbers — RK 2026, VAT rate 16%, currency — tenge ₸), where subaccounts detail the counterparty/contract/nomenclature:
- Dr 1210 Cr 6010 — income from sales is reflected; subaccounts for Dr: "Counterparties", "Contracts"; for Cr — "Nomenclature Groups".
- Dr 1210 Cr 3130 — VAT 16% is accrued on the sale amount.
- Dr 7010 Cr 1330 — cost of goods is written off; subaccounts "Nomenclature", "Warehouses".
Summary for the sales document of 100,000 ₸ excluding VAT: Dr 1210 116,000 ₸; Cr 6010 100,000 ₸; Cr 3130 16,000 ₸ (VAT 16%).
The "Subaccount" catalog only provides analytical values — sums and correspondences are formed by documents, not by the catalog itself.
6. Related Objects and Input Based on
- Chart of Accounts (Cost Accounting) — subaccounts from the catalog are assigned to accounts as types of analytics; this is the main consumer of the catalog.
- Accounting Register — uses subaccount values as values for dimensions "SubaccountDr"/"SubaccountCr".
- Accounting Documents (sales, receipts, banking and cash operations, adjustments) — when posted, they fill the subaccounts of accounts with values from this and related catalogs.
- Electronic Documents of the RK — ESF (IS ESF) and SCT are generated based on primary documents; analytical subaccount (counterparty, contract, nomenclature) is used when filling them, but is not directly created by the catalog itself.
Input Based On: for the classifier of types of analytics, the "input based on" mechanism is typically not applied — elements are created manually or through FillProcessing during programmatic filling.
7. Extension Points
- Configuration Extension: adding custom attributes (for example, classification code, grouping attribute) and subscriptions to events
BeforeSaving/FillProcessingwithout removing the configuration from support. - Additional Attributes and Information: connection through the "Properties" mechanism (with the corresponding functional option enabled), which allows expanding analytical characteristics without changing metadata.
- Forms: overriding/extending
ElementFormandListFormto add custom controls and conditional formatting. - Regulatory Control: placing uniqueness and correctness checks of the hierarchy in the
BeforeSavingobject module (in the extension). - Data Exchange: including the catalog in exchange/export rules during integrations where synchronization of types of analytics is required.
Requires verification (version-specific): the composition of included functional options and the availability of the additional properties mechanism for this catalog in build 3.0.74.2.