Unable to assign an account to a customer billing block

Products

• CloudHealth

Issue/Introduction

Why can I not assign an AWS account to my Customer's billing block?

Resolution

There are a couple of reasons why an account may not be available for assignment to your Customer's billing block:

1. The account has a 'No Current Billing' account type.
   This means that CloudHealth has not detected any spend for this account. You may need to check that you have the current Payer account configured in CloudHealth to allow us to collect spend for this account.
   
   
2. There is a Linked account with CUR configured. In this case, the account scanner job will fail and won't update the Account type for any newly linked accounts.
   You can check for any linked accounts with CUR configured in the account report by adding the Cost and Usage Report Bucket/Path fields. (See the screenshot below)
   
   Please remove the CUR configuration from CloudHealth from the linked account as a workaround.
   
   
3. The account is already assigned to another billing block, either under the same customer or another.
   A single account cannot be assigned to more than one billing block at a time.  You should review where the account needs to be assigned currently and then make any necessary changes.

It's worth noting that if you remove the account from another billing block and request to regenerate any historical bills for that customer, the costs for this account will be removed. Similarly, if you request to regenerate historical bills for the customer you've moved the account to, historical costs for this account will be present.