Version: 26.9.1.0 (Manager Cloud)
Summary
When a custom theme is applied to a Customer Statements (Unpaid Invoices) statement, the theme receives the Customer Statements (Transactions) payload instead of the unpaid-invoice payload. The document then lists paid invoices and payment receipts, which defeats the purpose of the report. With the custom theme toggled off, the same statement renders correctly.
Steps to reproduce
- Have a customer with one invoice partly or fully paid and one still open.
- Reports → Customer Statements (Unpaid Invoices) → View that customer.
- View with the custom theme off — correct.
- Toggle the custom theme on — wrong.
Expected (custom theme off)
- Header: a single
Datefield - Columns:
Date | Invoice | Description | Invoice total | Overdue | Balance due - Only invoices with an outstanding balance
Actual (custom theme on)
- Header:
From/To(a period, not an as-at date) - Columns:
Date | Description | Debit | Credit | Balance - Rows include paid invoices and payment receipt lines
- Totals:
Total debits/Total credits/Closing balance
That is exactly the Transactions statement output.
Example
A customer with invoice #3629 (6,300, receipt #4502 of 3,150 applied) and invoice #3675 (6,300, unpaid):
- Theme off → invoice #3629 with Balance due 3,150, plus #3675.
- Theme on → three rows, including “Invoice 3629 — Payment Receipt 4502 — Payment Received against invoice #3629”, period 03/05/2026–09/09/2026, Closing balance 9,450 Dr.
Note on the theme
The theme is generic — it only iterates table.columns, table.rows and table.totals, with no report-specific logic. Per the theme schema there is a single body table, so the theme cannot be selecting the wrong data set; it is being handed the wrong one. This reproduces with any custom theme applied to this report.
Impact
Unpaid-invoice statements cannot be sent to customers while a custom theme is in use, since they disclose settled invoices and payment history, and show a period-based closing balance rather than the amount actually due.