What changes in property restoration operations
Property restoration groups manage branches handling water, fire, mold, and rebuild work with different reporting rhythms. Their central team needs a business view that separates recurring program units from project activity and identifies branch exceptions early. Keep each period tied to its branch, rule, quantity, price source, supporting document request, and review state so urgent work does not erase ordinary controls.
Watch for these gaps
- Using project milestones as recurring service quantities
- Letting an urgent job bypass period ownership and review
- Leaving a temporary branch override in place after the project ends
A repeatable billing run simulation workflow
- 01
Open Billing simulation and choose the authorized organization or franchise scope.
- 02
Select the reporting context and start a preview without creating invoices.
- 03
Review eligible, deferred, blocked, and projected results in the preview.
- 04
Correct setup or data issues and rerun the preview before handing off to processing.
Bring the industry records into the review
For property restoration companies, use branch directory with service mix and operating status; program or service-unit quantities by reporting period; project-period exceptions and supporting 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
The preview scope does not match the intended run.
Stop and correct the selection when the simulated organization, franchise set, or reporting context is wrong.
The simulation returns multiple outcome groups.
Review eligible, deferred, and blocked items separately so unresolved work is not hidden in the total.
The preview exposes a blocker or unexplained total.
Correct setup or data issues and rerun the simulation when projected output is incomplete or unexpected.
The eligible output and remaining deferrals are understood.
Sign off the exact simulation scope and time before handing it to processing.
A common mistake to avoid
Assuming a simulation created invoices or charges when it only previewed what a run could do.
Before you mark the work complete
A simulation signoff that records scope, period, eligible and deferred work, blocked items, projected totals, and rerun decisions.
- The simulated organization or franchise scope is correct.
- Eligible, deferred, and blocked entries are understood.
- Projected totals are reviewed before approval.
Separate recurring program work from project milestones before checking amounts. Confirm the branch owner and period, then review whether any override is temporary and tied to the right cycle. Use a preview before saving, follow up on missing documents, and keep urgent exceptions visible until the accountable reviewer closes them.
Download the property restoration review worksheet →A situation to work through
A restoration operator can select a program, search a branch, and see the reported unit count, organization price, local override, and effective amount together. A project-related correction can be documented without rewriting the recurring rule. The operator reviews the row's current version before saving and keeps the period status visible while a supporting document is still requested.
Apply the billing run simulation 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.
What is billing simulation used for?
Simulation previews eligible entries, deferred or blocked work, and projected totals before invoice creation. Teams can inspect the authorized scope, correct setup or data issues, and rerun the preview before approving processing.
Put the workflow into practice
Granite's billing simulation previews eligible, deferred, blocked, and projected results before processing.
Use this guide to organize your process, then configure the applicable franchises, reporting periods, and billing rules in Granite.