Overview of Multi-Org
This topic gives an overview of Zuora Multi-Org and explains how it enables organizations to manage multiple operational units within a single Zuora environment.
As businesses expand into new geographies, form joint ventures, or grow through mergers and acquisitions, managing revenue across multiple organizational units becomes complex. These businesses must support new markets with different operating models and products, work with multiple transactional and reporting currencies, and meet rising expectations for integrity, compliance, data protection, and security.
Zuora provides Multi-entity and Data Access Controls (DAC) to address data security and data segmentation needs. These capabilities deliver important value but do not fully meet the complex, multidimensional requirements of modern enterprises.
What is Zuora Multi-Org?
Zuora Multi-Org allows you to model and operate multiple organizational units within a single Zuora tenant. You can define an org hierarchy under one company and assign users, configuration (such as the product catalog), customer accounts, and transactions to individual Org Units with clear, configurable boundaries. As a shared capability across Zuora Billing and Zuora Revenue, Multi-Org supports a unified, end-to-end order-to-revenue process across all Org Units.
Key capabilities include:
-
Manage all Org Units under a single tenant as a hierarchy.
-
Label and segment transactional and configuration data.
-
Configure selective user access to the data.
-
Run operational processes securely within permission scopes.
-
Support org-unit-specific and org-unit-independent processes.
For core terminology see Basic concepts and terms of Multi-Org.
Multi-Org user personas
Multi-Org is relevant to the following personas:
- Accounting and finance teams (central or per Org Onit)
- Product catalog maintainers and product managers
- Pricing decision makers
- Financial controllers
- Organization hierarchy administrators
- IT and enterprise application owners who centrally manage Zuora users and access controls
Each persona interacts with Multi-Org differently. For example, a persona might define the org hierarchy, assign user access, maintain shared or org-specific product catalogs, or consume org-specific financial reports.
How does Zuora Multi-Org work?
Zuora Multi‑Org lets you model your company as a parent–child org hierarchy. For example, Acme Corp, a global company headquartered in Germany, can be set up as the root Org Unit, with regional Org Units such as Western Europe and Central Europe, and country‑level Org Units such as Spain, France, Germany, and Austria beneath them.
Each business unit in this hierarchy is an Org Unit and can transact at all levels of this organizational hierarchy. Each Org Unit can be configured as either:
-
Transacting Org Unit: Owns customer accounts and runs billing and revenue operations; businesses can transact at any level. For example, at the Acme Corp root level, a regional unit like Central Europe, or a country unit like Germany.
- Reporting Org Unit: Does not own customer accounts or transactions, but aggregates and reports on data from its child org units.
The Acme Corp example illustrates one of many ways to structure an organizational hierarchy in Zuora Multi-Org.
Multi-Org object model
The Multi-Org object model provides a high-level view of how the key objects are related to each other and the Org Unit(s) within an organizational hierarchy.
Users to Org Units: many-to-many
You can assign a single user to multiple Org Units, and each Org Unit can have multiple users.
Org Units to configuration objects: many-to-many
You can share configuration objects (for example, products and rate plans) across multiple Org Units, and each org unit can use many configuration objects.
Accounts to Org Unit: many-to-one
Each customer account is associated with exactly one Org Unit, but a single Org Unit can own many accounts.