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 audit review workflow
- 01
Open organization billing activity or the permitted organization audit view.
- 02
Filter recent events by source or outcome and confirm the active scope.
- 03
Inspect the recorded actor, state, and linked invoice or report where available.
- 04
Use the retained evidence to explain the operational decision without exposing raw provider details.
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
The activity or audit history contains more than one operating context.
Set the organization, date range, and event source before interpreting a change.
A configuration or processing event is selected.
Read the actor, source, and recorded outcome together rather than inferring intent from the current state alone.
The audit event points to an operational record.
Open the linked invoice or report when the event includes one and compare the evidence at both ends of the link.
The event and current record disagree.
Record the discrepancy and owner for follow-up when the retained event does not explain the observed result.
A common mistake to avoid
Using today's configuration as the explanation for a past billing decision without reviewing the recorded event.
Before you mark the work complete
A trace note that connects an organization billing event to its actor, source, linked record, outcome, and follow-up question.
- The organization and scope are the intended audit context.
- The event actor, source, and outcome are readable.
- Linked invoice or report evidence is available where relevant.
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 audit review 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 can billing changes be traced later?
Use billing activity and organization audit history to filter recent changes, open linked invoices or reports, and inspect the recorded actor and state. The product keeps operational evidence reviewable without exposing provider payloads or implementation details.
Put the workflow into practice
Granite's billing activity and audit views connect recorded changes to their actors and linked invoices or reports.
Use this guide to organize your process, then configure the applicable franchises, reporting periods, and billing rules in Granite.