Billing & Invoicing
Zuora
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Zuora, Inc. · www.zuora.com
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.
Zuora at a glance
- Vendor
- Zuora, Inc.
- Headquarters
- Not stated on the vendor’s pages as of 3 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 3 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 3 Nov 2026
- Panel verdict
- The AI panel rates Zuora 3/5, the mean of 6 judges. Zuora's strength in this billing and invoicing bench is the subscription engine: five of six judges scored it 7, pointing to a documented quote-to-subscription lifecycle with amendment, renewal and cancellation quotes, ramp deals, usage charges and multi-currency billing. how scores are made
- As of
- Vendor pages captured 3 Nov 2026; evaluated by the panel 3 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Zuora's strength in this billing and invoicing bench is the subscription engine: five of six judges scored it 7, pointing to a documented quote-to-subscription lifecycle with amendment, renewal and cancellation quotes, ramp deals, usage charges and multi-currency billing. Collections and dunning and tax handling follow — a long named gateway list with settlement reconciliation and card-only configurable or AI-driven retry, plus tax rates down to county, zip and geocode with effective dating. Invoicing compliance scored 6 across the bench: PEPPOL BIS 3.0 XML export from your own templates is generally available, but Zuora states it is not a PEPPOL access point and ships no prebuilt integrations, so sending runs through partners such as Sovos. Revenue reporting and accounting handoff is weakest at 4-6, the only two-point spread: judges credited deep MRR reporting, while the skeptic's 4 reflects exports narrowed to Invoice PDF and a users list CSV and no public information on deferred revenue schedules or webhooks. Every sovereignty attribute is recorded as unknown and scored 0; no prices appear on the captured pages.
Speaks for it
- Quotes convert into subscriptions with documented amendment, renewal and cancellation flows, ramp deals, usage charges and multi-currency billing.
- Collections span a long named gateway list — Adyen, GoCardless, SlimPay, Worldline, Worldpay and more — with batch reconciliation against gateway settlement reports.
- PEPPOL BIS 3.0 XML generation from your own templates is generally available, with country-specific e-invoicing templates.
- Tax rates apply down to county, zip and geocode level with effective dating, per-account exemptions and an Avalara integration.
- MRR and TCV reporting is editable to any point in time and groupable by account, product, subscription or rate plan.
Held against it
- Zuora states it is not a PEPPOL access point and PEPPOL Extract includes no prebuilt integrations, so sending runs through partners such as Sovos.
- The documentation states tax rates are invoice display amounts, not remittance amounts, and no public information was found on VIES VAT ID validation, reverse charge or One-Stop-Shop.
- Configurable Payment Retry supports card payments only, with ACH, SEPA, BACS and PAD documented as unsupported.
- The available predefined exports are Invoice PDF and All Users List CSV, with other data exports deprecated, and no public information on deferred revenue schedules, a DATEV export or webhooks.
- No public information was found on any sovereignty attribute — contracting entity, data residency, hosting, DPA — or on prices, tiers or fees.
Best for
- You sell subscriptions quote-first out of a Salesforce org and need amendment, renewal and cancellation quotes plus ramp deals in a documented flow.
- You collect card payments across many gateways and want reconciliation against settlement reports plus configurable or AI-driven retry.
- You maintain your own tax rate tables (CSV, Taxware or CCH) or use Avalara and need rates applied to fine geographic levels.
- You can build the PEPPOL sending leg yourself and want PEPPOL BIS 3.0 XML generated from your own invoice templates.
Avoid if
- You expect the billing vendor itself to act as a PEPPOL access point or to ship prebuilt e-invoicing integrations.
- You rely on automated payment retry for direct debit methods such as SEPA, ACH, BACS or PAD.
- You need the product's tax figures as remittance amounts — the documentation presents them as invoice display amounts.
- Your month-end close needs booking-ready accounting exports — the documented predefined exports are Invoice PDF and a users list CSV.
The scores
| Criterion | Panel median |
|---|---|
| Plans, pricing models & subscription lifecycle | 3.5 of 5 |
| Invoices & e-invoicing compliance | 3 of 5 |
| Cross-border VAT & tax handling | 3 of 5 |
| Payment collection, dunning & portability | 3.5 of 5 |
| Revenue reporting & accounting handoff | 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
The commercial model is clearly there: recurring billing, usage charges, credits and multi-currency charges are named as billing sources, quotes built in Quote Studio convert straight into Zuora Billing subscriptions, and amendment, renewal and cancellation quotes plus ramp deals cover the lifecycle changes I would otherwise hand to a developer. What I could not find is trials, proration on upgrades and downgrades, or a self-service portal where my customer cancels without emailing us. 2 3 5
The Finance Lead
The lifecycle from quote to subscription is documented end to end: quotes created from opportunities in Quote Studio and sent to Zuora Billing, amendment, renewal and cancellation quotes, ramp deals, usage charges and multi-currency billing. We found no public information on a customer self-service portal, trials, or proration on mid-cycle changes. 2 3 5
The Billing Engineer
Quotes become subscriptions and then flow through documented amendment, renewal and cancellation quote flows, with ramp deals, usage charges and multi-currency charges listed as billing sources and the subscription owner changeable mid-life; MRR can be reported historically at any point in time per account, product or subscription, so subscription history is clearly kept per customer. The captured pages do not show usage metering through an API, a customer self-service portal, trials with proration, or entitlements the selling application can read, which keeps this short of the top level. 2 3 5 10
The Service-Business Owner
Quotes built in Quote Studio convert into Zuora Billing subscriptions, and amendment, renewal and cancellation quotes, ramp deals, usage charges, credits and multi-currency charges are all documented — that covers my contract changes and ramped maintenance retainers. I found no public information on trials, proration, seat-based or tiered pricing with metering, minimum terms and notice periods, or a self-service portal where customers change or cancel their own contracts. 2 3 5
The Tax Adviser
The commercial model is deep: recurring billing, usage charges, credits and multi-currency charges are named billing sources, quotes convert into subscriptions from an opportunity or account, and subscriptions can then be amended, renewed, cancelled or reassigned, with ramp deals supported. I found no public information on metering through an API, seat or tiered price models, trials, minimum terms or a customer self-service portal, so I hold it just below the top band. 2 3 5
The Skeptic
The documentation shows a real subscription engine: amendment, renewal and cancellation quotes, ramp deals, usage charges, multi-currency charges, and quotes that convert straight into subscriptions. But we found no public information on trials, proration, seat or tiered pricing, metering through an API, or a self-service portal where the customer cancels — the quoting documented runs inside a Salesforce org for the seller's reps, not the buyer. 2 3 5
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-invoicing is real: billing documents export in PEPPOL BIS 3.0 XML, templates can be configured per country, invoices are created, validated, exchanged and tracked with partner workflows from Sovos and Avalara, and credit and debit memos handle corrections. But the vendor itself states Zuora is not a PEPPOL access point and that PEPPOL Extract has no prebuilt vendor integrations, so I would build the sending leg myself, and we found no public information on XRechnung or ZUGFeRD formats, sequential numbering, GoBD archiving or retention of the invoices themselves. 4 5 6
The Finance Lead
Structured e-invoicing is documented — PEPPOL BIS 3.0 XML generated from customer-defined templates, country-specific invoice templates, credit and debit memos for corrections, partner workflows via Sovos and Avalara for PEPPOL and government platforms, and invoice and tax data exportable for audit. Two things hold me back: the vendor documents that it is not a PEPPOL access point and my own system must connect to one for the custom route, and we found no public information on sequential numbering, unalterable archiving, or country-specific mandates such as France, Italy or Poland. 4 5 6
The Billing Engineer
E-invoicing is genuinely built in: invoices are created, validated, exchanged and tracked, templates are configurable per country for local formats, credit and debit memos handle corrections, and PEPPOL Extract exports PEPPOL BIS 3.0 XML generated from your own templates, now generally available. But Zuora states it is not a PEPPOL access point, the extract route ships no prebuilt partner integrations, and we found no public information on sequential numbering, GoBD archiving, XRechnung or ZUGFeRD, or named country mandates — partner workflows through Sovos and Avalara are the answer given, with their coverage undescribed. 4 5 6 11
The Service-Business Owner
PEPPOL BIS 3.0 XML generation from my own templates is generally available, country-specific e-invoicing templates and government platform connectivity run through qualified partner workflows, and credit and debit memos handle corrections. However, Zuora itself is not a PEPPOL access point and there are no prebuilt integrations, and I found no public information on XRechnung or ZUGFeRD output, GoBD-compliant numbering or unalterable archiving — exactly what my public-sector customers audit. 4 5 6
The Tax Adviser
Credit and debit memos handle corrections instead of edits, e-invoice templates are configurable per country for local format and submission requirements, billing documents export as PEPPOL BIS 3.0 XML, and partners such as Sovos and Avalara power the compliance workflows. But the documentation states that Zuora is not a PEPPOL access point and cannot connect to one for you, and I found no public information on sequential numbering, GoBD-compliant archiving, XRechnung or ZUGFeRD, or the e-invoicing mandates in named EU countries. 4 5 6
The Skeptic
Structured PEPPOL BIS 3.0 XML export and country-specific templates are documented, credit and debit memos replace edits, and invoice data is exportable for audit support. We found no public information on sequential numbering, mandatory content, GoBD-compliant archiving or retention, or XRechnung and ZUGFeRD formats. 4 5 6
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
Tax goes deep on geography: inclusive and exclusive VAT, rates applied at country, state, county, zip and geocode level driven by the sold-to contact, per-account exemptions, effective-dated rate tables and integrations with Avalara and Sovos, which would cover US sales tax. But for me the deal-breaker is that we found no public information on VAT ID validation, reverse charge for business customers or OSS, and the documentation states that Zuora tax rates are the amounts displayed on invoices rather than remittance amounts. 5 6 7
The Finance Lead
Rates are applied by country, state, county, zip and geocode driven by the sold-to contact, per charge with its own tax codes, on effective-dated rate tables, with exemptions per customer account and US sales tax through named engines Avalara and Sovos. We found no public information on VIES VAT-ID validation, reverse charge or One-Stop-Shop reporting, and the documentation itself notes the rates are invoice display amounts, not remittance amounts — for filing I would lean on the tax-data export and the partner engines. 5 6 7
The Billing Engineer
Taxation is driven by the sold-to contact down to city/county, zip and geocode levels, with per-charge tax codes, per-account exemptions, effective-dated rates preloaded by period, and rate tables importable as CSV from any corporate provider such as Taxware or CCH, alongside an Avalara integration for US sales tax. Inclusive and exclusive handling plus VAT, GST and nexus-based sales tax are all listed, and tax data exports support remittance and audit. We found no public information on VIES VAT ID validation, reverse charge or OSS reporting, and Zuora itself notes the calculated rates are invoice display amounts, not remittance amounts. 5 6 7
The Service-Business Owner
Taxation is applied by country, state, county, city and geocode from the sold-to contact, with up to three independent taxes per charge, per-account exemptions, effective-dated rate tables loaded as CSV files, VAT among the supported tax types and an Avalara integration. For cross-border B2B work I found no public information on VAT ID validation through VIES, reverse charge or One-Stop-Shop reporting. 5 6 7
The Tax Adviser
Taxation runs off the sold-to contact at country, state, county, city and geocode level, with up to three independent taxes per charge, effective-dated rates loaded from CSV or imported from providers such as Taxware or CCH, per-account exemptions, and US sales tax through the named engine Avalara. For cross-border Europe I find no VAT ID field with reverse charge, no VIES validation and no One-Stop-Shop reporting data — and the documentation itself cautions that tax rates are invoice display amounts, not remittance amounts. 5 6 7
The Skeptic
Rates can be applied by country, state, county, zip and geocode with effective dating, exemptions are set per customer account, Avalara is a named engine integration, and tax data is exportable for remittance. But the documentation itself states the rates in Zuora are the amounts displayed on invoices and not the remittance amounts owed to tax authorities — the operator loads the rate tables as CSV files. We found no public information on VAT ID validation through VIES, reverse charge for business customers, or the One-Stop-Shop. 5 6 7
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
This is close to what I want for failed cards: configurable payment retry with AI-driven smart retry per customer group, manual retry logic keyed to gateway response codes, a metrics dashboard showing whether retries actually work, and batch reconciliation against a dozen named gateways including Adyen, GoCardless, SlimPay and Worldline. Two gaps hold me back: the retry feature is stated to support card payments only, with ACH, SEPA, BACS and PAD unsupported, and we found no public information on dunning email sequences, service suspension, card updaters, or any documented path for migrating subscriptions and payment tokens out. 8 9
The Finance Lead
Collection is gateway-agnostic and well evidenced: a long named gateway list from Adyen to Worldline, batch reconciliation of payments and refunds against gateway settlement reports including chargeback and reversal stages, and configurable or AI-driven retries with per-customer-group logic and an effectiveness dashboard. Two gaps matter to me: the smart-retry feature supports cards only, not SEPA or other direct debit, and we found no public information on dunning sequences, escalation or suspension rules, or on moving subscriptions and stored payment details to another provider. 8 9
The Billing Engineer
Collection is gateway-agnostic across a long named list — Adyen, BlueSnap, Chase Orbital, Checkout.com, Citi, CyberSource, GoCardless, PayPal, SlimPay, Vantiv/Worldpay and Worldline — and payment and refund transactions are reconciled against gateway settlement reports through chargebacks and reversals. Configurable Payment Retry runs custom logic per gateway response code per customer group plus an AI-driven smart retry with a recovery metrics dashboard, though the vendor states it supports card payments only, not ACH, SEPA, BACS or PAD. We found no public information on dunning email sequences, service suspension, SEPA mandate management, or any migration path for subscriptions and stored payment tokens. 8 9
The Service-Business Owner
A long list of named gateways — Adyen, GoCardless, SlimPay, Worldline, Worldpay, PayPal and more — supports settlement reconciliation, and Configurable Payment Retry offers custom or AI-driven retry logic per customer group with an effectiveness dashboard. The retry tooling is documented as card-only, with SEPA direct debit explicitly excluded from it, and I found no public information on SEPA mandate management, dunning letter sequences, service suspension, a collection-agency handover or moving subscriptions to another provider. 8 9
The Tax Adviser
Collection spans a named gateway list including Adyen, GoCardless, SlimPay, PayPal and Worldline, reconciled against gateway settlement reports, with configurable or AI-driven retries whose effectiveness shows on a metrics dashboard. The retry logic is documented as card payments only, with ACH, SEPA, BACS and PAD explicitly unsupported, and I found no public information on dunning email sequences, escalation rules or service suspension. 8 9
The Skeptic
Collection runs across a long list of named gateways (Adyen, GoCardless, SlimPay, Worldline, Worldpay and more) with reconciliation against gateway settlement reports, and retries are configurable or AI-driven with a metrics dashboard on retry effectiveness. Two catches: the retry capability is documented as supporting card payments only, with ACH, SEPA, BACS and PAD listed as unsupported, and we found no public information on dunning email sequences, escalation or service suspension rules, card updaters, or any migration path for subscriptions and payment tokens out of the product. 8 9
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
MRR reporting is genuinely good: standard reports for total MRR, by account and by product, editable to any point in time, TCV grouped by product or subscription, CSV exports usable in any reporting tool, and a single AR subledger that feeds the GL across entities. But we found no public information on churn or cohort metrics, deferred revenue schedules, a named accounting export such as DATEV, or a documented API with webhooks, so I cannot see my month-end close from here. 1 10 11
The Finance Lead
MRR reporting is genuinely there — total, by account and by product, reportable at any point in time with editable grouping, plus TCV per account and product — and the vendor claims a single AR subledger automatically feeding the GL across entities. For the handoff I found no public information on deferred-revenue schedules, a DATEV or booking-ready journal export, churn metrics or a named accounting integration; the documented exports are data sources and CSV files. 1 10 11
The Billing Engineer
MRR reporting is deep — standard reports for total MRR, MRR by account and by product, editable to any historical point in time via effective dates, with TCV grouped by product, account, subscription or rate plan — and a single AR subledger feeds the GL, with CSV exports for any reporting tool and more powerful data sources alongside. But we found no public information on revenue recognition or deferred revenue schedules, churn or cohort metrics, a named accounting or DATEV integration, or documented webhooks, and the general data exports have narrowed to Invoice PDF and a users list CSV. 1 10 11
The Service-Business Owner
Standard MRR reports (total, by account, by product) can be edited to report at any point in time, TCV is groupable per account, subscription and rate plan, a single AR subledger is said to feed the general ledger, and tenant data exports to CSV exist. I found no public information on a DATEV export, a named accounting-system sync, revenue recognition with deferred revenue schedules, churn or cohort reporting, or webhooks. 1 10 11
The Tax Adviser
Standard reports give total MRR, MRR by account and by product at any point in time, plus TCV grouped by product, account or subscription, and the vendor page claims a single AR subledger that automatically feeds the general ledger across entities. CSV exports feed any reporting tool, but I found no public information on revenue recognition or deferred revenue schedules, a DATEV or other named accounting-system export, or webhooks. 1 10 11
The Skeptic
MRR and TCV reporting is real and editable — total, by account, by product, at any point in time — and the product page claims a single AR subledger that automatically feeds your GL. But the export documentation lists Invoice PDF and All Users List CSV as the available predefined exports, with other data exports deprecated, and we found no public information on churn reporting, a named accounting integration such as DATEV, revenue recognition with deferred revenue schedules, or a documented API with webhooks. 1 10 11
European sovereignty
panel opinion
n/r
n/r
n/r
n/r
n/r
n/r
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 not rated — no public information
We found no public information on the contracting entity's jurisdiction, where customer, invoice and payment data are hosted, the subprocessor list, a data processing agreement, or any security certifications. None of the captured pages, including the vendor homepage, address the sovereignty chain for billing data. 1
The Finance Lead not rated — no public information
We found no public information on the contracting entity, hosting location, subprocessors, a data processing agreement or security certifications in any page read; the closest statement is that retention of exported files is governed by a data retention policy. 1 11
The Billing Engineer not rated — no public information
We found no public information on the contracting entity and parent company, hosting locations for customer, invoice and payment data, or subprocessors, and no data processing agreement appears on the captured pages. Every sovereignty dimension is unknown to me, so there is nothing here I can score, and I will not guess. 1
The Service-Business Owner not rated — no public information
I found no public information on the contracting entity's jurisdiction, where customer, invoice and payment data are hosted, the subprocessors involved or a data processing agreement on the captured pages; a Zuora data retention policy is referenced by name for exported files but nothing of its contents is shown. 1 11
The Tax Adviser not rated — no public information
We found no public information on the contracting entity, hosting location, subprocessors or a data processing agreement — every sovereignty dimension is recorded as unknown. The nearest item in the captured pages is a passing reference to a Zuora data retention policy governing exported files. 1 11
The Skeptic not rated — no public information
We found no public information on the contracting entity's jurisdiction, where customer, invoice or payment data is hosted, the subprocessors in the chain from hosting to payment gateway to email delivery, a data processing agreement, or security certifications on the captured pages; every sovereignty attribute is recorded as unknown. 1
Pricing transparency
not rated — the vendor publishes no price
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 not rated — no public information
The captured pages, including the vendor homepage and the e-invoicing product page, show no tiers, platform fees, revenue percentages, minimum terms or VAT treatment. We found no public information on pricing at all, so I could not begin to compute my annual cost. 1 5
The Finance Lead not rated — no public information
We found no public information on pricing: no tiers, platform fee, percentage of billed revenue, per-invoice or module prices appear on the vendor or product pages read. 1 5
The Billing Engineer not rated — no public information
We found no public pricing information on the captured pages — no tiers, no platform fee or revenue percentage, no per-invoice or module pricing, no setup fee or minimum term. A buyer cannot compute an annual cost from what was captured, and I will not invent a figure. 1 5
The Service-Business Owner not rated — no public information
I found no public information on prices on the vendor homepage or the e-invoicing product page — no tiers, fees, revenue percentages, minimum terms or setup costs — so the annual cost for my two hundred contracts cannot be computed from what was captured. 1 5
The Tax Adviser not rated — no public information
We found no public information on pricing in the captured pages — no prices, tiers, revenue bands, module fees, setup costs or terms appear anywhere I read. 1
The Skeptic not rated — no public information
We found no public information on plan prices, tiers, a revenue percentage or per-invoice fee, setup costs, minimum terms or which modules cost extra; the captured product and documentation pages contain no figures, so a real annual cost cannot be computed from them. 1 5
European sovereignty — proven facts
0 of 6 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 |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Zuora
Is Zuora European?
Not determined: the vendor’s pages as captured do not say where Zuora is based.
Where does Zuora store data?
Not stated on the vendor’s pages as of 3 Nov 2026.
Does Zuora have a free plan?
Not stated on the vendor’s pages as of 3 Nov 2026.
What are the best alternatives to Zuora?
As of 4 Nov 2026, the panel rates Chargebee (3.5/5), Younium (3.5/5) and Stripe Billing (3.5/5) highest among the other 15 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: Zuora alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 3 Nov 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.
- We found no public information on pricing on the pages we read (zuora.com, docs.zuora.com/en/zuora-cpq/manage-subscriptions/subscription-management-in-cpq-x/create-subscription-quotes-using-quote-studio, docs.zuora.com/en/zuora-cpq/manage-subscriptions/subscription-management-in-cpq-x/amendment-quotes-or-renewal-quotes-creation, docs.zuora.com/en/zuora-billing/bill-your-customer/leverage-advanced-capabilities/e-invoicing/e-invoicing-with-peppol-extract, zuora.com/products/billing-software/e-invoicing-and-tax-compliance, docs.zuora.com/en/zuora-billing/set-up-zuora-billing/apply-taxes/overview-of-zuora-tax and 5 more). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- We could not confirm any compliance information on the vendor’s own pages as captured, so this page shows none rather than a statement we cannot stand behind. Know more? Tell us
- 13 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
- 1 integrations 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 (11)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.zuora.com Checked 3 Nov 2026 Details →
- 2 Plans, pricing models & subscription lifecycle — found from sitemap docs.zuora.com Checked 3 Nov 2026 Details →
- 3 Plans, pricing models & subscription lifecycle — found from sitemap docs.zuora.com Checked 3 Nov 2026 Details →
- 4 Invoices & e-invoicing compliance — found from sitemap docs.zuora.com Checked 3 Nov 2026 Details →
- 5 Invoices & e-invoicing compliance — found from sitemap www.zuora.com Checked 3 Nov 2026 Details →
- 6 Cross-border VAT & tax handling — found from sitemap docs.zuora.com Checked 3 Nov 2026 Details →
- 7 Cross-border VAT & tax handling — found from sitemap docs.zuora.com Checked 3 Nov 2026 Details →
- 8 Payment collection, dunning & portability — found from sitemap docs.zuora.com Checked 3 Nov 2026 Details →
- 9 Payment collection, dunning & portability — found from sitemap docs.zuora.com Checked 3 Nov 2026 Details →
- 10 Revenue reporting & accounting handoff — found from sitemap docs.zuora.com Checked 3 Nov 2026 Details →
- 11 Revenue reporting & accounting handoff — found from sitemap docs.zuora.com Checked 3 Nov 2026 Details →