Back to blog
automation·June 19, 2026·9 min read·By Yehonatan Saadia

How to Automate Recurring Billing: Subscriptions, Dunning, and Receipts

A practical guide on how to automate recurring billing - subscriptions, failed-payment retries and dunning, automatic invoices and receipts, the right tools, and the steps to set it up.

If your business charges customers on a repeating basis - a subscription, a retainer, a membership, a monthly service - then recurring billing is quietly one of the most important systems you own. Done by hand it is a nightmare: chasing renewals, re-running failed cards, writing invoices, remembering who is on which plan. Done automatically it runs itself and you barely think about it. In this guide I will show you how to automate recurring billing end to end: the subscription lifecycle, the failed-payment recovery that quietly saves real revenue, automatic invoices and receipts, the tools that do the heavy lifting, and the order I set it all up in.

The thing most owners underestimate is how much money leaks out of a manual or half-automated billing setup. A card that expires and never gets re-charged. An invoice you forgot to send. A customer who churned because nobody followed up on a failed payment. Automation does not just save you time here - it directly protects revenue you have already earned.

How to automate recurring billing: define your plans first

Before you touch any tool, get clear on what you actually sell. This sounds obvious, but messy plan structures cause most billing headaches. Decide:

  • What you charge for - per seat, per usage, a flat fee, tiers.
  • How often - monthly, annual, or both, and whether annual gets a discount.
  • Trials and intro offers - free trial, paid trial, or none.
  • Upgrade and downgrade rules - what happens to the charge when someone switches plans mid-cycle.

Nail this down on paper first. Changing your plan structure after hundreds of customers are subscribed is painful, so the clarity you build now pays off for years.

Pick a platform and let it hold the cards

The heart of automated billing is a platform that securely stores customer payment details and charges them on a schedule. You should never store card numbers yourself - it is a security and compliance burden you do not want. Let a specialist handle it.

ToolBest forNotes
StripeSaaS, online services, developersPowerful subscriptions, dunning, invoices; handles tax
Paddle / Lemon SqueezyDigital products, software salesMerchant of record - they handle global tax for you
Local providerRegion-specific cards and invoicingBetter local payment methods and compliant invoices
PayPal subscriptionsSimple, low-volume recurringEasy to start, less flexible automation

For most software and service businesses, Stripe is the default for good reason: its subscription engine handles plans, proration, retries, and invoices out of the box. If selling globally and the tax paperwork scares you, a merchant-of-record platform like Paddle takes that entire burden off your plate. Match the tool to your product and your customers' location.

Automate the whole subscription lifecycle

A subscription is not a one-time charge; it is a relationship that changes over time. Good billing automation handles every state without you lifting a finger:

  • Sign-up: customer subscribes, card is stored, first charge runs, access is granted.
  • Upgrades and downgrades: customer switches plans and the next charge adjusts automatically, prorated for the time used.
  • Pauses: let customers pause instead of cancelling, which saves far more of them than an all-or-nothing choice.
  • Cancellations: handled cleanly, with access ending at the right time and a final receipt.

The key principle: customers should be able to manage their own subscription through a self-service portal without emailing you. Every change they can make themselves is a support ticket you never have to handle.

Dunning and retries: where the real money is

This is the part most businesses get wrong, and it is the most valuable. Cards fail all the time for boring reasons - expired card, insufficient funds, a bank block, a temporary glitch. If you do nothing, every one of those failures is a lost customer. Dunning is the automated recovery process, and it has two parts.

First, smart retries: instead of trying the card once and giving up, the platform retries on an intelligent schedule - a day later, three days later, a week later - because many failures are temporary and clear on their own. Second, reminder emails: a polite sequence telling the customer their payment failed and asking them to update their card, with a direct link to do it. Together, good dunning recovers a large share of failed payments that would otherwise just vanish. This is the same follow-up logic I apply to leads in automating lead follow-up and to overdue invoices in automating invoicing and payment reminders - persistent, polite, automatic.

Automatic invoices, receipts, and tax

Every successful charge should produce paperwork automatically. The customer gets a clean receipt or invoice in their inbox the moment they are charged, and your accounting records it without anyone typing anything. Crucially, the system should apply the correct tax or VAT based on the customer's location - this is where a lot of businesses quietly fall out of compliance. The major billing platforms either calculate tax for you or, in the merchant-of-record model, handle the entire tax filing on your behalf. Set this up once and your books stay clean forever.

Monitor the metrics that matter

Once billing runs itself, the job shifts to watching the numbers. The ones worth a dashboard are:

  • Monthly recurring revenue (MRR) - the heartbeat of a subscription business.
  • Churn rate - how many customers cancel each month, and why.
  • Failed-payment recovery rate - what share of failed charges your dunning saves.
  • Trial-to-paid conversion - if you offer trials.

These tell you whether the system is healthy and where to improve. A small lift in recovery rate or a small drop in churn compounds into serious money over a year.

Connect billing to the rest of your business

Billing should not be an island. The real power comes from piping billing events into your other systems so the whole business reacts automatically. When someone subscribes, your CRM creates a customer record. When a payment fails, your support team gets a heads-up. When someone cancels, a win-back email fires. This is exactly the joined-up thinking I describe in business automation for small business - billing is one node in a connected system, not a standalone tool. When you go fully custom, the cost trade-offs are worth understanding too; I cover them in how much business automation costs.

A realistic order to build it

Build it in this sequence and each step works before you add the next: define your plans on paper, set up the platform and connect payments, wire the subscription lifecycle with a self-service portal, turn on dunning and retries, enable automatic invoices and tax, then connect billing events to your CRM and email tools. Start with the basics and let recovery and reporting come once the core is solid.

If you want recurring billing automated properly - subscriptions, dunning that actually recovers revenue, compliant invoices, and the whole thing wired into your CRM and accounting - book a call and tell me how you charge customers today. I will map the setup that fits your product and give you an honest plan. You can also reach me through the contact form.

#how to automate recurring billing#recurring billing#subscriptions#dunning#stripe

Frequently asked questions

What tool should I use to automate recurring billing?

For most software and service businesses, Stripe is the default because its subscription engine handles plans, proration, retries, and invoices out of the box. If you sell digital products globally and want someone else to handle worldwide tax, a merchant-of-record platform like Paddle or Lemon Squeezy takes that burden off you. For region-specific cards and compliant invoices, a local provider can be better. Match the tool to your product and where your customers are.

What is dunning and why does it matter?

Dunning is the automated process of recovering failed payments. Cards fail constantly - expired, insufficient funds, bank blocks - and without recovery each failure is a lost customer. Dunning has two parts: smart retries that re-attempt the charge on an intelligent schedule because many failures are temporary, and a sequence of polite reminder emails asking the customer to update their card. Good dunning recovers a large share of failed payments that would otherwise vanish, which is why it is the most valuable part of billing automation.

Do I have to store customer credit card numbers?

No, and you should not. A billing platform like Stripe or Paddle securely stores the payment details and charges them on schedule, so you never touch the card number yourself. This removes a major security and compliance burden - storing cards yourself means meeting strict PCI requirements you almost certainly do not want to take on. Let the platform hold the cards and you focus on your product.

How does automated billing handle invoices and tax?

Every successful charge generates and sends an invoice or receipt automatically, and the system applies the correct tax or VAT based on the customer's location. The major billing platforms either calculate the tax for you or, in the merchant-of-record model, handle the entire tax filing on your behalf. This keeps your books clean and keeps you compliant with zero manual work - you set it up once and it runs forever.

Can recurring billing connect to my CRM and accounting?

Yes, and this is where it gets powerful. Billing events can be piped into your other systems so the whole business reacts automatically: a new subscription creates a customer record in your CRM, a failed payment alerts support, a cancellation triggers a win-back email, and every charge flows into your accounting. Connecting billing to the rest of your stack turns it from a standalone tool into one node in a coordinated system that runs your business.

Keep reading

About the author

Yehonatan Saadia

Freelance automation, web & MVP engineer

I'm Yehonatan Saadia, a senior engineer who builds business automation, custom websites, and MVPs for small and mid-sized companies across the US, Europe, and Israel. These guides come from real client work, not theory.

Work with me

Have a project like this?

Tell me what you're trying to automate or build and I'll tell you the fastest reliable way to ship it.