> ## Documentation Index
> Fetch the complete documentation index at: https://docs.withorb.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Multi-entity billing

# **Introduction**

An entity is one of your company's legally registered sellers. With multi-entity billing, one Orb account can bill customers from several entities, without duplicating customers, plans or items. Each invoice shows the correct seller name, address and tax IDs, and each payment settles into the correct payment account.

Use a multi-entity setup to easily manage:

* Regional subsidiaries: Acme Inc. (US) and Acme Ltd. (UK), each with its own tax registration.
* An acquired business: a company kept as a separate legal seller after an acquisition, still invoicing under its own name.
* Separate payment accounts: two sellers that must settle into different payment accounts for compliance or accounting reasons.

> [!NOTE]
>
> This feature is available to all Orb customers on our **Enterprise** Plan. Contact Orb to learn about access and upgrade options.

# **The Entity object**

Entities are created and managed at the Orb account level. Multiple entities can exist in a single Orb account, and there is no limit to the number of supported entities.

![Entities 1](https://mintcdn.com/orb-9bba378a/pADlgS2JSx6BmJ0w/images/entities-1.png?fit=max\&auto=format\&n=pADlgS2JSx6BmJ0w\&q=85\&s=16d5bdf573fed4d1f9d199dbfc7104de)

## What it stores

| Field | Functional impact | Required? |
| :- | :- | :- |
| Company name | Seller name printed on invoices/credit notes | Yes |
| Company address | Seller address printed on invoices/credit notes | No |
| Tax IDs | Seller tax ID (e.g. VAT or EIN) printed on invoices | No |
| Default invoice memo | Seller-specific memo details printed on invoices | No |
| Payment accounts | The Stripe accounts or Adyen merchant accounts that can collect payment for this entity's invoices. One can be marked as the default. | No |

## How it relates to other Orb objects

| **Object** | **Relationship to entities** |
| :- | :- |
| Account | Holds one or more entities. |
| Customer | Shared across all entities. A customer can hold subscriptions with different entities. You can optionally set a Default Entity per customer. |
| Items, prices and plans | Shared across all entities, in any currency. You can optionally set a Default Entity per plan. |
| Subscription | Belongs to exactly one entity, chosen when the subscription is created. It cannot be changed afterwards. |
| Subscription invoice | Uses the entity of its subscription. |
| One-off invoice | Uses the entity chosen when the invoice is created. |
| Credit note | Uses the entity details of the invoice it applies to. |

## Functional impacts

* Subscription and one-off invoices issued from this entity carry the entity specific seller details on the invoice – company name, address, merchant tax IDs, and default memo.
* Automatic [payments](https://docs.withorb.com/invoicing/payments.md#payments) for entity issued invoices are charged to the corresponding payment account.
* All downstream data accessible via API and data exports includes an entity-identifier for reporting.

# **Getting started**

## Setup

1. Ensure you are on Orb’s Enterprise plan.
2. Go to *Settings > Entities.*
3. Select *Add entity.*
   1. Enter the Company name. 
   2. Optionally add the company address, [tax IDs](https://docs.withorb.com/integrations-and-exports/tax/index.md#merchant-tax-ids) and a default invoice memo.
   3. Optionally add the payment accounts scoped to this entity. Select one or more connected [Stripe accounts](https://docs.withorb.com/integrations-and-exports/stripe.md) or [Adyen merchant accounts](https://docs.withorb.com/integrations-and-exports/adyen.md), and choose a default. Payment accounts must first be connected in *Settings > Integrations*. See Payment connections.
4. *Save*.

## Subscription creation

When creating new subscriptions or one-off invoices, select an entity this subscription belongs to.

> [!WARNING]
>
> A subscription's entity cannot be changed after the subscription is created. To move a customer to a different entity, end the subscription and create a new one with the new entity.

## Entity defaults

The account-wide default entity pre-fills the entity value for all new subscriptions and one-off invoices. This value can be overridden at subscription creation time. 

Customer- and plan- level Default Entities are optional conveniences. Use them to override the account-level default entity, when a customer or plan line is always sold by the same entity.

* Customer: On the customer's details page, edit Default entity.
* Plan: On the plan's details page, edit Default entity..

## Invoice lifecycle

Invoices reflect the seller details of the corresponding entity **at invoice issuance time.**

* Draft invoices stay in sync with the entity since they're not yet finalized. Any change on the entity carries through until issuance.
* Issued invoices lock seller details at the moment of issuance. Editing the entity afterward has no effect on invoices already issued.
* Regenerating an issued invoice re-pulls seller details from the entity, so if the entity has changed since issuance, the regenerated invoice will reflect that update.
* Credit notes always inherit the seller entity from the invoice they were created against.

# **Not currently supported**

These related features and capabilities are not yet supported, but coming soon.

* Entity-scoped in-app reports – filter and pivot by entity on billings, revenue, and AR reports in Orb
* Entity routing of ERP connections (Quickbooks/NetSuite)
* Additional entity-scoped invoice settings – custom invoice templates, currency presets, invoice numbering


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.