Report "Account Statement (Standard)" - Technical Description

1. Identification

Purpose. The report is designed for detailed viewing of all movements (entries) for the selected accounting account over a specified period. It is a basic daily analytical tool for accountants: checking the accuracy of accounting, analyzing balances and turnovers, and searching for errors in entries. The report shows the opening balance, debit and credit turnovers broken down by corresponding accounts, and the closing balance — with the option to display currency amounts and quantitative accounting. It supports customizable frequency (day, month, quarter), filtering by organizations and departments, and detailed breakdown mode.

An example of a typical scenario: the account card 1210 "Short-term receivables from customers" in the breakdown of sub-accounts "Counterparties"/"Contracts" shows the revenue accrual on the credit 6010 and the cash receipt on the debit 1030; the card 3130 "VAT payable" reflects VAT amounts at the rate of 16% from sales and receipt documents.

2. Attributes (parameters) and table parts

The report is implemented on the data composition system (DCS). The "Header attributes" here are the parameters and settings of the DCS set by the user in the form.

2.1 Report Parameters

2.2 Table Parts

The report does not contain its own table parts in the metadata. The result is formed in a tabular document using DCS based on the data from the accounting register.

3. Forms

There are no separate settings forms, variants, or others in the object — management of variants and filters is performed using standard DCS tools within ReportForm.

4. Key Procedures of Modules

No explicit BSL code is attached in evidence, so below are the typical report handlers on DCS for this configuration (object module and form module):

• OnResultComposition(ReportResult, DecodingData, StandardProcessing) (object module) — interception point of composition: substitution of period/account parameters, setting formatting, programmatic generation of the result when StandardProcessing = False.
• OnCreationOnServer(Error, StandardProcessing) (form module) — form initialization, setting default values (current period, BU indicator), restoring user settings.
• SetInitialSettings() / FillQuickSettings() — filling quick settings fields (account, period, organization) in the header of the form.
• OnIndicatorChange() / PeriodStart-EndPeriodOnChange() — synchronization of quick settings of the form with user settings of the composer and re-composition.
• Generate() — command to build the report: applying filters, calling the layout composer, and outputting to the result area.
• ResultDecodingProcessing(...) — decoding processing: transition to entry/source document, opening sub-account card or nested report.

Requires verification: the exact composition of general building modules (for example, calls to the "Accounting Reports" subsystem) depends on the specific build of BSP/configuration.

5. Data, Registers, and Formation Logic

The report is not a posted document and does not create movements — it only reads data. Data source:

• Accounting Register "Standard" (AccountingRegister.Economic/Standard) — the main source of turnovers and balances.
• Virtual tables: BalancesAndTurnovers, Turnovers, MovementsWithSubAccounts — for opening balance, turnovers by correspondence, and line-by-line output of entries.

The output logic follows the standard algorithm of the account card:

1. Opening balance at StartPeriod for the selected account (considering sub-accounts, organization, department).
2. Line-by-line output of entries for the period: date, source document, content, corresponding account, debit, credit, as well as currency amount and quantity if the corresponding indicators are included.
3. Turnovers for the period and closing balance at EndPeriod.

Typical accounts from the chart of accounts of the RK, with which the card is most often built:

An example of correspondences visible in the card (Kazakhstan, 2026):

• Sale of goods: Dr 1210 Cr 6010 (revenue), Dr 1210 Cr 3130 (VAT 16%), Dr 7010 Cr 1330 (write-off of cost).
• Receipt of payment: Dr 1030 Cr 1210.
• Receipt from supplier: Dr 1330 Cr 3310, Dr 1420 Cr 3310 (VAT to be credited 16%).

Electronic source documents (ESF from the ESF IS, SN) are reflected as registering documents of the corresponding entries and are accessible through decoding.

6. Related Objects and Input on the Basis

• Chart of Accounts "Standard" — source of the parameter value "Account" and structure of sub-accounts.
• Accounting Register "Standard" — data source.
• Registering documents (Sale, Receipt, Payment order, ESF, SN, etc.) — opened from the report lines via decoding.
• Related accounting reports: "Turnover and Balance Statement", "Turnover and Balance Statement by Account", "Account Analysis", "Account Turnovers", "Report by Entries" — transitions between them are available from decoding.

Input on the basis for the report is not provided (the report is not a source object for documents). The reverse scenario is possible: a source document is opened from the line of the card.

7. Extension Points

• Configuration extension: adding custom user settings for DCS, additional fields/resources, and formatting by modifying the main data composition scheme.
• Object module handlers: interception of OnResultComposition for programmatic post-processing of the tabular document (additional totals, hiding/highlighting rows).
• Form handlers: OnCreationOnServer, handlers for the Generate command and ResultDecodingProcessing — for additional default settings and non-standard navigation during decoding.
• Additional reports (external) through the BSP subsystem "Additional Reports and Processing" — as an alternative to modifying the standard object.
• Report variants: saving user/predefined variants of composition settings without changing the code.

Requires verification: the availability of specific extension points depends on the support mode of the configuration (removal from support / extension) and the version of the platform.