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 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 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
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.
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 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.