Report "Counterparty Dossier" (Reports.CounterpartyDossier)

1. Identification of the Object

Purpose. The "Counterparty File" is a specialized analytical report for the comprehensive collection of all-round information about a counterparty (supplier, buyer, partner). It consolidates data from several sources: the "Counterparties" directory and its attributes (BIN/IIN, bank accounts, contact information), history of mutual settlements, executed documents, and debt status. The report is aimed at accountants, client managers, executives, and security service employees. Typical scenarios: checking the reliability of a counterparty before signing a contract, analyzing current mutual settlements, preparing a summary file for management.

Important. The report is a read-only object. It does not conduct, does not create documents, and does not generate records in registers. It only reads already existing accounting data and outputs it in a tabular document.

2. Header Attributes and Table Parts

According to the metadata, the object belongs to the type "Report," so it has no own attributes and table parts at the configuration level.

2.1 Header Attributes

The report does not contain its own attributes at the metadata level. All parameters (selected counterparty, analysis period, organization, detail flags) are set by the user on the form and passed to the generation algorithm as attributes/parameters of the form.

2.2 Table Parts

The report does not contain table parts at the metadata level. The result is dynamically formed in a tabular document (TabularDocument) based on layouts and queries to accounting data.

2.3 Generation Parameters (set on the form)

3. Forms

For reports of this configuration, this is the only user form. Printing and saving the result are performed using standard tabular document tools (report panel), a separate settings form for the reporting subsystem is not required, as the report is generated programmatically.

4. Key Module Procedures

Application BSL text in the reference evidence is not attached, so below are typical handlers for the report, generated programmatically in a tabular document. Specific procedure names should be clarified according to the form module of this version.

Form Module (Form):

• OnCreateOnServer(Reject, StandardProcessing) — form initialization: setting default period, organization, restoring saved settings, preparing counterparty selection fields.
• Generate(Command) — client command, calls the server procedure for generation and outputs the result in the tabular document field.
• GenerateOnServer() — main server algorithm: checks the filling of the counterparty, executes queries to accounting data, fills layouts, outputs areas to the tabular document.
• CounterpartyOnChange(Element) — handling counterparty selection (substituting related attributes, clearing previous results).

Report Object Module:

• Procedures/functions for preparing query texts and processing selections (for example, obtaining counterparty attributes, turnover and balance of mutual settlements, list of documents). In reports on the reporting subsystem, this role is played by the layout scheme; in programmatically generated reports — auxiliary functions for forming areas.

Requires verification in the specific assembly 3.0.74.2: exact procedure names and the presence of the object module (implementation may be fully in the form module).

5. Data Sources (Registers and Accounts)

Since the report is not conducted, instead of "movements," reading sources are considered. The file collects data from typical registers and accounts of the chart of accounts of the RK:

Attributes and Links:

• Directory "Counterparties" and subordinate data: BIN/IIN, "Bank Accounts," "Contact Information," "Counterparty Contracts."

Mutual Settlements (balance and turnover):

• Accounting register "Economic Calculation" (typical chart of accounts of the RK):
  • 1210 "Short-term receivables from buyers" — what the counterparty owes us as a buyer;
  • 3310 "Short-term payables to suppliers" — what we owe the counterparty as a supplier.
• Registers of mutual settlements and specialized registers of settlements with counterparties (by contracts and settlement documents).

Related Analysis Blocks (when building an extended file):

• Income/expenses by counterparty: 6010 "Income from sales of goods and services," 7010 "Cost of goods sold and services rendered."
• Cash movements on settlements: 1030 "Cash on current bank accounts."
• Commodity operations: 1330 "Goods."
• Tax liabilities on operations with the counterparty: 3130 "VAT payable" (VAT rate in the RK from 2026 — 16%).
• Electronic documents related to the counterparty: ESF (ESF IS) and SNT — used when analyzing documentary support for supplies.

The report aggregates this data as of the date/for the period and outputs it in summary; it does not create any postings or records in registers.

6. Related Objects and Input Based On

The report does not participate in "input based on" (this is a document mechanism). The links are of a data source and call point nature:

• Directory "Counterparties" — the main object of analysis; from its list/item forms, the "File" command is called.
• Directory "Counterparty Contracts" — detailing mutual settlements by contracts.
• Settlement Documents (sales, receipts, payment documents, advance reports) — source of the operation history lines.
• Accounting Register "Economic Calculation" and registers of mutual settlements — source of balance and turnover.
• Electronic Documents ESF/SNT — when analyzing document flow with the counterparty.

7. Extension Points

For modifications without removing from support, it is recommended to use configuration extensions:

• Report Form Extension — adding form attributes (new section flags, additional filters), new commands and handlers; overriding GenerateOnServer through wrapping procedures of the extension.
• Adding Layout Areas — including own blocks in the file (for example, indicators of the counterparty's tax burden, limits by contracts).
• Borrowing Module Procedures (&Instead / &Before / &After) — modifying the algorithm for generating queries and output.
• Additional Handlers — if the configuration has the "Additional Reports and Processes" subsystem, a report analog can be connected as external without changing the typical one.

Requires verification: the list of export procedures available for borrowing and the presence of a programming interface for generation depend on the specific assembly 3.0.74.2.