1. Identification
| Property | Value |
|---|---|
| Object Type | Report |
| Name | OverduePayablesToSuppliers |
| Full Name | Report.OverduePayablesToSuppliers |
| Synonym | Overdue payables to suppliers |
| Configuration | Accounting for Kazakhstan, edition 3.0, version 3.0.74.2 |
| Implementation Basis | Data composition system (DCS) |
| Posting / Movements | None — the report does not record data, it only reads |
| Navigation Link | e1cib/list/Report.OverduePayablesToSuppliers |
Purpose. The report is designed for analyzing the overdue accounts payable of the organization to suppliers by counterparties, contracts, accounting accounts, and overdue periods. It is used by accountants, financial managers, and executives to monitor the timeliness of settlements, assess the volume of liabilities, and plan the payment calendar. It can be generated for any date and allows for flexible data regrouping (by organizations, counterparties, contracts, accounts). The typical frequency of use is weekly or monthly when managing accounts payable.
Where to find in 1C: section "For the Manager" → "Overdue payables to suppliers". Direct access is via the navigation link e1cib/list/Report.OverduePayablesToSuppliers.
Accounts payable to suppliers are recorded in account 3310 "Short-term accounts payable to suppliers and contractors" of the standard chart of accounts of the RK. The balances of this account (and related sub-accounts) are the subject of the report's analysis.
2. Attributes and Settings
Since the object is a report in DCS, the "header" and "table parts" here are the structure of user settings for composition (parameters and output structure), not the attributes of the document.
2.1 Settings Attributes (Composition Parameters)
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| Period | Date (dateTime) | Not checked | The date for which the report is generated. Defines the boundary of analysis — which liabilities are considered overdue at this moment. |
| ListOfOrganizationsRepresentation | String | Not checked | String representation of selected organizations for the report header and filtering. Automatically generated when organizations are selected. |
| PlacementOfAdditionalFields | Number (decimal) | Not checked | Enum-like value controlling the placement of additional columns in the layout (in separate columns / in groupings). |
| DetailingMode | Boolean | Not checked | Flag for detailed breakdown (drill-down to primary documents). Provides navigation to the sources of debt. |
2.2 Table Parts (Output Structure Elements)
Grouping
Purpose: management of levels of detail — the order of data grouping (by counterparties, contracts, accounting accounts, etc.).
| Name | Type | Purpose |
|---|---|---|
| Usage | Boolean | Activity of grouping. If unchecked — grouping is not applied. |
| Field | String | System name of the DCS field for grouping (Counterparty, CounterpartyContract, AccountingAccount). |
| Representation | String | User-defined name of the field in settings and headers. |
| GroupingType | EnumRef.GroupingDetailType |
Type of detail (detailed records / only totals / totals and detailed records). Controls the output of intermediate totals. |
AdditionalFields
Purpose: list of additional columns besides the main indicators of debt (attributes of the counterparty, contract, analytics).
| Name | Type | Purpose |
|---|---|---|
| Usage | Boolean | Inclusion of the additional field in the layout. |
| Field | String | System name of the field from the composition scheme. |
| Representation | String | Name of the column in the table header. |
3. Forms
For the standard report in DCS, a set of forms is provided:
| Form | Purpose |
|---|---|
| Report Form (main) | A unified form for setting parameters (Period, Organizations, groupings, additional fields), launching the generation, and outputting the result in the table document field. Contains a settings panel and a "Generate" button. |
| Settings Form (design option) | Extended configuration of structure, selections, and conditional formatting through the standard DCS mechanism (when using the "Settings in a separate window" option). |
| Report Variant Form | Management of saved variants (user-defined composition settings). |
In the standard delivery, the report uses the common form mechanism of DCS (extension of the managed report form of BCP). Separate custom forms are generally not overridden; all construction logic is performed by the data composition scheme.
4. Key Module Procedures
No separate special BSL code is attached in evidence — the report is built by the standard DCS engine. Below are the typical handlers characteristic of reports of this type in BK 3.0 (based on BCP "Report Variants"):
| Procedure / Handler | Module | What it does |
|---|---|---|
OnResultComposition |
Report object module | Intercepts the composition: substitutes the parameter Period, limits by organizations, calculates calculated fields (days overdue, payment term ranges). |
ReportFormSettings / OnCreateOnServer |
Form module | Initialization of the settings panel, restoration of the user variant, setting default values (current date in Period). |
OnLoadVariantOnServer |
Form module | Application of the selected saved composition variant. |
BreakdownProcessing / Breakdown |
Form module | Processing DetailingMode — transition from the report line to primary documents (invoices, receipts, payments). |
| Layout Procedures-Functions of DCS | Composition scheme | Main query to the accounting register, calculation of the balance of debt and overdue payment terms of the contract. |
Requires verification for the specific version 3.0.74.2: the presence of a custom object module with
OnResultComposition— in terms of releases, the calculation of overdue has been entirely moved to calculated fields of DCS without programming code.
5. Data Sources (Registers and Accounts)
The report does not generate movements and postings — this is its fundamental difference from documents. It performs a query to the accounting data as of the date Period.
Main data source:
- Accounting register "Economic Calculation" — balances on account 3310 "Short-term accounts payable to suppliers and contractors" (credit balance by sub-accounts Counterparties and Contracts).
Accounts of the RK involved in analysis and breakdown (standard chart of accounts):
| Account | Name | Role in the report |
|---|---|---|
| 3310 | Short-term payables to suppliers and contractors | Analyzed liability (credit balance) |
| 1030 | Cash on current bank accounts | Source of repayment — when breaking down to payments |
| 1330 | Goods | Correspondence upon receipt of goods and materials |
| 3130 | VAT payable | Related VAT amounts in settlements |
Logic of determining overdue. For each liability, the report compares the date of the debt's occurrence and the payment term specified in the counterparty's contract with the date Period. A liability is considered overdue if the payment term has passed and the credit balance on account 3310 is not closed. Amounts are grouped by overdue ranges (for example, up to 30 / 31–60 / 61–90 / over 90 days) depending on the settings of the variant.
Example of reference context RK-2026 (for reconciling numerical data of related operations): VAT rate — 16%, ESF amounts are generated in the ESF system with accompanying invoice; calculated indicators for taxes (individual income tax, social tax, social tax) are not directly related to this report but are relevant when analyzing related settlement obligations.
6. Related Objects and Input Based On
The report is a "reading" object, so it does not have an "input based on" mechanism. Relationships are expressed through data sources and breakdowns:
| Related Object | Nature of the Relationship |
|---|---|
Directory.Counterparties |
Sub-account of debt, grouping field |
Directory.CounterpartyContracts |
Payment term (basis for calculating overdue), grouping field |
Directory.Organizations |
Selection and representation of the list of organizations |
Document.GoodsAndServicesReceipt (and analogs) |
Source of debt occurrence; purpose of breakdown |
Document.OutgoingPaymentOrder / BankAccountWriteOff |
Repayment of debt; purpose of breakdown |
| Accounting register "Economic Calculation" | Main source of balances on 3310 |
Available from the report (through breakdown): opening the card of the counterparty/contract, opening the primary document, transitioning to the "Turnover and Balance Statement for account 3310".
7. Extension Points
- Report Variants (DCS). Adding custom groupings, selections, conditional formatting, and additional fields without changing the configuration — through user-defined/predefined variants.
- Data Composition Scheme. Extending the query (additional fields of the counterparty, manager, analytics), changing overdue ranges, adding calculated fields.
- Configuration Extension. Overriding
OnResultCompositionand form handlers for non-standard overdue logic or additional filtering. - Additional Fields / Attributes. Through
PlacementOfAdditionalFields— managing the composition and arrangement of columns. - Integration with the payment calendar. Using the report result as a source for payment planning (external processing/extension).
- Role-based access settings. Limiting visibility by organizations through RLS and roles — relevant for multi-company accounting.