Recurring Invoice: When to Use One (and How It Differs From a Subscription)

A recurring invoice is any invoice that repeats automatically on a schedule — monthly, quarterly, annually, or whatever cadence the engagement requires. It's the right tool when you're billing the same client the same (or substantially similar) amount on a predictable rhythm, and you'd rather not rewrite the invoice from scratch every period.

The term gets used loosely. People call retainers, subscriptions, service contracts, and even rent invoices "recurring." They're all recurring invoices in the sense that they repeat, but the underlying engagement is different in each case, and the invoice you send should reflect that.

This guide explains when a recurring invoice is the right billing model, how it differs from a subscription with card-on-file, and how to set one up without losing track of which client is on which schedule.

What "recurring invoice" actually means

In its narrow sense, a recurring invoice is:

A regular invoice (with line items, amounts, payment terms)
That is sent on a fixed schedule (e.g., the 1st of every month)
Where the client receives it and pays via their normal AP process (ACH, check, card, wire)

It is not the same as:

A subscription with card-on-file. Subscriptions auto-charge a saved payment method — the client doesn't approve each charge. Recurring invoices send a new invoice each period that the client (or their AP) actively pays.
A standing order or autopay. Those are payment automations, not invoice automations. A recurring invoice can have autopay attached but doesn't require it.

The key distinction: recurring invoices put the invoice on a schedule. Subscriptions put the payment on a schedule.

When a recurring invoice is the right model

Three engagement patterns that fit:

1. Retainer or ongoing service work

A monthly retainer is the canonical recurring invoice. Same client, same scope, same amount, every month. The recurring invoice templatizes a process that would otherwise be 5 minutes of copy-paste-and-edit every month.

2. Subscription-style services with B2B customers

A SaaS service billed quarterly or annually to an enterprise customer is typically delivered as a recurring invoice rather than a card-on-file subscription. Reasons:

Enterprise AP doesn't do card-on-file for large amounts
The customer needs an invoice in their system for budgeting and audit
Renewal decisions are made deliberately, not auto-charged

3. Service contracts (maintenance, support, hosting)

A managed-hosting contract at $500/month, a website maintenance retainer at $250/month, a quarterly compliance review at $2,000/quarter — all natural recurring invoices.

When a recurring invoice is NOT the right model

Variable consumption. If the amount changes meaningfully each period (e.g., usage-based pricing), a recurring template with a fixed amount will be wrong half the time. Bill in arrears with the actual consumption.
B2C subscriptions under ~$100/month. For consumer subscriptions, card-on-file is the right tool. Sending a monthly invoice and waiting for the consumer to pay it is friction that loses customers.
One-time deposits and balance invoices. A deposit invoice followed by a balance invoice is two invoices, not a recurring sequence. Don't shoehorn it into a recurring template.

Recurring invoice vs subscription: which to pick

| Dimension | Recurring invoice | Subscription (card-on-file) | |---|---|---| | Who initiates payment | Client (active payment each period) | Provider (auto-charge each period) | | Typical customer | B2B, enterprise, AP-driven | B2C, SMB, consumer | | Payment method | ACH, check, wire, sometimes card | Card-on-file (usually) | | Cancel friction | Low — client just stops paying | Variable — depends on provider's flow | | Dunning needed | Yes — follow up on unpaid invoices | Mostly handled by payment processor | | Best for amounts | Any, especially > $500/month | Smaller, especially < $200/month | | Procurement friendly | Yes — invoice fits AP workflow | Often not — enterprise AP avoids card-on-file |

The decision usually comes down to who your customer is:

B2B selling to enterprise → recurring invoice
B2C selling to consumers → subscription
B2B selling to small businesses → often either; ask the customer's preference

How to structure a recurring invoice

A recurring invoice has the same structure as a one-time invoice (see how to write an invoice) with a few additions:

1. Period in the line item

Always state the period the invoice covers:

Hosting service — May 2026                          $500.00

Not just "Hosting service." When the client's bookkeeper looks at three identical invoices in a row, the period is the only thing distinguishing them.

2. Invoice number convention

Recurring invoices should follow a numbering pattern that makes the sequence obvious:

2026-05-ACME — year-month-client (good for low-volume retainers)
INV-2026-0501 — sequential with date prefix (good for higher volume)
ACME-2026-05 — client-prefixed monthly

Pick one and stick with it. See invoice number format for the full breakdown.

3. Reference to the underlying agreement

The invoice should reference the contract or order that authorizes it:

Per Master Services Agreement dated Jan 15, 2026.
Renewal: monthly. Next invoice: June 1, 2026.

The "next invoice" line is optional but it's a quiet pre-empt of the "we didn't authorize that" objection three months in.

4. Consistent fields across periods

The first recurring invoice sets the template. Every subsequent invoice in the series should have:

Same billing entity
Same contact (or updated if AP changed)
Same payment terms
Same line items (only the period and date change)

If any of these change mid-stream, send a one-time email to the client noting the change before the new invoice arrives. Surprises here cause AP to bounce the invoice for review.

Sample recurring invoice

INVOICE #ACME-2026-05                       Issue date: May 1, 2026
                                              Due date: May 31, 2026 (Net 30)

Bill to: Acme Co.
         123 Market St, San Francisco, CA 94103
         AP: [email protected]

From:    Jane Smith LLC
         EIN: 12-3456789
         [email protected]

Description                                              Amount
----------------------------------------------------------------
Managed hosting service — May 1–31, 2026                $500.00
  Per Service Agreement dated Jan 15, 2026.
  Renewal: monthly. Next invoice: June 1, 2026.

                                                Total: $500.00

Payment terms: Net 30.
ACH preferred: routing 000000000 / account 0000000000
Late payments are subject to a 1.5% monthly fee.

Common recurring schedules

| Cadence | Best for | Watch out for | |---|---|---| | Weekly | Rare — usually only for high-volume B2B (e.g., temp staffing) | Heavy AP load on the client; clients often consolidate to monthly | | Monthly | Default for retainers, hosting, support contracts | Pick a consistent day (1st or 15th) so AP can predict the cycle | | Quarterly | SaaS, compliance services, larger retainers | Spell out the months covered; clients forget what Q2 dates are | | Annually | Annual contracts, enterprise SaaS | Send a renewal notice 60 days before — gives AP time to budget |

Default to monthly unless you have a specific reason otherwise. Monthly fits the client's accounting close, monthly fits your cash-flow forecasting, and monthly gives both sides multiple chances per year to spot a problem before it becomes structural.

Automation: tooling for recurring invoices

A few options, from least to most automated:

Manual templates. Save a template, duplicate and edit the date each month. Works for 1–3 recurring clients; tedious beyond that.
Recurring invoice generator. A tool that lets you set the schedule and auto-generates each invoice on the right day. Common feature in invoicing tools — you set "monthly, day 1" once and the invoice generates and emails itself.
Recurring invoice + autopay. The invoice generates, the client's saved payment method auto-charges, and you receive cash without follow-up. Most relevant for SMB clients on cards; enterprise rarely wants this.
Full subscription billing. For consumer-scale recurring revenue, a subscription platform (Stripe Billing, Chargebee, etc.) replaces invoices entirely. Different tool, different model.

For most freelancers and small agencies the right answer is option 2: a recurring invoice generator without autopay. You get the time savings without forcing the client into a payment method they don't want.

Handling changes mid-stream

What to do when the engagement evolves:

Price change

Two weeks' notice minimum. Email the client, get acknowledgment, then the next invoice reflects the new price. The first invoice at the new rate should have a brief note: Rate updated per agreement of [date].

Scope change

Same as price change. If the scope expanded and the rate went up, both belong in the same notification email.

Pause or skip a period

Send a note in advance — e.g., "Pausing the May invoice; client is on hold for the month." Resume with a clear note on the next invoice: Service resumed May 15. Invoice covers half-month at $250.

Cancellation

Two scenarios:

You're canceling the service. Send a final invoice covering the last period worked. Note "Final invoice — service concluded [date]" in the description.
The client is canceling. Honor the notice period in your contract. The last invoice should cover the notice period whether or not work was actively performed.

FAQ

What's the difference between a recurring invoice and a subscription?

A recurring invoice is an invoice that repeats on a schedule — the client still actively pays each one through their AP process. A subscription is a payment that auto-charges a saved card on a schedule, typically without a new invoice each time. Recurring invoices fit B2B; subscriptions fit B2C and consumer SaaS.

Can a retainer be a recurring invoice?

Yes — a retainer is typically delivered as a monthly recurring invoice. The retainer is the engagement; the recurring invoice is the billing mechanism that implements it.

How do I number recurring invoices?

Use a consistent pattern that makes the sequence obvious. 2026-05-ACME, ACME-2026-05, or sequential INV-2026-0501 all work. The key is not the format — it's that you stick with one format so the client's bookkeeper can scan a year of invoices and immediately see the pattern. See invoice number format.

What payment terms should a recurring invoice have?

Net 30 is the safe default for B2B recurring invoices. Net 15 if your contract calls for it; Net 60 only when the client demands it and you've priced it in. Don't use Due Upon Receipt for recurring invoices — the urgency mismatch confuses AP teams used to monthly cycles.

How do I handle a price increase on a recurring invoice?

Give at least 2 weeks' (better: 30 days') written notice before the new rate takes effect. Get email acknowledgment. The first invoice at the new rate should have a brief note in the description: Rate updated per agreement of [date]. Surprising the client with a higher amount on an otherwise identical invoice causes AP to flag it for review, delaying payment.

Should I auto-charge a card for a recurring invoice?

For SMB clients on cards, yes — it's the lowest-friction option for both sides. For enterprise clients, almost never — AP teams don't keep cards on file for large vendor payments and won't allow it for compliance reasons. Match the payment method to the customer type.

What's the difference between a recurring invoice and a standing order?

A recurring invoice is a document the seller generates and sends each period. A standing order (also called automatic payment) is a payment instruction the buyer sets up at their bank to send a fixed amount on a schedule. They can coexist — the seller sends a recurring invoice for the record, the buyer's standing order pays it — but they're different mechanisms.

Can a recurring invoice have variable amounts?

It can, but you lose most of the automation benefit. If amounts change every period (usage-based pricing, time-and-materials), bill in arrears as a regular invoice each period rather than forcing it into a recurring template. Recurring is for stable, predictable amounts.