Report "Accounts Receivable by Debt Maturity" (Accounting for Kazakhstan 3.0.74.2)

1. Identification

Purpose. The report is intended for detailed analysis of accounts receivable from customers, broken down by time intervals of overdue payments (current debt, 1–30 days, 31–60 days, 61–90 days, over 90 days, etc.). It is used by financial managers, accountants for customer settlements, and managers to assess the quality of accounts receivable, identify problematic counterparties, and plan debt collection activities.

The report is generated for a specific date, supports flexible grouping settings (counterparty, contract, manager, organization), filters by organizations, adds additional analytical fields, exports results, and schedules dispatch. It integrates with “Manager's Monitor” to display key indicators of overdue debts.

Important: this is a report, not a document. It does not perform postings or generate movements in registers or accounts — it only reads accounting data (see section 5).

Where to find in 1C: section “For the Manager” → “Customer debt by debt terms”. Navigation link: e1cib/list/Report.CustomerDebtByDebtTerms.

2. Header Attributes and Table Parts

2.1 Report Attributes (Parameters)

2.2 Table Part “Intervals”

Defines time ranges (in days) for segmenting debt by overdue terms. Each row sets the boundary of the interval; the system automatically forms groups such as “0–30 days”, “31–60 days”, etc.

2.3 Table Part “Grouping”

Manages the structure of grouping report rows (by which dimensions to group: counterparty, contract, manager, organization, etc.).

3. Forms

The report is built on the data composition system (DCS), so the set of forms is typical for reports in BC 3.0:

User settings (Period, filtering by organizations, composition of intervals) are displayed on the main form as quick settings.

4. Key Module Procedures

The attached evidence does not include software modules (BSL), so below are standard report handlers for this type of object in BC 3.0:

• Object Module → OnResultComposition(ReportResult, DecryptionData, StandardProcessing) — interception point for outputting the result. Here, the layout is usually fine-tuned: substituting overdue intervals from the table part “Intervals”, calculating the number of overdue days relative to the Period parameter, distributing amounts across the overdue columns.
• Form Module → OnServerCreation — initialization of parameters (filling Period with the current date, default values for table parts “Intervals” and “Grouping”), setting field visibility based on DetailingMode.
• Form Module → BeforeFilling / SetReportParameters — receiving external parameters when opening from the “Manager's Monitor” (including setting DetailingMode = True).
• Form Module → handlers for changes in table parts “Intervals”/“Grouping” — reassembly of layout settings when adding/removing intervals and toggling Usage flags.
• OnFillingCheck — control of the mandatory attribute Period (implementation of ShowError).

Requires verification on a specific delivery 3.0.74.2: exact names of procedures and path path:string — the provided handlers reflect the standard implementation of DCS reports, but the composition may differ with modifications.

5. Data Sources (Registers and Accounts)

The report does not generate postings or movements — it aggregates already existing accounting data. The source is the balances for settlements with customers:

• Accounting Register “Cost Accounting” — balances on account 1210 “Short-term accounts receivable from customers and clients” (standard chart of accounts of the RK) broken down by subaccounts “Counterparties” and “Contracts”.
• The date of debt occurrence is taken from the movement/document data; the number of overdue days = Period − DebtDate (considering the payment schedule by contract, if specified).
• The debt amount is grouped by the intervals of table part “Intervals”.

Related accounts involved in forming the debt itself (for understanding the context of accounting):

Sales to customers that generate debt on 1210 are accompanied by electronic documents ESF (ESF IS) and, if necessary, SNT; this does not affect the amounts of tax indicators in the report — it only operates with debt amounts.

6. Related Objects and Input Based On

Reports in 1C do not support “input based on” and are not entered based on documents themselves. Functionally, the report is related to:

• Directories “Counterparties”, “Contracts”, “Organizations”, “Individuals/Managers” — dimensions of groupings and filters.
• Documents for settlements with customers — “Sale of goods and services”, “Act of completed works”, “Receipt of money”, “Debt adjustment”, “Mutual settlement” — generate movements on account 1210, which the report reads.
• “Manager's Monitor” — calls the report with preset parameters (including DetailingMode).
• Electronic documents ESF / SNT — accompany the sale that generated the debt.

7. Extension Points

• Report Variants (DCS) — adding new grouping/formatting options without changing the code.
• Configuration Extensions — overriding OnResultComposition, adding form attributes and columns (extending the form/object module).
• Additional Fields through AdditionalFieldsPlacement — outputting user analytics in columns/rows.
• Table Part “Intervals” — flexible adjustment of the overdue scale to the organization's regulations.
• Scheduled Dispatch and Export — integration into regulatory tasks and external reporting.
• Event Subscriptions / External Processing — pre-processing parameters when opening from external locations (manager's monitor, desktop).