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 billing processing run workflow
- 01
Open Billing processing and select the prepared run that has a reviewed preview.
- 02
Confirm the eligible and deferred work before choosing the approval action.
- 03
Approve and submit the run once, keeping its operation context visible.
- 04
Follow the resulting invoice and notification states for completion or recovery.
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 prepared run or preview is available.
Select the prepared run whose scope and preview are the ones the team reviewed.
The preview contains deferred or blocked entries.
Resolve or explicitly record deferred work before approval so it is not mistaken for eligible work.
The reviewed run is ready for processing.
Approve and submit once, then follow the operation state rather than starting a second run.
The run finishes with anything other than the expected complete state.
Open the resulting invoice or delivery record when processing reports a partial or failed outcome.
A common mistake to avoid
Approving a different or older preview because its totals look similar to the run under review.
Before you mark the work complete
A processing approval record linking the reviewed preview to one submission and its resulting invoice and notification states.
- The approved run matches the reviewed preview.
- Eligible and deferred work is understood.
- Invoice and notification outcomes are followed afterward.
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 billing processing run 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 should an organization process an invoice run?
Start from a prepared preview, review eligible and deferred work, approve the run once, and follow the resulting invoice and notification states. Processing preserves the run context so teams can investigate a failed or incomplete outcome.
Put the workflow into practice
Granite's billing processing workspace connects a reviewed preview to one approval and its resulting states.
Use this guide to organize your process, then configure the applicable franchises, reporting periods, and billing rules in Granite.