Overhead allocation
Open Reports → Overhead Allocation in Thermal →
What it's for
Overhead allocation previews how indirect spend would be shared across jobs based on their labor hours in the selected period. It does not post amounts to job costs or Job P&L.
Open Reports → Overhead allocation.
Tabs
This report has one allocation preview, with no tabs.
Panels and controls
Use From, To, and Branch, then select Filter. The branch choices respect your assigned branch access.
Summary tiles show Overhead pool, Labor hours, Rate per hour, Allocated, and Unallocated.
The table shows each Job, Site customer, Bill-to customer, Agreement payer, Labor hours, Rate / hour, Allocated overhead, and Reason. Select a job to open its record. A job with no qualifying hours receives zero overhead; if no jobs have qualifying hours, the pool stays unallocated.
What it accepts
The date range defaults to the current calendar month in your company's time zone. Both selected dates are included.
The pool uses approved field-purchase amounts assigned to overhead by purchase date, including signed corrections. Hours come from approved, closed regular, overtime, and double-time entries on jobs that have not been canceled or deleted, counting only time within the selected dates. Travel, nonchargeable, open, and unapproved entries are excluded. Each hour has the same weight, including overtime and double time.
Jobs created before the selected period can still receive overhead when they have qualifying hours in it. The pool and hours use the same branch scope. Displayed rates are rounded; allocations use the full rate and preserve whole cents.
How to configure it
Assign field-purchase amounts to overhead and approve the purchases and allocations. Approve completed time entries on the relevant jobs. Select the period and branch to preview their allocation; this report saves no allocation settings and posts no costs.
Who can see it
You need access to Reports and the View costs and margins permission. Owners and office users have that permission by default; dispatchers do not. Custom roles and individual overrides can change access. The permission is checked on the server, including when you open a direct link.
See Roles & permissions.