Report "General Ledger (Standard)" — Accounting for Kazakhstan 3.0

1. Identification

Purpose. An analytical accounting report that generates consolidated information on accounting accounts with detailed movements, corresponding accounts, and balances (beginning/end) for the selected period. Used by accountants and chief accountants for monitoring account movements, analyzing correspondences, and preparing regulated reporting of the RK. Data source — accounting register; the report does not generate its own movements. Generated on demand, usually at the end of the period (month, quarter, year) for reconciling entries and verifying balances. Currency representation — tenge (₸).

2. Attributes and Table Parts

The report is built on a data composition scheme (DCS), and the attributes listed below are parameters/settings for generation, stored in the attributes of the report object and variant settings.

2.1 Header Attributes (Generation Settings)

Note for the RK: detailing of subaccounts is relevant for the standard chart of accounts of the RK — for example, account 1210 (short-term receivables from buyers and customers) when BySubaccounts = True expands to analytical subaccounts, and correspondences with 1030, 1330, 3310, 6010, 7010 — when ByGroupsOfCorrespondingAccounts = True.

2.2 Table Parts

DocumentList

Table part for storing a list of documents used as a potential filter/data source. In the current version of the configuration, it is actively not used in the business logic of the report module (reserved). Contains columns-references to documents; has no practical impact on the generated report.

3. Forms

If the object does not have its own form specified — the platform uses the auto-generated report form of DCS. The quick settings panel is formed from the attributes of section 2.1.

4. Key Module Procedures

No specific BSL fragments with paths/strings in evidence are attached (except for the mention of filling check processing), so below are typical report handlers on DCS in BK 3.0:

• FillingCheckProcessing(Refusal, CheckedAttributes) — controls the filling of mandatory settings. The attribute OrganizationListRepresentation is generated automatically and removed from CheckedAttributes to avoid blocking generation with an empty string representation.
• OnResultComposition(DocumentResult, DataDecoding, StandardProcessing) (object module) — interception point of composition: preparation of parameters (StartPeriod, EndPeriod, Frequency, detail flags), fine-tuning the composition layout, post-processing of the final tabular document (including the logic of SplitBySheets).
• OnCreationOnServer / OnOpening (form module) — initialization of the default period, filling the organization list and OrganizationListRepresentation, restoring user settings.
• Generate(Command) (form module) — launching the composition of the result in the area of the tabular document.
• DCS Settings Handlers — applying selections by organization/accounts and groupings according to the flags BySubaccounts, ByAccountGroups, BySubaccountsOfCorrespondingAccounts, ByGroupsOfCorrespondingAccounts.

5. Data Source and Movements

The report does not perform postings and does not generate movements — it is a read-only object. Data is read from the accounting register (turnovers, beginning and ending balances, correspondences) through a query/composition scheme.

The logic of formation follows the standard scheme of the "Main Book":

• for the period for each account, beginning balance, debit and credit turnovers broken down by corresponding accounts, ending balance are displayed;
• period breakdown is managed by the attribute Frequency (month/quarter/year);
• detailing down to subaccounts and grouping by sections of the chart of accounts — flags from section 2.1.

The standard chart of accounts of the RK, involved in correspondences (examples):

An example of a correspondence for the sale of goods read by the report: Dr 1210 Cr 6010 (income), Dr 1210 Cr 3130 (VAT 16 %), Dr 7010 Cr 1330 (write-off of cost). These entries are generated by sales documents; the "Main Book" only aggregates them from the accounting register.

6. Related Objects and Input Based On

Input based on for the report is not applied. The connections are of a source and navigation nature:

• Accounting Register — the main data source.
• Chart of Accounts (standard RK) — defines accounts, subaccounts, and groups (sections) by which rows and columns are built.
• Directory "Organizations" — selection and header (OrganizationListRepresentation).
• Document Registrars (sales, receipts, bank, cash, etc.) — primary objects whose movements are aggregated; from the report cells, decoding to the document and its entries is available.
• Adjacent Accounting Reports: "Turnover Balance Statement", "Account Analysis", "Account Card", "Chess Statement" — used for cross-checking.

Electronic documents of the RK (ESF in the ESF IS, SNT) are not directly related to the report but are generated based on the same sales/receipts documents whose entries fall into the "Main Book".

7. Extension Points

• Report Variants (DCS) — creating user variants with different groupings, selections, and formatting without changing the configuration.
• Configuration Extension — overriding/adding OnResultComposition and form handlers, adding custom settings attributes and columns.
• Additional Selections — by organization, account, department through composition settings.
• User Fields and Conditional Formatting DCS — for highlighting rows/sums.
• Saving and Distribution — saving user settings, output to tabular/office document, inclusion in report distributions.

Requires verification (version-specific): the exact composition of the quick settings panel and the presence of a separate variant form may differ between releases of the 3.0.74.x line — check against the specific build of the configuration.