Recurring billing goes wrong in small, expensive ways: silent renewals, failed cards, price rises nobody announced. Most of it is preventable with decisions made in advance.
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.
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.
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.
Charging a customer a set amount on a repeating cycle — monthly or annually — rather than invoicing each purchase separately.
Yes, particularly for annual subscriptions. It prevents disputes and chargebacks, and in a number of jurisdictions advance notice for consumer subscriptions is a legal requirement — check what applies where your customers are.
With a proration rule decided in advance and written down: charge the difference immediately, or apply it at renewal. Inconsistency here produces disputes and manual credit notes.
A defined retry schedule, a clear notification that does not look like marketing, and a stated point at which access is suspended. Failed payments are a large share of lost subscription revenue and are the cheapest to recover.
Common dates make your month-end simpler; anniversary dates are fairer to customers and avoid proration on every signup. Pick one deliberately rather than drifting into both.
No. Annual upfront billing front-loads cash relative to earned revenue and monthly billing does the opposite, so the cash forecast has to be built from billing dates rather than from MRR.
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.
Credit control is the set of decisions made before an invoice exists — who gets terms, how much, and what happens when they slip. Chasing is what you do when those decisions were never made.
AP automation is sold as one product, but it is four separate jobs with very different payback. Capture and matching are where the software earns its price; approval and payment are mostly a question of whether anyone wrote the rules down.
Dynamic pricing in retail means moving prices with demand, stock and competition. It reliably raises margin and just as reliably damages customer trust when the rules behind it are not defensible.