As of 28 Oct 2026, the panel rates Frisbii (formerly billwerk+) 3/5 and Stripe Billing 3.5/5 in Billing & Invoicing. Weighted by what each judge cares about, 0 of the 6 judges pick Frisbii (formerly billwerk+) and 6 pick Stripe Billing. Frisbii (formerly billwerk+) scores higher on 1 of 6 criteria (Invoices & e-invoicing compliance). Stripe Billing scores higher on 5 of 6 criteria (Payment collection, dunning & portability, Plans, pricing models & subscription lifecycle, Cross-border VAT & tax handling, plus 2 more). Provenance — Frisbii (formerly billwerk+): EU-Made; Stripe Billing: Rest of world. Ratings are the AI panel’s opinion, formed from public evidence: how scores are made.
Criterion leans run to Stripe Billing on subscription engine (8.0 to 6.7, six judges to zero), collections and dunning (8.0 to 6.3, six to zero), revenue and handoff (8.0 to 7.0, six to zero), tax handling (7.2 to 6.2, five lean Stripe Billing, one tie) and pricing transparency (5.8 to 5.5, three lean Stripe Billing, one Frisbii, two tie). Frisbii (formerly billwerk+) takes invoicing compliance, 6.7 to 4.8, six judges to zero — Factur-X 1.0.07 / ZUGFeRD 2.3 e-invoicing on the EN16931 profile, against the vendor's own statement that Stripe Invoicing does not itself generate or transmit legally compliant e-invoice files. Sovereignty is low for both (4.2 to 4.5) and near-tied: five tie, one lean Stripe Billing. The published weighted totals — 6.6 to 6.3, 7.3 to 6.2, 6.5 to 6.3, 6.5 to 5.9 — each favour Stripe Billing; with invoicing compliance six-to-zero the other way, the split, not a winner, is the answer.
Choose Frisbii (formerly billwerk+) if
You need the billing platform itself to generate legally compliant e-invoice files: invoicing compliance leans Frisbii six judges to zero (6.7 to 4.8), built on Factur-X 1.0.07 / ZUGFeRD 2.3 e-invoicing on the EN16931 profile, and the verdict quotes the vendor's own statement that Stripe Invoicing does not itself generate or transmit such files.
Your invoices must carry German e-invoicing formats without bolting on a third-party file service — on Stripe Billing, the verdict notes, UBL, CII and Peppol BIS Billing 3.0 files come from third parties, and the invoicing-compliance lean is Frisbii's, six judges to zero.
You must be able to record EU-only data residency in your vendor paperwork: Frisbii's data residency attribute stands at EU-only, while Stripe Billing's data residency attribute stands at unknown.
Choose Stripe Billing if
Your pricing models go beyond flat rates — per-seat, tiered, volume and graduated: subscription engine leans Stripe Billing six judges to zero (8.0 to 6.7), with those models documented to the API tier fields.
Failed payments are where you lose revenue: collections and dunning leans Stripe Billing six judges to zero (8.0 to 6.3), on Smart Retries with a recommended default of 8 attempts within 2 weeks.
You recognise revenue under ASC 606 or IFRS 15 and hand off to QuickBooks Desktop or NetSuite: revenue and handoff leans Stripe Billing six judges to zero (8.0 to 7.0).
You bill customers across many countries and want tax handled inside the billing platform: tax handling leans Stripe Billing, 7.2 to 6.2, five judges with one tie.
You want published pay-as-you-go pricing before signing: pricing transparency leans Stripe Billing three to one with two ties (5.8 to 5.5), on the public 0,7 % pay-as-you-go rule and card rates — noting add-on modules carry no published prices.
Read this comparison as one judge. Each weighs the same scores by what they care about.
The Skeptic
Has seen "automated recurring revenue" turn into a tool that takes a percentage of every euro billed and keeps the payment tokens when the customer leaves. Reads "e-invoicing ready" that means a PDF, "global tax compliance" with no word on who is liable, merchant-of-record terms that let the vendor change fees at will, and subprocessor lists that stop at the hosting provider — and asks what leaving would cost.
Frisbii (formerly billwerk+)
Stripe Billing
This judge's pick
Criterion by criterion
Plans, pricing models & subscription lifecycle
Frisbii (formerly billwerk+)
Plans, add-ons, discounts and coupons, trials, usage-based and hybrid pricing and a self-service portal where customers upgrade and downgrade themselves are all documented, and the lifecycle runs unusually deep — pending, trial, on-hold, cancelled-to-expire and non-renewing states, scheduled actions, and per-subscription events exposed through the API. The commercial model plainly lives in the product on the Growth and Scale plans, with advanced entitlements and multi-entity setup named at the top. I found no public information on proration, on metering usage through an API, on quotes that convert into subscriptions, or on tiered, volume or seat-based pricing — and that is what keeps this below the top level.
Stripe Billing
Seat, tiered, graduated and volume pricing are documented down to the API fields, with trials, quotes, a customer portal and scheduled multi-phase subscription changes, in more than 135 currencies. The price on a product cannot be edited once a subscription exists for it, and the advanced usage-based engine (Metronome) is stated to sit outside the product at custom pricing.
Invoices & e-invoicing compliance
Frisbii (formerly billwerk+)
Structured e-invoicing is documented, not just promised: invoices and credit notes are issued as Factur-X 1.0.07 / ZUGFeRD 2.3 hybrid documents using the EN 16931 profile, invoice numbers are generated automatically with configurable prefixes and separate sequences for credit notes, a credit note cancels an invoice while the original document stays untouched, and PDFs are generated and archived. Correction discipline and numbering are well covered. I found no public information on sending through Peppol, on XRechnung, on GoBD-compliant unalterable archiving, on an export for a tax audit, or on e-invoicing mandates in named countries — and without those, an EN 16931 hybrid PDF is only half of compliance.
Stripe Billing
Credit notes are handled as unmodifiable documents with documented effects on paid and unpaid invoices, and invoices go out in 135 currencies and 35 languages. But the vendor itself states it does not generate or transmit legally compliant e-invoice files — that runs through third-party partners such as Billit — and we found no public information on sequential numbering, mandatory content or a documented archive.
Cross-border VAT & tax handling
Frisbii (formerly billwerk+)
VAT is determined automatically from the customer's country, with a standard setting presetting the normal rates of the 20 main European countries, reverse charge applying to EU business customers with a VAT number configured, exemption texts printed for non-EU customers, VAT groups and reverse charge, and the German 16%/5% rate change preconfigured with key dates and automatic splitting of continuous services. The division of responsibility is at least honest — the help pages state that Frisbii Billing does not verify whether a VAT group legally exists and direct you to your tax advisor. I found no public information on VIES validation of VAT IDs, on OSS reporting data (the accounting export states that for EU B2C the system assumes you take part in the OSS procedure), on US sales tax, or on customer-location evidence being kept.
Stripe Billing
Calculation breadth is real: sales tax, VAT and GST across more than 90 countries with product tax codes, threshold monitoring, and registration and filing directly or through partners. The pages are silent on VIES validation of VAT IDs, OSS reporting data and evidence of customer location, and the captured terms state no division of tax liability between seller and vendor.
Payment collection, dunning & portability
Frisbii (formerly billwerk+)
Dunning is genuinely built in: temporary failures such as an exceeded credit limit are retried automatically, permanent ones such as an expired card trigger dunning at once, intervals and actions are configurable down to automatic cancellation, SEPA direct debit via PPRO or EBICS comes with configurable return handling, and a beta AI collections agent contacts customers and records promises to pay under human oversight. One gateway covering 50+ European payment methods is included in all plans, with partner gateways named as an option on the media plan. I found no public information on card updaters, bank-transfer reconciliation, a handover to a collection agency, or any documented path for moving subscriptions and stored payment details to another provider — the question I always ask before signing.
Stripe Billing
Smart Retries with AI-chosen timing, per-segment retry policies, expired-card updates, pause-or-cancel rules after failed renewals, automatic bank-transfer reconciliation and a reported 8.2 billion dollars in failed payments recovered in 2025. What the captured pages never document is portability out: no export path for subscriptions and stored payment details to another provider is stated anywhere.
Revenue reporting & accounting handoff
Frisbii (formerly billwerk+)
Finance gets named dashboards — revenue with MRR and ARR, customer health with retention and churn, receivables with collection performance, and the full invoice lifecycle — plus a DATEV export documented in unusual depth: SKR03 or SKR04, EXTF or ASCII formats, overridable posting keys and accounts, automatic debtor IDs, revenue accounts per tax country, rate and currency, and delivery on monthly, weekly or daily intervals to SFTP, Google Drive or OneDrive. A documented API with subscription events and a Salesforce-native integration complete the handoff. I found no public information on deferred-revenue schedules, on a full export of customers, subscriptions and invoices a successor system could import, or on data-warehouse sync.
Stripe Billing
Recognition to ASC 606 and IFRS 15 is stated, with a preview API exposing six debit/credit report types by customer, price, invoice and line item, plus named QuickBooks and NetSuite handoffs and data-warehouse sync as an upcharge. We found no public information on a DATEV export, on MRR movements explained per customer, or on a complete successor-ready export of customers and subscriptions — and the revenue API is a public preview whose fields may change.
European sovereignty
Frisbii (formerly billwerk+)
The contracting side is verifiably German — Frisbii Germany GmbH in Frankfurt with commercial register number and VAT ID, a German data protection officer, and a data processing agreement published in four languages — and deletion duties and the client's ownership of its data are written into the terms. But the captured pages do not say where the billing platform's customer, invoice and payment data are hosted: the privacy notice offers only that data is processed 'in some cases' on servers in Germany and the EU, the Salesforce-hosted app's region is unstated, and the subprocessors I could see named — Borlabs, doo, HubSpot, Google, Microsoft, Automattic — belong to the marketing website, not to the hosting, payment and email chain that touches billing data. I found no public information on security certifications such as ISO 27001 or SOC 2.
Stripe Billing
A Dublin-registered contracting entity authorised by the Central Bank of Ireland exists, with a published data processing agreement, a published subprocessor list and ISO 27001 and SOC 2 named. But the vendor's own pages state no hosting location and no subprocessor locations, and the parent company sits in the US — where invoice and payment data physically rest cannot be verified from what was captured.
Pricing transparency
Frisbii (formerly billwerk+)
The lower tiers are genuinely public: Starter at €49/mo with one seat, Growth at €299/mo with up to five seats, the scaling rule spelled out as a 0.95% charge on processed billing, standalone payments at €0.08 per transaction, and VAT treatment and the three-month cancellation notice stated. Above that, pricing becomes a conversation: Scale and Scale for Media carry 'Tailored pricing' behind a sales call, Scale for Media adds variable fees per subscription, transaction and users that the captured pages do not quantify, and merchant bank processing and customer/card import fees are deferred to a fee breakdown the pricing page references but does not show. A buyer can compute the entry cost; I could not compute the cost at the top end from these pages.
Stripe Billing
The core scaling rule is public and precise: 0.7% of billing volume pay-as-you-go, 0.67% for volume above 80,000 euros monthly, and 1.5% + 0.25 euros for standard European cards. But revenue recognition, tax registration and filing, metering above 100 million included events, data-warehouse sync and third-party payments are all marked available at upcharge with no prices, the usage engine Metronome is priced only on request, and the VAT treatment of the fees is not stated — a buyer cannot compute a real annual cost from these pages.
Sovereignty, side by side
Dimension
Frisbii (formerly billwerk+)
Stripe Billing
Legal entity
Not determined
Not determined
Ownership
Not determined
Not determined
Data residency
Not determined
Not determined
Subprocessors
US CLOUD Act reach
Not determined
Facts, side by side
Only facts both products carry under the same definition — anything else would not be a fair row.
Questions about Frisbii (formerly billwerk+) and Stripe Billing
Which is better, Frisbii (formerly billwerk+) or Stripe Billing?
As of 28 Oct 2026, the panel rates Stripe Billing higher: 3.5/5 against 3/5. Weighted by what each judge cares about, 0 of the 6 judges pick Frisbii (formerly billwerk+) and 6 pick Stripe Billing. Which one fits depends on the criteria that matter to you; the table on this page shows both side by side, and each judge’s reading has its own page. Both were scored by the same AI bench under the same rubric, from public evidence only, as the methodology describes.
Is Frisbii (formerly billwerk+) or Stripe Billing European?
Frisbii (formerly billwerk+) is European (EU-Made). Stripe Billing is not European by provenance (Rest of world). Provenance is read from each company’s own legal pages: who builds it and who owns it.