What changes in appliance repair operations
Appliance repair networks coordinate dispatch branches, maintenance programs, warranty-related work, and recurring service plans. Corporate teams need branch-level quantities that are easy to compare without blending one-time calls with recurring units. A focused record shows the rule, cycle, price source, owner, and next action so an incomplete report can be resolved before the period is closed.
Watch for these gaps
- Counting dispatched calls when the rule counts completed visits
- Combining warranty work with customer-paid service units
- Allowing a branch to submit a stale count after another edit
A repeatable invoice payment workflow
- 01
Open the franchise invoice detail and confirm the open balance and due state.
- 02
Start the available Stripe Checkout handoff from that invoice.
- 03
Complete the card payment in the provider checkout flow.
- 04
Return to the invoice and verify the provider-reported payment status.
Bring the industry records into the review
For appliance repair businesses, use branch roster with service area and operating status; maintenance-plan or recurring-call quantities by period; branch corrections and supporting service-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
The invoice status and amount have been confirmed.
Use the payment handoff only when the invoice is open and the displayed balance is understood.
The payer is ready to begin the card payment.
Start checkout from the intended invoice and keep its identifier with the payment attempt.
The provider flow does not return a completed payment result.
Treat an interrupted or abandoned checkout as unresolved until the invoice status is checked again.
The payer returns from checkout or the provider reports a result.
Close the handoff only when the invoice reflects the provider-reported payment outcome.
A common mistake to avoid
Treating a return from checkout as confirmation that the invoice was paid.
Before you mark the work complete
A payment handoff record connecting the invoice, open balance, checkout attempt, provider result, and final invoice status.
- The invoice is open and the amount is understood.
- The checkout is started from the intended invoice.
- The invoice status is rechecked after checkout returns.
Confirm whether the unit counts dispatched, completed, or recurring work, and keep warranty activity separate when the rule requires it. Review branch status and period owner, then inspect blank, zero, and overridden rows. Preview changes before saving, and reload any stale row instead of applying a correction to an outdated version.
Download the appliance repair review worksheet →A situation to work through
An appliance repair operator can filter to a branch, compare its completed service quantity with the configured rule and effective amount, and see whether the row is open or ready. A warranty exception stays visible without changing the rule for every branch. Before saving a revised count, the operator checks the row version and reviews the proposed result.
Apply the invoice payment 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 does a franchise pay an open invoice?
Open the invoice detail, confirm the amount and due state, start the available Stripe Checkout flow, and return to the invoice to verify the provider-reported status. Granite supports card checkout while keeping payment records tied to the invoice.
Put the workflow into practice
Granite's invoice checkout hands open-balance payment to Stripe Checkout and returns status to the invoice.
Use this guide to organize your process, then configure the applicable franchises, reporting periods, and billing rules in Granite.