What changes in car washes operations
Car wash networks track locations, membership activity, wash programs, and seasonal operating changes. Their shared workspace should make it easy to find a location, understand which quantity rule applies, and see what still needs review. A clear distinction between saved location quantities, per-cycle entries, and effective prices prevents local exceptions from becoming permanent network assumptions.
Watch for these gaps
- Treating a paused location as a zero-producing active location
- Using membership totals when the rule counts completed washes
- Losing the reason for a temporary seasonal override
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 car washes, use wash location roster with active, paused, or archived state; membership or wash-program quantities by reporting cycle; location-level price overrides and change history 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.
Check location state before reviewing cycle quantities, especially after a pause or reopening. Confirm the unit label matches the source count, distinguish a saved quantity from a per-cycle entry, and review effective price after any override. Close the cycle only after overdue locations, deliberate zeros, and temporary adjustments have been addressed.
Download the car washes review worksheet →A situation to work through
A car wash operator can select a wash program, search for a location, and see the organization price, local override, effective price, and cycle quantity in one row. A paused location can remain visible for historical review without receiving new active work. When a count changes, the operator saves the row after previewing its current version and resulting amount.
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.