Report "Cash Balances" (Accounting for Kazakhstan 3.0.74.2)

Important about the object type. In the task, the object is passed as Documents.CashBalances (type "Document"), and the navigation link is indicated as e1cib/list/Documents.CashBalances. However, the attached evidence clearly describes a report: a set of attributes (Period, PlacementOfAdditionalFields, DetailingMode), tabular parts Grouping / ColumnGrouping / AdditionalFields and the wording of the purpose — this is the structure of settings for a standard report in the Data Composition System (DCS), not a document. A document does not have such attributes, it does not "form balances as of the date" and does not have column groupings. Therefore, the description below is compiled for the report. The correct type and metadata: Report.CashBalances; the correct navigation link is e1cib/app/Report.CashBalances. The value Documents.… in the original card should be corrected.

1. Identification

Purpose. The report is intended for operational analysis of the organization's cash resources as of a specific date. It is used by accountants and managers to control liquidity, plan payments, and monitor cash flow across cash registers and bank accounts (in tenge and foreign currency). It generates an analytical slice of balances from the accounting register with the ability to group by organizations, accounts, currencies, and other dimensions. It is included in the standard manager's dashboard and is used daily for management decisions.

Where to find in 1C: section "For the Manager" → "Cash Balances". Navigation link: e1cib/app/Report.CashBalances.

2. Attributes and tabular parts

2.1 Attributes (configuration parameters)

Attributes store user settings for report generation. All are optional (DontCheck).

2.2 Tabular parts

Grouping

Defines the structure of grouping report rows (hierarchy of data nesting).

ColumnGrouping

Manages the structure of report columns (horizontal data breakdown).

AdditionalFields

Stores a list of additional analytical dimensions displayed in the report.

3. Forms

A fragment of evidence with a list of forms is incomplete (…), so below is the standard composition for reports in DCS; the specific set should be verified in the configurator for version 3.0.74.2.

4. Key module procedures

BSL code (object/form module) in evidence not attached, so standard report handlers for DCS for BK 3.0 are provided:

• OnResultComposition(...) (report object module) — overrides/complements the composition: substitution of the Period parameter, formation of ListRepresentationOfOrganizations, column management through PlacementOfAdditionalFields, inclusion of detailing mode by the DetailingMode flag.
• OnDeterminingUsedSettings / OnLoadingVariantOnServer — initialization of user settings, restoration of saved groupings and additional fields.
• Breakdown handler (BreakdownHandler in the form or AdditionalBreakdownHandler) — when DetailingMode = True provides a transition from the report row to the source documents of cash movements (cash/bank documents).
• OnCreationOnServer / Generate (report form) — sets the default period (usually the current date), selection values by organization, starts composition.

The exact names and signatures of procedures for 3.0.74.2 — require verification in the configurator (evidence for BSL is missing).

5. Data source and movements

The report does not conduct and does not generate movements/entries — it is an analytical object. It reads data from the accounting register "Cost Accounting" (the main chart of accounts of the RK) for accounts in the "Cash" section and outputs balances as of the Period parameter.

Analyzed accounts of the standard chart of accounts of the RK (section "Cash", group 1000):

The main analytical breakdown is account 1030 (current accounts) and 1010 (cash), with detailing by subaccounts: "Bank accounts" / "Cash registers", "Currency", "Organization". For foreign currency accounts, balances are displayed in currency and in tenge (₸) based on the register data.

Logic for data retrieval: a query to the balance table of the accounting register AccountingRegister.CostAccounting.Balances(&Period, Account In (…cash accounts…), , Organization = &Organization) with subsequent composition according to the configured row/column groupings.

Other numerical norms of RK-2026 (VAT rate 16%, MRP 4,325 ₸, MSP 85,000 ₸, deduction of individual income tax 30 MRP/month and no more than 360 MRP/year, individual income tax 10%/15%, OPE 10% with a ceiling of 50 MSP, OPER 3.5%, VOSMS 2%, OSMS 3%, SO 5%, social tax 6%) do not apply to this report: it does not calculate taxes and contributions, but only reflects the balances of cash accounts. They are indicated for the context of the configuration.

6. Related objects and breakdown

• Accounting register "Cost Accounting" — source of balances.
• Directories of cash account analytics: BankAccounts, CashRegisters, Organizations, Currencies.
• Source documents of movements (available through breakdown when DetailingMode = True): "Receipt to current account", "Write-off from current account", "Cash receipt order", "Cash expenditure order", "Payment order", etc.
• Input based on the report is not applicable (reports do not participate in the input mechanism based on).

7. Extension points

• Report variants — creation of user/additional layout variants (saving groupings, selections, formatting) without changing the configuration.
• Configuration extensions — adding form attributes, overriding OnResultComposition, enhancing the breakdown handler.
• Data composition scheme (DCS) — expanding the set of fields/resources, adding calculated fields and new analytical breakdowns.
• Additional fields (tabular part AdditionalFields) — standard mechanism for including new analytical dimensions without editing DCS.
• Additional reports and processing (BSP) — connecting an external variant/analogue through the subsystem of additional reports.