Report "AnalysisOfUnpaidSupplierInvoices" — technical description (Accounting for Kazakhstan 3.0.74.2)

1. Identification

Purpose. The report is intended for analyzing the organization's liabilities to supplier counterparties for issued but unpaid invoices (accounts payable). It is used by accountants, financial managers, and executives to control accounts payable, plan payments, and manage cash flows. It is generated on demand — usually at the end of a reporting period (week, month) or during operational analysis of payment discipline. It supports flexible configuration of groupings, filters, and additional fields through the DCS mechanism.

Where to find in 1C: the "Executive" section → "Invoices unpaid to suppliers" (or through the navigation bar using the link above).

The report is a reading object: it does not modify data and does not generate register records. Section 5 is provided for completeness of understanding of which accounting data the report draws information from.

2. Attributes and settings tabular sections

For a DCS-based report, the "header attributes" are, as a rule, the attributes of user settings and composition parameters, while the "tabular sections" are collections of setting elements (groupings, filters, additional fields). Below is data per the evidence.

2.1 Header attributes (parameters/settings)

2.2 Tabular sections (settings collections)

Grouping

Purpose: fields by which data is grouped (counterparties, contracts, organizations).

AdditionalFields

Purpose: additional columns (statuses, payment dates, comments).

In addition to the above, the standard BK report contains service collections of DCS settings (Filter, Conditional appearance, User fields, Sorting) — they are inherited from the common mechanism of standard reports and are not detailed in the evidence.

3. Forms

The object, as a rule, has no custom nonstandard forms — the mechanism for automatically building a DCS report form is used.

4. Key module procedures

The BSL code (path:line) is not provided in the attached evidence, so below are the typical handlers of a DCS report in BK/SSL. Specific lines require verification against the module of this version.

Object module / form module:

• ПриКомпоновкеРезультата(ТабличныйДокумент, ДанныеРасшифровки, СтандартнаяОбработка) — output interception: possible refinement/formatting of the spreadsheet document before output, programmatic generation of the result.
• ПриОпределенииНастроекФормы / ПриСозданииНаСервере — form initialization: setting the default period (for example, the current month via КонецПериода), filling in ПредставлениеСпискаОрганизаций, determining available options.
• УстановитьПараметрыОтбора / ПередЗагрузкойВариантаНаСервере — programmatic application of filters (by organization, counterparty, contract), adjustment of the composition of quick settings.
• The КонецПериода requirement check handler — during generation, filling in of the end date is monitored (corresponds to the ShowError flag of the attribute); with an empty value an error is issued and the report is not built.
• Decryption mode handling — when opened with РежимРасшифровки = Истина, part of the validations is skipped and drill-down settings are applied.

Data composition schema (DCS) — the report's main "algorithm":

• A "Query"-type dataset to the mutual settlements/payment registers (see section 5), with the parameters НачалоПериода, КонецПериода, and the list of organizations.
• Calculated fields: invoice amount, payment amount, balance due (unpaid balance), debt term (if a payment date field is present).
• Resources: debt amounts with totals by groupings.

5. Data sources and relation to accounting (the report generates no records)

The report is not posted and does not create records — it only reads accounting data. According to the standard logic of the configuration, the data is taken from registers and documents of settlements with suppliers:

Source registers (typical for BK 3.0):

• The accumulation register "MutualSettlementsWithCounterparties" / accounting registers — turnovers and balances of debt to suppliers;
• Data of the "SupplierPaymentInvoice" documents, receipts (inventory/services), and payment documents for matching "issued ↔ paid".

RK chart of accounts (typical), to which the analyzed data is related:

Example of an amount by account. A supplier invoice for goods of 1,000,000 ₸ excluding VAT → VAT 16% = 160,000 ₸ → payable 1,160,000 ₸. If payment has not been made, the unpaid balance of 1,160,000 ₸ by counterparty appears in the report (Dr 1330 / Dr 1300-VAT, Cr 3310).

Electronic supply documents (ESF via the ESF IS, SNT) do not directly participate in the report, but they form the primary data on supplies and VAT from which accounts payable is composed.

6. Related objects and entry based on

• The report is a reading object; entry based on it and into it is not performed.
• Related source documents: "SupplierPaymentInvoice", inventory/services receipt documents, payment orders/expense operations on account 1030, mutual settlement documents.
• Related catalogs (dimensions of groupings/filters): "Organizations", "Counterparties", "Contracts", "Currencies" (tenge, ₸).
• Decryption (drill-down): from the report rows, navigation to the recorder documents and to other standard reports is available (account 3310 card, account balance sheet, subconto analysis) — in this case the child report is opened with РежимРасшифровки = Истина.

7. Extension points

• Report options (DCS): adding custom options with ready-made groupings/filters (by debt terms, by responsible managers) without changing the configuration.
• Configuration extension: refining the composition schema (new fields/datasets), adding ПриКомпоновкеРезультата, ПриСозданииНаСервере handlers to the form module via an extension.
• Additional fields (the "AdditionalFields" tabular section): output of statuses, payment dates, comments without editing code.
• External reports / additional reports (SSL): implementation of an alternative version based on the same set of registers, connected via the "Additional reports and processing" subsystem.
• DCS conditional appearance: highlighting overdue debt, emphasizing the largest counterparties.
• Period parameterization: overriding the default values of НачалоПериода/КонецПериода in the form initialization handler.

Requires verification (version-specific): the exact composition of datasets and DCS field names, the presence of a separate SettingsForm, and the specific lines of the module handlers — to be verified against release 3.0.74.2, as they may change between versions.