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 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 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
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.
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 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.