Multi-Entity Billing for Lago

Multi-entity billing is the feature that separates startup grade billing from enterprise grade billing. Large companies do not bill from one company record. They bill from many legal entities, each with its own invoice numbering, tax setup, user permissions, and finance workflows. Zuora already supports that structure inside one tenant, while Lago today is strongest for a single billing entity with flexible usage logic and developer control.

• In practice, a multinational customer may need one team in France issuing invoices from a French entity, another in the US billing from a US entity, and central finance still wanting shared administration and reporting. Zuora is built to isolate bill runs, payment runs, and settings by entity while keeping them under one system.
  3 zuora 4 zuora
• Lago already gives developers the hard part of modern usage billing, event ingestion, pricing logic, invoice generation, and integrations to systems like Salesforce, NetSuite, Xero, Anrok, and Avalara. Adding multi-entity would let that same engine serve companies whose products are global but whose legal and accounting structures are fragmented.
  1 sacra 2 sacra
• This matters commercially because Lago monetizes premium features. Multi-entity billing sits in the same bucket as dunning and advanced analytics, features that free self hosted users often do not need early, but larger finance teams will pay for once billing spans subsidiaries and jurisdictions.
  1 sacra 2 sacra

The next step is clear. If Lago pairs multi-entity billing with its new e-invoicing compliance adapters, it can move from being a strong developer led billing tool into a credible replacement for Zuora in multinational deployments. That would pull the company upmarket, raise contract sizes, and convert more open source adoption into paid infrastructure revenue.