1. Identification
| Parameter | Value |
|---|---|
| Object Type | Report |
| Name | Sales |
| Full Name | Report.Sales (Reports.Sales) |
| Synonym | “Sales” (in the metadata tree, the synonym is not specified separately — it matches the name) |
| Configuration | Accounting for Kazakhstan, edition 3.0.74.2 |
| Implementation Basis | Data Composition System (DCS) |
| Sample Currency | tenge (₸) |
Purpose. The “Sales” report is intended for analytical analysis of data on the sale of goods, works, and services by nomenclature, counterparties, periods, managers, and other dimensions. It is used by managers, financial analysts, and sales managers to assess sales dynamics, identify the most profitable areas, and plan. It supports several pre-installed options (by nomenclature groups, by counterparties with calculations by shipment and by payment) and is integrated with the manager's monitoring to display key indicators on the main dashboard.
Where to find:
- Interface: section “For the Manager” → “Sales” (also available from the “Reports” section).
- Navigation link 1C:
e1cib/list/Report.Sales
The report is a read-only object: it is not processed and does not generate movements/entries. It selects and aggregates already existing accounting data (see section 5).
2. Settings Attributes and Table Parts
For the report in DCS, the “header attributes” are the parameters for formation settings (user settings/parameters), and the “table parts” are the structure tables (groupings, selections, indicators).
2.1 Header Attributes (Formation Parameters)
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| StartPeriod | xs:dateTime |
Not checked | The start date of the analyzed sales period. The left boundary of the selection. |
| EndPeriod | xs:dateTime |
Not checked | The end date of the analyzed period. The right boundary of the selection. |
| Frequency | xs:decimal |
Not checked | The time grouping interval (day, week, month, quarter, year). Controls the detail of time series. |
| Organization | CatalogRef.Organizations |
Not checked | The organization for which the report is generated. Limits the selection to one legal entity. |
| IncludeSeparateBranches | xs:boolean |
Not checked | Flag for including data on separate branches (affiliates) of the selected organization. When “True”, sales are aggregated across all branches. |
| PlacementOfAdditionalFields | xs:decimal |
Not checked | Code for the placement of additional fields (rows, columns, separate area). Controls the layout. |
| DetailingMode | xs:boolean |
Not checked | Flag for activating detailing. Determines the possibility of transitions from the report to the primary sales documents. |
| IndicatorSum | xs:boolean |
Not checked | Inclusion of the “Sum” indicator. When “True”, summary data on sales is displayed. |
| IndicatorQuantity | xs:boolean |
Not checked | Inclusion of the “Quantity” indicator. When “True”, quantitative data is displayed. |
| IndicatorDetermineSumByPayment | xs:boolean |
Not checked | Switching the sum calculation mode. “True” — sums by actual payments, “False” — by shipments. |
| RepresentationOfListOfOrganizations | xs:string |
Not checked | Text representation of selected organizations for the report header. Automatically generated when multiple selections are made. |
2.2 Table Parts
Grouping
Purpose: defines the dimensions by which data grouping and detailing are performed (nomenclature, counterparty, period, manager, etc.).
| Name | Type | Purpose |
|---|---|---|
| Usage | xs:boolean |
Flag for activating the grouping row. Only rows with the value “True” participate in the report. |
In addition to the table provided, the DCS report structure includes standard sections for analytical reports: Selections (conditions for limiting the selection), SelectedFields/Indicators (set of displayed resources — Sum, Quantity, Cost), Sorting, and ConditionalFormatting. These areas are configured by the user through the standard DCS settings form.
3. Forms
| Form | Purpose |
|---|---|
Main report form (ReportForm) |
Unified form for launching and viewing. Contains a quick settings panel (period, organization, indicators, mode by shipment/payment), a table document field with results, and a command panel (Generate, Settings, Save, Print). For the DCS report, an automatically generated DCS form or a thin wrapper over it is usually applied. |
| Settings form (standard DCS) | Full editing of the structure: groupings, selections, fields, sorting, conditional formatting. Called by the “Settings” button. |
| Report variant form | Selection and management of pre-installed variants (“By nomenclature groups”, “By counterparties (by shipment)”, “By counterparties (by payment)”). |
Separate forms for the report list/selection are not required — opening is done via the navigation link
e1cib/list/Report.Sales.
4. Key Module Procedures
The attached evidence does not provide the source code (BSL) of the report modules, so below are listed typical handlers for the DCS report in the BSP/“Accounting for Kazakhstan” configurations. Specific names and lines should be clarified according to the object module in the specific assembly.
Object module / report manager module:
OnResultComposition(DocumentResult, DataDetailing, StandardProcessing)— intercepts composition: substitutes period parameters, sets the mode “by payment/by shipment”, preliminary prepares the DCS layout.FormSettings(...)/DefineFormSettings(...)(integration with BSP) — registration of report variants, configuration of the quick settings panel, availability of commands.OnDeterminingFrequencySettings(...)— matches theFrequencyattribute with standard DCS periods.
Report form module:
OnCreationOnServer(Failure, StandardProcessing)— initialization of default parameters (current month as period, main organization, indicators “Sum” and “Quantity”).OnLoadingVariantOnServer(Settings)— fine-tuning parameters for the selected variant (for example, including the payment indicator for the “by payment” variant).- Quick settings command handlers — response to changes in organization, flag for separate branches, sum calculation mode.
- Detailing handler (
DocumentResultDetailingProcessing) — transition to primary sales documents whenDetailingModeis enabled.
Requires verification (version-specific): the exact composition of integration procedures with the “Manager's Monitor” and the naming of methods for connecting to the key indicators panel depends on the assembly 3.0.74.2.
5. Data Sources and Accounting Logic (instead of processing)
The report does not generate movements and entries — it reads data already formed by sales documents. Below are the sources it uses and how it relates to the standard Chart of Accounts of the RK.
Data sources for DCS (typical for the configuration):
- Accounting register “Cost Accounting” — turnovers on income and cost accounts.
- Accumulation registers of the sales/reconciliation subsystem — quantitative and monetary turnovers of sales, status of reconciliations and payments (used in the “Determine sum by payment” mode).
Entries that the report analyzes (formed by sales documents, e.g., “Sale of goods and services”, not by the report itself), according to the standard Chart of Accounts of the RK:
| Operation | Debit | Credit | Comment |
|---|---|---|---|
| Recognition of income from sales | 1210 (short-term receivables from customers) | 6010 (income from sales) | For the sale amount excluding VAT |
| Accrual of VAT on sales | 1210 | 3130 (VAT payable) | At the rate of 16% (Kazakhstan, 2026) |
| Write-off of cost | 7010 (cost of sales) | 1330 (goods) | Forms the cost/margin indicator |
| Receipt of payment from the customer | 1030 (cash in current accounts) | 1210 | Closes receivables; accounted in “by payment” mode |
Example of calculating report indicators (₸, VAT rate 16%):
- Sale of goods for an amount excluding VAT: 1,000,000 ₸ → income (6010) = 1,000,000 ₸.
- VAT 16%: 160,000 ₸ (3130). Total payable by the customer (1210) = 1,160,000 ₸.
- Cost (7010) = 700,000 ₸ → gross margin = 300,000 ₸.
Sum calculation modes:
IndicatorDetermineSumByPayment = False— the sum is taken by shipment (moment of income recognition, turnovers on 6010/1210).IndicatorDetermineSumByPayment = True— the sum is taken by actual payment (receipts on 1030, repayment of 1210).
Electronic documents accompanying sales in the RK — ESF (invoice in the ESF IS) and SNT (accompanying invoice for goods) — are formed by sales documents, not by the report. The report can be used to reconcile sales volumes with issued ESF/SNT.
6. Related Objects and Input on the Basis
The report is the final consumer of data, so “input on the basis” does not apply to it. Related objects:
- Source documents: “Sale of goods and services”, “Act of completed works”, “Retail sales report”, payment documents (PKO, receipt to the settlement account) — their data enters the report.
- Detailing: when
DetailingModeis enabled, transitions from the report cells to the listed primary documents are performed. - Reference dimensions: “Organizations”, “Nomenclature”, “Counterparties”, “Contracts”, “Departments”, “Users” (managers) — used as groupings/selections.
- Electronic documents: ESF (ESF IS), SNT — linked through sales documents.
- Manager's Monitoring: the report provides key sales indicators to the dashboard.
7. Extension Points
- Report variants. Creation of user/additional DCS variants (new groupings, margin/profitability indicators) without changing the code.
- Configuration extension. Adding settings attributes, new fields to the DCS schema, refining forms through extension (without removing from support).
- External report / additional processing. Connection through the “Additional reports and processing” subsystem (BSP) — an alternative to editing the standard object.
- DCS handlers. Redefining
OnResultCompositionfor non-standard logic (for example, recalculating VAT at a rate of 16%, adding calculated columns). - Conditional formatting. Configuring the highlighting of indicators (sales leaders/outsiders, deviations from the plan) using DCS tools.
- Integration with monitoring. Publishing additional report indicators on the manager's panel.
Recommendation for implementers: all modifications should be carried out through configuration extension or additional DCS variants to keep the object under support when...
```