What changes in electrical services operations
Electrical service groups coordinate branches that may handle inspections, repairs, installations, and recurring programs. Corporate staff need a reliable way to compare what each branch reported with the unit rule that governs it. A focused operations record links the branch, period, quantity, price source, supporting files, and review state so a discrepancy can be resolved without losing context.
Watch for these gaps
- Blending installation projects with recurring inspection units
- Leaving a local override in place after the underlying program changes
- Assuming every branch uses the same currency or unit label
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 electrical services, use branch directory with assigned manager and active or archived state; inspection, repair, or program-unit quantities by period; price overrides and reviewer changes tied to a specific branch row 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 branch and program pairing before looking at amounts. Check that the quantity represents the configured work unit, that any override is intentional, and that the effective price is the one used for the open period. Review archived branches separately, resolve version conflicts by reloading, and keep a short business reason with every exception.
Download the electrical services review worksheet →A situation to work through
Imagine a multi-state electrical group reviewing a monthly inspection program. The corporate reviewer selects the rule, searches for a branch, and sees the base organization price, any branch override, and the effective amount beside the reported quantity. The reviewer can save a corrected row through its preview, while the branch's existing period entry remains version-aware and traceable.
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.