Chargebee vs Recurly

Billing model and price basis

A B2B SaaS billing platform has two pricing questions. The first is what your product charges customers: a fixed plan, per-seat quantity, usage, a tiered allowance, annual commitment or negotiated quote. The second is what the billing vendor charges your company for operating that system. Keep those questions separate. A platform fee based on monthly invoicing volume can rise even when the product catalog remains unchanged, while a customer usage tier can change an invoice without changing the vendor contract.

Chargebee’s current Flow listing gives two choices: $0 plus 0.80% of monthly invoicing volume, or $99 plus 0.65%. The published breakeven is $66K. At $66K, the percentage component is $528 in the first option, while the base option is $99 plus $429, also $528. Make the decision against the contract definition of invoicing volume, including credits, refunds, taxes and annual invoices. Do not apply the percentage to MRR automatically.

Recurly pricing is on request for this entry. Ask for the calculation basis, included subscribers or invoices, gateway scope, API limits, support, implementation and renewal terms. If Recurly quotes a flat platform fee, compare it with the Chargebee percentage on the same forecast. If it quotes a revenue component, put both formulas into one model and show the breakpoints.

Both vendors should be evaluated on total running cost. Include engineering time for API and webhook work, finance time for reconciliation, support time for amendments, tax-service charges, gateway charges and the one-time cost of moving subscriptions and tokens. A cheaper tier can cost more if it forces manual work or a second system for quotes and revenue schedules.

• Define monthly invoicing volume the same way for both proposals.
• Separate platform, payment, tax, accounting and services costs.
• Model a base month, growth month and month with refunds or a large annual invoice.
• Ask for renewal pricing and minimum term.

Plan catalog, usage and quote-to-cash

Start with a catalog workshop rather than a generic feature list. Write down every plan, add-on, entitlement, quantity, usage event and invoice line. A B2B SaaS catalog may combine a platform fee, seats, included workflow runs, overage units and a negotiated annual minimum. It may need a parent account with subsidiaries and a contract that starts on a date different from the first invoice. The platform must preserve those decisions without making finance rebuild them in a spreadsheet.

Chargebee’s Flow listing calls out a price book and invoicing, usage-based billing, usage limits and alerts, and up to 100 million usage events per month. Test idempotency, late events, duplicate imports, included units, credits, overages, rounding and invoice presentation. Engineering should verify that a plan change updates product access at the intended moment.

Test Recurly against the same catalog. Create a base subscription, an add-on, a seat quantity, a trial, a coupon and a metered or threshold component if your product needs one. If an external usage service or CRM is required, document who owns the final invoice and how a failed sync is corrected. A clean checkout does not prove that a late usage event can be audited and billed once.

Quotes and CPQ matter when a sale includes negotiated discounts, start dates, ramp schedules or approvals. Chargebee lists CPQ Lite as free for the first 50 quotes for Billing customers; Enterprise materials list approvals on price points and contract terms. Ask how a quote becomes a subscription, how amendments reference the contract and how finance sees list price, discount and net invoice. For Recurly, determine whether those controls are native or belong in a CRM, CPQ tool or custom service.

1. Draw a self-serve plan, sales-led plan and usage component.
2. Create monthly, annual, prepaid, trial and negotiated test customers.
3. Replay normal, duplicate, late and corrected usage.
4. Approve a quote, change its start date, amend seats and reconcile the invoice.

Revenue recognition, tax and finance controls

Billing and revenue recognition are different systems. An invoice states what the customer owes; RevRec determines when performance obligations become revenue. Annual prepayments, implementation fees, usage, discounts and amendments need schedules that finance can explain during close. Map contract, invoice, cash, deferred revenue and recognized revenue objects before choosing a tier.

Chargebee lists RevRec as a separate product and says to request pricing. Ask whether the proposed setup supports contract modifications, allocations, deferred revenue, multiple books, catch-up entries, schedules, audit history and accounting exports. A Billing subscription that looks right in a product demo does not prove that the close will work without manual journals.

For Recurly, ask whether schedules are native, exported or owned by an accounting or ERP integration. Have finance inspect a multi-year contract with an annual prepayment, onboarding fee, discount, mid-cycle upgrade and refund. Require an explanation of the journal or schedule outcome, not only a dashboard.

Tax needs a parallel review. Chargebee lists US sales tax, EU VAT and global taxes, while its gateway list includes cards, wallets and direct debit. Confirm where tax is calculated, where exemption evidence is stored, how VAT IDs are checked and how a credit note changes tax. Ask Recurly to show domestic, EU reverse-charge and tax-exempt cases.

• Give finance a contract-to-cash test pack before accepting a proposal.
• Ask for journal, schedule and credit-note examples.
• Define which system owns tax, exemption evidence and invoice numbering.
• Document integration sync direction, retries and correction ownership.

Dunning and failed-payment recovery

Failed payments are an operations workflow, not only a retry setting. A card can fail because it expired, a bank rejected a debit, a fraud check blocked it or a customer has a temporary issue. The platform must retry at a sensible cadence, notify the right contact, offer a secure card-update route, preserve subscription state and tell support what happened. Test Chargebee and Recurly with the same failure matrix and communication policy.

Chargebee lists smart dunning and multiple reminders or follow-ups on Flow. Define the first failed event, retry schedule, grace period, invoice status, customer notice, payment-method update and final cancellation or pause. Confirm that a successful retry stops reminders, that manual payment is logged and that finance can distinguish recovery from write-off.

For Recurly, request a concrete demonstration of retry timing, configurable rules, payment-update links, portal behavior, grace periods and reports by failure reason. Test a subscription with an outstanding invoice that changes plan during dunning. The resulting invoice, credit, access change and communication should be clear to support and finance.

Do not promise a recovery percentage without a source and cohort definition. Measure time from failure to notice, payment-method updates, manual touches, recovered invoice value, false cancellations and support escalations. A clear event trail is more useful than a headline that does not match your gateways or geography.

1. Create expired-card, insufficient-funds, bank-rejection and temporary-error failures.
2. Log retry, email, invoice, access and support states at each step.
3. Update the payment method and confirm reminders stop cleanly.
4. Export recovery data and reconcile it to invoices and settlements.

Migration of subscriptions and payment tokens

Moving a live subscription base is a data and payment-vault project. Inventory customers, plans, quantities, add-ons, coupons, trial dates, billing anchors, tax attributes, invoices, credits, payment methods and gateways. Decide which history remains searchable. A migration that moves only active subscriptions can still fail when support needs an old invoice or finance needs a credit trail.

Chargebee explicitly lists migration support and billing-data portability, including payment methods. Ask for a gateway-specific runbook. Confirm source and destination vaults, token format, consent, PCI boundary, mapping and reconciliation. Ask who handles tokens that cannot be moved and whether a customer must re-enter a card.

For Recurly, request the same detail. Token migration may depend on the current gateway, and some methods may require customer action. Ask whether it imports next-bill dates, coupons, credits and historical invoices, and how it prevents a duplicate charge. Require a reconciliation artifact, not only a clean-import promise.

Use a staged migration. Export source records, map old plan IDs, import a small cohort, calculate the next invoice in both systems and compare tax, discount, credit and payment outcomes. Set a freeze window, name the approver, retain a rollback path and reconcile active subscriptions, open invoices, tokens, credits and the first settlement after cutover.

1. Inventory active and historical objects, gateways, tax data and contacts.
2. Map plans, add-ons, quantities, dates, currencies and payment methods.
3. Run a sandbox import and compare invoices, tax, discounts, credits and access.
4. Transfer tokens with gateway and compliance owners and reconcile the count.
5. Cut over in a defined window and retain the source export for audit.

Worked B2B SaaS scenario at $100,000 MRR

Consider a B2B SaaS company with $100,000 MRR, 420 business customers and a six-person finance and operations group. Sixty percent of revenue is an annual commitment billed upfront and the rest is monthly. The product charges a platform fee plus seats and usage over an included allowance. Sales creates 35 negotiated quotes each month. The company uses Stripe for cards, ACH for larger US accounts and an external tax service for US and EU obligations. It wants a safe catalog, reliable dunning and a path to RevRec.

For Chargebee Flow, the $99 plus 0.65% option produces an illustration at $100,000 monthly invoicing volume: $99 + (0.0065 × $100,000) = $749 for the platform component that month. This is derived from the published formula, not a complete bill. Model gateway processing, tax-service costs, separate RevRec or Enterprise scope, implementation and the effect of annual invoices or credits on the invoicing base. The $0 plus 0.80% option would be $800 at the same volume.

Do not assign Recurly a guessed price. Request a proposal using the same 420 customers, $100,000 MRR, invoicing volume, gateway mix, 35 quotes, usage events, tax countries, support level and migration scope. The quote should state whether pricing is flat, revenue-based or another measure. Put separate gateway, usage or service charges on their own rows.

The pilot uses a monthly self-serve account, an annual enterprise account with a discount and a usage-heavy account that exceeds its allowance. The team creates each plan, imports usage, changes seats, issues a credit, fails a payment, updates the method, exports accounting data, approves a quote, generates the first invoice and checks tax. Choose the system with fewer ambiguous handoffs for product, finance, support and engineering.

If the company expects more entities, parent-child accounts, contract approvals and complex usage, Chargebee merits the first technical evaluation. If the catalog stays standard and the team values focused recurring billing, Recurly may fit, subject to a successful usage, dunning, tax and migration demonstration. The final choice follows the same scenario and written scope.

• Chargebee illustration: $99 + 0.65% × $100,000 = $749.
• The illustration excludes gateways, tax services, RevRec, Enterprise, implementation and migration.
• Recurly remains pricing on request until a comparable proposal is supplied.
• Use the same assumptions in both evaluations.

How to choose and questions for the proposal

Choose Chargebee first when the catalog has multiple price books, usage events, hybrid charges, negotiated quotes, parent-child accounts or a finance-led need for revenue operations. Its published product information gives concrete questions about Flow, Enterprise, CPQ Lite and RevRec. The choice still depends on implementation and commercial scope.

Choose Recurly first when the immediate problem is recurring subscription administration and the team wants a focused workflow for plans, payments, dunning and self-service. This recommendation depends on a proposal that demonstrates gateways, usage behavior, tax, quote handoff, reporting and migration. A simpler product can fit better when the catalog is stable and integrations are owned.

Ask both vendors for the same evaluation workspace. Require written answers about price basis, volume, gateways, tax, token transfer, dunning stop conditions, API limits, webhook retries, support, export, contract term, renewal changes and retention. Have product, engineering, finance, tax and support sign off on the workflow each owns.

• Show the complete catalog, including usage, seats, annual prepay, discounts and amendments.
• Show quote, approval, subscription, invoice, payment failure, recovery and credit-note paths.
• Show tax, gateway, token, accounting and RevRec boundaries.
• Separate software, services, gateway, tax and migration costs.
• Name owners for catalog governance, dunning, reconciliation and support.