Many contractor invoicing platforms offer recurring invoices, and sending an invoice from your phone before you pull out of the driveway is standard. IntelliDrive OS does the second and not the first: it takes payment at the job through a texted or emailed payment link, but it does not generate recurring invoices, so a contract that bills every month or quarter is a routine you run — a billing list, a billing day, and a payment link per cycle. In software that has the feature, "recurring invoice" means you define the customer, the line items, the amount, and the interval once, and the system issues the invoice on schedule — quarterly pest treatments, HVAC maintenance agreements, cleaning routes, seasonal landscaping contracts, and detailing memberships all run this way. This guide covers how that works, which billing model fits which contract, and how to run the same routine by hand without missing a cycle.
The two halves of that answer are more connected than they look. Recurring invoicing is how you get paid for the work you promised in advance; immediate mobile invoicing is how you get paid for the work you just did. Most service businesses have both kinds of revenue and only automate one of them.
What a recurring invoice actually does
This section describes the feature as it works in software that has it. IntelliDrive OS does not have it; the routine you can run instead is laid out further down.
A recurring invoice is a template plus a schedule. The template holds the customer, the service lines, the price, the tax treatment, and any notes that should appear every time. The schedule holds the interval — monthly, quarterly, seasonally, annually — and the anchor date. From there, each cycle produces a real invoice with its own number, its own date, and its own payment status, which is the part that matters for your books: recurring billing should generate discrete, auditable documents, not a running balance that nobody can reconcile.
What it saves is not really the typing. It's the forgetting. A quarterly pest program billed by hand means somebody has to remember, four times a year, per customer, across a route with a few hundred stops. The realistic failure rate on that is not zero, and every missed cycle is revenue you performed the work for and never asked to be paid for. Automating it converts a memory problem into a configuration problem, which is a much better class of problem.
The second thing it buys is forecastability. Once a meaningful share of your revenue is on a schedule, you can see next month before it arrives. The Small Business Administration's guide to managing your finances starts from keeping proper books of revenue and expenses, and recurring agreements are the easiest revenue in a service business to track, because the amount and the date are both known in advance.
Which billing model fits which contract
Not every repeating job should be billed the same way. Choosing wrong is how a profitable agreement turns into an argument at renewal.
| Billing model | How it bills | Best fit | Cash-flow effect | Watch out for |
|---|---|---|---|---|
| One-off per visit | Invoice created and paid at each job | Demand work, first-time customers, variable scope | Lumpy but immediate | No revenue predictability between calls |
| Recurring flat monthly | Same amount every month regardless of visit count | HVAC maintenance plans, detailing memberships, managed cleaning | Smooth and forecastable | Heavy-use customers can erode margin |
| Recurring per-visit | Invoice issued each time a scheduled visit is completed | Quarterly pest treatments, route-based cleaning, mowing season | Tracks the work closely | Skipped visits need an explicit rule |
| Prepaid package | Customer buys a block of visits up front | Detailing packages, seasonal tune-up bundles | Cash arrives first, work follows | Unearned revenue and expiry terms need care |
The trade shapes the answer. HVAC maintenance agreements almost always want flat monthly or annual coverage billing, because the customer is buying peace of mind and priority scheduling more than they're buying two specific visits — the structure is covered in detail in our guide to HVAC invoicing and maintenance contracts. Pest control usually wants recurring per-visit or quarterly billing tied to the treatment schedule, since the visit is the product; the scheduling side of that is in recurring treatment scheduling for pest control. Landscaping is seasonal by nature and frequently splits into a flat monthly figure across the growing season plus separate line items for one-off work, which is its own billing discipline — see seasonal contracts and crew billing. Detailing tends toward memberships and prepaid packages, where the mechanics of unused visits and expiry matter most, as covered in membership packages for auto detailing.
Anniversary billing versus billing on completion
This is the question owners get wrong most often, and it has a clean rule.
Bill on the anniversary when the customer is buying coverage. An HVAC agreement that includes two seasonal tune-ups, priority dispatch, and a parts discount is a coverage product; the value exists between visits, not only during them. Anniversary billing on that agreement is honest and produces the cleanest revenue curve. It also survives a mild winter, when the customer didn't need you and would otherwise wonder what they paid for.
Bill on completion when the customer is buying visits. A quarterly termite treatment is a discrete deliverable; the customer's mental model is "you came, you treated, I pay." Trying to bill that as a flat monthly subscription invites the question "what am I paying for in the months you don't show up?" — a question with no good answer.
The hybrid case is common and worth naming: an annual agreement paid monthly, where the invoice recurs on the anniversary of the sign-up regardless of visit timing, but the agreement text spells out exactly how many visits the year includes. That gives you smooth cash flow and gives the customer a countable deliverable. It works as long as both facts appear on the invoice.
One operational detail that gets skipped: recurring invoices should still record which technician performed the work and what parts were consumed, even when the amount doesn't vary. Otherwise your recurring book looks profitable in aggregate and hides the specific customer whose "flat monthly" costs you three hours and $60 in materials each visit. In IntelliDrive OS, credit the technician on each cycle's sale and attach parts with "Part used on this job", so the cost lands on the sale.
When a visit gets skipped
Weather, access, a locked gate, a customer who isn't home. Skipped visits are routine, and the way you handle them should be decided once and written down, because deciding it customer-by-customer is where recurring revenue goes to die.
Three defensible policies, in rough order of how common they are:
Carry forward. The visit becomes a credit and gets performed later; billing continues uninterrupted. This is the cleanest for flat-monthly coverage agreements and is what most HVAC and cleaning contracts do in practice.
Pause the cycle. Billing skips too. Simple and obviously fair, but it damages the predictability you bought the agreement for, and it invites customers to request pauses casually.
Coverage pricing. The agreement is priced as annual coverage where no single visit is separately owed, so a skipped visit doesn't change the bill at all. This only works if the agreement said so clearly at signing.
Whichever you choose, put it in the agreement text and echo it on the invoice — a one-line note on the document that a customer is already reading is worth more than a policy on page four of a contract. And when the skip was your fault rather than theirs, credit it immediately and visibly. The cost of a credited visit is far below the cost of a canceled agreement.
IntelliDrive OS has no credit balance or visit counter, so a carried-forward visit is a note on the customer record and a line on the next cycle's sale.
Changing prices mid-agreement
Recurring revenue is passive revenue, which means the customer isn't thinking about it — and a surprise increase is what makes them think about it. Handle changes at boundaries: notify before the renewal date, apply the new price at the renewal or the anniversary, never mid-cycle. Say what the change covers rather than citing costs in the abstract, and consider grandfathering your longest-tenured customers if the increase is steep. Existing agreements are the cheapest revenue you will ever have; the discount you extend to keep one is almost always smaller than the acquisition cost of replacing it.
If your agreements carry a balance between cycles, on-account terms are the right mechanism rather than an informal understanding — the workflow for that is in our guide to on-account billing for service businesses.
Running the cycle by hand in IntelliDrive OS
IntelliDrive OS does not generate recurring invoices, so the cycle is a routine. It is short, and it holds up for a few dozen agreements before it needs a spreadsheet's help:
- Keep an agreement list. Customer, plan, amount, itemized lines, billing day, and the date of the next visit — a spreadsheet is fine. Put the agreed line items in the customer's notes so every cycle is rung up identically.
- Ring up the cycle on the billing day. Create the sale in Sell with the same lines, credit the technician, and text or email the payment link. For a contract customer you have marked credit-authorized, ring it up on account instead and send their statement; a bill-to account carries the PO number.
- Set a repeating calendar reminder for the billing day, so the cycle does not depend on anyone's memory.
- Check the Payment Links page weekly for links that are still unpaid, and re-send them.
- Offer annual prepay. One payment link a year replaces twelve chances to miss.
If you need invoices that issue themselves, that is a real gap, and the software to evaluate for it is one that has the feature; the comparisons against Jobber and Housecall Pro cover where each fits.
The maintenance work recurring billing still requires
Automated billing is not unattended billing, and the failure modes are quiet ones. Three things need a standing check.
Unpaid cycles. With stored-card autopay, an expired card makes the recurring charge fail silently; with payment links, the failure is a link nobody opens. IntelliDrive has no stored-card autopay, so each cycle is a link, and a weekly pass through the unpaid ones — five minutes, not a project — catches it before it becomes three missed cycles and an awkward call.
Renewal dates. An annual agreement that auto-renews without a conversation is fine until the customer notices the charge and feels ambushed. A short heads-up before the renewal date costs nothing and converts a potential dispute into a retention touch.
Drifting scope. The customer who signed for two visits a year and now calls monthly is technically on the same agreement and is no longer the same customer economically. This is only visible if the recurring invoice records the visits and the parts consumed, not just the amount. Review the heaviest-use accounts once a season and reprice them at renewal rather than absorbing the difference indefinitely.
None of these are complicated. They are the reason recurring revenue gets described as passive and behaves like a small, cheap maintenance routine — one that pays for itself the first time it catches an unpaid cycle on a good customer.
The other half: invoicing before you leave the driveway
Recurring billing handles the predictable revenue. The rest of the money is earned on demand jobs, and there the whole game is compressing the gap between finishing the work and asking to be paid.
The mechanics are unglamorous and they work. Build the sale at the job from your catalog rather than typing it from scratch: tap the part, tap the labor line, tap the trip charge, and tax calculates. Then collect with a texted payment link the customer opens on their own phone — IntelliDrive OS has no card-present hardware, and the link also works for after-hours calls and for the customer whose card is inside the house. On a payment-link sale the customer signs and accepts the terms on that page, and IntelliDrive keeps the signature with the sale. The payment-link workflow, including what to put in the message so it doesn't read like spam, is covered in payment links for service businesses.
Two reasons this matters more than it sounds. First, cash timing: Stripe, for example, lists a standard two-business-day settlement for U.S. accounts (Stripe's payout documentation), so collecting at the job means real money in the account the same week rather than whenever a mailed check arrives; other processors set their own schedules. Second, collection odds: late and unpaid invoices strain any small business's cash flow (QuickBooks' cash-flow resources cover invoice terms and past-due follow-up), and the longer the gap between the work and the ask, the harder the invoice is to collect. The invoice you send while standing next to the customer is the one most likely to get paid.
The same principle applies to recurring agreements: ask for payment the day the cycle is billed, in the same message. IntelliDrive has no stored-card autopay, so each cycle is a payment link — which is why annual prepay, one link a year, is worth offering. A recurring invoice that emails a PDF and waits is a recurring receivable, which is a worse product than the one you sold.
Wiring both halves into one record
The practical reason to run recurring and on-demand billing in the same system is that most customers generate both. A pest control customer on a quarterly program also calls for a one-off wasp nest. An HVAC maintenance-plan holder also needs a compressor. If the agreement lives in one tool and the emergency call lives in another, nobody can answer the only question that matters at renewal: is this customer profitable in total?
One record fixes that. In IntelliDrive OS, one-off sales, quotes that convert to a sale in one step, on-account credit sales, and preorder deposits all attach to the same customer record, parts come off stock at the location they were sold from, and completed sales and invoices go to QuickBooks Online through a one-way push you start yourself. A recurring cycle is a sale you ring up on the billing day, so it lands in the same record. The result is that renewal conversations happen with numbers instead of impressions. IntelliDrive is $79/month flat, billed monthly, with unlimited users; if you want to see your own agreement structure modeled before committing, try the demo and model a real contract.
Recurring invoices don't make a service business predictable on their own. They make the revenue you already earned show up on time, every time, without anyone remembering to ask — and combined with getting paid at the job on everything else, that's most of what separates a business with a cash-flow problem from one without.
Related reading: Customer deposits in a service business · How IntelliDrive OS mobile invoicing works · Managing seasonal cash flow. For a complete machine-readable feature and pricing reference, see our LLM reference page.