M
Glossary
Multi-Entity Invoicing
Multi-entity invoicing is a billing setup where a company issues invoices from more than one legal entity, each with its own tax registration, numbering sequence, and statutory ledger. The entity that issues an invoice determines who legally sells, which tax rules apply, and where the revenue lands.
Key Takeaways
The selling entity is an attribute of the invoice, not a filter on a report. It sets the tax registration, the numbering series, and the ledger revenue posts to.
Seller entities and customer hierarchies are independent axes. One entity can bill a twenty-subsidiary group, and three entities can each bill the same customer.
India's CGST Rule 46(b) caps an invoice serial number at sixteen characters and requires it to be unique for a financial year, so an Indian entity can't share a group counter.
Intercompany invoices inflate group revenue until consolidation eliminates them. A $15,750 internal charge inside a $40,000 customer deal overstates group revenue by 39%.
When do you need multi-entity invoicing?
You need it as soon as a second legal entity starts selling to customers, which usually arrives earlier than the finance roadmap assumes. The trigger is rarely a decision to go multi-entity.
The situations that force the change:
A local selling entity in a new country. Customers want a domestic supplier, or local law requires a resident entity to invoice residents.
An acquisition. The acquired company keeps invoicing under its own tax ID while contracts novate.
An e-invoicing mandate. Clearance regimes validate invoices against the supplier's registered tax ID, so the issuing entity has to be the registered one.
Distinct brands with separate P&Ls. Two products, two companies, one billing pipeline.
How do teams structure entities and customers?
Teams that get this right treat seller entities and customer accounts as two independent axes and map between them explicitly. Collapsing them into one hierarchy is the mistake I see most often, and it surfaces as invoices issued by the wrong company.
Axis | What it describes | Set by |
|---|---|---|
Selling entity | Which of your companies issues the invoice | Your corporate structure, tax registrations, licences |
Customer hierarchy | Which account is billed and which consumed | The customer's group structure and contract |
Entity-to-customer mapping | Which entity serves which customer account | Contracts, jurisdiction, transfer pricing policy |
The third row carries the work. One customer group can hold contracts with two of your entities at once, and each bills separately.
Intercompany billing is the other half. When one entity delivers work that another invoices externally, it bills that entity internally, and the document gets flagged so it disappears on consolidation. A US parent invoices a customer $40,000. The EU subsidiary delivered $15,000 of it and charges the parent cost plus a 5% markup, so $15,750. Group external revenue stays $40,000, but book both without an intercompany flag and the group reports $55,750.
Consolidated invoicing runs the other way, combining charges across a customer's subsidiaries onto one document. That's the customer axis, and both axes operate at once.
What does multi-entity invoicing require from a billing system?
It requires entity to be a first-class field on the invoice, carried into numbering, tax, currency, and the accounting export.
The requirements that actually bite:
Per-entity numbering sequences. India's CGST Rule 46(b) requires "a consecutive serial number not exceeding sixteen characters, in one or multiple series ... unique for a financial year" (CBIC, CGST Rules). An Indian entity needs its own series, reset on 1 April, inside sixteen characters. One group-wide counter breaks all three conditions.
Per-entity tax registration. Each entity holds its own tax IDs, and the rate resolves from the issuer rather than the parent.
Per-entity currency of record. Functional currency belongs to the entity. Presentment and conversion belong to multi-currency billing.
Entity-tagged accounting exports. Every posting carries its entity, plus the registered address and company number the document prints, so intercompany lines eliminate cleanly.
A shared metering layer underneath. Usage gets measured once and routed to whichever entity owns the contract, so no event gets rated twice.
Flexprice is enterprise-grade, open source usage based billing infrastructure for AI and SaaS companies. It can be deployed in your own VPC, on-prem, or on Flexprice's managed cloud. Entity structures are where that range pays off, because an entity bound by data residency rules runs the same engine in its own data centre while the rest of the group stays on managed cloud. Parent-child customer accounts come with the open source build rather than an upgrade, so the hierarchy an entity bills against needs no custom code over a flat account model. This multi-entity billing software comparison sets the platforms side by side, and you can book a demo to walk through your entity map.
Related terms
Entity structure sits between the tax layer above it and the invoice mechanics below it.
Consolidated Invoicing combines a customer group's charges onto one document, the mirror image of splitting by seller entity.
Merchant of Record names the entity that legally sells and carries tax and chargeback liability.
Multi-Currency Billing handles the currency an entity presents and settles in.
E-Invoicing Mandate explains the clearance regimes that tie an invoice to a registered supplier.
Tax Engine resolves the rate that applies once the issuing entity is known.
Invoice Line Item is the row where an entity's rates and tax treatment land.
FAQ
What's the difference between multi-entity invoicing and multi-company accounting?
Multi-entity invoicing is the outbound half and multi-company accounting is the inbound half. Invoicing decides which entity issues a document and under which tax registration. Accounting decides how those documents post into statutory ledgers, and it can't be right if the first step never tagged the entity.
Do subsidiaries need separate invoice numbering sequences?
In several jurisdictions yes, and it's safest to assume yes everywhere. India's CGST Rule 46(b) requires a serial number unique for the financial year and capped at sixteen characters, which one group-wide counter can't satisfy. Separate sequences also keep gaps explainable during an audit.
Can one billing system issue invoices from multiple legal entities?
Yes, provided entity is a field on the invoice rather than a setting on the account. The system needs per-entity numbering, tax registrations, currencies, and templates, plus an entity tag on every export. Model entity as a report filter and you get invoices that read correctly and fail an audit.
Back to glossary
