Billing & Invoicing
Orb
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Orb, Inc. · www.withorb.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.
Orb at a glance
- Vendor
- Orb, 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
- Yes, per the vendor’s own page source, captured 3 Nov 2026
- Panel verdict
- The AI panel rates Orb 3/5, the mean of 6 judges. Orb is a billing and invoicing platform judged strongest on tax handling, the subscription engine and revenue and handoff, and weakest on pricing transparency and sovereignty. how scores are made
- As of
- Vendor pages captured 3 Nov 2026; evaluated by the panel 4 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Orb is a billing and invoicing platform judged strongest on tax handling, the subscription engine and revenue and handoff, and weakest on pricing transparency and sovereignty. Tax is delegated to six named engines — Anrok, Avalara, Numeral, Sphere, Stripe Tax, TaxJar — with reverse charge validated against VIES and a timeline record for every tax decision. Pricing transparency sits at the floor because the captured pricing pages are an atlas of other companies' prices (64 examples, including Airtable, Slack and Figma) and no captured page states an Orb plan, fee or tier, so an annual cost cannot be computed. Sovereignty scores low despite an annual SOC 2 Type II audit and encryption at rest and in transit: the hosting region, the contracting entity's jurisdiction and subprocessor locations are unknown, with Amazon Web Services named as host in a virtual private cloud. Collections and dunning and invoicing compliance trail: we found no public information on SEPA direct-debit mandates, configurable dunning steps or structured e-invoices. The flagged splits report none; score differences are ranges, not splits.
Speaks for it
- Tax handling delegated to six named engines — Anrok, Avalara, Numeral, Sphere, Stripe Tax, TaxJar — with reverse charge for B2B customers validated against VIES and every skipped tax logged with its reason.
- Revenue recognition accords with ASC 606, straight-lines fixed fees daily, and monthly accounting-period locks push closed-period changes into the next open period.
- Plan changes run immediately, on a future date or at term end, with day-based proration credited to the customer balance and a full audit trail of every plan assignment.
- Failed payments retry automatically on a 1, 4 and 9 day schedule across Stripe and Adyen, with an immediate retry the moment the customer updates their payment method.
- The security program is documented in detail: an annual SOC 2 Type II audit, encryption at rest and in transit, third-party penetration testing, and deletion on request with evidence of deletion.
Held against it
- No Orb plan, fee or tier appears on any captured pricing page — those pages document other companies' prices — so an annual cost cannot be computed.
- The hosting region, contracting entity's jurisdiction and subprocessor locations are unknown, and the data processing addendum is available on request by email rather than published.
- We found no public information on structured e-invoices such as XRechnung, ZUGFeRD or Peppol, or on GoBD-compliant archiving.
- Retries follow a fixed 1, 4 and 9 day schedule rather than configurable steps, and we found no public information on SEPA direct-debit mandates or card updaters.
- We found no public information on MRR or churn metrics, a DATEV export, or a documented export of subscriptions and payment data to another provider.
Best for
- You sell hybrid models — minimums, prepaid credits and allocations — and need day-based proration, automatic credit notes on mid-period cancellation and a full audit trail on every change.
- Your finance team closes monthly under ASC 606 and needs deferred revenue excluding tax, accounting-period locks and catch-up postings in the next open period.
- You want cross-border tax delegated to a named engine, with VIES-validated reverse charge and a logged reason for every tax decision.
- You already run QuickBooks for accounting and Stripe or Adyen for payments.
Avoid if
- You must compute an annual cost before committing — the captured pricing pages catalog other companies' prices and state no Orb fee, tier or scaling rule.
- Your customers pay by SEPA direct debit — the documented autopay methods are credit cards, ACH, Stripe Link, Apple Pay, Google Pay and Amazon Pay.
- You need verifiable EU data residency — the pages name Amazon Web Services as host and state no hosting region, contracting jurisdiction or subprocessor locations.
- You need configurable dunning ladders, card updaters or service suspension — the documented behavior is a fixed 1, 4 and 9 day retry schedule ending in a payment-failure email.
The scores
| Criterion | Panel median |
|---|---|
| Plans, pricing models & subscription lifecycle | 3.5 of 5 |
| Invoices & e-invoicing compliance | 2 of 5 |
| Cross-border VAT & tax handling | 4 of 5 |
| Payment collection, dunning & portability | 3 of 5 |
| Revenue reporting & accounting handoff | 3.5 of 5 |
| European sovereignty | 1.5 of 5 |
| Pricing transparency | 0 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
Plan changes run immediately, on a future date or at end of term with day-based proration credited to the customer balance; minimums, prepaid credits with a cost basis and expiry, and zero-cost inclusions are all documented, and every subscription change is internally versioned with a full audit trail — the commercial model genuinely lives in the product. Net terms are configurable per plan, subscription or invoice. We found no public information on trials, customers changing or cancelling their own subscription, quotes or multi-currency price books, which keeps me a step below the top. 3 10 11
The Finance Lead
Plan changes can run immediately, on a future date or at end of term, with day-based proration credited to a customer balance, cancellations that automatically issue credit notes for fees paid in advance, and every subscription change internally versioned with a full audit trail — that is solid lifecycle machinery, plus prepaid credits, minimums and allocations. We found no public information on trials, quotes that convert into subscriptions, or the breadth of usage-based, tiered and seat-based pricing models. 3 5 10 11
The Billing Engineer
Plan changes run immediately, on a future date, or at term end, with day-based proration credited to the customer balance, automatic credit notes on mid-period cancellation, net terms configurable per plan, subscription or invoice, and the subscription versioned on every change with a full audit trail under the same subscription ID. Purchased credits with a cost basis, minimums and allocations approach hybrid commercial modelling without custom code. The captured pages show nothing on trials, quotes converting into subscriptions, price books, or a customer changing their own subscription in a portal. 3 5 10
The Service-Business Owner
Plan changes run immediately, on a chosen future date or at term end, unused advance fees are credited to the customer balance through day-based proration, and every change is versioned with a full audit trail of plan assignments — the machinery I need for two hundred retainers. Commitments, minimum amounts and prepaid credits with a cost basis are documented as plan components. I found no public information on trials, quotes, or a customer portal where the customer changes their own subscription. 3 10 11
The Tax Adviser
Orb documents a real subscription lifecycle: plan changes run immediately, on a future date or at end of term, unused in-advance fees are credited to the customer balance through day-based proration, mid-period cancellations auto-issue credit notes, and every subscription is internally versioned with an audit trail of each plan assignment. Minimums, prepaid credits recognised at cost basis and free allocations point to commitment-style hybrid pricing, and net terms are configurable at plan, subscription or invoice level. We found no public information on trials, quotes that convert into subscriptions, or a self-service portal where the customer changes their own subscription. 3 5 10 11
The Skeptic
Plan changes can be applied immediately, on a future date or at term end, unused in-advance fees are credited back through day-based proration, and every change versions the subscription with an audit trail of each plan assignment; minimums, prepaid credits with cost basis, allocations and per-plan net terms round out a genuinely hybrid model. We found no public information on trials, quotes, or a portal where the customer changes or cancels the subscription themselves, which is the half of the lifecycle I care about when renewals come due. 3 5 10 11
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
Invoice numbering is a random prefix plus a sequentially increasing counter, account-wide or unique per customer, and corrections are done the audit-safe way: adjustment and refund credit notes, automatic credit notes on mid-period cancellation, and voids, with tax recalculated in proportion. Cross-border invoices show both parties' country names, merchant tax IDs appear in the From section, and issuance fails on an invalid address. We found no public information on structured e-invoices to EN 16931, XRechnung, ZUGFeRD or Peppol, on retention or archiving, or on invoice languages, which for my nine EU countries caps this mid-scale. 5 6 7
The Finance Lead
Invoice numbers carry a randomly generated prefix and a sequentially increasing number starting at 1, per account or per customer, corrections happen through adjustment and refund credit notes rather than edits with proportional tax adjustments reported to the tax provider, and issuance fails without a valid customer address with tax shown broken down by jurisdiction. We found no public information on structured e-invoices such as XRechnung, ZUGFeRD or Peppol, on GoBD-compliant archiving, or on invoice retention. 5 6 7
The Billing Engineer
Invoice numbers are a configurable prefix plus a strictly sequential per-account or per-customer counter starting at 1, issuance fails without a valid customer address, tax IDs and per-jurisdiction tax breakdowns print on the documents, and corrections happen through adjustment or refund credit notes and voids rather than edits — including automatic ones when a subscription is cancelled mid-period. We found no public information on structured e-invoices such as XRechnung, ZUGFeRD or Peppol, on GoBD archiving and retention, or on invoice languages. 5 6 7
The Service-Business Owner
Invoice numbers are sequential under an account-wide or per-customer prefix, issuance fails without a valid customer address, tax IDs and country names print on the invoice, and corrections run through adjustment or refund credit notes with proportional tax instead of edits. I found no public information on XRechnung, ZUGFeRD or Peppol, on GoBD-compliant retention, or on a documented invoice archive — exactly what my public-sector customers demand. 5 6 7
The Tax Adviser
Corrections are done the way an auditor wants: credit notes are auto-typed into adjustments and refunds, capped at the invoice value, carry the proportional tax, and replace any edit to an issued invoice. Invoice numbering is documented as a randomly generated prefix plus a sequentially increasing number, either one account-wide prefix or a unique prefix per customer — workable, but per-customer prefixes give many small series rather than one clean account sequence. We found no public information on structured e-invoices such as XRechnung, ZUGFeRD or Peppol, on GoBD-compliant archiving, or on invoices in several languages, which an EU business needs now the B2B e-invoice mandate is live. 5 6 7
The Skeptic
Invoice numbers are a random prefix plus a sequentially increasing counter, and corrections go through proper credit notes — adjustment or refund, capped at invoice value, tax recalculated at issuance — instead of edits, which is the discipline a German auditor looks for. Beyond that the captured pages describe PDFs, jurisdiction tax breakdowns and portal receipts; we found no public information on structured e-invoices such as XRechnung, ZUGFeRD or Peppol, on GoBD-compliant archiving, or on any country's e-invoicing mandate being addressed. 5 6 7 10
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
Reverse charge for B2B customers with VIES validation, per-invoice tax reasons (taxed, reverse charge, exempt, zero-rate) and a timeline event recording every tax decision with its reason — that is the reverse charge that is right without thinking about it. Rates and filings are delegated to named engines: Anrok covering US sales tax plus global VAT/GST across 100+ countries with tax codes mapped per item, plus Avalara, Numeral, Sphere, Stripe Tax and TaxJar. We found no public information on OSS filing data or a written division of tax liability in the terms, so I hold it here. 7 8
The Finance Lead
Orb positions itself as the system of record for invoices while six named tax engines — Anrok, Avalara, Numeral, Sphere, Stripe Tax and TaxJar — supply rates, law and filings, with reverse charge for EU business customers validated against VIES, tax computed from the shipping or billing address, transactions reported for filing at invoice issuance, and every tax skip recorded on the invoice timeline with a reason. That reaches the automatic, per-country, per-product level with explainable decisions; we found no public information on filings themselves, a stated rate-change maintenance process, or a written division of tax liability in the terms. 7 8
The Billing Engineer
Tax is delegated to named engines — Anrok, Avalara, Numeral, Sphere, Stripe Tax, TaxJar — with Orb as the invoice system of record and the provider the source of truth for rates and filings; reverse charge requires a valid B2B tax ID checked against VIES, and tax reasons like reverse charge, exemption and zero-rating are recorded per invoice, with a timeline entry capturing the reason whenever tax is skipped. Anrok covers US sales tax plus VAT/GST in 100+ countries and the transaction is reported for filing at invoice issuance. We found no public information on OSS filings themselves, named-country mandates, or a written division of tax liability. 7 8
The Service-Business Owner
Tax is delegated to named engines — Anrok, Avalara, Numeral, Sphere, Stripe Tax and TaxJar — with reverse charge for EU business customers validated against VIES, calculation from the shipping address with billing-address fallback, per-item tax codes, and a reason recorded on the invoice timeline for every tax decision. Anrok covers US sales tax plus VAT/GST across more than 100 countries, and transactions are reported for filing when the invoice is issued. Rate maintenance and filings rest with the connected provider rather than the vendor, and I found no public information on OSS reporting. 7 8
The Tax Adviser
Tax is delegated but disciplined: six named engines are supported (Anrok, Avalara, Numeral, Sphere, Stripe Tax, TaxJar), EU VAT IDs are validated against VIES before reverse charge applies, tax follows the shipping address with billing-address fallback, issuance fails without a valid address, and every tax skip is recorded on the invoice timeline with its reason. Filing data flows out to the provider — Anrok transactions are reported at invoice issue and Avalara commits when the invoice is paid — and tax codes are configured per item. Orb itself applies no rates: with no provider connected no tax is calculated, and we found no public information on OSS-specific reporting or a written division of tax liability between seller and vendor in the terms. 7 8
The Skeptic
Tax is delegated, and at least honestly: six named providers including Anrok covering US sales tax and global VAT/GST across 100+ countries, reverse charge gated on a B2B tax ID validated against VIES, tax computed from the shipping address with billing fallback, and every skip decision logged on the invoice timeline with its reason and timestamp. But the vendor's own words make the provider the source of truth for tax law, rates and filings — the seller carries that contract and the liability — and we found no public information on OSS reporting data or who answers to a tax authority when it goes wrong. 7 8
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
Failed payments are retried automatically after 1, 4 and 9 days with a payment-failure email, and the moment a customer updates their card Orb retries immediately — exactly the churn protection I run on — across Stripe and Adyen, with autopay on cards, ACH and wallets, per-customer method exclusion and handling of Stripe's small-invoice minimum. That documented retry schedule is fixed rather than configurable. We found no public information on SEPA direct-debit mandates, card updaters, service suspension rules or a documented path to move subscriptions and payment details out of Orb. 9 10 6
The Finance Lead
Collection runs through two named gateways, Adyen and Stripe, with autopay across cards, ACH and wallet methods, automatic retries at 1, 4 and 9 days ending in a payment-failure notice, immediate retry when a customer updates their payment method, and receipts generated the moment an invoice turns paid. We found no public information on SEPA direct-debit mandates, card updaters, service-suspension rules or a collection-agency handover; the portability shown is invoice-numbering consistency when migrating in from Stripe subscription billing, not an export path out. 6 9 10
The Billing Engineer
Collection spans Stripe and Adyen with autopay across cards, ACH, Stripe Link, Apple Pay, Google Pay and Amazon Pay, automatic retries on a documented 1, 4 and 9 day schedule, an immediate retry the moment a customer updates their payment method, per-customer payment-method exclusions for enterprise deals, and receipts generated at the paid transition. The documented retries follow a fixed schedule with a single payment-failure email, and we found no public information on configurable dunning steps, SEPA mandates, card updaters, service suspension, or an export path for subscriptions and payment tokens — only invoice-numbering continuity when migrating in from Stripe is documented. 6 9 10
The Service-Business Owner
Collection runs through Stripe and Adyen with automatic retries after 1, 4 and 9 days, an immediate retry when the customer updates their payment method, per-customer payment-method exclusions, and receipts generated the moment an invoice turns paid. The documented autopay methods are credit cards, ACH and wallets; I found no public information on SEPA direct debit with mandates — how my German customers actually pay — nor on dunning escalation, a collection-agency handover or recovery reporting. 9 10
The Tax Adviser
Collection runs through the named gateways Adyen and Stripe with autopay across cards, ACH and the wallet methods, receipts the moment an invoice turns paid, per-customer exclusion of card methods for enterprise contracts, and automatic handling of Stripe's minimum charge amount for small invoices. Failed payments retry at day 1, 4 and 9, a payment-failure notice goes out at exhaustion, and an updated payment method triggers an immediate retry. We found no public information on SEPA direct-debit mandates, configurable dunning steps, card updaters, or an export path for subscriptions and payment tokens to another provider — the documented numbering configuration covers moving from Stripe subscription billing into Orb, not out of it. 6 9 10
The Skeptic
Collection runs through two named gateways, Stripe and Adyen, with cards, ACH and the wallet methods, automatic retries after 1, 4 and 9 days, a payment-failure email, payment information pulled back from the gateway, and even a documented path for keeping invoice numbering consistent when migrating subscription billing over from Stripe. What I do not see is SEPA mandates, escalation or service-suspension rules, a collection-agency handover, recovery reporting per step — or one word on exporting subscriptions and stored payment details back out when you leave. 6 9 10
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
The recognition engine is genuinely deep: revenue recognized to ASC 606, deferred revenue defined as invoiced but unrecognized excluding tax, monthly accounting period locks with catch-up postings in the next open period, and a configurable fiscal year — plus a QuickBooks accounting and invoicing sync with item and tax mapping. For a European finance team the handoff is thin: we found no public information on MRR and churn dashboards, a DATEV export or booking-ready journal, CRM or data-warehouse syncs, or a complete data export a successor system could take. 11 12
The Finance Lead
Recognition accords with ASC 606, fixed fees are straight-lined daily, deferred revenue is defined as invoiced amounts excluding tax not yet recognized, monthly accounting period locks push closed-period changes into the next open period as catch-up, and voids land as negative revenue — the close discipline I want, with a billings report by invoice date and a QuickBooks sync for invoices and taxes. We found no public information on MRR and churn metrics, a DATEV export or booking-ready journal, CRM or data-warehouse integrations, or a documented full data export. 11 12
The Billing Engineer
Recognized revenue accords with ASC 606, with deferred revenue defined as invoiced-but-unrecognized excluding tax, straight-line fixed fees, daily-recognized minimums, credits recognized at cost basis, and monthly accounting-period locks that push any closed-period change into the next open period as a catch-up — plus a configurable fiscal-year offset, which is a real month-end close capability. The accounting handoff is QuickBooks, with item, tax and customer mapping configurable in the dashboard or via API, and the product exposes a documented API and webhooks. We found no public information on MRR or churn metrics, a DATEV export, CRM or warehouse sync, or a complete successor-ready export. 11 12
The Service-Business Owner
Recognition is the strongest part: ASC 606-conformant straight-line daily recognition, deferred revenue by service period, monthly accounting-period locks with catch-up in the next open period, and a billings report by invoice date. Invoices, customers, items and taxes sync to QuickBooks, and an API and webhooks are documented. I found no public information on MRR or churn metrics, a DATEV export, CRM or warehouse integrations, or a complete data export. 11 12
The Tax Adviser
This is the part an auditor will like: recognition accords with ASC 606, fixed fees are straight-lined daily, deferred revenue excludes tax, monthly accounting-period locks push late changes into catch-up entries in the next open period, and voids and credit notes post as negative revenue. Invoices and taxes sync to QuickBooks with customer and item mapping, and the API carries the configuration. We found no public information on MRR or churn dashboards, a DATEV export, CRM integrations, or a documented complete export of customer and subscription data. 5 11 12
The Skeptic
Recognition is the real thing: ASC 606 stated, straight-line daily recognition on fixed fees, deferred revenue defined as invoiced-but-unrecognized, monthly period locks with catch-up posted to the next open period, and voids recorded as negative revenue in line with the lock posture. The handoff to QuickBooks with item, tax and customer mapping plus a documented API and webhooks is credible; we found no public information on MRR or churn reporting, a DATEV export, or a complete data export a successor system could import. 5 11 12
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 security page is credible — SOC 2 Type II audited annually, encryption in transit and at rest, third-party penetration tests, AWS hosting in a VPC, a maintained subprocessor list, and a DPA plus evidence of deletion available on request. But the hosting region is not stated, the subprocessor list is maintained rather than published with locations, and we found no public information on an EU contracting entity or EU data residency — as a seller in nine EU countries that is the part I would have to chase before signing. 2
The Finance Lead
The security program is real — AWS infrastructure in an isolated VPC, annual SOC 2 Type II audits, third-party penetration testing, encryption at rest and in transit, deletion on request with evidence, and a subprocessor list Orb maintains. But the captured pages state neither the contracting entity's jurisdiction nor the hosting region, give no locations for the subprocessors, and offer the data processing addendum only on request, so no European dimension is proven. 2
The Billing Engineer
The security page names AWS inside a virtual private cloud as the infrastructure, SOC 2 Type II audited annually, Cloudflare proxying select endpoints, a maintained subprocessor list, deletion on request with evidence of deletion, and a data processing addendum available on request by email. Hosting region, the contracting entity's jurisdiction and any EU residency option are unstated on the captured pages, and the subprocessor list's contents are not shown, so nothing evidences a European chain. 2
The Service-Business Owner
The security pages name AWS as the infrastructure with VPC isolation, state an annual SOC 2 Type II audit and third-party penetration testing, and offer a data processing addendum on request; customer data can be deleted on request with evidence of deletion. A subprocessor list is maintained but not published with locations, and I found no public information on the hosting region, the contracting entity's jurisdiction, or any EU safeguard — so from these pages I cannot confirm that billing data stays in Europe. 2
The Tax Adviser
Orb publishes a serious security posture — SOC 2 Type II audited annually with the report available to customers, encryption at rest and in transit, third-party penetration testing, and a data processing addendum available on request — and names Amazon Web Services as its host in a virtual private cloud. What a European buyer needs is not stated on the captured pages: the hosting region, the subprocessors with their locations, and the contracting entity's jurisdiction are all unstated. I can prove neither European hosting nor a European entity from these pages, so this sits low despite the certifications. 2
The Skeptic
As documented the chain is American: Amazon Web Services for hosting with no region stated, source code on GitHub, Cloudflare in front, and a contracting entity whose jurisdiction the captured pages never establish. A data processing addendum exists only on request by email, the subprocessor list is said to be maintained but is not published with locations, and beyond SOC 2 Type II there is nothing here a European buyer could call sovereign — no EU entity, no EU hosting, no published safeguards. 1 2
Pricing transparency
n/r
n/r
n/r
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 captured pricing pages are a pricing atlas profiling other companies' per-seat models — 64 examples, 46 of them with a free tier — with nothing on Orb itself. We found no public information on Orb's own pricing: no tiers, no scaling rule against billed revenue, no term, setup or module fees, so I cannot even begin to compute what Orb would cost us as revenue grows. That is disqualifying for a buyer whose rule is that the billing bill must not grow faster than revenue. 4
The Finance Lead not rated — no public information
We found no public information on Orb's own plans, tiers or fees. The pricing pages captured are a pricing atlas documenting other vendors' price lists and a catalogue of pricing-model examples, not a price list for Orb itself. 1 4
The Billing Engineer not rated — no public information
We found no public information on what Orb itself costs — no plan, fee, percentage or revenue band for Orb appears on the captured pages, including the homepage. The pricing pages captured are a pricing atlas documenting how other products are priced, with per-seat and usage figures for Airtable, Slack, Figma and dozens of other vendors, which describes those products rather than Orb's own price list. 1 4
The Service-Business Owner
The captured pricing content is an atlas describing other companies' price books — Airtable, Figma, Slack and dozens more, down to exact dollar figures. I found no public information on Orb's own platform fee, tiers, or how its cost scales with billed revenue, so no annual cost can be computed from these pages. 1 4
The Tax Adviser not rated — no public information
We found no public information on Orb's own prices: the captured pricing page is an atlas documenting other companies' price points per seat, per user or per credit, and no fact from any captured page states an Orb plan, platform fee, revenue percentage, per-invoice fee or minimum term. A buyer cannot compute an annual cost from what was captured. 4
The Skeptic
The captured pricing pages are a directory of other companies' prices — Airtable, Figma, Slack and dozens more, catalogued by the vendor as a pricing atlas — and not one price, tier, fee or scaling rule for the vendor's own product appears on any page we read. A buyer cannot begin to compute annual cost: whether cost scales with billed revenue, invoice volume or modules, and what a gateway or the revenue recognition engine costs extra, is invisible. 1 4
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 ⚠ unverified | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Orb
Is Orb European?
Not determined: the vendor’s pages as captured do not say where Orb is based.
Where does Orb store data?
Not stated on the vendor’s pages as of 3 Nov 2026.
Does Orb have a free plan?
Yes. Orb has a free plan, per the vendor’s page captured 3 Nov 2026.
What are the best alternatives to Orb?
As of 3 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: Orb 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.
- Weak sourcing — Data processing agreement. Not confirmed on the vendor’s own pages as captured.
- 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.
- 26 pricing 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
- 8 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 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
Sources (12)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.withorb.com Checked 3 Nov 2026 Details →
- 2 Security / trust page — found from the homepage www.withorb.com Checked 3 Nov 2026 Details →
- 3 Plans, pricing models & subscription lifecycle — found from sitemap docs.withorb.com Checked 3 Nov 2026 Details →
- 4 Plans, pricing models & subscription lifecycle — found from sitemap www.withorb.com Checked 3 Nov 2026 Details →
- 5 Invoices & e-invoicing compliance — found from sitemap docs.withorb.com Checked 3 Nov 2026 Details →
- 6 Invoices & e-invoicing compliance — found from sitemap support.withorb.com Checked 3 Nov 2026 Details →
- 7 Cross-border VAT & tax handling — found from sitemap docs.withorb.com Checked 3 Nov 2026 Details →
- 8 Cross-border VAT & tax handling — found from sitemap docs.withorb.com Checked 3 Nov 2026 Details →
- 9 Payment collection, dunning & portability — found from sitemap docs.withorb.com Checked 3 Nov 2026 Details →
- 10 Payment collection, dunning & portability — found from sitemap docs.withorb.com Checked 3 Nov 2026 Details →
- 11 Revenue reporting & accounting handoff — found from sitemap docs.withorb.com Checked 3 Nov 2026 Details →
- 12 Revenue reporting & accounting handoff — found from sitemap docs.withorb.com Checked 3 Nov 2026 Details →