This feature allows you to create Cost Centers within SHI One that represent different showback and chargeback entities within your organization. This enables reporting in SHI One to provide insight into consumption data across all cloud platforms by these Cost Centers.

It also customizes the ways organizations are billed for their AWS and Microsoft cloud spend.

Currently available for AWS and Azure/M365, when you purchase your AWS or Microsoft Cloud through SHI.

Need to have a contract with at least one cloud platform (AWS/Azure/GCP).

Best results for multicloud experience to have at least two contracts to see consumption across all clouds.

Customized invoices require a contract with AWS or Azure/M365.

You need Admin privileges to set up Cost Centers. Navigate to Cloud -> Cost Centers, then in the upper righthand corner click New Cost Center to create a new Cost Center and assign specific cloud platform accounts to the entity.

When setting up a Cost Center, the following fields are available:

Once you have filled out the desired fields and are ready to use the Cost Center, click Create.

After creating Cost Centers, you can select a specific Cost Center on the Cloud -> Cost Centers page and edit the Cost Center Name, Description, and PO Number. You can also delete Cost Centers from the editing screen. Finally, in the Cloud Subscriptions tab of a selected Cost Center, you can see a count of associated cloud accounts and licenses per cloud provider.

By default all Cost Centers on an account are billed collectively on one single invoice. When Cost Centers are given different Billing PO Numbers, each unique Billing PO Number will be billed to a separate invoice.

Cost Centers can have different names for reporting but use the same Billing PO Number for billing, or vice versa. This grants more flexibility and customization for organizations who have different needs for reporting and billing.

For AWS, any changes to PO Numbers made on or before the 12th of the month will be reflected in the previous month's AWS bill.  For example, a change on July 5th would impact June consumption's billing that is invoiced on July 13th.  A change on July 14th would impact July consumption's billing that is invoiced on August 13th.

For Microsoft, any changes to PO Numbers made on or before the end of the month will be reflected in the previous month's Microsoft bill.  For example, a change on June 30th would impact June consumption's billing that is invoiced on July 8th.  A change on July 1st would impact July consumption's billing that is invoiced on August 8th.

Currently Billing PO Numbers are available only for AWS or Azure/M365 accounts.

Unallocated Cost Centers grant the ability to assign a single Billing PO Number to any license/subscription that has not been assigned to a Cost Center. If no Billing PO Number assigned, they default to specific values based on the cloud provider:

Any license/subscription not allocated to a specific Cost Center would default to populating the Billing PO Number associated with the Unallocated Cost Center on the monthly invoice.

Unallocated Cost Centers can be edited on the Cloud -> Cost Centers page; the Cost Center Description, and PO Number can be edited. In the Cloud Subscriptions tab of Unallocated Cost Centers, you can see a count of associated cloud accounts and licenses per cloud provider.

Currently Billing PO Numbers are available only for AWS or Azure/M365 accounts.

Once Cost Centers are set up, you can access reporting in two places:

Clicking the 'By Cost Center' tab shows consumption by Cost Center.

Applied filters include: