1. Identification
| Parameter | Value |
|---|---|
| Object Type | Report |
| Name | SupplierDebtByDebtTerms |
| Full Name | Report.SupplierDebtByDebtTerms |
| Synonym | “Supplier debt by debt terms” |
| Configuration | Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) |
| Mechanism Basis | Data composition system (DCS) |
| Navigation Link | e1cib/list/Report.SupplierDebtByDebtTerms |
Purpose. The report is designed for analyzing the organization's accounts payable to supplier counterparties, grouped by time intervals of payment delays. It is used by accountants and financial managers to monitor the repayment deadlines, plan the payment calendar, and assess critical overdue payables. It can be generated for any date and segments the debt by intervals (for example: current debt, 1–30, 31–60, 61–90, over 90 days). It is integrated with the manager's monitor for operational control of KPIs.
Where to find in 1C: section “For the Manager” → “Supplier Debt by Debt Terms” (or by following the navigation link above).
2. Attributes and Table Parts
2.1 Header Attributes (report parameters)
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| Period | Date (dateTime) | Mandatory (ShowError) | The date for which the debt and delays are calculated; a key parameter for determining the age of the debt |
| OrganizationListRepresentation | String | Not checked (DontCheck) | Text representation of the list of organizations for which the report is generated; displayed in the header |
| AdditionalFieldsPlacement | Number (decimal) | Not checked | Controls the placement of additional analytical fields in the table part (vertically / horizontally) |
| DetailingMode | Boolean | Not checked | Detailing flag: True — hide details, show only totals; False — full detailing by documents and counterparties |
2.2 Table Part “Intervals”
Stores user-defined time intervals for classifying debt by payment delay terms.
| Name | Type | Purpose |
|---|---|---|
| Value | Number (decimal) | Interval boundary in days (end of the period): for example, 30 for the range of 1–30 days |
| Representation | String | Text of the report column (for example, “From 1 to 30 days”, “Over 90 days”) |
2.3 Table Part “Grouping”
Configuration of report groupings (by counterparties, contracts, organizations, etc.).
| Name | Type | Purpose |
|---|---|---|
| Usage | Boolean | Flag for including grouping |
| Field | String | Internal name of the field for grouping (“Counterparty”, “Contract”) |
| Representation | String | User representation of the field for UI |
| GroupingType | EnumRef.GroupingDetailingTypes | Detailing type: grouping header, detailed records, only totals |
2.4 Table Part “AdditionalFields”
Management of additional analytical fields (departments, projects, product groups, etc.).
| Name | Type | Purpose |
|---|---|---|
| Usage | Boolean | Flag for including the additional field in the result |
| Field | String | Internal name of the field (for example, “Department”) |
| Representation | String | Text of the report column |
3. Forms
For reports in DCS, the own set of forms is minimal; the main interaction occurs through the auto-generated composition form. The object includes:
| Form | Purpose |
|---|---|
Main Data Composition Scheme (MainDataCompositionScheme) |
Defines data sets (queries to accounting data), relationships, fields, resources, parameters, and output settings. It is responsible for forming the tabular document of the report |
| Settings Form (report variant) | User customization of selection, groupings, intervals, and additional fields on top of the predefined variant. Uses attributes and table parts described in section 2 |
| Auto Report Form | Standard form “1C: Libraries of Standard Subsystems” (BSP) for launching, selecting a variant, entering parameters (Period, list of organizations), generating and printing the result |
Separate forms of the object (
ReportForm,SettingsForm) are overridden only in non-standard UI; in the standard delivery, the BSP mechanism “Report Variants” is used.
4. Key Module Procedures
Evidence with BSL code of modules is not attached, so below are typical report handlers in DCS within the architecture of BSP “Accounting for Kazakhstan” (object module and report manager module):
| Procedure / Handler | Module | What it does |
|---|---|---|
| OnResultComposition(ReportResult, DecodingData, StandardProcessing) | Object Module | Interception of composition: substitution of calculated overdue intervals, calculation of debt age relative to Period, fine-tuning the layout before output |
ReportSettings(...) (DefineFormSettings) |
Manager Module | Registers the report in the “Report Variants” subsystem, describes predefined variants, placement in the “For the Manager” panel, availability of quick settings |
| BeforeLoadingVariantFromSettings / OnLoadingUserSettingsOnServer | Object Module | Restores user-defined intervals and groupings when opening a saved variant |
| OnDefiningUsedTables | Object Module | Indicates the used tables for controlling the relevance of the totals of registers |
The application logic for classification by intervals is implemented mainly in the DCS itself (calculated fields, parameters, data sets), rather than in BSL. “Requires verification”: the exact composition of overridden handlers of the object module is version-dependent and is specified for the specific build 3.0.74.2.
5. Data Sources and Movements
The report does not perform posting and does not generate movements in registers — it is a read-only object. It retrieves data from already formed postings and registers of accounts payable with suppliers.
The main source is accounting data on the accounts payable to suppliers and related registers of mutual settlements:
| Account (standard chart of accounts of the RK) | Role in the report |
|---|---|
| 3310 — Short-term accounts payable to suppliers and contractors | Main analyzed account: credit balance = amount of debt to the supplier |
| 1210 — Short-term accounts receivable from customers | Related account of mutual settlements (for advances/set-offs included in the analysis) |
| 1030 — Cash on current bank accounts | Reflects the repayment of obligations (debt write-off) |
| 1330 — Goods | Formation of debt upon receipt of goods and materials |
| 3130 — VAT payable | VAT included in receipts (rate 16% for the RK in 2026) |
The logic of calculating the age of the debt: for each unpaid obligation (settlement document), the difference between Period and the date of occurrence/due date according to the contract is calculated, then the sum is assigned to the corresponding interval from the table part “Intervals”.
Example: receipt of goods for 1,160,000 ₸ (including VAT 16% = 160,000 ₸) is reflected Dr 1330 / Cr 3310 for 1,000,000 ₸ and Dr 1420 (VAT to be refunded) / Cr 3310 for 160,000 ₸. The unpaid balance on Cr 3310 enters the report and is classified by the debt term.
Electronic documents of receipt (electronic invoice (ESF) through IS ESF, SNT) affect the report indirectly — through the postings they generate for 3310/3130; the report itself does not interact with IS ESF.
6. Related Objects and Input Based On
The report is the end consumer of data, so “input based on” is not applicable for it. Related objects:
- Source documents of debt: “Receipt of goods and services”, “Return to supplier”, “Write-off from current account”, “Cash expenditure order”, “Debt adjustment”, “Set-off of advances”.
- Analytical reference books:
Counterparties,Contracts,Organizations,Departments— used in groupings and additional fields. - Subsystem “Report Variants” (BSP) — storage and distribution of settings.
- Manager's Monitor / Target Indicators — the report is integrated as a source of KPIs for accounts payable.
- Regulated accounting — data is reconciled with the turnover of account 3310 (reconciliation act, balance sheet for the account).
7. Extension Points
- Configuration Extension: adding custom report variants, new groupings or fields by overriding the DCS scheme and the
ReportSettingsprocedure of the manager module. - User variants and intervals: editing table parts “Intervals”, “Grouping”, “AdditionalFields” without changing the configuration — standard adaptation mechanism.
- Additional reports (external): connecting an external variant through the subsystem “Additional reports and processing” of BSP.
- Handler
OnResultComposition: implementing calculated columns (for example, share of overdue debt, criticality indicator) without modifying DCS. - Access Rights (RLS): limiting visibility by organizations/counterparties through profiles and access groups of BSP.
“Requires verification”: the set of predefined report variants and their exact placement in the command interface may differ within the sub-releases 3.0.74.x.