A Complete Guide to Recurring Invoices for Subscription Businesses

Recurring invoicing is one of those features that every invoice app advertises and few implement well. "Send the same invoice every month" sounds simple. In practice, real subscription businesses have to handle pauses, upgrades, downgrades, end dates, prorated periods, variable amounts, per-client discounts, and the occasional client who wants their invoice on the 15th instead of the 1st. An app that handles the simple case and fails on these edge cases is worse than no automation at all — because the failures happen quietly and you don't notice until a client points out the broken invoice.

This guide is the complete design specification for recurring invoicing that survives real-world subscription businesses. It applies to anyone with monthly retainers, software subscriptions, gym memberships, music lessons, ongoing maintenance contracts, professional retainers, or rental agreements.

The eight things every recurring schedule must handle

1. The base case: identical invoice each period

The simplest scenario. Same line items, same amount, same period (monthly, quarterly, annually). Every recurring system handles this. It's the rest that separates good from bad.

2. End conditions

A schedule needs three possible end conditions, picked per schedule:

• No end (open-ended): bills until manually cancelled. Useful for evergreen retainers and SaaS subscriptions.
• End by date: bills until a specified date, then stops. Useful for fixed-term contracts.
• End after N invoices: bills exactly N times, then stops. Useful for installment plans and retainer packages with a fixed number of months.

Without all three, you'll find yourself manually pausing schedules to fake the missing options.

3. Pause and resume

Real clients sometimes ask to pause. Maternity leave. Sabbatical. Cash-flow trouble. The schedule needs to pause cleanly and resume on a specified date, without losing its history or breaking its numbering. "Cancel and recreate" is not a substitute for pause — it loses the original schedule's identity.

4. Variable amounts

Two kinds of variability:

Pre-defined variability — the amount changes on a known schedule. Example: discounted first three months, then full rate. The schedule should let you specify per-period amounts in advance.

Ad-hoc variability — this month is different from last month due to overage usage, additional services, or one-off adjustments. The schedule should let you edit the next generated draft before it goes out.

5. Per-client overrides

Even within a single recurring product (say, a £200/month consulting retainer), individual clients have differences: a different tax rate, a personalized discount, a unique payment instruction, a specific invoice day-of-month. The schedule needs to remember these per-client without forcing you into a generic template.

6. Proration

When a subscription starts mid-period, the first invoice may need to be prorated. When a subscription ends mid-period, the last invoice may need to be prorated (or refunded). A good system supports both automatic proration based on day count and manual adjustment.

7. Draft mode vs auto-send

Some businesses want fully automated send-without-review. Others want a draft generated for review and one-tap send. Both should be possible per-schedule, not as a global setting. A small client with reliable billing can be auto-send; a complex one with frequent adjustments should be draft.

8. Catch-up on missed periods

If the app was offline or the schedule was paused and you want to back-bill, the system should let you generate the missing invoices in one operation rather than forcing you to recreate each manually.

The numbering problem

Many tax authorities (Italy, Germany, Brazil, Mexico, and others) require gap-free sequential invoice numbering. Recurring schedules need to slot into this numbering scheme correctly:

• Auto-generated invoices use the next sequential number at the moment of generation.
• If multiple schedules generate on the same day, the order of generation determines numbering order.
• If a recurring invoice is voided, the number cannot be reused (in jurisdictions that require this); the void itself must be logged.
• The numbering scheme can include the year, the schedule type, or the business profile (CONS-2026-001, RET-2026-001).

Apps that ignore numbering integrity create compliance problems that surface only at audit time.

The reminder problem

Recurring invoices that get generated but aren't paid need follow-up. The follow-up rules differ by business:

Soft reminders

3 days after due date — a polite "just a reminder that invoice XYZ is awaiting payment." Most clients respond to this and never need anything stronger.

Firm reminders

10 days after due date — clear language, payment options, late-fee mention. Triggers customer attention without damaging the relationship.

Service-pause warnings

For subscription businesses where access depends on payment — gym memberships, software, ongoing services — a service-pause warning at 14-21 days protects the business: "If payment isn't received by [date], your access will be paused."

These reminders should be configurable per-schedule, with templated language that doesn't require composition each time.

The email-template integration

The PDF is half of a sent invoice. The email body is the other half. Recurring invoicing without email-template integration produces robotic-looking sends.

Good recurring schedules let you:

• Use a saved email template with merge fields (client first name, invoice number, amount, due date).
• Vary the template by schedule type (the retainer reminder reads differently from the SaaS subscription notification).
• Include a personal note field that you can update per-period without changing the template itself.

The tax-rate problem

Tax rates change. VAT rates change. Sales tax rates change. Local rates change when a client moves. A recurring schedule should:

• Pull the current tax rate at generation time, not at schedule creation.
• Allow per-client tax overrides (different states, different countries).
• Handle reverse-charge scenarios for cross-border B2B EU invoices.
• Apply different rates to different line items if needed.

The currency problem

For international subscriptions, the currency policy matters:

• Locked-currency subscriptions: billed in the same currency forever, regardless of FX moves. Best for B2B retainers.
• Tracking-currency subscriptions: the price in your home currency is fixed, but the client-facing amount changes monthly with exchange rates. Common for some international SaaS.
• Anchored-rate subscriptions: use the FX rate from a reference date (typically the contract date) for the life of the subscription.

Each has tax and accounting implications. The schedule should let you pick.

Reporting that subscription businesses need

Beyond the invoicing itself, recurring billing needs reporting:

MRR / ARR

Monthly recurring revenue and annual recurring revenue. The aggregate value of all currently active schedules. Should update in real time as schedules are added, paused, ended, or modified.

Churn

Number and percentage of schedules ended per period. Lets you spot retention issues.

Expansion revenue

Schedules whose amounts have increased (upgrades, additional services). The difference between growth and churn.

Failed-payment rate

Percentage of generated invoices that haven't been paid by 30 days. A health metric for your customer base.

What not to automate

The instinct with recurring billing is to automate everything. Resist this for two categories:

Initial setup of new schedules

The first invoice in a subscription often has a personal touch — a welcome message, an initial proration, an introductory discount. Manual generation of the first one, then auto-generation thereafter, produces a better client experience.

Major changes

When a client upgrades, downgrades, or significantly modifies their subscription, the next invoice deserves human review. Auto-generating it risks sending the wrong amount, missing a prorated credit, or applying the wrong start date.

Building the right setup in InvoiceFlow

Each recurring schedule in the app handles all the above: end conditions (none, by-date, after-N), pause/resume, variable amounts (pre-defined or ad-hoc draft), per-client overrides, optional auto-send vs draft mode, catch-up on missed periods, gap-free numbering, configurable reminders, email-template integration, and current tax-rate application at generation time. Reports include MRR, churn, expansion, and failed-payment rate per profile.

None of this is glamorous. None of it sells software in screenshots. All of it is what separates a recurring-billing system you can run a business on from a recurring-billing feature you'll outgrow in three months.

The wider lesson

If you operate any kind of subscription, retainer, or membership business, the quality of your recurring-billing setup determines the ceiling of your business. With good setup, you can scale to hundreds of subscribers without proportional admin overhead. With bad setup, you cap out somewhere around 30-50 subscribers because the manual handling of edge cases consumes all your time.

Pick well. Set it up properly. Then forget about it.