1. Identification
| Property | Value |
|---|---|
| Object Type | Report (Reports / Отчет) |
| Name | ChessStatementStandard |
| Full Name | Report.ChessStatementStandard |
| Alias | “Chess statement (accounting)” |
| Configuration | Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) |
| Implementation Basis | Data composition scheme (DCS) |
| Navigation Link | e1cib/list/Report.ChessStatementStandard |
Purpose. The chess statement is a standard synthetic analytical report for analyzing the correspondence of accounting accounts. It forms a matrix (“chess”) representation of transactions: rows represent debit accounts, columns represent credit accounts, and the intersection shows the amount of entries corresponding to the correspondence for the selected period. The report is used by accountants to verify the correctness of entries, analyze transactions between accounts, and control balance ratios; it is generated regularly at the end of the month/quarter during data reconciliation and financial reporting preparation.
For example, when selling goods in the RK, the standard correspondence for the period will be reflected as follows: the intersection of row 1210 (short-term accounts receivable from customers) and column 6010 (revenue from sales) will show revenue, including VAT of 16%; the intersection of 3130 (VAT payable) in credit will show the accrued tax; row 7010 / column 1330 will show the cost of goods sold.
Where to find in 1C: section “Reports” → “Chess statement (accounting).”
2. Attributes and Table Parts
The report does not have object attributes and table parts in the conventional sense of a document: the data set and field structure are described in the data composition scheme, and the parameters listed below serve as configuration attributes (DCS parameters / report form attributes).
2.1 Parameters (attributes of settings header)
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| StartPeriod | xs:dateTime |
Not checked | The start date of the analysis period for account movements. Sets the left boundary of the transaction selection. |
| EndPeriod | xs:dateTime |
Not checked | The end date of the analysis period for movements. Sets the right boundary of the transaction selection. |
| OrganizationListRepresentation | xs:string |
Not checked | Text representation of selected organizations for the header and data filtering. |
| DepartmentListRepresentation | xs:string |
Not checked | Text representation of selected departments for the header and data filtering. |
| ByCurrencies | xs:boolean |
Not checked | Flag for detailing transactions by currencies. When set, currency amount columns are added (relevant for currency transactions converted to tenge ₸). |
| DataByDepartments | xs:boolean |
Not checked | Flag for detailing by organization departments — transactions broken down by structural units. |
| BySubaccounts | xs:boolean |
Not checked | Flag for detailing by subaccounts. Accounts are disclosed to the level of subaccounts of the standard chart of accounts of the RK. |
| ByOffBalanceAccounts | xs:boolean |
Not checked | Flag for including off-balance accounts (inventory on responsible storage, leased fixed assets, etc.). |
| DetailingMode | xs:boolean |
Not checked | Flag for detailing mode with a transition to primary documents from report cells. |
2.2 Table Parts
Table parts are absent. The report uses the data composition scheme to form a matrix representation of transactions.
3. Forms
| Form Name | Purpose | Main |
|---|---|---|
| ReportForm | The only form: setting parameters, generating and viewing the chess statement. Contains a settings panel with filters, fields for selecting the period and organization, a tabular result field, as well as buttons for generating, printing, and emailing. | Yes |
The form contains about 279 control elements. Additional settings forms (variant, selection, conditional formatting) are provided dynamically by the platform's DCS mechanism and are not stored as separate objects in the metadata tree.
4. Key Module Procedures
For the report on DCS, the application code is minimal — the main work is performed by the data composition system. The standard set of handlers for this type of object includes:
- Form Module →
OnCreateOnServer— initialization: setting the default period, substituting the main organization of the user, restoring saved user settings, filling in the representations of organization/department lists. - Form Module →
Generate(command) — composition of the result: callingSettingsComposer→ executingDataCompositionProcessorand outputting to the tabular document of the result field. - Form Module →
ResultDetailingProcessing— processing detailing mode: clicking on a cell opens the detail of the transaction down to the primary source documents (controlled by the DetailingMode flag). - Form Module → flag handlers (
ByCurrenciesOnChange,BySubaccountsOnChange,ByOffBalanceAccountsOnChange, etc.) — redefining the structure/groupings and columns of DCS settings before generation. - Object Module →
OnCompositionResult(if available) — programmatic adjustment of the composition layout: hiding service fields, formatting totals, adding currency columns.
“Requires verification”: exact names and presence of procedures in
Report.ChessStatementStandard.Form.ReportFormand object module are version-specific for release 3.0.74.2 — to be clarified with the configurator during refinement.
5. Data Sources and Movements
The report does not generate movements and entries — it only reads them. The data source is the accounting register “Cost Accounting” (accounting totals and transactions). The composition scheme selects debit/credit transactions for the period [StartPeriod; EndPeriod] with selection by organization and (when flags are enabled) by department, currency, subaccounts, and off-balance accounts.
The logic of matrix formation:
- Rows — debit account, columns — credit account; in the cell — the amount of the transaction for this correspondence.
- Totals by row = debit turnover of the account, totals by column = credit turnover; the overall total by rows equals the total by columns (control of equality of turnovers Dt = Kt).
- When ByCurrencies = True, currency amount columns are added with conversion to tenge (₸).
- When ByOffBalanceAccounts = True, off-balance accounts are included in the selection.
Standard accounts of the chart of accounts of the RK, between which transactions are analyzed: 1210 (short-term accounts receivable from customers), 1030 (cash in current accounts), 1330 (goods), 3310 (accounts payable to suppliers), 3130 (VAT payable, rate 16%), 6010 (revenue from sales), 7010 (cost of sales).
6. Related Objects and Input on Basis
- Accounting Register “Cost Accounting” — the only data source for the report.
- Primary source documents (Sale, Receipt, Payment Order, Operation, etc.) — accessible from the report through detailing mode: double-clicking on a cell opens the list of entries, and then the source document.
- Electronic documents of the RK — ESF (IS ESF) and SCT are generated based on primary documents of sale/receipt and do not participate in the report itself, but affect the VAT amounts (3130) included in the statement.
- Input on basis is not provided for the report (the report is not a source document).
7. Extension Points
- User variants and DCS settings — saving formatting variants, selections, additional groupings without changing the configuration.
- Configuration extension — adding columns/indicators through borrowing the composition scheme, redefining form procedures (
Generate, detailing handler). - Additional reports (external) — connection through the subsystem “Additional reports and processing” without removing from support.
- Detailing mechanism — point of customization for transitioning to primary documents (flag DetailingMode and handler
ResultDetailingProcessing).
