What changes in plumbing services operations
Plumbing franchises work across emergency calls, scheduled maintenance, and project-based repairs. Their records become easier to manage when the central team can distinguish location assignments, service units, and period state. Give branch managers a clear path to report quantities and corporate reviewers a clear path to investigate exceptions without editing the underlying rule by accident.
Watch for these gaps
- Treating emergency call volume as the same unit as scheduled maintenance
- Changing a branch assignment to work around an unreviewed quantity
- Finalizing an entry while a correction request is still unresolved
A repeatable payment destination setup workflow
- 01
Open Billing setup and review the organization's configured payment destinations.
- 02
Confirm the standard or fallback destination used by the applicable billing rule.
- 03
Add or update an allowed Stripe account when the current role permits it.
- 04
Confirm the destination status and return to readiness or the rule before processing.
Bring the industry records into the review
For plumbing services, use branch and territory assignments with current operating status; scheduled service or maintenance-unit quantities for each cycle; correction notes and audit history for changed period entries 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 organization or Stripe account is in view.
Confirm the destination belongs to the intended organization before adding or editing its routing record.
A new or rotated provider credential is being prepared.
Use the approved key mode and keep the full credential out of notes, screenshots, and worksheets.
The saved destination is not in a ready state.
Resolve verification or webhook setup issues before assigning the destination to a billing rule.
The provider status and organization setup are confirmed.
Recheck the fallback or standard route after the destination is ready.
A common mistake to avoid
Copying a full Stripe key into an operational record while trying to prove that routing is configured.
Before you mark the work complete
A routing readiness record naming the organization destination, non-secret key metadata, verification state, and rules that use it.
- The destination belongs to the intended organization.
- Its provider status is configured and readable.
- Rules and readiness point to the intended route.
Map each branch to the service rule it actually uses, then check the cycle's unit label and due date. Review open and overdue entries separately from completed work, and do not use a pricing override to correct a quantity mistake. Save only after the preview is clean, and record a specific reason for any reopen or void action.
Download the plumbing services review worksheet →A situation to work through
A plumbing network can review its open cycle by branch, search directly for a franchise, and see which rows are ready, overdue, or still incomplete. The reviewer compares the saved service count with the local manager's submission, makes a bounded correction when needed, and keeps the original period and version context visible before the entry is finalized.
Apply the payment destination setup 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 are invoice payment destinations prepared?
Review the organization's configured Stripe destinations and the fallback or standard route used by billing. Add or update an allowed account, confirm its status, and return to billing readiness or the rule before processing invoices.
Put the workflow into practice
Granite's payment destinations workspace connects permitted Stripe accounts to billing rules and readiness.
Use this guide to organize your process, then configure the applicable franchises, reporting periods, and billing rules in Granite.