Billing & Invoicing
Chargebee
Rest of world Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Chargebee Inc. · www.chargebee.com
Compare with Recurly → Compare with Stripe Billing → Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Chargebee at a glance
- Vendor
- Chargebee Inc.
- Headquarters
- Not stated on the vendor’s pages as of 26 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 26 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 26 Oct 2026
- Panel verdict
- The AI panel rates Chargebee 3.5/5, the mean of 6 judges. Chargebee is a cloud-based billing and revenue management platform from Chargebee Inc., a US company. how scores are made
- As of
- Vendor pages captured 26 Oct 2026; evaluated by the panel 28 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Chargebee is a cloud-based billing and revenue management platform from Chargebee Inc., a US company. It scores strongest on revenue and handoff and on the subscription engine, both at 8 to 9: documented ASC 606 and IFRS 15 recognition in a drillable revenue subledger with automated journal postings; tiered, usage-based and hybrid pricing with configurable proration and scheduled subscription changes; and collections and dunning at 7 to 8, spanning 40+ gateways with a twelve-retry ceiling on retries. Weakest is sovereignty at 3 to 5: the contracting entity is Chargebee Inc. at a Maryland address, processing may occur in the United States, European Union, India and Australia, and we found no public information on subprocessors or security certifications. Pricing transparency scores 5 to 6: the published tiers are "$0 + 0.80%" and "$99 + 0.65%", while the RevRec, CPQ and Growth modules carry no public price; tax handling scores 6 to 7, where the captured support pages give different pictures of the VAT ID check. Invoicing compliance landed at a uniform 7; weighted totals range from 6.4 to 7.4.
Speaks for it
- Revenue recognition runs to ASC 606 and IFRS 15 in a controlled revenue subledger drillable to the individual transaction, with period locking and summarized journal entries posted automatically to the general ledger
- Tiered, usage-based, flat-fee and hybrid pricing models are documented with a price book and prepaid credits, proration configurable in both the interface and the API, and scheduled future subscription changes
- Collection spans 40+ gateways with routing by market, currency and method, SEPA among the direct-debit schemes, and smart dunning retrying soft declines up to twelve times
- Structured e-invoices are delivered through Peppol, Italy's SDI and India's IRP across 20+ countries including Germany and Denmark, with real-time status tracking
- An open-source customer portal lets customers change plans, add-ons, addresses and card details themselves
Held against it
- Sovereignty scores sit at 3 to 5, with the contracting entity Chargebee Inc. in Maryland, processing locations named as the United States, European Union, India and Australia, and we found no public information on subprocessors or security certifications
- Pricing transparency scores sit at 5 to 6: only two tiers are public — "$0 + 0.80%" and "$99 + 0.65%" — while the Enterprise tier, the RevRec, CPQ and Growth modules and the listed paid add-ons carry no public price
- Tax handling scores sit at 6 to 7: the documented reverse-charge logic under manual taxation keys on the buyer-versus-supplier country difference alone rather than the buyer's tax registration number, and we found no public information on VIES or OSS reporting data
- The terms make the customer solely responsible for exporting service data before termination, assistance may cost a reasonable fee, and we found no public information on a documented migration path for subscriptions and payment tokens
- We found no public information on XRechnung, ZUGFeRD or EN 16931 as named formats, sequential numbering, GoBD-compliant archiving, or a DATEV export
Best for
- You need automated revenue recognition under ASC 606 and IFRS 15, with a drillable subledger, period locking, and journal entries posted to your general ledger on your fiscal calendar
- You sell on tiered, usage-based or hybrid pricing with frequent subscription changes and want customers changing plans, add-ons and card details through a self-service portal
- You collect across many markets and want gateway routing by market, currency and method plus dunning that retries soft declines up to twelve times
- You must send structured e-invoices through Peppol, SDI or IRP across 20+ countries
Avoid if
- You require a demonstrably European or certified processing chain — the contract is with Chargebee Inc., processing may occur in the United States, European Union, India and Australia, and we found no public information on subprocessors or security certifications
- Your VAT treatment must depend on the buyer's tax registration number — the documented manual-taxation logic applies reverse charge on the country difference alone
- You need a guaranteed data exit — the terms make you solely responsible for exporting service data, assistance may cost a fee, and service data is retained for 120 days after termination
- You want a short commitment on the full stack — only Billing Starter and Flow run month-to-month, while other subscriptions run twelve months, auto-renew, and need ninety days' written notice to exit
The scores
| Criterion | Panel median |
|---|---|
| Plans, pricing models & subscription lifecycle | 4.5 of 5 |
| Invoices & e-invoicing compliance | 3.5 of 5 |
| Cross-border VAT & tax handling | 3 of 5 |
| Payment collection, dunning & portability | 4 of 5 |
| Revenue reporting & accounting handoff | 4.5 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 3 of 5 |
Plans, pricing models & subscription lifecycle
Show reasoningHide reasoning
How this is scored
How the product models what is sold and to whom: plans, add-ons and price points, trials, upgrades and downgrades with proration, usage-based and seat-based pricing, contract terms and renewals, quotes, and a self-service portal where the customer changes or cancels their own subscription.
0 — No subscription model; recurring charges are set up by hand per customer or per invoice.
3 — A recurring invoice or a fixed plan that repeats on a schedule, but no proration, no trials, no add-ons and no usage component.
5 — Plans with add-ons and trials, upgrades and downgrades with proration, renewals and cancellations handled by the system, and a customer portal for viewing and changing the subscription.
8 — Usage-based, tiered, volume and seat-based pricing with metering through an API, contracts with minimum terms, ramps and notice periods, quotes that convert into subscriptions, multiple currencies and price books, and the subscription history kept per customer.
10 — The commercial model lives in the product: hybrid pricing (commitments, prepaid credits, overage) without custom code, price changes rolled out to existing customers with grandfathering, entitlements exposed to the selling application, and every change to a subscription versioned and attributed.
The SaaS Founder
Usage ingestion, tiered and hybrid pricing with prepaid credits in a no-code price book, proration choices in both the interface and the API, scheduled future changes, and quotes with approval workflows mean the commercial model really does live in the product. The open-source portal handles plan, add-on and card changes in-app. We found no public information on rolling price changes out to existing customers with grandfathering, which is the one gap between this and the top level. 1 2 5 6 13
The Finance Lead
The commercial model clearly lives in the product: tiered, usage-based and hybrid plans with prepaid credits in a price book, multi-year CPQ quotes with approval workflows, proration I can override per change from the UI or the API, scheduled future subscription changes, and a self-service portal where customers change plans and add-ons themselves. I found no public information on rolling price changes out to existing customers with grandfathering or on every subscription change being versioned and attributed, so I stop just short of the top. 1 2 5 6 13 14
The Billing Engineer
Tiered, usage-based, flat-fee and custom models are documented alongside a price book with prepaid credits and hybrid plans, with usage ingestion up to 100M events a month included and 500M as a paid add-on. Proration is configurable in both UI and API, subscription changes can be scheduled and applied automatically, quotes come through the CPQ module with approval workflows, and an open-source customer portal handles plan changes, add-ons and upgrades inside your own app. I stop short of the top because grandfathering on price changes and versioned, attributed subscription changes are not documented, and entitlements appear only indirectly as pricing and limits enforcement. 1 2 5 6 13
The Service-Business Owner
This is the breadth my two hundred contracts need: tiered, usage-based, flat-fee and hybrid plans with prepaid credits in a price book, proration configurable per business metric with overrides in both the interface and the API, scheduled future subscription changes applied automatically, contract terms and thirty-level account hierarchies on the enterprise plan, and an open-source self-service portal where customers change plans, add-ons, addresses and card details themselves. CPQ quotes with approval workflows and multi-year ramp contracts close the enterprise loop. I found no public information on grandfathering existing customers through price changes or on versioned subscription histories, which is what the very top level describes. 1 2 5 6 13
The Tax Adviser
The commercial model plainly lives in the product: tiered, usage-based and hybrid pricing with prepaid credits in a price book, usage ingestion, proration with configurable methods and overrides in both interface and API, scheduled subscription changes, a self-service and open-source customer portal, and CPQ quoting for multi-year deals. Contracts with minimum terms, ramps and 100-entity account hierarchies are documented, so this sits just under the top anchor; grandfathering of price changes and attributed versioning of every subscription change are not described. 1 2 5 6
The Skeptic
Tiered, usage-based, flat-fee and hybrid models with prepaid credits, a multi-currency price book, CPQ quotes with approval workflows, scheduled subscription changes, proration with API-level override controls, trials and a customizable self-service customer portal are all documented. The enterprise tier adds contract terms, account hierarchies up to 30 levels and up to 100 business entities. We found no public information on grandfathering for price rollouts or on subscription changes being versioned and attributed, which is what the top of this scale asks for. 1 2 5 6 13
Invoices & e-invoicing compliance
Show reasoningHide reasoning
How this is scored
Whether the invoices the product issues are legally valid where the customer is: mandatory invoice content, sequential numbering, credit notes and cancellations instead of edits, retention and archiving to GoBD, and structured e-invoices (XRechnung, ZUGFeRD/Factur-X, Peppol) for business customers and public bodies.
0 — No invoices; the product charges cards or sends payment requests and the seller writes invoices elsewhere.
3 — PDF invoices from a template, but numbering, mandatory content, corrections and retention are not described.
5 — Invoices with sequential numbering and the mandatory content stated, credit notes and cancellations instead of edits, invoices in several languages and currencies, and a documented archive.
8 — Structured e-invoices to EN 16931 issued as XRechnung or ZUGFeRD/Factur-X and sent through Peppol, GoBD-compliant numbering and unalterable archiving stated, invoice data exportable for a tax audit, and the e-invoicing mandates in named EU countries addressed.
10 — Invoicing that stands up in any audit it may face: e-invoicing to public bodies and businesses in several EU countries with the channels named, clearance and reporting models (France, Italy, Poland) supported where they apply, a Verfahrensdokumentation or equivalent offered, and every invoice traceable to the subscription event that produced it.
The SaaS Founder
Structured e-invoices go out through Peppol, Italy's SDI and India's IRP across 20+ countries, with real-time status tracking, recurring e-invoicing, a no-code template builder, credit notes and custom invoice fields. We found no public information on sequential numbering, retention or audit export, and the captured pages do not name XRechnung, ZUGFeRD or EN 16931 — strong on delivery channels, quieter on the German audit specifics I would be asked about. 2 5 7 8
The Finance Lead
Structured e-invoicing is documented through Peppol, SDI and IRP across 20-plus named countries including Germany and Denmark, with real-time status tracking and e-invoices generated automatically even as subscriptions change. I found no public information on sequential numbering, mandatory invoice content, GoBD-compliant archiving, or XRechnung and ZUGFeRD as named formats, which is the first thing my German auditors would ask about. 1 5 7 8
The Billing Engineer
E-invoices are delivered through named networks — Peppol, Italy's SDI, India's IRP — across 20+ countries including Germany and Denmark, with real-time status tracking, recurring e-invoices that follow subscription changes, mandate-adherence claims and a no-code template builder for regional formats, spanning B2B, B2C and B2G. Credit notes, multi-language support and multi-currency invoices are documented, and invoices are described as locally compliant and customizable. I hold back because sequential numbering, GoBD-compliant unalterable archiving, audit export of invoice data and a Verfahrensdokumentation do not appear on the captured pages, and the structured formats are not named as EN 16931, XRechnung or ZUGFeRD. 7 2 5 8
The Service-Business Owner
The captured pages show e-invoicing across twenty-plus countries with Germany and Denmark named, invoices delivered to customers and tax authorities through major e-invoicing networks, real-time status tracking, recurring e-invoices that survive subscription changes, B2B/B2C/B2G scope, plus credit notes, custom invoice fields and multi-language, multi-currency invoices from a no-code template builder. For my public-sector customers I would still want the German format names: I found no public information naming XRechnung or ZUGFeRD, and nothing on sequential numbering, GoBD-compliant archiving or a Verfahrensdokumentation. 1 2 5 7 8
The Tax Adviser
Structured e-invoicing through Peppol, SDI and IRP across 20-plus countries including Germany and Denmark, covering B2B, B2C and B2G, with real-time invoice status tracking and credit notes, is genuinely strong for the mandates that bite this year. What I cannot find anywhere is sequential numbering, GoBD-compliant archiving or an audit export of invoice data, and XRechnung or ZUGFeRD as named formats, so I stop just short of the audit-proof level. 1 2 5 7
The Skeptic
Structured e-invoices delivered through Peppol, Italy's SDI and India's IRP, coverage across 20+ countries with Germany and Denmark named, real-time status tracking, recurring e-invoicing when subscriptions change, credit notes and multilingual invoices are documented. We found no public information on XRechnung, ZUGFeRD or EN 16931 formats, on sequential numbering, on GoBD-compliant unalterable archiving or on a Verfahrensdokumentation, so the audit-hard parts of invoicing rest on the delivery networks rather than documented retention. 2 5 6 7
Cross-border VAT & tax handling
Show reasoningHide reasoning
How this is scored
How the product gets tax right when the seller sells across borders: VAT rates per country and product type, reverse charge for business customers with VAT ID validation (VIES), the EU One-Stop-Shop, US sales tax — or, for a merchant of record, which tax liability it takes on in its contract and which it leaves with the seller.
0 — No tax handling; the seller types the rate on every invoice.
3 — One configurable VAT rate or a manual rate table, with no customer-location logic and no VAT ID check.
5 — Tax rates applied by customer country and status, reverse charge for business customers with a VAT ID field, and tax shown correctly on invoices and in reports.
8 — Automatic VAT per country and product type, VIES validation of VAT IDs, OSS reporting data, evidence of customer location kept, US sales tax through a named engine — or a merchant-of-record contract that states the tax liability it assumes and in which countries.
10 — Tax is discharged and evidenced: filings or filing data for OSS and the countries sold into, rate changes maintained by the vendor with a stated process, tax decisions per invoice explainable, and the division of liability between seller and vendor written into the terms.
The SaaS Founder
Real-time tax rates and US, EU and global tax profiles are included in both plans, and a configurable VAT validation setting blocks invalid VAT numbers at customer creation. But the documentation states reverse charge is applied on the buyer-versus-supplier country difference alone — even when a tax registration number exists — must be enabled per country, and is supported only for cross-border transactions; we found no public information on VIES, OSS reporting data or a named sales-tax engine. For my nine-country setup this is closer to right-with-attention than right-without-thinking. 2 7 9 10
The Finance Lead
Real-time tax rates across US, EU and global regions, configurable cross-border reverse charge with an invoice note, a VAT validation feature that blocks invalid VAT numbers at customer creation, and third-party tax providers that can apply reverse charge independently — that covers the everyday cases. The support pages state reverse charge is applied purely on buyer-versus-seller country even when the buyer holds a tax registration number, and I found no public information on OSS reporting, a named US sales-tax engine, or a vendor-maintained rate-change process. 2 7 9 10
The Billing Engineer
Real-time tax rates are applied automatically with US sales tax, EU VAT and global taxes across multiple tax profiles and regions, and third-party tax integrations can apply reverse charge regardless of the local configuration. Reverse charge is documented in detail — cross-border only, configurable per country, an editable note on the invoice, a VAT number stored on the customer and a validation setting that blocks invalid numbers at customer creation — though on manual taxation the check is country difference alone, without reading the registration number. I found no public information on OSS reporting data, customer-location evidence being kept, or a named US tax engine. 2 7 9 10
The Service-Business Owner
EU VAT and reverse charge are genuinely handled: real-time tax rates with multiple tax profiles and regions, reverse charge on cross-border transactions with an editable note on the invoice, and a VAT number stored on the customer with validation I can switch on so invalid numbers are rejected at customer creation. But VIES is never named, I found no public information on OSS reporting data, kept evidence of customer location, or a named engine behind the US sales tax support, and the documented reverse-charge logic keys on the country difference alone rather than the VAT ID. 2 7 9 10
The Tax Adviser
Real-time rates across US, EU and global tax with multiple tax profiles, and reverse-charge mechanics documented down to the invoice note, are the right shape — but the two support pages give different pictures of the VAT ID check: one states reverse charge is applied whenever buyer and supplier countries differ, even where the buyer has a tax registration number, while another documents a VAT validation setting that blocks invalid numbers at customer creation. We found no public information on VIES validation as such, OSS reporting data, evidence of customer location kept for audits, or a named US sales tax engine, so the tax position is not yet one I could defend unaided at year-end. 2 7 9 10
The Skeptic
Real-time tax rates with multiple tax profiles and regions, US, EU and global sales tax, a VAT number stored on the customer and configurable VAT validation that blocks invalid numbers at customer creation are documented, alongside a reverse-charge mechanism. But the product's own help text says reverse charge is triggered only by the buyer and supplier being in different countries and is not checked against the buyer's tax registration number, and domestic reverse charge is unsupported on manual taxation. We found no public information on VIES validation by that name, on OSS reporting data, or on a named US sales-tax engine. 2 7 9 10
Payment collection, dunning & portability
Show reasoningHide reasoning
How this is scored
How invoices turn into money: which payment providers and methods the product works with, SEPA direct-debit mandates, automatic retries and dunning sequences, payment reconciliation, collections handover — and whether the seller can move subscriptions and stored payment details to another provider.
0 — No collection; invoices are sent and payment is chased by hand.
3 — One built-in payment provider with card payments, and failed payments reported but not retried or chased.
5 — Several payment providers or methods including SEPA direct debit with mandates, automatic retries of failed payments, dunning emails with configurable steps, and payments matched to invoices.
8 — Gateway-agnostic collection across named providers, smart retries and card updaters, dunning with escalation and service suspension rules, bank-transfer reconciliation, a handover to a collection agency, and recovery reported.
10 — Collection is portable and measurable: subscriptions and payment tokens importable and exportable with a documented migration path, routing across providers per country or method, recovered revenue reported per dunning step, and no lock-in to the vendor's own payment service stated in the terms.
The SaaS Founder
SEPA sits among 50+ methods across 40+ gateways routed by market, currency or method; smart dunning retries soft declines up to twelve times with configurable cadence, and a machine-learned retry model reads 200+ signals with a dashboard reporting recovery rates and revenue recovered by method and gateway. Automated reminder workflows and configurable final actions on both the subscription and the invoice complete the picture. We found no public information on card-account updaters, a collection-agency handover or exportable payment tokens, and the terms make exporting my data my responsibility before termination. 1 2 4 11 12
The Finance Lead
Gateway-agnostic collection across forty-plus gateways with routing by market, currency and method, SEPA among the direct-debit methods, smart dunning that retries soft declines up to twelve times and waits for a card update on hard ones, configurable final actions on both the subscription and the invoice, and a recovery dashboard reporting revenue recovered by payment method and gateway. I found no public information on a handover to a collection agency or a documented migration path for subscriptions and stored payment tokens, so I hold below the top. 1 2 4 11 12
The Billing Engineer
Forty-plus gateways with routing by market, currency or method, SEPA among the named direct-debit schemes, tokenization, hosted and full-API checkout, and an Adyen-powered option for unified billing and payments. Dunning is deep: smart retries reading 200+ signals with a 12-retry ceiling and failure playbooks, custom cadences up to 5 retries, configurable final actions on both subscription and invoice, a payment failure dashboard with pre-built cohorts, and a recovery dashboard that reports revenue recovered and benchmarks against your previous retry logic. What I miss is a documented migration path for moving subscriptions and payment tokens out — the terms make export the customer's job and assistance may cost a fee. 2 11 12 4 1
The Service-Business Owner
Collection is the strongest area for me: SEPA direct debit sits among the supported methods, over forty gateways with routing by market, currency and method, smart dunning that reads error codes and retries soft declines up to twelve times, an AI retry model reading 200+ signals with a dedicated recovery dashboard, configurable final actions on both the subscription and the invoice, and automated reminder workflows with pre-built risk cohorts. I found no public information on a handover to a collection agency or on a documented migration path for subscriptions and payment tokens, and the terms place data export responsibility on me, with assistance possibly charged a fee. 1 2 4 11 12
The Tax Adviser
Gateway-agnostic collection across 40-plus providers with routing by market, currency and method, SEPA among the direct-debit methods, smart retries with a documented retry ceiling, configurable final actions on both subscription and invoice, rule-based recovery workflows and a dashboard reporting recovered revenue per gateway and method — that is the full anchor level for collection. Portability is the weak point: we found no public information on a documented migration path for subscriptions and payment tokens, and the terms make the customer solely responsible for exporting data and permit a fee for assistance. 1 2 4 11 12
The Skeptic
Collection is strong: 40+ gateways with routing by market, currency and method, SEPA/ACH/BACS and other direct debit, tokenization, smart retries reading 200+ signals under a 12-retry ceiling, configurable dunning final actions and a dashboard reporting recovery rates and revenue recovered by method and gateway. The portability half of the top level is not: we found no public information on importing or exporting subscriptions and payment tokens with a documented migration path, and the terms make the customer solely responsible for export, allow a reasonable fee for export assistance and destroy all service data 120 days after termination. 1 2 4 11 12
Revenue reporting & accounting handoff
Show reasoningHide reasoning
How this is scored
What finance gets out of billing: MRR, ARR, churn and cohort reporting, revenue recognition and deferred revenue, the export or sync to the accounting system and to DATEV, CRM and data-warehouse integrations, an API and webhooks, and a complete export of customer and subscription data.
0 — No reporting and no export beyond downloading individual invoices.
3 — A revenue overview and a CSV export of invoices, with no subscription metrics and no accounting integration.
5 — Subscription metrics (MRR, churn) on a dashboard, an export or sync to at least one named accounting tool, and a documented API with webhooks.
8 — Revenue recognition with deferred revenue schedules, a DATEV export or booking-ready journal for the ledger, native CRM and accounting integrations named, MRR movements explainable per customer, and a full data export documented.
10 — Billing is the system of record for revenue: recognition to IFRS 15 / ASC 606 stated, month-end close supported with reconciled reports, data-warehouse sync, audit trail of every financial event, and a complete export of customers, subscriptions and invoices that a successor system can import.
The SaaS Founder
Recognition runs on the ASC 606 and IFRS 15 five-step model with a drillable revenue subledger, deferred-revenue waterfall, period locking, automated journal entries to the general ledger, and live ARR and NRR dashboards, plus warehouse exports to Snowflake and S3 at the enterprise tier and an audit trail from signed contract to journal entry. Native CRM and accounting integrations propagate modified invoices and credit notes immediately. We found no public information on a DATEV export, and a successor-importable full export is not fully documented: the terms put export on me, assistance may cost a fee, and data is retained 120 days after termination. 2 4 5 6 13 14
The Finance Lead
This is close to what I close the month on: recognition to ASC 606 and IFRS 15, a revenue subledger drillable to sales order, product, period and transaction, deferred revenue waterfalls, period locks, summarized journal entries posted automatically to the general ledger on my fiscal calendar, an audit trail from signed contract to journal entry, ARR and NRR dashboards with A/R aging and roll-forward, and export to Snowflake, GCS and S3. The handoff gap is real though: no DATEV export is named, and the terms make the customer solely responsible for exporting service data before termination, with assistance possibly at a reasonable fee. 2 4 7 13 14
The Billing Engineer
RevRec runs ASC 606 and IFRS 15 five-step recognition with a controlled revenue sub-ledger drillable to the transaction, deferred-revenue waterfalls and forecasts, an SSP library, period locking, and a complete audit trail from signed contract to journal entry. Summarized journal entries post to the general ledger on your fiscal calendar, A/R aging and roll-forward reports are native, native CRM and accounting integrations reflect modified invoices and credit notes, and there is a REST API with webhooks plus warehouse export to Snowflake, S3 or GCS as an Enterprise add-on. I dock a point because a complete export a successor system could import is not documented, and the terms charge a possible fee for export assistance during the retention window. 13 14 2 7 5 4
The Service-Business Owner
The revenue recognition product is a proper subledger: ASC 606 and IFRS 15 recognition with deferred-revenue waterfalls and multi-year ramps, summarized journal entries posted automatically to the general ledger on my fiscal calendar, period locking, an audit trail from signed contract to journal entry, live ARR and NRR dashboards, A/R aging reports, native CRM and accounting sync, and data export to Snowflake, S3 and Google Cloud Storage as an enterprise add-on. DATEV is the hole for my tax adviser — I found no public information on a DATEV export — and a complete export that a successor system could import is not documented. 2 5 7 13 14
The Tax Adviser
Revenue recognition to ASC 606 and IFRS 15 in a controlled revenue sub-ledger with deferred-revenue waterfalls, drill-down to the individual transaction, period locking, an audit trail from signed contract to journal entry and automated journal posting to the general ledger is exactly what I want to see at an audit. Native CRM and accounting sync, REST APIs with webhooks and warehouse export as a paid add-on round it out; we found no public information on a DATEV export or a complete documented export a successor system could import, which is why this is not a ten. 2 4 5 7 13 14
The Skeptic
Recognition to ASC 606 and IFRS 15 via the five-step model, a controlled revenue subledger with recognition schedules and deferred-revenue waterfalls, AR aging and roll-forward reports, period locking, a complete audit trail from signed contract to journal entry, summarized postings to the general ledger, live ARR and NRR dashboards, native CRM and accounting syncs, data-warehouse export and a documented REST API with webhooks are all evidenced. The one gap is exit: warehouse export sits in the enterprise tier's paid add-ons, and the terms put the export burden on the customer with a possible fee for help rather than documenting a successor-importable export. 2 4 5 7 13 14
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where customer, invoice and payment data are hosted, and who the subprocessors are (hosting, payment providers, tax engines, email delivery). Independently sourced by the sovereignty pipeline; billing data is personal and financial at once, so the whole chain counts, not only the database.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.
5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (tax engine, email, analytics, support) run through non-EU providers without a stated safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor, data export and deletion documented, and certifications published with their scope rather than implied.
The SaaS Founder
The contract is with Chargebee Inc. of North Bethesda, Maryland, processing may occur in the United States, European Union, India or Australia, and we found no public information on an EU hosting commitment, a subprocessor list, or ISO 27001 or SOC 2 certifications — a data processing addendum is incorporated by reference, an Amsterdam entity serves as EU representative, and Data Privacy Framework participation plus standard contractual clauses are stated. For billing data that is personal and financial at once, the chain beyond the database is not evidenced, which sits just above the policy-and-DPA-exist level. 3 4
The Finance Lead
The contracting entity is Chargebee Inc. at a Maryland address, an Amsterdam entity serves as EU representative, and a data processing addendum is incorporated into the terms, with processing locations given only as the United States, European Union, India and Australia. I found no public information on the hosting infrastructure, a subprocessor register for the service, or ISO 27001 or SOC 2 certifications — only commercially reasonable security measures — which is thin comfort for billing data that is personal and financial at once. 3 4
The Billing Engineer
The contracting entity is Chargebee Inc. in Maryland, with an EU representative in Amsterdam and a UK representative, a data processing addendum incorporated into the terms, and Data Privacy Framework participation plus Standard Contractual Clauses for transfers. Processing may occur in the United States, European Union, India and Australia, so EU processing is possible but not committed as hosting; the captured pages list no subprocessors with locations and state no ISO 27001 or SOC 2 certification. Deletion on written request after termination and a 120-day retention period are documented, while Google Analytics and third-party AI processing appear on the website side of the chain. 3 4
The Service-Business Owner
The contract is with Chargebee Inc., a US entity in Maryland, processing may occur in the United States, the European Union, India and Australia, and I found no public information on the subprocessors, on security certifications, or on any commitment to keep billing data in Europe — the stated commitment is only 'commercially reasonable security measures'. A data processing agreement is published and incorporated into the terms, an EU representative in Amsterdam and standard contractual clauses plus Data Privacy Framework participation exist, but nothing here evidences European hosting on named infrastructure. 3 4
The Tax Adviser
The contracting entity is Chargebee Inc. in the USA with an EU representative, Chargebee B.V. in Amsterdam, a data processing agreement incorporated into the terms, and processing locations named as including the EU alongside the US, India and Australia. That earns the mid anchor, but the chain is not sovereign: no subprocessor list, no named EU hosting infrastructure, no security certifications stated, and Google Analytics plus a possible CCPA 'sale' of data via advertising cookies sit in the processing chain, with only framework safeguards such as SCCs and the Data Privacy Framework named. 3 4
The Skeptic
The contracting entity is Chargebee Inc., a US company in North Bethesda, Maryland, with an EU representative in Amsterdam; personal information may be processed in the United States, European Union, India and Australia, with transfers resting on the Data Privacy Framework and standard contractual clauses. A data processing addendum is published and incorporated into the terms. We found no public information on a subprocessor list with locations or on security certifications — the privacy text names Google Analytics and third-party AI providers, and the only stated commitment is "commercially reasonable security measures". 3 4
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: platform fee, percentage of billed revenue or per-invoice fees, which modules (revenue recognition, e-invoicing, tax, extra gateways) cost extra, overage above a revenue band, setup and minimum term, and the merchant-of-record fee where it applies.
0 — No public prices at all; every customer is a sales call.
3 — A starting price or a free tier exists, but how cost scales with billed revenue, invoices or modules is unclear.
5 — Tiers are public with their main inclusions and revenue bands, but at least one commonly needed piece (e-invoicing, revenue recognition, extra gateways, overage) is unpriced or "on request".
8 — Every tier priced publicly with its scaling rule (revenue percentage, per invoice, per subscriber), overage and add-ons listed, minimum term and VAT treatment stated.
10 — Complete price computability: annual cost derivable for a given billed revenue, invoice volume and module set, with every add-on, setup, support and payment or merchant-of-record fee and the cancellation and data-return terms published.
The SaaS Founder
The public rates are "$0 + 0.80%" and "$99 + 0.65%", with 100M usage events a month, tax profiles and multi-currency included in both plans, and the terms state a twelve-month auto-renewing term, taxes excluded, a 90-day non-renewal notice and no downgrades. But the RevRec, CPQ and Growth modules and the enterprise add-ons carry no public prices, and the captured pricing page does not state what the percentage applies to — so I cannot compute my real annual cost from public pages alone. 2 4
The Finance Lead
Two tiers are published with their scaling rules — "$0 + 0.80%" and "$99 + 0.65%" — with 100M usage events/mo included, and the terms state a twelve-month auto-renewing term, ninety days' non-renewal notice, and fees that are non-refundable and exclusive of taxes. The Enterprise tier, its paid add-ons, and the RevRec and CPQ modules beyond the first fifty free quotes carry no published price, so I cannot compute a full annual cost from public pages alone. 2 4
The Billing Engineer
The two billing tiers are priced publicly with an explicit scaling rule — "$0 + 0.80%" up to $500K, then "$99 + 0.65%" — plus 100M usage events a month included and the first 50 quotes free, and the contract terms are equally public: 12-month auto-renewing term, 90-day non-renewal notice, fees non-refundable and exclusive of taxes, 1.5% per month late interest. But the Enterprise tier and the RevRec, CPQ and Growth modules carry feature lists with no prices, every paid add-on (500M events, access controls, data export) is unpriced, and I found no public information on overage above the revenue band. A buyer can price the low end of the stack but not the whole thing. 2 4
The Service-Business Owner
Two tiers are priced publicly with a clear scaling rule on billed revenue — '$0 + 0.80%' and '$99 + 0.65%' — with one hundred million usage events included and month-to-month billing, while the terms state a twelve-month auto-renewing subscription with ninety days' notice, non-refundable fees exclusive of taxes. The revenue recognition module, the enterprise tier, CPQ beyond the first fifty free quotes and every listed paid add-on carry no public price, so I cannot compute the real annual cost of the stack a German service business needs. 2 4
The Tax Adviser
The two published bands are refreshingly concrete — a $0 base plus 0.80%, then $99 plus 0.65%, with 100 million usage events a month included and month-to-month terms for the lower tiers. But a buyer still cannot compute the real annual cost: the Enterprise tier and its listed paid add-ons carry no prices, and we found no public information on what the revenue recognition or e-invoicing modules cost; the twelve-month auto-renewing default term with 90-day non-renewal notice is at least stated in the terms. 2 4
The Skeptic
Two tiers are public with exact scaling rules — "$0 + 0.80%" and "$99 + 0.65%" — plus 100 million usage events per month included, with month-to-month terms for Billing Starter and Flow while other subscriptions run twelve months, auto-renew, need ninety days' notice to exit and are non-refundable and exclusive of taxes. But the enterprise tier and its paid add-ons carry no public prices, and we found no public information on what CPQ, RevRec, Growth or the e-invoicing capability cost, so a buyer cannot compute the real annual total from public pages alone. 2 4
European sovereignty — proven facts
0 of 4 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined | — | uncited Report an error |
| Subprocessors | Not determined | — | uncited Report an error |
Questions about Chargebee
Is Chargebee European?
No. whats-best.ai classifies Chargebee as Rest of world.
Where does Chargebee store data?
Not stated on the vendor’s pages as of 26 Oct 2026.
Does Chargebee have a free plan?
Not stated on the vendor’s pages as of 26 Oct 2026.
What are the best alternatives to Chargebee?
As of 28 Oct 2026, the panel rates Younium (3.5/5), Stripe Billing (3.5/5) and Fakturia (3.5/5) highest among the other 12 Billing & Invoicing products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Younium (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Chargebee alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 26 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 15 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 5 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 data fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 subprocessors fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
Sources (14)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.chargebee.com Checked 26 Oct 2026 Details →
- 2 Pricing page www.chargebee.com Checked 26 Oct 2026 Details →
- 3 Privacy policy www.chargebee.com Checked 26 Oct 2026 Details →
- 4 Terms of service www.chargebee.com Checked 26 Oct 2026 Details →
- 5 Plans, pricing models & subscription lifecycle — found from sitemap www.chargebee.com Checked 26 Oct 2026 Details →
- 6 Plans, pricing models & subscription lifecycle — found from sitemap www.chargebee.com Checked 26 Oct 2026 Details →
- 7 Invoices & e-invoicing compliance — found from sitemap www.chargebee.com Checked 26 Oct 2026 Details →
- 8 Invoices & e-invoicing compliance — found from sitemap www.chargebee.com Checked 26 Oct 2026 Details →
- 9 Cross-border VAT & tax handling — found from sitemap support.chargebee.com Checked 26 Oct 2026 Details →
- 10 Cross-border VAT & tax handling — found from sitemap support.chargebee.com Checked 26 Oct 2026 Details →
- 11 Payment collection, dunning & portability — found from sitemap www.chargebee.com Checked 26 Oct 2026 Details →
- 12 Payment collection, dunning & portability — found from sitemap www.chargebee.com Checked 26 Oct 2026 Details →
- 13 Revenue reporting & accounting handoff — found from sitemap www.chargebee.com Checked 26 Oct 2026 Details →
- 14 Revenue reporting & accounting handoff — found from sitemap www.chargebee.com Checked 26 Oct 2026 Details →