⚠️ Important note on the object type
The object is declared as Document.CustomersReceivables; however, its composition and purpose correspond to a report:
- the PeriodStart, PeriodEnd, AdditionalFieldsPlacement, and DrilldownMode attributes are used as report configuration parameters;
- the Grouping and AdditionalFields tabular sections form part of the standard report settings structure;
- the only form is ReportForm, with a panel for groupings, filters, sorting, and conditional appearance;
- the object's purpose is to analyze counterparties' receivables owed to the company as of a specified date.
The object is described below according to its actual purpose—as a report. The sections on data generation and related objects take this feature into account. In the specific distribution of version 3.0.74.2, the object identifier should be checked against the configuration metadata tree.
1. Identification
| Parameter | Value |
|---|---|
| Full name | Report.CustomersReceivables; declared name — Document.CustomersReceivables |
| Object name | CustomersReceivables |
| Synonym | Customers' receivables |
| Type based on object composition | Report based on the Data Composition System |
| Configuration | “Accounting for Kazakhstan,” edition 3.0, version 3.0.74.2 |
| Settlement currency | Tenge (₸) |
| Purpose | Analysis of customers' and clients' receivables owed to the company as of a specified date, settlement control, and support for debt collection activities |
Where to find it in 1C:
- In the interface: “For Manager” section → “Customers' Receivables.”
- The standard way to launch the report is to open its form. The command display and location depend on the user's permissions and interface settings.
The report is intended to analyze accounting data on settlements with counterparties. The composition of accounts and analytical dimensions is determined by the accounting settings and the selected report variant.
2. Attributes and tabular sections (report settings)
2.1 Parameters (form and settings attributes)
| Name | Type | Completion check | Purpose |
|---|---|---|---|
| PeriodStart | Date | Not checked automatically | Start of the receivables analysis period; used when generating data for the selected interval |
| PeriodEnd | Date | An error is displayed if no value is entered | End of the analysis period and the date for calculating the closing receivables balance |
| OrganizationsListPresentation | String | Not checked automatically | Text representation of the selected companies for the report header |
| AdditionalFieldsPlacement | Number | Not checked automatically | Determines how additional data is placed in the generated report |
| DrilldownMode | Boolean | Not checked automatically | Controls the detail mode and the composition of available report structure elements |
2.2 “Grouping” tabular section
The tabular section controls the hierarchy for grouping report data, for example by counterparty, contract, or company.
| Name | Type | Purpose |
|---|---|---|
| Use | Boolean | Grouping activity flag |
| Field | String | System name of the grouping field, for example “Counterparty” or “Contract” |
| Presentation | String | User-facing field name in the interface |
| GroupingType | Standard report detail type | Controls the level of detail, subtotals, and total rows |
2.3 “AdditionalFields” tabular section
The tabular section controls additional columns, including counterparty and contract attributes.
| Name | Type | Purpose |
|---|---|---|
| Use | Boolean | Flag for including the additional field in the report |
| Field | String | System name of the additional field |
| Presentation | String | User-facing column name |
3. Forms
| Form | Role | Description |
|---|---|---|
| ReportForm | Main form | Contains a settings panel with groupings, filters, additional fields, sorting, and conditional appearance, as well as a result area. The form is used to configure, generate, drill down into, and display the report |
The described object does not contain the separate item, list, and selection forms typical of documents and catalogs. The user works with the report form and its settings.
4. Key module procedures
The exact names, parameters, and locations of procedures are determined by the object's implementation in configuration version 3.0.74.2. When studying the report's program logic, particular attention should be paid to the following areas:
- Result composition handler — prepares composition parameters and settings before displaying the data.
- Form creation and opening handlers — set the initial values for the period, companies, groupings, and additional fields.
- Generate command — initiates data retrieval and displays the result in the tabular area.
- Drilldown processing — enables navigation from a report indicator to its details, counterparty, contract, or settlement document.
- Loading and saving settings — supports user-defined variants of groupings, filters, sorting, and appearance.
The list of procedures should be reviewed directly in the object and form modules: an implementation using the classic Data Composition System differs from one based on the common standard report framework.
5. Data source and generation logic
The report obtains information from accounting data recorded by infobase documents. Generating the report does not modify accounting data.
General generation logic:
- The user specifies the period, company, and other available parameters.
- The system retrieves balances and turnover for settlements with customers over the selected period.
- The data is restricted by the specified filters and report variant settings.
- The result is grouped by the selected analytical dimensions: counterparties, contracts, companies, and settlement documents.
- The report displays the available indicators for opening balance, turnover, and closing balance in the accounting currency.
The composition of indicators depends on the selected report variant. To analyze a specific amount, the accountant reconciles it against the account card, trial balance, and settlement documents for the same period.
Example of calculating an amount including VAT: if the price excluding VAT is 100 000 ₸, VAT at the rate of 16 % is 16 000 ₸, and the total settlement amount with the customer is 116 000 ₸. If this amount is paid in full within the selected period, the closing receivable for the corresponding settlement will be 0 ₸.
6. Related objects
The report's relationships with other objects are implemented through accounting data and the drilldown mechanism:
- Debt origination documents: documents recording the sale of goods, work, services, and other assets and reflecting settlements with the customer.
- Settlement documents: bank and cash documents, offsets, and debt adjustments.
- Analytics: counterparty and contract catalogs, as well as counterparty settlement documents if this level of detail is used in accounting.
- Electronic documents: related Electronic Invoices and Accompanying Consignment Notes are displayed through the links to sales documents provided by the configuration.
- Management control: final receivables data may be used in the configuration's analytical dashboards available to the user.
Drilling down helps identify the data that makes up the amount. The set of available navigation options is determined by the indicator type, user permissions, and analytical settings.
7. Extension points
- Report variants: the user can save sets of groupings, filters, and additional fields as separate variants if permitted by their access rights.
- Additional fields: available attributes of the counterparty, contract, and other analytical dimensions can be included in the report.
- Configuration extension: a developer can add fields, filters, or other processing of composition settings without modifying the main configuration.
- External report: a separate analytical variant can be implemented as a pluggable additional report.
- Conditional appearance: appearance rules make it possible to visually highlight amounts based on user-defined conditions.
The available customization method depends on the report architecture, configuration compatibility mode, access rights, and infobase safe mode settings. Before modifying the extension, the developer should check the fields being used against the current composition schema in version 3.0.74.2.
Questions and answers
Why is the object described as a report even though its name indicates a document?
Its purpose, form, and set of settings correspond to a report. For technical identification in a specific infobase, use the name displayed in the metadata tree of configuration version 3.0.74.2.
As of what date are receivables calculated?
The closing balance is calculated as of the end date of the selected period. To obtain a comparable result in related accounting reports, set the same period, company, and analytical filters.
Why might the report amount differ from the data for an individual counterparty?
A discrepancy occurs when different periods, companies, contracts, currencies, grouping variants, or sets of included settlements are used. Indicators must be compared using identical settings and the same level of detail.
How can I find the documents that make up the receivables?
Drill down from the indicator to the counterparty, contract, and settlement document. The available drilldown depth depends on the analytics used when recording the transactions.