Recurring billing: running subscriptions without surprises

Recurring billing is charging a customer the same amount on a repeating cycle rather than invoicing each transaction separately. It is the operational half of a subscription business, and it fails in ways that are individually small and collectively serious: cards that expire, renewals nobody was told about, price changes applied without notice, and invoices that do not match what the customer thinks they agreed.

Almost all of it comes down to decisions made once, in advance, and then applied consistently. The billing mechanics matter less than the policy around them.

What to decide before the first renewal

• The cycle and the anniversary: monthly or annual, and whether everyone renews on their signup date or on a common date. Common dates simplify your month; anniversaries simplify the customer's.
• Proration: what happens when someone upgrades mid-cycle, and whether downgrades take effect immediately or at renewal. Decide once, write it down.
• Advance notice of renewal, especially for annual contracts. In several jurisdictions this is a legal requirement for consumer subscriptions, and it is good practice everywhere.
• Notice for price changes, and whether existing customers are grandfathered.
• What happens when payment fails: how many retries, over how many days, and when access is suspended.
• Cancellation: how a customer does it, when it takes effect, and whether any refund applies.
• Tax treatment, which for cross-border digital subscriptions can depend on where the customer is rather than where you are.
• What the invoice shows — the period covered, the plan, the quantity — so it is checkable rather than a bare total.

Announce annual renewals in advance, in a message that is clearly not marketing. A customer surprised by a renewal charge disputes it, and a dispute costs you the revenue, the fee and the relationship. A short reminder two to four weeks before is the cheapest retention and goodwill measure available — and in some jurisdictions it is required rather than optional.

Running the cycle

1. Keep one source of truth for who is on what plan at what price. Disagreement between the billing record and the sales record is where wrong invoices come from.
2. Raise invoices on a fixed schedule and check the exceptions rather than every line — new customers, changes, cancellations.
3. Send the renewal notice before the charge, not with it.
4. Chase failed payments quickly and politely, and separate them from genuine cancellations in your own records.
5. Apply price changes with the notice you promised, and grandfather where you said you would.
6. Reconcile invoiced revenue against the plan list monthly. The gap is usually a change somebody made without updating the other system.
7. Record every cancellation with a date and a reason, so churn measurement has an input.
8. Review annually: which plans are actually in use, which discounts have outlived their reason, which customers are on prices you no longer offer.

Cash, not just revenue

Recurring billing shapes cash more than most founders expect. Annual upfront billing brings a year's cash in at once, which funds growth but creates a renewal cliff and an obligation you have already been paid for. Monthly billing smooths income and delays it. Mixing both, which most companies end up doing, means the cash-flow forecast cannot be derived from MRR at all — it has to be built from actual billing dates. That is a good reason to keep the billing schedule and the forecast in the same place.

In Ettex, the invoices themselves live in Ettex Invoices: line items with quantities, rates, multiple tax rates and discounts, notes and terms fields for the period covered, sequential auto-numbering with your own prefix, a client book so the same customer gets the same details, and statuses from draft through paid so you can see what is outstanding at a glance. The plan list and the billing calendar fit Ettex Sheets, renewal reminders can be scheduled from Ettex Mail with reusable text, the ledger side sits in Ettex Books with recurring entries and bank reconciliation, and the terms customers agreed to go through Ettex Signature.

The boundary, stated plainly: Ettex is not a billing platform. It does not store cards, take payments, charge customers automatically, retry failed payments, manage subscriptions, prorate upgrades, or handle tax rules by customer location. Invoices are documents you issue; the money is taken through whatever payment provider you use. For automated subscription billing at volume, that is exactly the software category to buy.

Regulators increasingly want the underlying data rather than a PDF. Electronic invoicing exchanges structured invoice data directly between systems, which is the basis of most mandatory reporting regimes.

Where recurring billing goes wrong

• Renewals charged without notice, which converts a quiet customer into a disputed transaction.
• Card expiry unmonitored, so revenue is lost to a solvable technical failure.
• Proration undefined, producing a different answer each time someone upgrades.
• Price changes applied to existing customers without the notice they were promised.
• Two records of who is on what plan, which guarantees wrong invoices.
• Cancellations processed without recording a reason or a date.
• Invoices showing a total with no period or plan, which customers cannot check and therefore query.
• Cash planned from MRR rather than from actual billing dates.

Recurring billing works when the policy is decided before the first renewal: cycle, proration, notice, retries, cancellation. Announce annual renewals in advance, chase failed cards fast, and build the cash forecast from billing dates rather than from MRR.