What changes in electrical services operations
Electrical service groups coordinate branches that may handle inspections, repairs, installations, and recurring programs. Corporate staff need a reliable way to compare what each branch reported with the unit rule that governs it. A focused operations record links the branch, period, quantity, price source, supporting files, and review state so a discrepancy can be resolved without losing context.
Watch for these gaps
- Blending installation projects with recurring inspection units
- Leaving a local override in place after the underlying program changes
- Assuming every branch uses the same currency or unit label
A repeatable billing processing run workflow
- 01
Open Billing processing and select the prepared run that has a reviewed preview.
- 02
Confirm the eligible and deferred work before choosing the approval action.
- 03
Approve and submit the run once, keeping its operation context visible.
- 04
Follow the resulting invoice and notification states for completion or recovery.
Bring the industry records into the review
For electrical services, use branch directory with assigned manager and active or archived state; inspection, repair, or program-unit quantities by period; price overrides and reviewer changes tied to a specific branch row 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.
Confirm the branch and program pairing before looking at amounts. Check that the quantity represents the configured work unit, that any override is intentional, and that the effective price is the one used for the open period. Review archived branches separately, resolve version conflicts by reloading, and keep a short business reason with every exception.
Download the electrical services review worksheet →A situation to work through
Imagine a multi-state electrical group reviewing a monthly inspection program. The corporate reviewer selects the rule, searches for a branch, and sees the base organization price, any branch override, and the effective amount beside the reported quantity. The reviewer can save a corrected row through its preview, while the branch's existing period entry remains version-aware and traceable.
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.