1. Identification
| Parameter | Value |
|---|---|
| Object Type | Report |
| Name | AccountsPayable |
| Full Name | Report.AccountsPayable |
| Alias | “Accounts Payable” |
| Configuration | Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) |
| Implementation Type | Report on SCD (data composition system) |
Purpose. The report is intended for analyzing the organization's accounts payable to suppliers on a specified date or over a period. It is one of the key analytical tools for accountants and managers: it allows for monitoring the status of settlements, identifying overdue debts, and planning payments. The report is generated based on the balances and transactions of the accounts payable account 3310 “Short-term accounts payable to suppliers and contractors” with details by counterparties, contracts, and accounting accounts. It is used daily for operational control and monthly for management reporting; integrated with the manager's monitor to display summary information about debts in real-time.
Where to find in 1C:
- Section “For the Manager” → “Accounts Payable”.
- Direct navigation link:
e1cib/list/Report.AccountsPayable.
2. Attributes and Table Parts
2.1 Header Attributes (Configuration Parameters)
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| StartPeriod | xs:dateTime |
DontCheck | The start date of the accounts payable analysis period. Determines from which date to consider balances and transactions on the accounts payable. |
| EndPeriod | xs:dateTime |
DontCheck | The end date of the analysis period. Determines until which date to generate the report. Together with StartPeriod sets the time interval for analysis. |
| OrganizationListRepresentation | xs:string |
DontCheck | Text representation of the selected organizations for display in the report header. Automatically generated when organizations are selected in the filter. |
| AdditionalFieldsPlacement | xs:decimal |
DontCheck | Controls the placement of additional fields (in rows or columns). Affects the visual representation of the analytics. |
| DetailingMode | xs:boolean |
DontCheck | Flag for detailing mode. When enabled, the logic of formation changes — the report is built for detailing a specific amount obtained from another report or document. |
2.2 Table Parts
Grouping
Defines the hierarchy of data grouping in the report (by counterparties, contracts, accounts, etc.).
| Name | Type | Purpose |
|---|---|---|
| Usage | xs:boolean |
Flag for the activity of the grouping row. If unchecked, the measure does not participate in the report formation. |
| Field | xs:string |
Identifier of the field for grouping (e.g., “Counterparty”, “Contract”, “Account”). Used by the data composer. |
| Representation | xs:string |
User-defined name of the grouping field for the interface and report headers. |
| GroupingType | cfg:EnumRef.GroupingDetailingTypes |
Type of grouping: only grouping, only detailed records, or grouping with detailed records. |
AdditionalFields
A list of additional indicators and analytical dimensions displayed alongside the main amounts of accounts payable.
| Name | Type | Purpose |
|---|---|---|
| Usage | xs:boolean |
Flag for including the field in the report. Allows flexible configuration of the column composition. |
| Field | xs:string |
Identifier of the additional field (e.g., “DebtTerm”, “ContractCurrency”, “Organization”). |
| Representation | xs:string |
Displayed name of the field in the report columns. Can be edited by the user. |
3. Forms
The report uses the standard SCD mechanism, so the set of forms is typical for reports of this configuration:
| Form | Purpose |
|---|---|
| ReportForm (main) | Main launch form: settings panel (period, organizations, selection by counterparties/contracts), “Generate” button, table document field with results. Provides interactive work and cell detailing. |
| Settings / Variant Form | Management of layout variants, selections, groupings, and conditional formatting (standard SCD forms). Allows saving user report settings. |
If only an auto-generated SCD form is defined for the report, a separate object form in the metadata may be absent — the platform builds the report form dynamically based on the data composition scheme.
4. Key Module Procedures
The attached evidence does not provide the program code of the modules (BSL), so below are typical handlers for the report on SCD in this type of configuration:
- Object Module →
OnResultComposition(DocResult, DataDetailing, StandardProcessing)— interception point for output: programmatic adjustment of the layout, calculation of service fields, management of standard composition processing. - Object Module →
SettingsForInternetSupportTechnology/ initialization of the scheme — setting the initial period, composition of groupings and selections when creating the report. - Report Form →
OnCreateOnServer(Error, StandardProcessing)— filling the default period, setting selection by organization, restoring saved user settings. - Report Form →
BeforeLoadingVariantOnServer/OnLoadingVariantOnServer— synchronization of form attributes (StartPeriod,EndPeriod,OrganizationListRepresentation) with composer settings. - Report Form → detailing handler — when
DetailingMode = Truegenerates detailing for the selected amount (transition to transactions for a specific counterparty/contract).
Requires verification: the presence and exact signatures of user procedures in the report module are version-specific and clarified for the specific build 3.0.74.2.
5. Data Sources, Registers, and Accounts
The report is analytical — it does not generate its own movements and entries. Data is read through SCD from the accounting register for accounts payable to suppliers.
Main source:
- Accounting register “Cost Accounting” (virtual tables
Balances,TransactionsDrCr,BalancesAndTransactions). - Account for accounts payable to suppliers — 3310 “Short-term accounts payable to suppliers and contractors” (if necessary — related accounts of group 33xx, advances issued, etc.).
Analytics (subaccount) of account 3310: Counterparties, Contracts, Settlement Documents — these dimensions are used by the report for grouping.
What the report shows:
- Credit balance of account 3310 — the amount of unpaid debt to the supplier.
- Transactions for the period — occurrence (Cr 3310) and repayment (Dr 3310) of the debt.
- Debt term and overdue (through the additional field “DebtTerm”).
Typical entries forming the analyzed debt (created by documents of receipt and payment, not by the report), considering the VAT rate of the RK 16%:
| Operation | Dr | Cr | Comment |
|---|---|---|---|
| Receipt of goods from the supplier | 1330 | 3310 | Cost of goods excluding VAT |
| VAT on receipt (by ESF) | 1420 | 3310 | VAT 16% on the delivery amount |
| Payment to the supplier from the current account | 3310 | 1030 | Repayment of debt |
Example: delivery of goods for 1,000,000 ₸ excluding VAT → VAT 16% = 160,000 ₸ → accounts payable on account 3310 will amount to 1,160,000 ₸ and will be reflected in the report until payment is made.
6. Related Objects and Input on Basis
As a report, the object does not participate in input on basis and has no posting mechanism. The connections are logical — with objects that form the analyzed data:
- Source documents of debt: “Receipt of goods and services”, “Receipt of VAT”, advance documents, debt adjustments.
- Repayment documents: “Write-off from current account”, “Cash expenditure order”, “Debt offset”.
- Electronic documents of the RK: ESF (IS ESF) and SNT — determine the amount of VAT (16%) in the debt, but are related to the report through primary receipt documents.
- Directories: “Counterparties”, “Contracts”, “Organizations” — dimensions of grouping and selection.
- Accounting register “Cost Accounting” — the only actual data source for the report.
- Manager's monitor — consumer of the report's summary data.
7. Extension Points
- Report Variants (SCD): adding custom layout variants with new groupings, selections, and conditional formatting without changing the configuration.
- Additional Reports (external): connecting an external report through the subsystem of additional reports and processing (BSP).
- Configuration Extension: borrowing the composition scheme, forms, and report module; overriding
OnResultCompositionfor programmatic adjustment of output. - Additional SCD Fields: expanding the composition of columns (debt term, contract currency, manager) through settings without modifications.
- Functional options and role rights: restricting access and visibility of the report through role tools and RLS.
Requires verification: the list of predefined layout variants and the composition of quick selections in the specific build 3.0.74.2.
