What changes in pest control operations
Pest control networks manage recurring service plans, one-time treatments, and branch-specific territories. Their operational data should show which service units belong to which cycle, who owns an exception, and whether an amount comes from the organization rule or a franchise override. Keeping those facts together makes recurring review faster and reduces unexplained adjustments between branches.
Watch for these gaps
- Counting a rescheduled visit as a second completed service
- Hiding a branch exception inside a network-wide adjustment
- Finalizing a zero without distinguishing no work from missing reporting
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 pest control services, use branch and territory directory with assignment status; recurring service-plan quantities and one-time work by cycle; open entry corrections, reviewer notes, and document follow-ups 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.
Begin with the territory and cycle assignment, then compare completed service units with the selected rule. Look for duplicate visits, blank quantities, and unexpected overrides. Use the preview before saving a correction, and ensure a reopened or voided entry includes its reason. Keep branch follow-up separate from the organization price so the calculation stays understandable.
Download the pest control review worksheet →A situation to work through
For a pest control group with many small branches, a reviewer can filter the current period to one franchise and immediately see its rule, quantity, status, and effective price. A submitted count that needs correction stays open and visible, while a confirmed zero can be finalized deliberately. The same view gives the operator a record of who changed the row and when.
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.