A company that sells from three European entities into eight countries issues invoices under three numbering sequences, four VAT registrations, two e-invoicing mandates with different formats, and posts them to an ERP per entity. The invoice itself is the easy part.

What breaks is the numbering that has to be gap-free per entity, the tax that depends on the pair of countries on each invoice, the e-invoicing network that each country requires, and the month-end that has to close in each ERP separately. This guide lists what compliant multi-entity invoicing requires, compares eight platforms on it, and ends with the mandates by country.

What compliant multi-entity invoicing requires

1. A billing entity object per legal entity, holding its name, address, VAT numbers, bank accounts, currencies and invoice template.

2. Sequential, gap-free invoice numbering per entity, with no number ever reused or skipped, including for credit notes.

3. Tax determination per invoice from the seller entity, the buyer's country and VAT status, and the supply type, including reverse charge and OSS where they apply.

4. Additional tax registrations per entity, for the countries where the entity is registered beyond its home country.

5. E-invoicing submission per country: France through an accredited platform, Peppol for Belgium, the Netherlands and Germany, SDI for Italy, KSeF for Poland, and the rest as they come due.

6. EU mandatory invoice fields on every document, in the format and language the country requires, with the issuance deadline respected.

7. One ERP connection per entity, posting invoices, payments and credit notes to the right ledger with the right tax codes.

8. Data residency and retention per entity, with EU hosting where the entity or its customers require it.

Platforms compared (as of October 2026)

Ownership, as of October 2026: Metronome belongs to Stripe, Orb to Adyen, m3ter to Salesforce, Zuora to Silver Lake and GIC. Solvimon, Chargebee, Hyperline, Sequence, Lago and Maxio are independent. The implication is whose roadmap your billing follows.

Solvimon

Solvimon was built for companies that bill from several entities into several countries, which is what Europe's payment companies do. Each billing entity carries its own numbering, tax registrations, currencies and bank details, and a customer can be billed by more than one of them. E-invoicing covers France, Peppol, Italy, Spain, Poland, Hungary and Estonia, with Avalara for the rest.

Montonio cut invoice discrepancies by 35%; Tebi bills eight markets on one setup. Pricing is 0.4% of volume at scale, with the first $3M free for qualifying AI companies. Where another platform is the better pick: a company on one entity with flat subscriptions does not need this and should look at Stripe Billing.

Chargebee

Chargebee has the longest list of integrations in the set and published EU hosting in Frankfurt. Multi-entity is supported, tax runs through Avalara or TaxJar, and e-invoicing goes through partners.

Pricing is a percentage of revenue with a small fixed fee at the entry tier. Where Chargebee is the better pick: a subscription business with a large self-serve base, heavy dunning needs and many SaaS tools to connect.

Hyperline

Hyperline is the closest EU alternative, with transparent entry pricing and a long e-invoicing list: France through Chorus Pro and an accredited platform in beta, Peppol for Belgium and Germany, XRechnung and ZUGFeRD, Italy SDI and Spain. Multi-entity consolidation sits in the Scale tier.

SOC 2 and ISO 27001 are published. Where Hyperline is the better pick: a team under $2M in revenue that wants a fixed price, CPQ inside Salesforce, HubSpot or Attio, and GoCardless or Airwallex as the PSP.

Sequence

Sequence handles multi-entity with per-entity tax, 25 currencies and percentage pricing with floors and caps, and has the strongest review signal in the set. E-invoicing runs through an Invopop partnership whose live status is not documented. Where Sequence is the better pick: contract-heavy UK or US B2B with bespoke terms, where AI contract intake saves a finance team real time.

Zuora

Zuora is the enterprise standard for multi-product, amendment-heavy contracts, with 40+ payment gateways, mature revenue recognition and a Frankfurt data centre. E-invoicing is through partners.

There is no list price; Vendr reports a median of about $170k a year with 20 to 40% on top for implementation. Where Zuora is the better pick: a listed group with dozens of product lines, a procurement process that wants an analyst-quadrant vendor, and an SI partner on hand.

Lago

Lago is open source under AGPL, self-hostable for free, with an EU cloud region. Multi-entity is possible because the code is yours.

E-invoicing is not documented. Where Lago is the better pick: an engineering-led team that wants to own billing logic and run it in its own region.

Stripe Billing

Stripe Billing is the fastest to start if payments are already on Stripe. Each legal entity is a separate Stripe account, tax runs through Stripe Tax, and e-invoicing goes through partners.

Pricing is 0.7% of billing volume, including volume processed off Stripe. Where Stripe Billing is the better pick: one entity, flat subscriptions, most revenue already on Stripe Payments, and no appetite to migrate.

Maxio

Maxio is finance-led SaaS billing with GAAP reporting, Avalara for tax and partners for e-invoicing. Wallets are in beta since September 2026. Where Maxio is the better pick: a US SaaS company whose finance team wants reporting first and bills from one or two entities.

E-invoicing mandates by country (2026)

See e-invoicing for the formats and the French reform for the 5-corner model. Check each country's tax authority for the current phase before relying on a date.

If you listed your entities, your customers' countries and the mandates in the table that apply to each pair, how many of the rows above does your current billing system submit to today?

Frequently asked questions

Which billing platforms support multi-entity invoicing in Europe?

Solvimon, Chargebee, Hyperline, Sequence, Zuora, Lago, Stripe Billing and Maxio all support more than one legal entity in some form. They differ on per-entity invoice numbering, native tax engines, which e-invoicing mandates they submit to and whether data can be hosted in the EU. The comparison table above lists each one as of October 2026.

What is multi-entity invoicing?

Multi-entity invoicing is issuing invoices from more than one legal entity in a single billing system. Each entity needs its own numbering sequence, VAT registrations, bank details, invoice template and ERP mapping, and the invoice must be issued by the entity that holds the contract.

Does each legal entity need its own invoice numbering sequence?

Yes. EU invoicing rules require a sequential, gap-free series per issuer. A billing platform that runs one global counter across entities fails an audit in most member states, so look for numbering scoped to the billing entity.

Which countries have mandatory B2B e-invoicing in 2026?

Italy, Belgium and Poland have mandates in force for B2B. France starts with mandatory receiving in September 2026, Germany is phasing issuing through 2027 and the EU-wide ViDA reporting rules start in 2030. The table above lists each country and its model.

Related guides

• What to look for in billing software. The 12 features that decide whether invoices come out right.

• Best billing software for fintech and payments companies. Percentage fees, floors, caps and nested rates across 7 platforms.

• Sequence alternatives. 8 billing platforms to move to after the Intuit acquisition.

• Month-end close for high-volume finance teams. Where close time goes and the stack behind a fast close.