Plans, seats, trials, upgrades and proration for a SaaS product on self-hosted Kill Bill or Lago: catalog design, invoicing and payment gateways, accounting sync, customer portal options and when a billing SaaS remains cheaper.
Metering tokens, API calls or compute and turning them into invoices with self-hosted Lago or Kill Bill: event ingestion volume, Postgres versus ClickHouse event stores, prepaid credits, real-time usage visibility and reconciling usage with invoices.
Keeping card data out of a self-hosted billing system: gateway tokens instead of stored PANs, which Kill Bill and Lago components fall into PCI scope, SAQ type implications and pairing billing with an orchestrator vault such as Hyperswitch.
When the billing system feeds revenue in financial statements: access and change controls for catalogs and price changes, invoice and credit approval trails, interfaces to the general ledger and the evidence auditors ask for from self-hosted Kill Bill or Lago.
Running billing, customer and usage data on EU infrastructure the company controls: what a billing SaaS exports outside the EU, self-hosting Kill Bill or Lago, payment gateway data flows and GDPR for invoice and contact data.
Calculating US sales tax and EU VAT on recurring invoices from Kill Bill or Lago: tax engine plugins such as Avalara, tax rules kept in the billing catalog, reverse charge, e-invoicing obligations and what finance must maintain.
Moving an acquired product's subscriptions onto the group's billing platform: catalog mapping, migrating active subscriptions mid-term, payment method tokens across gateways, invoice numbering and revenue continuity.
Requirements to define before choosing Kill Bill, Lago or a billing SaaS: pricing models, metering volume, currencies, tax, payment gateways, dunning, invoicing formats, revenue reporting, integrations and who operates the platform.
Questions for partners bidding on a self-hosted billing implementation: experience with Kill Bill or Lago, catalog migration, gateway and tax plugins, high availability, upgrade handling, support model and enterprise edition needs.
Cost of ownership by component: billing SaaS fees that scale with revenue against hosting, implementation, plugins, optional enterprise support such as Kill Bill Aviate, and engineering time for self-hosted Kill Bill or Lago.