I’ve moved my end customers linked accounts to a different payer account, what are the effects of doing so?

Products

• CloudHealth

Issue/Introduction

This may result in costs being split across multiple accounts and make reporting confusing.

As an example, we will take a look at the ‘Customer 123’ below. This customer has linked Accounts A and B assigned to them currently from Payer Account Y: 

 

 

On October 16th, linked Accounts A and B were moved to another payer account, Payer Account Z.  The Accounts A and B will now show a ‘Disabled’ message on the Partner Generated Billing assignment table.

 

 

At the Partner level, costs will be visible when categorizing the Cost History report by Billing Account on the daily interval and these account costs will switch over to the new Payer account on October 16th. 

From a customer account standpoint, costs do not appear from October 16th onwards.  This is due to the fact that, via Partner Generated Billing, the platform is not able to generate an end customer billing file stemming from two separate Partner Payer Accounts.

The platform will read the costs from the Payer Account that you’d prefer so it may require re-pointing the account for Partner Generated Billing.  In other words, you are able to decide if you’d like for your end customer to have visible access to the costs either from 1st-16th October or 16th-31st October (but not both simultaneously).

Once the October AWS bills have finalized (usually within the first 5-7 days of the following month), the engineering team can commence a ‘bill stitching’ task to combine the two separate payer account costs.  This involves extracting the line items from each Payer Account and merging these to create a complete end customer billing file showing costs for the entire month.

For this task to be completed, please submit a ticket to our Technical Support Team confirming:

• Customer Name
• Customer linked accounts that were moved
• Payer accounts, original and new
• Date that you moved the linked accounts