Splitting Billing Data
Configuring how billing data gets split between your child organizations requires you to create a rule-based dimension (RBD) with the name Bill Split and add rules to the Bill Split RBD to assign billing costs to your child organizations.
Note:Bill Split is a special default rule-based dimension. You must use this special RBD. It is only possible to have one such dimension for your organization; however, you can add multiple rules to this particular dimension to allocate accounts to your customers.
Creating the Rule-Based Dimension Required for Bill-Splitting
Important:To create a rule-based dimension, you must have the Manage organization or Manage rule-based dimensions role. For complete descriptions of each role available in Flexera One, see Flexera One Roles.
A special, default rule-based dimension Bill Split is required for bill-splitting. Once the dimension is created, continue by adding rules to allocate costs to different child organizations.
The rules you add to the Bill Split dimension relate vendor accounts to the child organizations you created for your customers. You can create a rules list with simple and basic rules on the Rule-Based Dimensions page. To create rules with nested expressions, use the Rules-Based Dimensions API. For more information, see FinOps Customizations API.
These rules are effective from the effectiveAt year and month setting you provide.
Rule-based dimensions support both multi-select value filters (using the dropdown list) and complex conditions (using the AND Boolean operator).
|
•
|
Use the multi-select value filter when allocating a cost to multiple values within the same dimension. |
For example, to allocate a cost across multiple cloud vendor accounts, select the Cloud Vendor Account dimension, and then select multiple account values from the dropdown list.
Note:For a clean, well-split RBD setup, create rules using the multi-select value filter by default. Use complex conditions only when the use case explicitly requires them.
|
•
|
Use complex conditions (using the AND Boolean operator) only for edge cases where the cost allocation requires a combination of multiple dimensions. For example, allocating costs based on a combination of Cloud Vendor Account and Bill Source dimensions. These scenarios are supported but not recommended unless absolutely necessary. |
Creating Rule-Based Dimension in a Logical Sequence
When defining multiple rule-based dimensions, it is important to maintain a clear and logical sequence for creating rules. This sequencing approach improves overall consistency and optimizes performance during rule execution.
Create all rules for one dimension before moving to the next. For example, if you are working with the Cloud Vendor Account dimension, complete all rules for this dimension first. Once you have finished creating all rules for one dimension, you should proceed to the next dimension, such as Customer Tenant ID. If you need to add another rule for a previously used dimension, you should create this rule immediately after the last rule for that dimension by using the Create New Rule option. This ensures that rules for the same dimension remain logically grouped together in sequence, even though the user interface does not physically separate them.
Following this sequencing approach ensures that:
|
•
|
Rules remain easier to read, review, and maintain |
|
•
|
Execution is optimized because the system processes related conditions together |
|
•
|
The overall RBD configuration stays clean, predictable, and consistent across teams |
To create a rule-based dimension required for bill-splitting:
|
1.
|
Go to the Rule-Based Dimensions page (Administration > Cloud Settings > Rule-Based Dimensions). |
|
2.
|
Click Create New Dimension. The Create New Dimension slideout opens. |
|
3.
|
In the Dimension Name box, enter Bill Split as the name of the dimension that you want to add. |
|
4.
|
From the Select Effective Month for Rules list, select the date (year-month) for the rules list to become effective. |
Note:A rules list describes how a rule-based dimension is populated. This rules list is effective at 12:00 UTC on the first day of the selected month, and remains effective until another set is defined for a subsequent month. For more information, see Creating Rules List.
|
5.
|
Click Save. The dimension added displays in the Dimensions list with the effective month added as a rules list under it. |
Note:Rbd_Bill displays next to the Bill Split dimension name.
|
6.
|
To add a rule to the rules list, click Create New Rule. The Create Rule slideout opens. |
|
7.
|
In the If section, add your condition for the rule: |
Note:Consider the following:
|
•
|
Rules determine how to allocate the costs. The rules are evaluated in the order they are listed. |
|
•
|
To add a rule immediately after the selected rule, click the three-dots icon next to the rule and select the Create New Rule After option. Or, select the checkbox next to the rule, and click the Create new rule after option that appears in the upper-left corner of the page. |
|
a.
|
From the Dimension dropdown list, select one of the following dimensions for bill-splitting: |
|
•
|
For Dedicated Master Payer (Full Ingestion) use the Bill Source or Billing Account ID dimension. |
|
•
|
For Dedicated Master Payer (Partial Ingestion) or Shared Master Payer (linked accounts), use the Cloud Vendor Account dimension. |
|
•
|
For Cloud Solution Providers (CSPs), use the Customer Tenant ID dimension. |
|
b.
|
Select the operator (equals) from the dropdown list. |
|
c.
|
From the Value dropdown list, select a value for the dimension for the rule to be applicable or enter a value. For example, if you select the dimension as Cloud Vendor Account, select the subscription ID prd-111115-entsrcdtes-0xxxxx7 and prd-111112-dexppr-bd-1xxxxxb. |
Note:To clear the values, click Clear all next to the Value box.
|
d.
|
In the Then section, from the Value dropdown list, select a value that you want to assign to this condition. For example, if you select 38659, the cost will be allocated to this child organization based on the condition specified. |
In this example, costs from the cloud vendor accounts prd-111115-entsrcdtes-0xxxxx7 and prd-111112-dexppr-bd-1xxxxxb will be allocated to the child organization 38659.
Note:You cannot add conditions when you select multiple values from the dropdown list. In this case, the Add Condition option is disabled.
|
e.
|
Click Save. The rule is added to the rules list. |
Consider the following:
|
•
|
To edit and delete a rule, click the three dots icon next to the rule, and then click Edit Rule and Delete Rule, respectively. |
|
•
|
To change the priority of a rule, click Reorder. You can move the rule up and down in the list by clicking the Up and Down arrows or you can change the priority of a rule by clicking the Move icon and selecting the priority and clicking Move. Or, you can drag the rule to a new location. Then, click Save Order. |