Report "Standard Journal Report" - Technical Description (Accounting for Kazakhstan 3.0.74.2)

1. Identification

Purpose. A standard tool for analyzing accounting transactions by periods, organizations, departments, and accounts. Designed for accountants and chief accountants: detailed audit of operations, verification of transaction correctness (debit/credit), analysis of turnover by accounts. Used daily for operational control and periodically (monthly/quarterly) during period closing. Supports a breakdown mode for transitioning to primary supporting documents and flexible configuration of indicators (accounting amount, currency amount, quantity).

Where to find in 1C: section “Reports” → “Accounting” → “Report by transactions (accounting)”. Navigation link: e1cib/list/Report.ReportByTransactionsStandard.

2. Attributes and Table Parts

2.1 Header Attributes (report parameters)

All attributes are parameters of DCS / form settings; mandatory checks at the metadata level are not performed (default values are set by the form and report options).

2.2 Table Parts

The report does not contain table parts in the object metadata. The resulting data set is formed dynamically through DCS (MainDataCompositionScheme) based on the accounting register and is output in the tabular document of the form.

3. Forms

The form ReportForm includes approximately 287 UI elements, of which ~15 are input fields (periods, filters, formatting flags). A specialized settings form is not allocated — management of the variant and DCS settings is built into the main form (standard BSP scheme).

4. Key Module Procedures

The report is built on DCS, so the main logic is declarative (in the composition scheme), and the program code is reduced to standard BSP handlers. Below is the standard set of handlers for reports of this type (evidence on BSL lines is not attached — the composition is provided according to the typical architecture of the object):

Report Object Module

• OnResultComposition(DocResult, DataBreakdown, StandardProcessing) — intercepts composition: substitutes representations of organizations/departments in the header, manages the composition of columns by indicator flags (AccountingIndicator, CurrencyAmountIndicator, QuantityIndicator), fine-tunes filters before output.
• DefaultOutputParameterSettings() / initializes the period — sets StartPeriod/EndPeriod (usually the current month).

Form Module

• OnCreateOnServer(Error, StandardProcessing) — initializes settings, restores user parameters, sets default period, applies functional options.
• Generate(Command) / UserSettingsCompositionSettings… — starts composition and outputs to the tabular document.
• ResultBreakdownProcessing(Element, Breakdown, StandardProcessing) — processes clicks on cells: when BreakdownMode is enabled, opens the document-basis of the transaction or details by subaccount/account.
• Handlers for indicator flags — when Indicator* changes, rebuild visibility of columns and reform the report.

Requires verification: exact names and signatures of export procedures may differ in the specific assembly 3.0.74.2 (evidence on the module is not provided).

5. Data, Movements, and Transactions

Important: the report does not conduct and does not generate movements — it is an object of type “Report”, it only reads data. The data source is the accounting register (standard CostAccounting / Accounting), from which DCS selects transactions for the specified period with a breakdown by debit/credit, subaccount, currency, and quantity.

The report displays transactions already formed by documents. Typical correspondences of the chart of accounts of the RK that fall into the selection:

Example of VAT amount. When selling for 1,000,000 ₸ (excluding VAT), VAT of 16% = 160,000 ₸ is accrued: Debit 1210 Credit 3130 — 160,000 ₸. Total to be received 1,160,000 ₸.

Electronic documents (electronic invoices (ESF) through the ESF IS, SCT) are formed by the primary documents of sales/receipts; in the report, they are visible as transactions of these documents and accessible through breakdown.

Output indicators (accounting currency — tenge ₸):

• Accounting — amount of the transaction in the currency of regulated accounting;
• Currency amount — amount in the currency of the contract (for foreign currency transactions);
• Quantity — turnover in natural expression for accounts with quantity accounting (1330 and others).

6. Related Objects and Input on Basis

• Accounting Register — the only source of data (transactions).
• Primary documents of transactions (Sale of goods and services, Receipt of goods and services, Payment order, Operation entered manually, etc.) — opened from the report in breakdown mode.
• Chart of accounts (standard chart of accounts of the RK), directories “Organizations”, “Structural Units”, “Counterparties”, “Nomenclature”, “Currencies” — used as dimensions/subaccounts and filters.
• No input on basis — the report is not a document and does not generate objects.

7. Extension Points

• Report variants in DCS — creation of user variants (groupings, filters, formatting) without changing the configuration; saving through the standard BSP mechanism.
• Configuration extension — overriding handlers OnResultComposition, breakdown processing; adding custom fields/resources to the composition scheme.
• Functional options — managing visibility of indicators (currency, quantity accounting) through configuration options.
• Conditional formatting — setting up highlighting of rows/cells based on conditions (for example, highlighting transactions by account 3130 VAT).
• Additional reports (external) — connecting through the subsystem “Additional reports and processing” of BSP as an alternative to editing the standard object.

Requires verification: availability of specific functional options and predefined variants depends on the assembly 3.0.74.2 and the included accounting functionality.