By clicking “Accept”, you agree that cookies may be stored on your device in order to improve site navigation, analyze site usage, and help us with our marketing efforts. Check out our for more information.

Guides

Multi-entity billing: the guide for groups and enterprises

#QUOTE-TO-CASH Insights
Opencell #QUOTE-TO-CASH Insights cover: Multi-entity billing, the guide

Multi-entity billing: the guide for groups and enterprises

OpencellNovember 21, 202614 min read

A group sells like one company. Yet it must bill like several.

Multi-entity billing is the ability to issue, from one system, the invoices of several legally separate companies: subsidiaries of a group, operations in several countries, brands run by different legal structures. Each entity keeps its own identity, invoice numbering, tax rules and accounting, but shares the group's catalog, customers and processes.

For a small business running two companies, a billing tool that can switch invoice headers is often enough. For a group selling subscriptions and usage-based services in several countries, to customers that are themselves organized as groups, it is a different story. You must know which entity bills what, to which customer entity, in which currency, with which tax, and how those flows reach each company's books and then the consolidated accounts.

Most search results on the topic are product documentation for startups. This guide is for groups and enterprise accounts: it explains the three multi-entity situations, the master data to control, intercompany billing, the impact of VAT and e-invoicing, and how to choose a multi-entity billing platform.

For the bigger picture, see our quote-to-cash guide.

What is multi-entity billing?

Multi-entity billing means managing the invoicing of several legal entities in one system instead of one tool per company. It gives a single view of customers and group revenue, applies common rules (catalog, prices, billing and dunning), and still respects each entity's obligations: legal mentions, numbering, tax and accounting.

For billing purposes, an entity is a legal person that issues invoices in its own name: it has its company name, registration and tax numbers, address, bank details and its own invoice number sequence. A group often has several, because it operates in several countries, has acquired companies or separates its businesses.

Multi-entity billing serves three goals:

  • a single view of the group's customers, contracts and revenue,
  • common rules: catalog, prices, billing and dunning processes,
  • compliance for each entity: legal mentions, numbering, tax, accounting.
One tool per entity Multi-entity billing
Offer and price catalog Duplicated, with discrepancies Shared, with variants by entity or country
Customer present in several countries Several unrelated records One account hierarchy
Launching an offer Repeated in every tool Configured once, opened to the relevant entities
Group revenue Consolidated by hand Available by entity and for the group
Acquiring a company One more tool One more entity

The three multi-entity situations

Multi-entity billing covers three situations that often combine in large groups: the seller has several entities (which entity bills which sale?), the customer has several entities (who receives the invoice and with what detail?), and the group's entities bill each other (how to reflect economic reality without errors?).

1. The seller has several entities

The group bills customers from several companies: one per country, per business or per brand. The core question is: which entity bills which sale? The answer depends on the customer's country, the offer, the contract or the sales channel. It determines numbering, currency, tax, invoice language and the bank account the customer pays into.

2. The customer has several entities

The customer is itself a group: a parent company, subsidiaries, sites, cost centers. It negotiated a master agreement at group level, but each subsidiary orders, consumes and pays on its own, or on the contrary expects a consolidated invoice. The core question is: who receives the invoice, and with what level of detail?

3. The group's entities bill each other

One subsidiary sells a service to a customer, but another group entity owns the platform, the staff or the licenses. Costs or revenue must be recharged between companies under precise tax rules. The core question is: how to reflect economic reality between entities, without errors or double counting?

The master data to control

Before invoices, master data decides whether multi-entity billing succeeds: the settings of each issuing entity, customer account hierarchies, a shared catalog with local variants, and explicit rules that assign each sale to the right issuing entity.

Issuing entities

For each entity: legal identity, tax IDs, address, bank details, numbering sequence, accounting currency, default language, invoice templates, chart of accounts and country tax rules. These settings must live in one place, with dated history: a new address or bank account must apply from a given date without rewriting past invoices.

Customers and their hierarchies

One customer can be served by several group entities, and be organized on several levels itself. The account hierarchy describes this structure: customer group, subsidiaries, billing accounts, sites or users. It is what lets you apply negotiated terms at the right level and produce the invoice the customer expects.

The offer and price catalog

A shared catalog avoids recreating each offer in each entity. It must still accept differences: prices by country or currency, offers reserved for some entities, country-specific tax rules. Our guide to pricing models details the price components to combine.

Assignment rules

Finally, explicit rules determine the issuing entity for each sale: based on customer country, type of offer, contract or channel. When these rules stay implicit, known only to a few people, wrong-entity errors become one of the main causes of rejected invoices.

Billing from several entities

Each issuing entity needs its own invoice numbering, legal mentions, currency handling, tax rules, languages and billing calendar. A multi-entity platform manages all of them in parallel from shared data, so one entity's cycle never blocks another's.

Numbering and mandatory mentions

Each entity needs its own chronological, continuous invoice number sequence. Mandatory mentions depend on the issuing entity's country and on the customer's. E-invoicing mandates add new ones: in France, for example, the buyer's company registration number and the category of transaction.

Currencies and exchange rates

An entity can bill in its own currency or in the customer's. The system must then apply a dated exchange rate, keep amounts in both currencies and handle exchange differences at payment. Prices can also be set directly in each currency, to avoid awkward converted amounts.

Tax by country

VAT rules, or sales and indirect taxes outside Europe, depend on the issuing entity's country, the customer's country, the type of service and whether the customer is a business or a consumer. A cross-border B2B service between two EU countries, for instance, generally falls under the reverse charge. A configurable tax engine, or one connected to a specialist tax service, avoids hard-coding these rules into each invoice template.

Languages and templates

An invoice reads better in the customer's language. Each entity can have its own templates, branding and mentions while sharing the same data structure. That is also what makes it possible to produce, from the same data, a readable PDF and a structured e-invoice.

Cycles and calendars

Entities do not always share a calendar: billing dates, month-end closes, public holidays, direct debit runs. The system must run billing cycles per entity, without blocking the others.

Billing a customer organized as a group

Enterprise customers negotiate at group level and expect those terms to apply automatically to every subsidiary, order and usage record. They choose between one consolidated invoice, invoices per subsidiary or a consolidated invoice with allocation detail, and impose their own purchase order and supplier portal rules.

Master agreements and negotiated terms

Large accounts negotiate at group level: discounts, specific prices, volume commitments, caps. These terms must apply automatically to each subsidiary, order and usage record, without re-entry. When the commitment covers the group's total volume, all subsidiaries' consumption must be added up to calculate tiers.

Consolidated invoice or one per subsidiary

Some customers want one invoice for the whole group, others one per subsidiary, others a consolidated invoice with detail by site or cost center. The same customer may change its mind after a reorganization. The system must let you choose, at each level of the hierarchy, who receives the invoice and who pays.

Mode For whom What to watch
Invoice per subsidiary Autonomous subsidiaries, local payment Still apply group terms
Consolidated invoice Centralized procurement Detail by subsidiary or cost center in an appendix
Consolidated invoice, split payment Groups that recharge internally Allocation data the customer can use
Invoice per seller entity Customer served by several group entities A consolidated account view despite several invoices

A customer served by several seller entities

The two situations intersect: an international customer may receive invoices from three group entities, each in its own country. For the sales team and the customer, it is still one account. The account hierarchy must link these invoices to give a consolidated view: total revenue, open balance, disputes, terms applied.

Portals and purchase orders

Large accounts often impose their own rules: a purchase order number on every invoice, upload to a supplier portal, a cost allocation reference. An invoice that misses them gets blocked, which lengthens payment times. Our guide to reducing DSO covers these causes of delay.

Intercompany billing

Group entities recharge each other for shared platforms, teams, licenses or brands, and subsidiaries resell services produced by other entities. Across borders, these flows follow transfer pricing rules and the arm's length principle. Automating them like external billing keeps both sides consistent and simplifies consolidation.

Why entities bill each other

In a group, one entity often carries costs or assets that serve the others: a technical platform, shared teams, licenses, a brand. It recharges them to the entities that benefit. A subsidiary can also resell locally a service produced by another entity.

Transfer pricing

When entities are in different countries, these recharges fall under transfer pricing. The arm's length principle, set out in the OECD Transfer Pricing Guidelines and applied by most tax administrations, requires that terms between related companies match those that independent companies would agree. Large groups must document their transfer pricing policies.

For billing, that means documented recharge rules, applied consistently and traceable: allocation key, markup, period, supporting data.

Automating intercompany flows

Manual recharges at quarter end, built from spreadsheets, are a frequent source of discrepancies between entities. The same mechanisms used for external customers can apply: each group entity is treated as a customer of the others, with a contract, pricing rules and automatic billing. Billing then produces consistent entries on both sides, which eases reconciliation and the elimination of intercompany transactions in consolidated accounts.

VAT, VAT groups and e-invoicing

VAT groups, available in many EU countries, treat closely linked companies as a single taxable person, taking transactions between members out of the VAT system. E-invoicing mandates apply entity by entity: each entity must issue the right format through the right channel, and a wrong-entity invoice becomes a rejection.

VAT groups

Many EU countries allow closely linked companies to form a VAT group, treated as a single taxable person. Transactions between members fall outside the scope of VAT, and invoices to third parties are issued in the name of the VAT group, usually identifying the member that made the supply. France introduced this option in 2023; under the French reform, transactions between members of a VAT group are subject neither to mandatory e-invoicing nor to e-reporting.

E-invoicing, entity by entity

E-invoicing mandates are spreading. According to impots.gouv.fr, since September 1, 2026 every French company must be able to receive e-invoices, and large and mid-sized companies must issue them; smaller companies follow on September 1, 2027. At EU level, the VAT in the Digital Age package adopted in 2025 will make e-invoicing the norm for cross-border B2B transactions from 2030.

For a group, what counts is the situation of each entity. Each entity must be connected to the channel required in its country, with its own invoicing addresses. On the customer side, invoices must reach the right entity, with the right identifiers: a wrong-entity error that used to be fixed with an email becomes a rejected invoice.

Outside Europe

Each country has its own rules, and more and more countries require or are preparing B2B e-invoicing. An international group must be able to produce, for each entity, the format expected in its country from shared billing data. The billing system supplies the data; transmission goes through each country's platforms or networks.

Payment, accounting and consolidation

Each entity collects on its own bank accounts and books its own entries, but the customer's open balance must stay visible at group level. When intercompany recharges come from the same system with shared references, consolidation eliminations are easier and discrepancies shrink.

Collecting in the right place

Each entity collects on its own bank accounts. Payments must be matched to the right entity's invoices, including when a group customer pays several invoices from several entities in one transfer. Dunning follows each entity's rules, but the open balance must stay consolidated at customer level.

Booking by entity

Billing produces each entity's entries, in its chart of accounts and currency, and sends them to the ERP. For companies reporting under IFRS or US GAAP, the system must also provide IFRS 15 revenue recognition data, or its ASC 606 equivalent, by entity.

Consolidating

Consolidated accounts eliminate transactions between group companies. When intercompany recharges are produced by the same system, with shared references on both sides, eliminations are easier and gaps between entities shrink.

How to choose a multi-entity billing platform

Small-business billing tools can often run several companies, each in its own space. A group selling subscriptions and usage to customers organized as groups needs more: entity settings with history, a shared catalog with variants, deep hierarchies, assignment rules, multi-currency tax, intercompany billing, e-invoicing, consolidated collections and ERP integration.

Criterion What to check
Entities Number of entities, settings per entity, dated history
Catalog Shared catalog with variants by entity, country and currency
Account hierarchies Several levels, inherited terms, consolidated or per-subsidiary invoices
Assignment Rules that automatically determine the issuing entity
Currencies and tax Multi-currency, dated exchange rates, tax engine by country
Intercompany Automatic recharges, traceable transfer pricing rules
E-invoicing Structured formats, connection to platforms, lifecycle statuses
Payment Multi-entity cash matching, dunning per entity, consolidated open balance
Accounting Entries per entity, ERP interface, revenue recognition data
Volumes and usage Ability to rate high usage volumes for every entity
Integration APIs to CRM, ERP, technical systems and e-invoicing platforms

Ask for a demo on a real case: a customer present in three countries, served by two group entities, with a master agreement, a consolidated invoice and an intercompany recharge. That is where solutions really differ. Our guide to subscription management software offers a broader grid.

Frequently asked questions about multi-entity billing

What is multi-entity billing?

It is the ability to issue, from one system, the invoices of several legally separate companies in a group, each with its own identity, numbering, tax and accounting, while sharing the catalog, customers and processes.

What is the difference between multi-entity and multi-company billing?

The terms are often used interchangeably. Multi-company stresses the legal entities; multi-entity also covers branches, countries or brands, and the handling of customers that are themselves organized in several entities.

Does each subsidiary need its own invoice numbering?

Yes. Each issuing entity needs its own chronological, continuous number sequence. One system can run these sequences in parallel.

How do you bill a customer with several subsidiaries?

With an account hierarchy: the master agreement is defined at customer group level and applies to its subsidiaries; the invoice can be consolidated at group level or issued per subsidiary, with detail by site or cost center.

What is intercompany billing?

It is billing between companies of the same group, for services, shared costs or licenses. Across countries, it must follow transfer pricing rules and the arm's length principle.

Do invoices between VAT group members fall under e-invoicing rules?

Transactions between members of a VAT group are outside the scope of VAT. Under the French reform, they are subject neither to mandatory e-invoicing nor to e-reporting; invoices to third parties are issued in the VAT group's name.

Is small-business billing software enough for a group?

For a few companies with simple sales, often yes. As soon as you need a shared catalog, group customers, several currencies, usage volumes and intercompany flows, a billing platform designed for these cases becomes necessary.

A complex organization, a simple invoice

Multi-entity billing is not about multiplying invoice headers. It is about faithfully representing the group's organization and its customers', so that every sale is billed by the right entity, to the right entity, at the right price, with the right tax.

Key takeaways:

  • three situations combine: multi-entity seller, multi-entity customer, intercompany flows,
  • master data (entities, hierarchies, catalog, assignment rules) drives invoice quality,
  • each entity keeps its own numbering, mentions, currency and tax,
  • group customers expect inherited terms and an invoice that fits their organization,
  • intercompany billing follows transfer pricing rules,
  • e-invoicing works entity by entity, and a wrong-entity error becomes a rejection,
  • one system for customers and intercompany flows simplifies consolidation.

The more complex the group, the simpler the invoice must be for the customer.

Go further with Opencell

Opencell is an agile, open source monetization platform that automates quote-to-cash, from quote to cash collection, for subscription and usage-based services. It is built for high-volume companies with complex offers: account hierarchies, negotiated contracts, hybrid subscription and usage offers, several entities and currencies, on one platform integrated with CRM and ERP through more than 200 APIs and connectors. Born in telecoms in 2007, it manages €14 billion in revenue for around fifty customers.

Does your group bill from several entities?

Optimize your recurring revenues with Opencell

Get a demo