Report. Report on Counterparty Data — Technical Description (Accounting for Kazakhstan 3.0.74.2)

1. Identification

Purpose. The report generates a detailed summary of data for one counterparty, several counterparties, or an entire group (with hierarchy disclosure). The report displays: main details of the counterparty, a list of contacts, contact information (phones, e-mail, addresses), additional details and information. It is used by accountants, client managers, and executives when preparing contracts, verifying and updating counterparty data, and generating analytical materials.

This is an informational reference report based on the reference directory. It does not perform calculations on accounting registers (settlements, turnovers, debts) and does not refer to accounting data — only to the counterparty card and related objects (contacts, contact information, additional details).

Where to find in 1C: section “Sales” → “Report by Counterparty Data”, as well as from the “Counterparties” directory via context menu commands (generate report for the selected item/group).

2. Attributes and Structure

2.1 Attributes (formation parameters)

2.2 Table Parts

Table parts are absent. The report is managed solely by the header attributes and the settings list SettingsList; the result is displayed in the area of the tabular document on the form.

3. Forms

No separate data layout settings form is allocated — the composition management is done through SettingsList directly on ReportForm.

4. Key Procedures of Modules

The original BSL code in evidence is not attached, so below is a typical set of handlers for a report of this type (form module ReportForm and report object module). Specific names/signatures should be clarified according to the metadata of the version.

Report form module:

• OnCreateOnServer(Refusal, StandardProcessing) — initial initialization: filling ReportDate with the current date, forming SettingsList from available sections, setting Counterparty from the opening parameter (when called from the counterparty card/list).
• OnOpen(Refusal) — automatic report generation if parameters are passed during opening.
• Generate(Command) → GenerateOnServer() — gathering parameters, traversing selected sections, and outputting counterparty data into the tabular document (result area).
• ShowAdditionalContactInfoOnChange(Element) — reforming/redefining the visibility of the block of contact information of contacts.
• Print(Command) — outputting the generated tabular document for printing.
• SendByEmail(Command) — packaging the result (tabular document / attachment) and calling the mail sending subsystem.

Report object module (when using the SDI / custom layout assembly):

• procedure for composing/assembling the result, combining the counterparty's attributes, collection of contacts, sets of contact information, and additional details; when selecting a group — recursive traversal of subordinate elements of the hierarchy.

5. Posting and Movements

The object is a report, not a document: it is not posted and does not generate movements in accumulation registers, information, or accounting. It has no postings or register records.

For completeness — information about the reference specifics of accounting in the RK, to which the counterparty card belongs (reference context, not movements of this report):

• Chart of Accounts of the RK (typical accounts of settlements to which the counterparty is linked in accounting documents): 1210 — short-term accounts receivable from buyers, 3310 — short-term accounts payable to suppliers, 1030 — money in current bank accounts, 1330 — goods, 3130 — VAT payable, 6010 — revenue from sales, 7010 — cost of sales.
• Electronic documents of the RK related to the counterparty in accounting operations: ESF (ESF IS) and SNT.
• VAT Rate (2026): 16 %.

These values are used by accounting documents (sales, receipts, payments), not by this report; they are provided here as context for the “Counterparties” reference.

6. Related Objects and Input Based On

• Directory Counterparties — the main source of data; called from its list forms and item via command.
• Directory Contacts (subordinate to the counterparty) — source of the block of contacts.
• Information Register ContactInformation — phones, e-mail, addresses of the counterparty and its contacts.
• Additional attributes and details (property subsystem) — displayed in the corresponding section.
• Mail sending subsystem — used by the “Send by email” command.

Input based on is not provided for reports (the “Input based on” mechanism applies to documents). Interaction goes in the reverse direction: the report is opened based on the selected counterparty/group.

7. Extension Points

• Configuration extension: adding intercepting handlers to form procedures (OnCreateOnServer, GenerateOnServer) to supplement the composition of sections or filter the displayed data.
• SettingsList: standard point for configuring the composition of sections — the list of displayed blocks can be expanded without modifying the layout.
• Additional attributes/details: new properties of the counterparty automatically enter the corresponding section without code modification.
• Additional reports (external): if different logic is needed, an external report can be connected through the “Additional reports and processing” subsystem, without changing the standard object (safe during updates).
• Output format: the tabular document is available for saving/printing/sending — a redefinable point for integration with external delivery channels.