Sales Funnel Report (Reports.ВоронкаПродаж) — technical description

1. Identification

Purpose. The report visualizes the progress of customer deals through the stages of the sales process and shows conversion between stages — from initial interest to a won/lost deal. It gives the manager and sales department head answers to questions: how many deals are in progress, at which stage they "get stuck," what the step-by-step and overall conversion is, and what volume of potential revenue (in ₸) is concentrated at each stage. This is an analytical report: it only reads accounting data and does not generate any movements or postings.

2. Settings, parameters and fields (analog of "attributes")

The report has no header attributes or tabular sections in the sense a document does. Its "set of fields" is defined by the data composition scheme. Below is the typical composition for a report of this kind.

Report parameters (settings panel)

Main fields (DCS resources and dimensions)

3. Forms

DCS-based reports in the standard configuration typically have no dedicated form — the universal system is used:

A dedicated managed form is only created if non-standard behavior is required (additional commands, a specific chart). If, in the specific 3.4.5.21 build, the report has a dedicated form — this needs to be checked in the configurator (requires verification in the specific build).

4. Key module procedures

No explicit BSL evidence for this object has been attached. DCS-based reports typically have the following handlers (object module / form module):

• ПриКомпоновкеРезультата(ДокументРезультат, ДанныеРасшифровки, СтандартнаяОбработка) (object module) — intercepts output: layout refinement, programmatic construction of the funnel chart, filling in calculated conversion fields, setting СтандартнаяОбработка = Ложь for fully manual composition.
• ПриКомпоновкеСостава(...) — manages the available set of fields/filters in user settings.
• ПриСозданииНаСервере / ПриОткрытии (form module) — presets the period (e.g., current month), filter values for the current manager user, initial DCS settings.
• ВоронкаПродажПриИзмененииОтбора / form command handlers — re-generates the result when the period, organization, or responsible person changes.

For data retrieval, the report relies on DCS data sources (a query to registers and objects of the CRM subsystem), not on posting procedures.

5. Data sources instead of movements

The report is a non-accounting object: it is not posted, does not write to registers, and does not generate accounting entries. The "posting and movements" section is not applicable to it. Instead, the report reads CRM and sales data:

• Customer deals (Справочник.СделкиСКлиентов) and their current stages;
• the register(s) of deal statuses / history of sales process stage changes;
• when displaying potential revenue amounts — planned deal amounts and related customer orders.

Actual financial postings are generated by other objects (sales, payments), and in the standard Kazakhstan chart of accounts they affect:

These accounts are provided for context on "what stands behind a won deal" — the "Sales Funnel" report itself does not use them and does not generate postings.

6. Related objects and input based on

• Справочник.СделкиСКлиентов — the key source; the deal card opens from the report via drill-down.
• Interactions (calls, emails, meetings) linked to deals — affect movement between stages.
• Sales processes and stages — a catalog/list of stages defining the funnel structure.
• Customer orders / Sales of goods and services — the result of a won deal; these generate document workflow (including electronic documents ESF via the ESF IS and SNT) and accounting movements.

"Input based on" is not applicable to the report (reports do not participate in the "input based on" mechanism). Drill-down of the result replaces this function: from a funnel cell you navigate to the list/card of deals.

7. Extension points

• Report variants (DCS): saving custom funnel variants (by manager, by deal type, by region) without changing the configuration.
• Configuration extension: borrowing the Отчет.ВоронкаПродаж object and overriding ПриКомпоновкеРезультата/scheme for additional indicators (e.g., average check per stage in ₸, closing forecast).
• Additional reports (external): alternative funnels connected via the BSP "Additional reports and data processors" subsystem without interfering with the standard one.
• Functional options: report visibility is controlled by CRM/sales subsystem options — when deal functionality is disabled, the report is hidden from the interface.
• Conditional formatting and custom DCS fields: adding calculated conversion fields and color indication of "bottlenecks" on the settings side, without code modification.