Landscaping

Recurring billing for landscapers: mowing routes that bill themselves

Updated October 3, 2026 · Alvin

Recurring routes should mean recurring revenue — billed on schedule, without the end-of-month scramble. Recurring billing for landscapers works by tying charges to the route sheet: a finished visit becomes a charge automatically, on a per-visit or flat-monthly plan the customer already approved. Alvin runs the cycle end to end: Alvin bills from the route sheet, retries failed cards, credits weather-skipped visits, and logs everything for the bookkeeper.

The monthly scramble, and what causes it

Here's how billing usually works in a landscaping shop. The crews run the routes all month. At month-end, someone in the office — often the owner, often late at night — exports the route sheets, checks which visits actually happened, builds the invoices, sends them, and then spends the next two weeks chasing the unpaid ones. It's a full-time job compressed into a few painful days.

The failure modes are boring and expensive. Visits get forgotten because the route sheet was scribbled. Invoices go out late because the office got buried. A card fails and nobody notices for a month. Cash flow dips mid-month because half the invoices are still "pending." None of this is a strategy problem — it's an operations problem, which is exactly why it responds to being handled automatically.

The route sheet is already the source of truth for scheduling the week's routes — it should be the source of truth for billing too. When a finished visit becomes a charge with no re-typing in between, the monthly scramble stops existing.

Per-visit or monthly flat: choose on purpose

Per-visit billing charges the customer after each completed visit. It's fair and transparent, and it fits irregular schedules — bi-weekly in winter, weekly in spring. The downside is lumpy bills: the customer sees a different amount every month, and every month has a line item for every visit.

Monthly flat billing charges the same amount every month, usually set as the annual cost divided by twelve. Cash flow smooths out, the customer stops asking "why is this month different," and the office sends one charge instead of four. The downside is that you need a written policy for what's included — how many visits per month, what happens on weather skips — or the flat rate becomes a source of arguments.

Most mow-and-blow routes run flat monthly; project-style or seasonal work stays per-visit. Either way, put the skip and weather policy in writing at signup. The billing model is a business decision — Alvin just runs whichever one you chose, exactly as you defined it.

How Alvin bills from the route sheet

1. The route sheet is the invoice. The crew marks visits done; each done visit fires the charge on the customer's plan. Nothing is re-typed, nothing is forgotten, and the charge always matches the work that actually happened.
2. Weather skips get credited, not forgotten. When a visit is skipped for rain, Alvin logs the skip the same day and either withholds the per-visit charge or applies your flat-plan skip policy. The customer sees the credit before they have to ask for it.
3. Failed cards retry on their own. A declined card triggers a retry sequence over the next several days, plus a polite text to the customer with a link to update their details. Most failures are expired cards, not deadbeats — the sequence treats them that way.
4. Chronic non-payers get flagged, not ignored. When the retry sequence runs out, Alvin flags the account for the owner with the balance and history. Whether service continues is your call — Alvin never cuts anyone off himself.
5. The bookkeeper gets a clean log. Every charge, retry, credit, and adjustment lands in one exportable log that matches the route sheet. Month-end becomes a review, not a reconstruction.

Failed cards don't need an awkward phone call

The failed payment is the moment most billing processes break down. The card declines, the invoice sits, and eventually someone has to call the customer about money — the call everyone dreads and keeps postponing. Automatic retries plus a simple text ("your card on file was declined — update it here") resolve most failures without a conversation at all.

What doesn't resolve gets flagged with context: how much is owed, how many retries happened, what the customer said. You walk into the conversation informed instead of discovering the problem. Pest control companies run the same failed-payment recovery on their recurring routes — the pattern works anywhere billing is tied to a schedule.

What stays with you

You set the pricing, the plans, and the skip policy once. You decide on holds, cancellations, and the accounts that need a human conversation. Alvin never changes a price, never cancels an account, and never charges without the approved plan behind it. The line is simple: Alvin does the billing, you make the business decisions.