Revenue backlog
Open Reports → Revenue Backlog in Thermal →
What it's for
Open Reports → Revenue backlog to see contracted revenue that remains to be invoiced, by agreement and project. Backlog is contracted value minus invoiced value, with a minimum of zero for each contract. It is separate from unpaid invoices: paying an invoice does not change backlog.
The report includes activated agreements, including expired agreements with unbilled value, and projects with a schedule of values. Canceled, deleted and pending-signature agreements are excluded. Canceled and deleted projects are excluded.
Tabs
The report has one view, with one row per agreement or project.
Panels and controls
The summary shows contracted, invoiced and backlog totals for priced contracts. The table shows the contract, payer or bill-to customer, site customer, contracted value, invoiced value, backlog and aging columns. Select a contract or payer to open its record.
Agreement values use the current term's installment total when available. Without installments, the report uses a recorded prorated renewal amount or the annual price multiplied by the term length. Previous and reverted renewal schedules are excluded. An agreement without a price or schedule remains Unpriced and is excluded from summary totals.
Project values are the sum of their schedule-of-values lines. Sent, partially paid and paid invoices reduce backlog by their value before tax. Draft, prebill, void and deleted invoices do not reduce it. A shared installment invoice contributes only each agreement's scheduled share. A project invoice linked through both a milestone and a progress application is counted once. Tax, outstanding balances and payments do not change the contracted revenue calculation.
Agreement backlog belongs to the agreement payer. Project backlog belongs to the project's customer, which may be a different bill-to customer from the site customer. The table keeps both identities visible.
Aging uses agreement installment due dates and, for project lines linked to milestones, the phase's planned end date. Overdue, 0–30 days, 31–60 days, 61–90 days and 91+ days are separate buckets. Undated or unallocated value appears under Unscheduled. These columns add up to backlog; a planned phase end is a forecast, not a promised invoice date.
Choose a branch and select Filter to narrow the report. Staff restricted to one branch remain within that branch. Projects without a site appear as company-wide projects. Related payers and invoices can belong to another branch without changing the contract's branch scope.
Select Export CSV to download the same rows and totals. Exported money columns are labeled in cents. The report's as-of date follows your company's time zone.
What it accepts
This is a read-only report. It accepts the branch selection available to you and does not create, send or change invoices.
How to configure it
There is no separate report setup. Keep agreement prices, installment schedules, project schedules of values and phase planned end dates current on their records. Leave undated amounts unscheduled until a billing date can be planned.
Who can see it
Staff with Reports access can open the report and export its results. Custom role and branch access rules still apply.
See Roles & permissions for the role matrix.