Franchise billing process workflow for hvac services

Process a prepared billing run with an explicit preview and approval step. Review eligible and deferred work, confirm the chosen run, submit it once, and follow the resulting invoice and notification state from the processing workspace.

What changes in hvac services operations

HVAC service networks manage maintenance plans, dispatch activity, replacement work, and seasonal demand across local branches. A corporate team benefits from a single operational view that distinguishes recurring plan units from project work. Keep branch assignments, period quantities, customer-facing documents, and billing readiness close together so high-volume seasons do not turn into manual reconciliation.

Watch for these gaps

  • Counting a quoted replacement as completed service
  • Using seasonal volume as a permanent saved quantity
  • Missing a branch whose reporting period is open but overdue

A repeatable billing processing run workflow

  1. 01

    Open Billing processing and select the prepared run that has a reviewed preview.

  2. 02

    Confirm the eligible and deferred work before choosing the approval action.

  3. 03

    Approve and submit the run once, keeping its operation context visible.

  4. 04

    Follow the resulting invoice and notification states for completion or recovery.

Bring the industry records into the review

For hvac services, use branch roster with service territory and operating status; maintenance-plan or service-unit quantities by reporting period; period exceptions, approvals, and supporting work-document requests as the evidence packet. Keep the franchise and reporting period attached to each record so a reviewer can follow the source without reconstructing the conversation.

What to do when the review finds a problem

More than one prepared run or preview is available.

Select the prepared run whose scope and preview are the ones the team reviewed.

The preview contains deferred or blocked entries.

Resolve or explicitly record deferred work before approval so it is not mistaken for eligible work.

The reviewed run is ready for processing.

Approve and submit once, then follow the operation state rather than starting a second run.

The run finishes with anything other than the expected complete state.

Open the resulting invoice or delivery record when processing reports a partial or failed outcome.

A common mistake to avoid

Approving a different or older preview because its totals look similar to the run under review.

Before you mark the work complete

A processing approval record linking the reviewed preview to one submission and its resulting invoice and notification states.

  • The approved run matches the reviewed preview.
  • Eligible and deferred work is understood.
  • Invoice and notification outcomes are followed afterward.

Check that each branch has the correct recurring rule and reporting owner. Review whether quantities represent completed maintenance units rather than proposals or appointments, and separate a temporary override from the saved organization amount. Before closeout, inspect overdue periods, confirm zero quantities explicitly, and retain the reason for any reopened or voided entry.

Download the hvac services review worksheet →

A situation to work through

During a summer surge, an HVAC operator can select the current period, search for a branch, and see its maintenance quantity beside the organization price and local override. A branch with a blank quantity stays open for follow-up; a confirmed zero can be finalized intentionally. The team can then compare the period record with its supporting documents before preparing downstream billing work.

Apply the billing processing run steps above to this situation. Record the original evidence, the unresolved question, and the person who can answer it before treating the item as complete. This is a planning example, not a customer result.

How should an organization process an invoice run?

Start from a prepared preview, review eligible and deferred work, approve the run once, and follow the resulting invoice and notification states. Processing preserves the run context so teams can investigate a failed or incomplete outcome.

Put the workflow into practice

Granite's billing processing workspace connects a reviewed preview to one approval and its resulting states.

Use this guide to organize your process, then configure the applicable franchises, reporting periods, and billing rules in Granite.