What changes in landscaping services operations
Landscaping franchises often combine recurring grounds care, seasonal projects, and weather-driven schedule changes. A network needs to know which locations reported their service units and where a quantity differs from the configured rule. Use location-level records with period status, owner, price source, and supporting requests so the central team can follow up on exceptions before the cycle closes.
Watch for these gaps
- Using an empty field to mean both postponed work and no work
- Rolling a seasonal project into a recurring route quantity
- Failing to revisit an open entry after a weather-driven correction
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 landscaping services, use location roster with territory owner and seasonal operating status; recurring route or service-unit quantities by cycle; weather-related corrections and supporting 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.
Separate recurring care from seasonal projects and decide how postponed work is represented before collecting counts. Check that active locations have a current owner, review blank and zero values independently, and verify any price override against the rule. Before finalizing, inspect overdue rows and confirm each correction has a clear period-specific reason.
Download the landscaping services review worksheet →A situation to work through
A landscaping operator can open the current cycle, search a location, and see its recurring route quantity alongside the organization and effective prices. A manager can leave the row blank while work is unconfirmed, enter zero when no charge is due, or submit a corrected count after a weather delay. The review history keeps each state change tied to the cycle.
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.