What changes in moving and storage operations
Moving and storage networks coordinate branches, move volume, storage units, seasonal demand, and local operating changes. A central team needs to distinguish recurring storage activity from project-based moves and see which branches still need to report. Keep branch assignments, period quantities, effective prices, and document follow-up in one reviewable workspace rather than stitching together dispatch and billing spreadsheets.
Watch for these gaps
- Using move jobs to explain recurring storage-unit quantities
- Ignoring a seasonal branch whose reporting period is overdue
- Changing an assignment instead of correcting a submitted quantity
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 moving and storage businesses, use branch directory with service area and operating state; move, storage, or recurring-unit quantities by cycle; branch exceptions, correction history, and 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.
Start by separating move volume from recurring storage units and confirming the branch's active status. Check the expected reporting cadence, then review blanks, zeros, overrides, and overdue rows. Use the rule's effective price when assessing the amount, and resolve stale versions before saving any correction so one branch cannot overwrite another reviewer's work.
Download the moving and storage review worksheet →A situation to work through
A moving network can review an open cycle by branch, search for a location, and see storage units or move counts beside their rule and effective amount. A branch with an overdue submission is easy to distinguish from one that intentionally reported zero. The operator can save a corrected row after preview and retain the branch's period-specific history for later questions.
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.