What changes in home cleaning services operations
Home cleaning franchises coordinate recurring visits, add-on services, territories, and local teams. Corporate operators need to see whether each territory has reported its activity and whether the configured service rule still matches the work being counted. A shared workspace turns territory follow-up, quantity review, billing preparation, and history into one repeatable operating flow.
Watch for these gaps
- Combining recurring visits and one-off add-ons into one unexplained total
- Finalizing a territory before its service count is confirmed
- Overlooking a franchise that changed ownership during the period
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 home cleaning services, use territory roster with franchise status and operating contact; completed visit and add-on quantities for each billing cycle; open corrections, document requests, and period submission 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 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.
Confirm the territory list and franchise status before reviewing quantities. Separate recurring visits from add-on work, look for blank values in otherwise active territories, and compare overrides with the organization price. Resolve stale rows before saving, then review the period history for any reopened or voided entry and the reason attached to that action.
Download the home cleaning services review worksheet →A situation to work through
Suppose a cleaning network receives cycle reports from forty territories. The operator can filter to one territory, verify visits and add-ons against the applicable rules, and see whether a manager left a quantity blank or entered zero. A correction can be saved with its expected version, while the period remains visibly open until the responsible team finishes review.
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.