Multi-Entity Billing for B2B SaaS: Platforms and Practices (2026)

Multi-entity billing means invoicing customers from the correct legal entity — with that entity's currency, tax registration, bank details, and ledger — while giving finance consolidated visibility across all of them. It becomes unavoidable the moment a company adds a second legal entity: a UK subsidiary, a US inc. above an original foreign parent, or an acquisition that arrives with its own billing stack.

Published August 2026. This guide covers what breaks when billing goes multi-entity, the platform options by company profile, and the questions to resolve before picking one.

What breaks when billing goes multi-entity

• Entity assignment: every new contract must bill from the right entity — wrong-entity invoices create tax exposure and rejected payments, and fixing them means credit notes and rebills.
• Currency and banking: each entity invoices in its own currencies with its own remit-to details; payments must land in and reconcile against the right entity's accounts.
• Tax: VAT, GST, and US sales tax obligations attach to the entity, not the group — invoices need the right registration numbers and tax treatment per entity.
• Intercompany: when one entity sells what another delivers, intercompany charges and transfer pricing documentation follow.
• Consolidation: group-level AR, DSO, and revenue reporting require rolling up ledgers that live in different systems, currencies, and charts of accounts.

The platform options

How LedgerUp handles multi-entity billing

LedgerUp treats the entity as a first-class attribute of every billing action. Ari reads the signed contract, determines the correct billing entity, creates the invoice in that entity's billing system with its currency and tax treatment, applies payments against the right entity's AR, and keeps a consolidated view of every entity's receivables — with approvals routed in Slack when an entity assignment is ambiguous. Because it operates across the systems you already run (NetSuite, Sage Intacct, QuickBooks per entity, Stripe accounts per entity), adding an entity means connecting it, not re-implementing billing.

Questions to resolve before choosing

1. How many entities, and how fast is the count growing? Two static entities and an acquisition pipeline are different problems.
2. Which system assigns the billing entity today — the CRM, the contract, or someone's memory?
3. Do entities share customers? Cross-entity customers are where wrong-entity invoicing concentrates.
4. Where must consolidation happen — the ERP, a BI layer, or the billing platform itself?
5. Who owns intercompany, and does any billing flow trigger it?

Frequently asked questions

What is multi-entity billing?

Multi-entity billing is invoicing customers from the correct legal entity within a corporate group — with that entity's currency, tax registrations, bank details, and general ledger — while maintaining consolidated receivables visibility across all entities. It spans entity assignment, per-entity invoicing and cash application, intercompany handling, and group-level reporting.

How do I handle multi-entity or multi-subsidiary invoicing in QuickBooks?

QuickBooks Online has no native multi-entity consolidation — each entity is a separate QuickBooks company file. The workable automation pattern: keep one QuickBooks company per entity, have the automation layer assign each contract to the right entity and post invoices, payments, and credits into that entity's file, and consolidate reporting above QuickBooks. LedgerUp runs this pattern directly; the alternative is graduating to a multi-entity ERP like NetSuite OneWorld or Sage Intacct.

When does a SaaS company need multi-entity billing?

Typically at the second legal entity — commonly international expansion (a UK or EU subsidiary for local contracting), a US flip above a foreign parent, or an acquisition. The billing pain arrives immediately: the first contract that should bill from the new entity forces the entity-assignment, currency, and tax questions.

Can Stripe handle multiple legal entities?

Stripe's standard pattern is one Stripe account per legal entity, each with its own settlement accounts and statement descriptors. That works for payment processing but leaves consolidated AR, cross-entity reporting, and entity-correct invoice creation to be solved above Stripe.