--- title: "Report \"Analysis of Unpaid Invoices to Customers\" - Technical Description" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-07 canonical: https://buhgpt.kz/suraqtar/otchet-analizneoplachennyhschetovpokupatelyam-tehnichesko-en source: BuhGPT --- # Report "Analysis of Unpaid Invoices to Customers" - Technical Description > **TL;DR:** 1. Identification Parameter Value Full name Report.UnpaidInvoicesAnalysis ( Reports.UnpaidInvoicesAnalysis ) Metadata object type Report Name UnpaidInvoicesAnalysis Synonym — (not specified in the configuration; the command "Invoices Unpaid by Customers" is used in the interfa --- 1. Identification Parameter Value Full name Report.UnpaidInvoicesAnalysis (Reports.UnpaidInvoicesAnalysis) Metadata object type Report Name UnpaidInvoicesAnalysis Synonym — (not specified in the configuration; the command "Invoices Unpaid by Customers" is used in the interface) Configuration Accounting for Kazakhstan, edition 3.0, version 3.0.74.2 Subsystem Standard accounting reports; section "Sales" Navigation link e1cib/list/Report.UnpaidInvoicesAnalysis Purpose. The report is intended for analyzing accounts receivable from customers for issued but unpaid invoices. It is used by accountants and managers to monitor settlements with counterparties, identify overdue debts, and plan cash inflows. The data is built based on the documents "Invoice to Customer": payment statuses and amounts are analyzed by counterparties, contracts, and periods. Frequency of use — regular (weekly/monthly). Where to find in 1C: section "Sales" → "Invoices Unpaid by Customers". Direct access — via the navigation link e1cib/list/Report.UnpaidInvoicesAnalysis. 2. Attributes of header and table parts 2.1 Header attributes (report settings) Name Type Mandatory Purpose StartPeriod Date (xs:dateTime) Not checked (DontCheck) Start date of the invoice analysis period; can be empty for analysis "from the beginning of time" EndPeriod Date (xs:dateTime) Mandatory (ShowError) End date of the analysis period; mandatory to limit the selection and correctly generate the report OrganizationListRepresentation String (xs:string) Not checked Text representation of selected organizations for display in the report header AdditionalFieldsPlacement Number (xs:decimal) Not checked Determines the placement method of additional fields in the layout (by columns / by rows) DetailingMode Boolean (xs:boolean) Not checked Flag for detailing mode; when True disables automatic application of default groupings (used when detailing cells) 2.2 Table parts Grouping Purpose: stores user settings for grouping report data (by counterparty, contract, period, etc.). Name Type Purpose Usage Boolean Flag for grouping activity; True — grouping is applied Field String Internal name of the field for grouping (e.g., "Counterparty", "Contract") Representation String User-defined name of the grouping field for display GroupingType EnumRef.StandardReportDetailingType Type of detailing: grouping, detailed records, etc. AdditionalFields Purpose: contains additional columns that the user has added to the report beyond the mandatory ones. Name Type Purpose Usage Boolean Field visibility flag; True — field is displayed in the report Field String Internal name of the additional field Representation String Name of the field for the column header 3. Forms Form Role Description ReportForm Main (only) The main and only form of the report, ~340 controls: input fields for the period (StartPeriod/EndPeriod), organization selection, tables for grouping and filtering settings, command panel, and a table document field for outputting the result. Through it, the user sets the selection and initiates the generation. There are no separate settings forms, variants, or detailing in the object — cell detailing is performed in the same form using the attribute DetailingMode. 4. Key procedures of modules No separate BSL evidence for modules is attached. For reports of this type (standard accounting report with manual generation of the table document), the typical composition of handlers is as follows. Form module (ReportForm): - OnCreateOnServer — initialization: setting the default period, restoring saved grouping and additional field settings, configuring element visibility. - Generate (command) → GenerateOnServer — main handler for report building: collecting parameters from header attributes, applying table parts Grouping and AdditionalFields, executing the query, and outputting to the table document field. - TableDocumentDetailingHandler — handling clicks on cells; when DetailingMode is active, opens detailing for the selected counterparty/contract/invoice. - EndPeriodOnChange — control of mandatory date filling and adjustment of period boundaries. Report object module: - Procedures for initializing the layout scheme and generating results based on parameters (GenerateReport), considering selection by organizations and period. Requires verification: exact names of procedures and the presence of a layout variant against the manual layout may differ in the specific version — check against the configurator 3.0.74.2. 5. Data sources (the report does not generate movements) The report is an object for reading only: it is not processed and does not create records in registers or postings. It reads already accumulated data. Sources according to the typical logic of the RK configuration: - Document "Invoice to Customer" — the basis for the list of issued invoices, their amounts, and payment statuses. - Accounting register "Cost Accounting" — for monitoring payments and the remaining debt on account 1210 "Short-term accounts receivable from customers and clients". - Registers of settlements/payments with customers — matching invoices with cash inflows. Related accounts from the typical chart of accounts of the RK involved in the analysis: Account Purpose 1210 Short-term accounts receivable from customers (main analyzed balance) 1030 Cash in current bank accounts (received payment, closing the invoice) 6010 Revenue from sales (when shipping against the invoice) 3130 VAT payable Example of interpreting numbers (Kazakhstan, 2026): for an invoice of 1,160,000 ₸ including VAT, the base is reflected as 1,000,000 ₸ and VAT at a rate of 16% = 160,000 ₸. In the report, the unpaid invoice generates a debt line on account 1210 for the full amount of 1,160,000 ₸ until payment is received on 1030. 6. Related objects and input based on - Document "Invoice to Customer" — primary data source for the report. - Document "Sale of Goods and Services" — shipment that closes the invoice (postings Dr 1210 Cr 6010, Dr 1210 Cr 3130). - Document "Cash Receipt" / bank statement — payment of the invoice (Dr 1030 Cr 1210). - Electronic documents: ESF (ESF IS) and SNK related to the sale against the invoice. - Input based on the report itself is not performed (reports are not the basis for documents). The report may be included in automatic mailings and the manager's dashboard. 7. Extension points - User settings — the composition of table parts Grouping and AdditionalFields allows standard configuration of slices without changing the code. - Configuration extension — adding form attributes, additional selections (e.g., by manager or overdue period), and columns through borrowing ReportForm. - Detailing handler — overriding TableDocumentDetailingHandler for non-standard detailing. - Programmatic generation — calling from external handlers/subscriptions for mailings with passing StartPeriod, EndPeriod, OrganizationListRepresentation. - Additional fields — the mechanism AdditionalFieldsPlacement allows managing the layout of added columns without editing the layout. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_