1. Identification of the Object
| Parameter | Value |
|---|---|
| Object Type | Report |
| Name | ReportOnSalesOfGoodsAndServices |
| Full Name | Report.ReportOnSalesOfGoodsAndServices |
| Synonym | Report on sales of goods and services (no separate synonym defined in metadata) |
| Configuration | Accounting for Kazakhstan, edition 3.0, version 3.0.74.2 |
| Currency of Calculations | tenge (₸) |
| Navigation Link | e1cib/list/Report.ReportOnSalesOfGoodsAndServices |
Purpose. The report is intended for analyzing the sales of goods and services in various analytical dimensions with a customizable set of indicators (amount, quantity, cost excluding VAT, VAT, excise, profit, returns) and groupings. It is used by accountants and managers to monitor revenue, analyze returns, and assess sales profitability. Data is generated based on sales documents for the selected period with filtering by organizations and departments. The mode of detailing down to primary documents is supported; the report can be included in automatic mailing.
Where to find in 1C: section "Sales" → "Report on sales of goods and services".
2. Parameters of Settings and Table Parts
As an object of type "Report", the object does not have document/reference parameters — the fields listed below are parameters of the form/settings of the composition (stored in variants and user settings of the report). In the evidence, they are described by XSD types of the settings serialization schema.
2.1 Header Parameters (Formation Parameters)
| Name | Type | Purpose |
|---|---|---|
StartPeriod |
dateTime | Start date of the report formation period |
EndPeriod |
dateTime | End date of the report formation period |
RepresentationOfListOfOrganizations |
string | String representation of selected organizations for display on the form |
RepresentationOfListOfDepartments |
string | String representation of selected departments for display on the form |
PlacementOfAdditionalFields |
decimal | Method of placement of additional fields (columns / rows) |
DetailingMode |
boolean | Inclusion of data detailing down to primary documents |
2.2 Indicators (Column Output Flags)
| Name | Type | Report Column |
|---|---|---|
IndicatorTotal |
boolean | Total sales |
IndicatorTotalExcludingTaxes |
boolean | Total excluding taxes |
IndicatorCost |
boolean | Cost (excluding VAT) |
IndicatorVAT |
boolean | Total VAT |
IndicatorExcise |
boolean | Total excise |
IndicatorQuantity |
boolean | Quantity of sales |
IndicatorProfit |
boolean | Profit (total profit) |
IndicatorTotalReturns |
boolean | Total returns from customers |
IndicatorTotalWithReturns |
boolean | Total sales considering returns (net revenue) |
IndicatorQuantityReturns |
boolean | Quantity of returns |
IndicatorQuantityWithReturns |
boolean | Quantity of sales considering returns (net sales) |
2.3 Table Part "Grouping"
Purpose: defines analytical dimensions for data grouping.
| Name | Type | Purpose |
|---|---|---|
Usage |
boolean | Flag of grouping activity in the current setting |
Field |
string | Internal name of the grouping field (e.g., Product, Counterparty, Department, SalesDocument) |
VAT indicators in the report are calculated based on the current rate in the RK of 16% (the value of 12% from earlier releases does not apply to periods of 2026). Amounts are displayed in tenge (₸).
3. Forms
| Form | Purpose |
|---|---|
Main report form (ReportForm / main) |
Input of period, filtering by organizations and departments, selection of indicators and groupings, launching formation, output of composition result, calling details |
Variant / settings form (SettingsForm) |
Extended configuration of report structure (groupings, filters, fields, formatting) through the settings of the composition tool |
If the object is implemented on the composition tool with a standard set of forms, system forms for selecting variants and settings generated by the platform are additionally available. User variants are stored in the report variants repository.
4. Key Procedures of Modules
In the attached evidence, the source code (BSL) of the modules is not provided, so below are typical handlers for reports of this type (composition tool / arbitrary schema). If a module is present, they should be compared with the actual implementation.
Report form module:
OnCreateOnServer— initialization of the period (by default, the current month/period), filling in filters for organizations/departments, restoring indicators.OnOpen— fine-tuning of the command interface, visibility of columns by flagsIndicator*.Generate/ComposeResult— assembling settings of the composition tool (groupings from table part "Grouping", filters, selected fields) and outputting the result in the table document field.- Handlers for changing indicator flags (
VATIndicatorOnChangeetc.) — managing the visibility of corresponding columns and fields of the composition tool. ResultDetailingProcessing— processing detailing down to primary documents whenDetailingModeis enabled.
Report object module:
OnComposeResult— programmatic fine-tuning of the composition layout: substituting VAT rate, calculating profit columns (Total excluding taxes − Cost excluding VAT), forming columns "with returns".SettingsOnPlacingInStorage/ initializing schema — when generating a data set by request.
5. Data Sources, Registers, and Entries
The report does not generate movements and entries — it only reads already posted data. Below are the sources from which it aggregates indicators, and the related standard entries of sales documents in the chart of accounts of the RK.
Data sources of the report:
- Accumulation register of sales/revenue accounting (turnovers on sales: amount, quantity, cost).
- Data of sales documents (
Sales of goods and services) and return documents from the customer for the period. - VAT register (for the indicator "Total VAT" at the rate of 16%).
Standard entries of the sales document (for the context of indicators), chart of accounts of the RK:
| Operation | Debit | Credit | Comment |
|---|---|---|---|
| Revenue from sales | 1210 (Accounts receivable) | 6010 (revenue from sales) | For the amount excluding VAT |
| Accrual of VAT | 1210 | 3130 (VAT payable) | VAT 16% of the amount excluding taxes |
| Cost of goods sold | 7010 (cost of sales) | 1330 (goods) | Forms indicators "Cost (excluding VAT)" and "Profit" |
| Receipt of payment | 1030 (cash in current accounts) | 1210 | Closing accounts receivable |
The indicator Profit = "Total excluding taxes" − "Cost excluding VAT" (cost according to account 7010). Columns "with returns" reduce revenue and quantity based on return documents.
Example: sales of 100,000 ₸ excluding VAT → VAT 16% = 16,000 ₸, total payable 116,000 ₸ (Dr 1210 Cr 6010 — 100,000; Dr 1210 Cr 3130 — 16,000). With a cost of 70,000 ₸ (Dr 7010 Cr 1330) Profit = 30,000 ₸.
6. Related Objects and Input on the Basis
As a report, the object does not participate in "input on the basis". The connections are informational:
- Source documents: "Sales of goods and services", "Return of goods from the customer", as well as electronic documents ESF (ESF IS) and SNT, accompanying the sale.
- Reference directories: Organizations, Departments, Products, Counterparties, Contracts.
- Detailing mechanism: from the report line (when
DetailingMode = True) a transition to primary sales/return documents is performed. - Report mailing: the object can be included in automatic mailing (scheduled task for report mailing).
7. Extension Points
- Report variants (composition tool): adding user variants of groupings, filters, and formatting without changing the configuration.
- Configuration extension (Extension): overriding
OnComposeResult/ form handlers to add custom indicators or columns. - Additional reports (BSP): connecting an external analogous report through the subsystem "Additional reports and processing".
- Additional fields/parameters: output of additional parameters of products/counterparties through the settings of the composition tool.
- Mailing and schedule: setting up automatic generation and sending on a schedule.
Requires verification in the specific build 3.0.74.2: the exact composition of system forms and the presence of the object programming module (sales on composition tool vs. arbitrary schema) — as the source BSL is not attached in the evidence.
