FieldproxyAI-native field service software

Billing and payments

How do I bill recurring lawn care customers without chasing failed cards?

Pick one billing model per customer (per visit, a level monthly amount across the season, or a prepaid season), create invoices automatically from completed visits on a set day, and charge a card or bank account the customer has authorized you to keep on file. Then let the payment system do the first round of chasing: automatic retries for soft declines, automatic card updates for reissued cards, and a short series of messages with a pay link. Only the accounts still unpaid after that reach a person, with a written rule for when service pauses.

  • Fewer, larger charges mean fewer declines to chase: monthly level billing makes about a quarter as many charges as weekly per-visit billing.
  • Get written or online authorization before you store a card or debit a bank account, and keep it.
  • Retries and card updates fix many declines with no call; a lost, stolen or closed card needs a new card from the customer.
  • Send failed-payment messages with a pay link that needs no login, before anyone picks up the phone.
  • Write down when service pauses (for example after 14 days and two reminders) and apply it the same way to everyone.

Book your demo

A video call with our team

Number of employees

This page is about collecting what customers already owe you. It does not cover sales tax rules for lawn services, which vary by state, or payment processor pricing, which you should check on your processor's own page.

Facts checked as of November 2026. Sources at the end of the page.

Step by step

How recurring lawn care billing works, step by step

Most of the Monday phone calls start before the card is charged: the billing model, the authorization and the timing decide how many declines you get and how many fix themselves.

1. Pick a billing model for each customer

Per visit: each completed mow is a line, billed weekly or monthly. Level (installment) billing: the season's expected visits divided into equal monthly payments, trued up at the end. Prepaid season: one payment up front, often with a discount. Per round: one charge per fertilizer or weed control application. Store the model on the customer or service agreement, not in someone's head.

2. Invoice from completed visits only

An invoice line should come from a visit the crew marked done, with the date, service and price. Skipped visits (rain, drought, gate locked) produce no line, or a zero line with a reason, so the customer never pays for a mow that did not happen.

3. Batch the invoices on a set day

Generate all invoices for the period at once, e.g. Monday morning for last week's visits, or the 1st of the month for level billing. Review the batch for missing prices or visits still open before anything is charged.

4. Collect authorization to keep a card or bank account on file

The customer agrees, in writing or online, that you may store their payment method and charge it on the agreed schedule. For ACH debits this is a mandate: Stripe's documentation says the debit requires customer authorization first and the mandate records the business name, whether it is one-time or recurring, and the date and method of acceptance.

5. Charge automatically

Charge each invoice in the batch to the method on file, and send a receipt. If a person still has to select invoices and press a charge button, write down who does it and when, because a missed Monday becomes a late week for every customer.

6. Retry soft declines and update reissued cards

A decline for insufficient funds or a temporary issue is worth retrying a few times over the following days. A card that was replaced by the bank can be updated through the card networks where your processor offers an updater. Stripe, for example, says it automatically attempts to update saved cards when a customer gets a new card, and that this is widely supported for cards issued in the United States.

7. Send dunning messages with a pay link

After the first failure, email or text the customer that the payment did not go through, with a link to pay or update the card without logging in. Follow up on a fixed schedule, e.g. day 3 and day 7, and stop as soon as it is paid.

8. Decide when service pauses

A written rule, e.g. after 14 days unpaid and two reminders, the account goes on hold and the next visits are skipped, not cancelled. When it is paid, the visits resume. Tell customers the rule when they sign up.

9. Sync invoices and payments to your accounting system

Each invoice and each payment, including failed and refunded ones, should reach QuickBooks or Xero once, against the right customer, so the books match the bank deposit. Processor fees should be recorded separately from the invoice amount.

Failure modes

Why the chasing never stops

Weekly charges multiply the declines

A weekly route of 300 customers makes 300 charges a week. Even a small decline rate turns into a phone list every Monday, while the same customers on monthly level billing produce one list a month.

Charging is still a manual step

In some tools the office selects invoices and presses Charge. When that person is out, the batch waits, and the customers who were going to decline anyway decline a week later.

Failed charges are tried once

If the tool does not retry, every insufficient-funds decline on a Friday becomes a call, even though the same card would often go through after payday.

Expired and reissued cards are not updated

Cards on file go stale as banks reissue them. Without an updater, the first sign is a decline, and the fix is a call asking the customer to read out a new number.

Invoices and visits disagree

When invoices are typed from a route sheet instead of created from completed visits, customers are billed for skipped mows, dispute the charge, and the office spends the week issuing credits.

Payments are entered twice

If payments are keyed into QuickBooks by hand after the processor deposit, a failed or refunded charge can be recorded as paid, and month-end reconciliation finds it weeks later.

Options

Ways to do it

Five real approaches, described from each vendor's own help or product pages. Ask each the same questions: are invoices created from completed visits, is charging automatic or a button someone presses, and what happens to a declined card.

ApproachHow billing and collection workWhat to check
Service Autopilot: bulk charge from the invoice listInvoices set to be paid by card land on an Invoices to Charge tab, and the office selects them and runs Actions > Charge Cards. Charges that fail stay on that tab with the reason in red. ACH uses a separate ACH Invoices to Charge tab and Actions > Charge ACH.Its help center says ACH needs Xplor Pay as the processor, ACH underwriting and a Client Portal subscription, and bank details can only be added by the client in the Client Portal. Ask who runs the charge each week and how failed charges are retried.
Jobber: automatic payments on recurring jobsTurned on per recurring job. Jobber creates invoices on the job's billing schedule (monthly on the last day, after each visit, when the job closes, or custom) and charges the saved card or bank account (ACH) through Jobber Payments. The client gets an emailed receipt.Jobber's help center says automatic payments are attempted only once. On a failure, admins are emailed and the invoice stays unpaid for Collect Payment. Bank payments carry a 1% fee per its help center.
GorillaDesk: invoice frequency or Stripe subscriptionsA recurring invoice can repeat weekly, monthly or yearly on its own schedule, with the action Charge to a card on file on the invoice date. On the Pro plan, Stripe Subscription billing can automatically charge the default payment method on file for a fixed plan amount.Needs Stripe or Square connected and a card stored on the customer. The help articles read for this page do not say what happens when a charge fails, so ask about retries and notices.
RealGreen: autopay, installments and prepayBuilt for lawn and tree care. RealGreen's own page describes autopay, installment billing with equal payments through the season, prepay promotions, card and ACH payments, and an Account Updater that refreshes card numbers and expiry dates.The page read for this answer is a product page, not a help article, and does not describe retries after a decline or batch charging. Ask for a demo of a failed payment.
Payment processor billing directly (Stripe Billing)If you bill outside a field service tool, Stripe's Smart Retries retries failed invoice payments at chosen times, by default up to 8 retries within 2 weeks for new accounts, with windows from 1 week to 2 months. Saved US cards are updated automatically when banks reissue them.Visits, routes and crews live in another system, so someone moves completed visits into invoices. Stripe does not retry hard declines such as a lost or stolen card without a new payment method.
A field service platform set up around your billing (Fieldproxy)Invoices are created from completed visits on the schedule you choose, cards and bank accounts are kept on file with autopay, and customers pay or update a card from a link with no login. Crews can take cards in person with Tap to Pay. Invoices and payments sync two ways with QuickBooks Online, Desktop or Enterprise, or Xero.AI agents draft the chase for overdue invoices, and a person approves each message before it sends. Billing rules are set up for your business during onboarding, so bring your current rules and a few real invoices.

Vendor facts are from each vendor's own help or product pages, read in November 2026. Features and fees change, so check the linked pages.

Worked example

A worked example: 300 weekly mowing customers

Say a lawn care company has 300 weekly mowing customers at $45 a visit, with a 28-visit season from April to October. Assume 4% of card charges decline on the first attempt. These are made-up figures for the example, not industry averages.

LineWeekly per-visit billingMonthly level billing
Season revenue per customer28 x $45 = $1,260$1,260 over 7 months = $180 a month
Charges per billing run300300
Billing runs per season287
Charges per season8,4002,100
First-attempt declines at 4%12 a week, 336 a season12 a month, 84 a season
Money held up per run12 x $45 = $54012 x $180 = $2,160

A worked example with made-up figures. 300 x 28 = 8,400 and 300 x 7 = 2,100; 4% of each is 336 and 84.

Monthly level billing does not change the decline rate, but it cuts the number of declines the office sees in a season from 336 to 84, because there are a quarter as many charges. The cost is a larger amount per decline and an end-of-season true-up: if a customer had only 25 visits, they paid $1,260 for $1,125 of mowing and are owed a $135 credit.

Now the chasing. Say the 12 weekly declines split into 8 soft declines (insufficient funds, temporary holds), 2 expired or reissued cards, and 2 hard declines (lost, stolen or closed). With retries over the following days, a card updater and a pay link sent on the first failure, the office only needs to look at the accounts still unpaid after day 7. In this example that is the 2 hard declines plus any soft declines that never recover, instead of 12 calls every Monday.

Over the season that is the difference between 336 phone calls and a short review list each week. The accounts that are still unpaid at day 14 go on hold under the written rule, and the crew skips them until they pay.

Before you buy

What to check before you choose a tool

Good signs

  • Invoices are created from visits the crew marked complete, with skipped visits left off.
  • Per visit, level monthly, prepaid season and per round billing can sit side by side for different customers.
  • Charging on the billing day happens without someone pressing a button.
  • Soft declines are retried automatically over several days.
  • Reissued cards are updated through the processor's card updater.
  • Customers get a pay or update-card link that works without an account or password.
  • Card and ACH are both offered, with the authorization stored against the customer.
  • Invoices and payments, including failed and refunded ones, sync to QuickBooks or Xero without retyping.

Red flags

  • A declined charge is tried once and then left for the office to find.
  • Charging cards is a manual batch step that only one person knows how to run.
  • Customers must create a portal login to pay a failed invoice or add a new card.
  • Level billing has no end-of-season true-up, so credits are worked out in a spreadsheet.
  • Payments are exported to accounting as a file someone imports by hand.
  • The vendor cannot show you, in the demo, what the customer and the office see after a decline.

In Fieldproxy

Setting it up in Fieldproxy

Fieldproxy is set up around how your office already bills. Values marked e.g. are examples to replace with your own.

Billing model on each customer

Each customer or agreement carries its billing model (per visit, level monthly, prepaid season or per round), its price and its payment method on file. Recurring visits come from your recurring job schedule.

Invoices from completed visits on your schedule

On the day you choose, e.g. Monday at 6 am for last week's mows, invoices are created from the visits crews completed in the technician app. Skipped visits carry a reason and are left off.

Cards and ACH on file, with autopay

Customers save a card or bank account from a payment link with no login, and the invoice is charged automatically on the billing day. Crews can take a card on site with Tap to Pay when a customer wants to pay at the door.

Autopilot chases what is still unpaid

Autopilot drafts the follow-up for each overdue invoice with its payment link, e.g. on day 3 and day 7, and a person approves each message before it sends. Accounts still unpaid at e.g. day 14 are flagged for a service hold.

Watcher agent on the exceptions

The Watcher agent flags completed visits with no invoice, invoices for visits that were skipped, and customers on hold who are still on next week's route.

Two-way accounting sync

Invoices and payments sync two ways with QuickBooks Online, QuickBooks Desktop or Enterprise, or Xero, so the office does not retype payments after the deposit lands.

Live within a day

Your billing setup is built with you and the first invoices can run the day after setup. Migration of customers, visits and balances from your current tool is free and assisted. Fieldproxy is one price per company with unlimited users.

Card or bank

Card or ACH: what changes

Many lawn care companies offer both. The trade-offs come from how bank debits work, not from any one tool.

Bank debits are usually cheaper but slower

Jobber's help center, for example, lists bank payments at a 1% fee and says they settle in 4 business days by default, so they reach your bank later than card payments. Check your own processor's rates for cards and ACH.

Bank debits fail later

Stripe's documentation says ACH Direct Debit can take up to 4 business days to confirm success or failure, so a failed debit shows up days after the billing run, not at the moment of the charge.

Retries are limited

Stripe retries failed ACH debits only for insufficient funds, at most 2 times within 40 days, and it does not retry card hard declines such as a lost or stolen card until a new payment method is added.

Customers can dispute a debit for weeks

Stripe says customers can generally dispute an ACH debit through their bank for up to 60 calendar days on a personal account, and a dispute cancels the mandate, so you need a new authorization before charging again.

How switching works

How switching to Fieldproxy works

We move your data over and set the system up to the way you already work. Fieldproxy replaces the old tool; it does not run alongside it.

  1. Bring one billing week

    Show us last week's route, the invoices you sent and the list of declines you called. We read your billing rules out of them with you.
  2. We set up your billing models and payment rules

    Per visit, level monthly, prepaid and per round customers, the billing day, the retry and reminder schedule and the hold rule, built before you commit.
  3. Customers save their payment method

    Existing customers get a link to save a card or bank account with no login. Customers, visits and balances move over in a free, assisted migration.
  4. Run one billing day side by side

    Generate a week's invoices in Fieldproxy, compare them with your current batch line by line, then switch the charging on.

FAQ

Questions people ask

Should I bill lawn care customers per visit or a flat monthly amount?
Per visit is simplest to explain and matches what was done. Level monthly billing smooths the customer's payments and means far fewer charges, so fewer declines, but it needs an end-of-season true-up for skipped or extra visits.
Do I need customer permission to charge a card on file?
Yes. Get the customer's agreement to store the card and charge it on a stated schedule, in your service agreement or an online form, and keep the record. Bank debits need an ACH authorization (a mandate) before the first debit.
What should happen when an autopay card declines?
Retry soft declines automatically over a few days, update reissued cards through the processor where it offers an updater, and send the customer a pay link the same day. Call only the accounts still unpaid after the reminders.
Is ACH cheaper than cards for lawn care billing?
Usually, but check your processor. Jobber's help center, for example, lists bank payments at 1%. ACH also takes days to confirm, so a failed debit shows up after the billing run, and customers can dispute a personal debit for up to 60 days.
When should I stop service for an unpaid account?
Pick a rule and publish it, e.g. after 14 days unpaid and two reminders the account goes on hold and visits are skipped until payment. Holding visits rather than cancelling the agreement makes restarting simple.
Can invoices be created automatically from completed mows?
They should be. Invoices built from visits the crew marked complete avoid billing for skipped mows, which is one of the most common reasons customers dispute a charge.
Will payments sync to QuickBooks automatically?
Ask each vendor to show a paid, a failed and a refunded invoice reaching QuickBooks. Fieldproxy syncs invoices and payments two ways with QuickBooks Online, Desktop and Enterprise, and with Xero.

Sources

Competitor details on this page come from the vendors' own pages and documentation, checked as of November 2026. Plans and prices change, so check the vendor's current page before you decide.

See it built on your workflow

Tell us how your jobs run today. We build a demo on your stages, forms and pricing before the call.