AWS Billing Conductor FAQs

A billing group is a set of accounts within your consolidated billing family – in the pro forma billing domain only – that share a common end customer. That end customer maintains the “Primary Account” and can see the cost and usage that accrues across its group. Each billing group’s pro forma usage is computed as its own consolidated billing family, sharing RI and Savings Plans benefits only within the group and accrues volume tier discounts (e.g., S3 and CloudFront) and an “always” free tier offering. An account can only belong to one billing group during a billing period.

While there isn’t a direct relationship between Billing Groups and Organizational Units today, you can easily mirror your Organizational Unit structure when creating your billing groups and import your OUs during the billing group creation process. To do that, you need organizations:ListAccounts and billingconductor:ListAccountAssociations IAM permissions to retrieve your account level data (ID, account name, email) in AWS Billing Conductor.

You can adjust pricing rates either globally, by billing entity, by individual service, or SKU within a service if needed. You will be able to create pricing plans, which are a collection of pricing rules that you can assign to one or to multiple billing groups in a billing period. Each billing group can have its own pricing plan, as needed. Global rules apply to all usage in a billing group. Billing entity rules (such as AWS Marketplace) only apply to charges that match that billing entity. Service-specific rates apply to a specific service consumed in the billing group. SKU pricing rules apply to the unique combination of usage type and operation, within a selected service.

A custom line item is an adjustment applied to a specific billing group for a specific billing period (either current month or last month). Custom line item can be one time or recurring, and calculated on a flat or percentage basis. Each adjustment has a free text description and can be edited or deleted during the current or last month.

Custom line items, and their free text description, will show up under the ‘Billing Conductor’ service name on the Billing console. For the CUR, custom line items will be under the product_product_name column as ‘AWS Billing Conductor’ with the free text description under the line_item_line_item_description column.

Yes. You can request a backfill of your existing billing group configuration. To do so, please cut a ticket to support and specify the billing group name and time period you need. Limitations apply.

Yes. While the AWS Billing Conductor logic shares many similarities with the standard AWS Billing data model, there are a few differences. The AWS Billing Conductor does not include credits (redeemed at the payer or linked account level), tax, support charges, or any non-public discounts. Additionally, the AWS Billing Conductor shares reserved instances and savings plans with the accounts placed within the same billing group, irrespective of your sharing preferences in the standard billing domain.

Margin is the difference between the charged amount (what accounts within a billing group are shown) and the actual AWS costs for the same set of accounts. Margin is shown from a month-to-date view on the dashboard, and in the margin analysis section of the AWS Billing Conductor console. If you are not interested in retaining margin, you can also use the margin calculation to determine the appropriate amount of “unallocated savings” which you can apply to your billing groups at your discretion.

AWS-issued credits are not directly reflected in the AWS Billing Conductor data. By excluding credits from pro forma computation, we are giving you the discretion to determine where your credits apply, which you can do using the credit custom line item.

To stop future AWS Billing Conductor charges, delete your billing group(s).

The AWS Billing Conductor computation flexes to the changes that you make in a given month, while retaining the historical integrity of your prior period billing data. This is best described with an example:

In this example, we have two billing groups, A & B. Billing group A starts the billing period with accounts 1-3 in the group. At the mid-month point, the payer account moves Account 3 to billing group B. At that point, the re-computation of the costs for billing groups A & B are required to accurately model the latest change. When Account 3 is moved, billing group A’s usage is modeled as if Account 3 was not a part of the billing group during the current billing period. Additionally, billing group B’s usage is modeled as if Account 3 was a part of billing group B since the beginning of the billing period. This approach eliminates the need to calculate complex rates and chargeback models when accounts move across groups within the billing period.