Choosing an automated billing system comes down to five questions: the pricing models you need now and next year, bundled processing versus your own gateway, the fee math at your volume, how failed payments get recovered, and how painful migration will be. Answer those before reading feature lists and the shortlist builds itself.
Start With Your Pricing Model, Not the Vendor List
Most billing evaluations start backwards: a vendor list, then a feature shootout. Start with your pricing instead. Write down every pricing model you run today and every one your roadmap might need in the next two years — flat-rate, per-seat, tiered, usage-based, hybrid — then drop every platform that cannot express them natively.
This is where expensive mistakes happen: a platform that handles flat subscriptions beautifully can fail the moment you add metered usage, because usage billing needs metering infrastructure, a rating engine, and entitlements at scale — it is not a feature you bolt on. If your AI product will meter tokens or API calls next year, confirm the platform meters events first-class today, not through a workaround. Our guide to usage-based billing explains what real metering support looks like.
Also list edge cases — converting trials, coupons with expiry dates, mid-cycle proration, multi-currency price books — and make the vendor demo each one live.
Checklist item: Document today's pricing models plus the two-year roadmap. Shortlist only platforms that support all of them natively.
Gateway Strategy: Bundled Processing vs Bring-Your-Own
The biggest structural decision is whether the billing layer and payment processing live with one vendor or two:
- Bundled (one vendor does both). Stripe Billing is the classic example: one contract, one dashboard, billing-layer and processing fees on one invoice. The tradeoff is lock-in — billing logic and money movement are tied to the same provider, and you cannot shop processing rates independently.
- Bring-your-own gateway (billing layer only). Platforms like Chargebee and Recurly orchestrate subscriptions and invoicing, then hand charges to whichever gateway you connect — so you can change processors without rebuilding billing. The tradeoff is two vendor relationships and two fee lines to model.
Neither is universally better. Bundled wins for small teams that value simplicity; bring-your-own wins once processing-rate negotiation becomes real money, you sell across regions with different payment methods, or you want a failover gateway.
A third option for teams that dread tax compliance: merchant of record services like Paddle — the legal seller of record, handling tax collection worldwide (see our Paddle vs Stripe comparison).
Checklist item: Decide bundled vs bring-your-own before comparing vendors. Already processing with Stripe and not planning to leave? Bundled is the path of least resistance. Need gateway flexibility? Filter for gateway-agnostic platforms first.
Run the Volume Math: Percentage vs Flat Fees
Billing platforms price in two shapes — a percentage of your billing volume, or a flat monthly fee (sometimes with a percentage on top) — and the cheaper shape depends entirely on your volume. Model three points: today, the 12-month projection, and the 24-month projection.
Worked example using published 2026 pricing — verify the vendor's current pricing page before signing, since figures change. Take a business billing $100,000/month:
- Percentage-shaped (Stripe Billing pay-as-you-go, 0.7% of billing volume): 0.007 × $100,000 = $700/month for the billing layer.
- Percentage-shaped (Chargebee Flow pay-as-you-go, 0.80%): 0.008 × $100,000 = $800/month.
- Flat-plus-percentage (Recurly Starter, $249/month + 0.9% above a $40,000 allowance): $249 + 0.009 × ($100,000 − $40,000) = $789/month.
Three structures, three answers within $100 of each other — at this volume. Move the volume and the answer flips: flat fees win at low volume (the percentage of a small number is tiny, but a $249 floor is not), percentages win when volume grows enough that the flat fee would have been cheaper as a fraction. Our billing-volume pricing guide has the crossover math in full.
Two traps. First, free allowances change the math: Recurly's Starter leaves the first $40,000 of monthly billings uncharged, so check what the percentage applies to. Second, annual commitments discount fees or percentages — model the committed price against the risk your volume lands below the tier you bought.
Checklist item: Model billing-layer cost at today's volume, 2× volume, and 5× volume. Include processing fees in every total. Read the fine print on allowances and annual commitments.
Dunning and Recovery: Ask for the Specifics
Failed payments are a quiet revenue leak — cards expire, banks decline, accounts run dry — and dunning (the retry-and-remind machinery) is where billing platforms earn their fee many times over. But "we have dunning" on a feature page tells you nothing. Ask:
- How many retry attempts, on what schedule? Fixed or configurable? Can you set different policies for different customer segments?
- Are retries smart or static? Static retries attempt the card again on fixed days; smart retries use machine learning to pick the moment a retry is most likely to succeed. Stripe includes Smart Retries in its Billing pricing; Recurly gates its intelligent retries to higher tiers.
- How many dunning campaigns can you run? One campaign for everyone, or separate sequences for trials vs annual plans vs high-value accounts?
Then ask for numbers: typical recovery rates and anonymized benchmarks. See our dunning management guide for how recovery mechanics translate into recovered revenue.
Checklist item: Get the retry schedule, campaign count, and smart-vs-static retry details in writing. Treat dunning as a revenue feature, not a checkbox.
Tax, Compliance, and Where You Sell
Billing systems calculate tax; they do not all handle tax. Know which you are buying:
- Tax calculation (what most billing platforms offer, sometimes as an add-on like Stripe Tax): the system applies the right rate at checkout based on the customer's location and your nexus settings. You still file and remit.
- Tax compliance as a service / merchant of record (Paddle and similar services): the vendor is the seller of record — it collects tax, files, and remits. You get a payout, not a tax headache.
B2B in one country usually needs only calculation; selling B2C across the EU, the US, and beyond makes the filing burden grow fast — get a straight answer on what the platform files versus what your accountant must handle.
Beyond tax, confirm the basics: PCI DSS (cards should be tokenized so raw card data never touches your servers — verify), SOC 2 Type II reports for enterprise buyers, GDPR data-processing terms for EU customers, and e-invoicing support (formats like PEPPOL) where regions mandate it.
Checklist item: Map every country you sell in (and plan to) against the platform's tax and e-invoicing support. Get the DPA and compliance reports before procurement asks for them.
Integrations: API, Webhooks, Accounting, CRM
Evaluate three integration surfaces:
- API quality. You will create subscriptions, change plans, and pull invoices programmatically. Read the API docs before the sales call — clear docs with working examples are a reliable proxy for engineering quality. Check for official SDKs in your stack's language.
- Webhooks. Billing is event-driven:
invoice.paid,subscription.updated,payment.failed. Your product needs these events to grant access, send onboarding emails, and trigger dunning flows. Confirm the event catalog covers your use cases and that delivery has retries and signing. - Accounting integration. Invoices, payments, refunds, and credit notes should flow into your accounting software (QuickBooks, Xero, NetSuite) without CSV exports. Ask whether the integration is native and bidirectional.
Also check the customer portal: customers update payment methods, change plans, and download invoices there — and an off-brand portal erodes trust at the exact moment a customer is paying you.
Checklist item: Read the API docs yourself. Confirm native accounting and CRM integrations. Test-drive the customer portal as if you were a paying customer.
Migration and Implementation Reality
Every billing-platform switch is two projects: moving the logic (plans, prices, coupons) and moving the money (customers and their payment methods). Payment-method data moves through secure vault-to-vault transfers between PCI-compliant providers, coordinated with both vendors — that is where migrations usually fail.
Before you sign, ask:
- Who does the migration? A dedicated migrations team, a self-serve importer, or "here are the docs, good luck"?
- What is the realistic timeline? Weeks for a few hundred subscriptions; a quarter for tens of thousands with custom contracts. Anyone promising days for a complex book is selling, not planning.
- How are trials and billing dates preserved? A migration that resets every customer's billing date to the switch date will spike support tickets and churn.
Also budget your team's time: somebody has to map every plan, coupon, and edge case onto the new system (our migration guide covers the full playbook).
Checklist item: Get migration support, timeline, and parallel-run options in writing. Assign an owner before the contract is signed.
Total Cost of Ownership Worksheet
Put every quote through the same worksheet so structures compare apples to apples:
| Cost line | What to enter |
|---|---|
| Billing-layer platform fee | Monthly fee and/or % of volume at your current volume |
| Processing fees | Your gateway's per-transaction rate × expected transaction count |
| Tax product | Included, add-on price, or separate vendor |
| Revenue recognition | Included or add-on (matters once finance needs ASC 606) |
| Add-ons you will actually use | Dunning upgrades, CPQ, analytics, extra seats |
| Implementation | Migration services, onboarding fees, your team's time |
| Annual commitment discount | Only if you would sign annual on day one |
Run the worksheet at today's volume and at 3× volume — the platform that wins today often loses at 3×, because percentage pricing gets pricier as you grow while flat fees get cheaper per dollar billed.
- Start from your pricing models and two-year roadmap — eliminate platforms that cannot express them natively.
- Decide the gateway strategy first: bundled processing (simpler, one vendor) vs bring-your-own gateway (flexible, two fee lines).
- Model billing-layer cost at 1×, 2×, and 5× volume, always including processing fees.
- Interrogate dunning specifics — retry schedules, smart vs static retries, campaign counts — not the checkbox.
- Map tax and compliance needs country by country; confirm PCI, SOC 2, and e-invoicing support.
- Read the API docs yourself, confirm native accounting/CRM integrations, and test the customer portal.
- Get migration support, timeline, and parallel-run options in writing before signing.
FAQs
What is the most important factor when choosing a billing system?
Pricing-model fit. If the platform cannot natively express the pricing you run today and the pricing your roadmap needs in two years — especially usage-based or hybrid models — every other feature is irrelevant.
Should I choose a billing platform that includes payment processing?
If you already process with Stripe and have no plans to leave, a bundled platform like Stripe Billing is the simplest path. If you want to negotiate processing rates, use regional gateways, or keep a failover processor, choose a gateway-agnostic billing layer like Chargebee or Recurly and bring your own gateway.
What should I ask about dunning during a demo?
How many retries on what schedule, whether retries are machine-learning-optimized or fixed, how many dunning campaigns you can run, and what the customer sees (emails, hosted card-update page). Ask for typical recovery-rate benchmarks.
How long does it take to migrate billing platforms?
Weeks for a few hundred simple subscriptions; a full quarter for tens of thousands with custom contracts. The critical path is usually the secure transfer of payment-method tokens, not the software configuration. Always ask about parallel-run options.
Conclusion
Choosing a billing system is a structural decision, not a feature comparison. Get the structure right and the shortlist nearly writes itself. Get it wrong and you will be migrating in eighteen months — the most expensive billing project there is.
Work the checklist in order, model total cost at three volumes, and read the API docs before the sales call — then see how Stripe Billing, Chargebee, and Recurly score.
Sources: Chargebee's features overview (gateway-neutral billing record, 30+ gateway connections, ASC 606/IFRS 15 revenue recognition); Stripe's published Billing pricing page (0.7% pay-as-you-go billing-layer pricing).