Best practices for Org Unit labeling

1. When Multi-Org is enabled in Zuora Billing, data access is controlled through Org Unit labels assigned to resources. To maintain proper data isolation, apply Org Unit labels consistently across all related catalog resources.

   If labeled and unlabeled resources coexist within the same product catalog hierarchy, users might encounter unintended cross-org visibility behavior. Unlabeled resources can remain visible across multiple Org Units, even when related resources are restricted to specific Org Units.

   To ensure consistent and predictable data isolation behavior in Multi-Org environments:

   • Apply Org Unit labels consistently to all related catalog resources, including products, rate plans and rate plan charges.

   • Do not mix labeled and unlabeled resources within the same product catalog hierarchy.
   Note: A combination of labeled and unlabeled resources in a Multi-Org environment is not a supported configuration and can result in unintended cross-org visibility.

2. When you create a new org for an existing Zuora Billing customer who is transitioning to Zuora Multi-Org, close any preexisting unlabeled accounting periods. Zuora automatically creates a new accounting period for the new org.

Multi-Org key considerations

• Zuora Analytics does not support Multi-Org.

• When the Enhanced OTR feature is enabled, accounting periods cannot be configured at the org level in Zuora Revenue. In integrated Zuora Revenue environments, accounting periods must be consistent across all org units.

• Zuora 360 supports integration with only a single Salesforce environment. Currently, a 1:1 mapping is enforced between a Zuora Multi-Org tenant and a single Salesforce org.

• Zuora Mediation does not segment events based on org configuration.

• For Marketplace and Connect Apps hosted on the Connect Framework, each app instance is visible to all Org units because this is a tenant level setting. For example, Promo Code App, Zuora Collections.

• Tenant-level settings, such as numbering formats, SKU formats, tax engine, and accounting codes, are shared by all org units. Per-org-unit overrides are not available. .

• If you use Multi-entity, you can enable Multi-Org at the leaf entity level. For more information about the co-existence of Zuora Multi-Org as a leaf entity in the Zuora Multi-entity environment, seeMulti-Org upgrade path.

• Multi-Org does not support intercompany transactions between org units, whether upstream, downstream, or lateral. Process any intercompany activity across org units outside of Multi-Org.

• Multi-Org does not support a many-to-many relationship between customer accounts and org units. Assign each customer account to exactly one org unit at any given time.

• Files generated from Zuora Billing, such as Data Source Exports (DSE), AQuA outputs, and reports, are not labeled with org tags. As a result, these files are not automatically segmented by org unit in their output.

• Multi-Org does not support configuration of custom objects or their records at the org level. Custom objects do not carry org labels and cannot be segmented natively by org unit.

• Zuora Collections supports data synchronization for Multi-Org tenants, but it does not support org-level data labeling. All synchronized data is handled the same across the tenant, and org hierarchy or labels are not applied within Zuora Collections.

• Orders are created at a single org unit. Each order is associated with exactly one org unit, and you cannot combine order lines from multiple org units into a single consolidated order.