Franchise billing process workflow for plumbing 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 plumbing services operations

Plumbing franchises work across emergency calls, scheduled maintenance, and project-based repairs. Their records become easier to manage when the central team can distinguish location assignments, service units, and period state. Give branch managers a clear path to report quantities and corporate reviewers a clear path to investigate exceptions without editing the underlying rule by accident.

Watch for these gaps

  • Treating emergency call volume as the same unit as scheduled maintenance
  • Changing a branch assignment to work around an unreviewed quantity
  • Finalizing an entry while a correction request is still unresolved

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 plumbing services, use branch and territory assignments with current operating status; scheduled service or maintenance-unit quantities for each cycle; correction notes and audit history for changed period entries 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.

Map each branch to the service rule it actually uses, then check the cycle's unit label and due date. Review open and overdue entries separately from completed work, and do not use a pricing override to correct a quantity mistake. Save only after the preview is clean, and record a specific reason for any reopen or void action.

Download the plumbing services review worksheet →

A situation to work through

A plumbing network can review its open cycle by branch, search directly for a franchise, and see which rows are ready, overdue, or still incomplete. The reviewer compares the saved service count with the local manager's submission, makes a bounded correction when needed, and keeps the original period and version context visible before the entry is finalized.

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.