1. Identification
| Property | Value |
|---|---|
| Object Type | Report |
| Name | DynamicsOfAccountsReceivable |
| Full Name | Reports.DynamicsOfAccountsReceivable (Report.DynamicsOfAccountsReceivable) |
| Synonym | Dynamics of accounts receivable |
| Configuration | Accounting for Kazakhstan, version 3.0 (3.0.74.2) |
| Basis | Report on SCD (Data Composition System) |
Purpose. The report analyzes the changes in accounts receivable of customers (account 1210 "Short-term accounts receivable from customers and clients") for the selected period, broken down by intervals (day/week/month/quarter/year). It shows the balance at the beginning of the interval, turnovers (incurrence and repayment of debts), and the balance at the end, allowing tracking of payment dynamics, identifying overdue and growing debts, and planning cash inflows. It supports detailing by counterparties, contracts, payment documents, organizations, and structural units.
Where to find in 1C: section “For the Manager” → “Dynamics of Accounts Receivable”.
Navigation link: e1cib/list/Report.DynamicsOfAccountsReceivable
The report is generated on demand, does not create movements in accounting registers — it only reads already formed data.
2. Attributes and Table Parts
Since the object is a report on SCD, the "header attributes" here are the parameters for configuring the composition, not fields of the accounting document.
2.1 Attributes (configuration parameters)
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| StartPeriod | Date (dateTime) | ShowError | Left boundary of the analyzed period. Mandatory for report generation. |
| EndPeriod | Date (dateTime) | ShowError | Right boundary of the analyzed period. Mandatory, sets the end of the analysis interval. |
| Frequency | Number (decimal) | ShowError | Interval for breaking down the period (day, week, month, quarter, year). Determines the discreteness of the time slice columns. |
| OrganizationListRepresentation | String | DontCheck | String representation of selected organizations for the report header. Automatically generated from the selection by organizations. |
| DetailingMode | Boolean | DontCheck | Detailing flag. When enabled, the report opens from the context menu of another report for in-depth analysis of the detailing element; affects the application of default settings. |
2.2 Table Part “Grouping”
Stores settings for multi-level grouping of the result. The order of rows sets the hierarchy (levels) of groupings in the finished report.
| Name | Type | Purpose |
|---|---|---|
| Usage | Boolean | Flag for the activity of the grouping row. Only rows with Usage = True are applied. |
| Field | String | Technical name of the SCD field (e.g., Counterparty, Contract, Organization). |
| Representation | String | User-friendly name of the grouping field in the settings interface. |
| GroupingType | EnumRef.GroupingDetailingTypes |
Detailing type: OnlyTotals, NoTotals, ValuesAndTotals — controls the output of intermediate totals. |
3. Forms
| Form | Role | Description |
|---|---|---|
| ReportForm | Main form | The only working form (≈321 control elements). Contains fields for the period, panel for grouping settings, selections, conditional formatting, area for the tabular document to display results, and command panel: Generate, print, send/distribute, save and load settings variants. |
Separate settings forms and variants are inherited from the standard SCD mechanism and standard accounting reports; the report does not contain its own additional forms.
4. Key Module Procedures
In the attached evidence, the original BSL code is not provided, so below are the typical handlers for the report on SCD for this type of configuration object BK 3.0.
Object / Manager Module:
OnResultComposition(DocumentResult, DetailingData, StandardProcessing)— intercepts the result formation, programmatic adjustment of the composition layout (header withOrganizationListRepresentation, formatting of dynamics columns).SettingsForDataAnalysisTechnology()/OnDeterminingSettings()— registration of variants, parameters, and default settings for standard reports.
Form Module (ReportForm):
OnCreationOnServer(Error, StandardProcessing)— initialization of the period (default current month/quarter), filling the table part “Grouping”, applying selection by organization from user settings.OnOpening— processing of detailing mode: whenDetailingMode = True, settings passed from the calling report are applied.- Handler for the Generate command (
Generate/GenerateOnServer) — composition of the result throughCompositionSettings. DetailingProcessing— opening this or a related report inDetailingModefor the selected element.
Requires verification: exact signatures and presence of the listed procedures depend on the specific build 3.0.74.2.
5. Data Source (instead of posting and movements)
The report is not posted and does not generate movements — this is an inherent property of objects of the type "Report". It reads data from already existing accounting registers.
The source is data on the accounts receivable of customers from the accounting register (“Cost Accounting”/accounting):
| Indicator | Source |
|---|---|
| Balance at the beginning of the interval | Debit balance of account 1210 at StartPeriod |
| Incurrence of debt (debit turnover) | Sales: Dr 1210 Cr 6010 (income from sales), simultaneously Cr 3130 (VAT payable, rate 16%) |
| Repayment of debt (credit turnover) | Customer payment: Dr 1030 (money in current accounts) Cr 1210 |
| Balance at the end of the interval | Debit balance of account 1210 at the end of each interval of frequency |
Related postings of sales, affecting the overall picture of settlements: write-off of cost Dr 7010 Cr 1330 (goods). Settlements with suppliers (3310) are not included in this report — it is focused only on accounts receivable from customers.
Electronic documents of the RK (ESF in the ESF IS, SNT) are generated at the stage of issuing sales and do not directly enter this report, but the corresponding sales documents are primary registrars of movements on account 1210.
6. Related Objects and Input on Basis
As a report, the object does not participate in input on basis and is not a registrar. The connections are informational:
- Source documents: “Sales of goods and services”, “Act of completed works”, “Payment from customer”/“Receipt to bank account”, “Debt adjustment”, “Cash receipt order” — generate turnovers on account 1210.
- Related reports: “Turnover and balance sheet for account 1210”, “Settlements with customers”, “Statement of settlements with counterparties”, “Analysis of subaccounts (Counterparties/Contracts)” — opened through detailing.
- Detailing mechanism: result elements (counterparty, contract, document) are revealed in detailed reports; when calling the report in
DetailingModefrom another report, settings are passed automatically.
7. Extension Points
- Report variants (SCD): adding custom settings variants through the variant storage without changing the code.
- Configuration extension: overriding
OnResultCompositionfor adjusting the layout, conditional formatting, or additional dynamics columns. - Additional selections/fields: expanding the composition scheme (calculated fields, resources) — for example, a flag for overdue debt or the number of days overdue.
- Subscriptions and distributions: including the report in the scheduled distribution through the standard report distribution mechanism.
- Detailing: adding custom scenarios for
DetailingProcessingto transition to application reports. - Access rights (RLS): restricting data visibility by organizations/counterparties through standard roles and record-level restrictions.