Split
How Split (Cost Division) Works.
Split allows you to segment cost data imported by an Organization Data Connector and redistribute it to an Organizational Unit based on defined rules.
When creating a Split, the platform automatically generates a derived Billing Connector responsible for representing only the data slice corresponding to that Unit.
Upon accessing the Organizational Unit and clicking Configure Split, the creation screen will appear.
Billing Connector Name You must define a name for the Billing Connector that will be generated. This name identifies the derived connector within the Organizational Unit.
Examples: AWS – Marketing, Azure – Project Alpha, GCP – Finance
This connector does not create a new cloud integration. It represents only a segmentation of the Organization's Data Connector.
You must select which Organization Data Connector will serve as the base for the Split.
This connector is responsible for importing raw Billing data (e.g., AWS CUR, Azure Export, GCP BigQuery).
The Split always uses an existing connector.
You cannot create a Split without a previously configured Data Connector."
Scopes
Scopes define the conditions that determine how data will be segmented.
A Split can contain one or more scopes.
Each scope represents a set of rules that filters a portion of the source connector data.
Important Rules
The Split does not modify the Organization's original data.
Multiple Splits can use the same Data Connector.
Poorly defined scopes may result in cost overlaps.
The Organizational Unit does not have its own cloud connector.
Last updated