What changes in hvac services operations
HVAC service networks manage maintenance plans, dispatch activity, replacement work, and seasonal demand across local branches. A corporate team benefits from a single operational view that distinguishes recurring plan units from project work. Keep branch assignments, period quantities, customer-facing documents, and billing readiness close together so high-volume seasons do not turn into manual reconciliation.
Watch for these gaps
- Counting a quoted replacement as completed service
- Using seasonal volume as a permanent saved quantity
- Missing a branch whose reporting period is open but overdue
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 hvac services, use branch roster with service territory and operating status; maintenance-plan or service-unit quantities by reporting period; period exceptions, approvals, and supporting work-document requests 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.
Check that each branch has the correct recurring rule and reporting owner. Review whether quantities represent completed maintenance units rather than proposals or appointments, and separate a temporary override from the saved organization amount. Before closeout, inspect overdue periods, confirm zero quantities explicitly, and retain the reason for any reopened or voided entry.
Download the hvac services review worksheet →A situation to work through
During a summer surge, an HVAC operator can select the current period, search for a branch, and see its maintenance quantity beside the organization price and local override. A branch with a blank quantity stays open for follow-up; a confirmed zero can be finalized intentionally. The team can then compare the period record with its supporting documents before preparing downstream billing work.
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.