Skip to content

Why is one linked account showing under the other linked accounts billing?

0

Why is one linked account showing under the other linked accounts billing?

  • Payable by Account ID: AAAAAAAAAAA which is the org account. This org account has 20 accounts.

However for some reason two of the linked accounts billing are linked. Account ID

  • Linked acc BBBBBBBBBBB shows billing for two account under it:

    Charges by account section:

  1. linked acc BBBBBBBBBBB (Linked1) USD 20 000
    
  2. linked acc CCCCCCCCCC (Linked2) USD 5000
    

However linked acc CCCCCCCCCC (Linked2) USD 5000

Charges by account section only shows:
  1. linked acc CCCCCCCCCC (Linked2) USD 5000

Both linked acc BBBBBBBBBBB (Linked1) USD 20 000, linked acc CCCCCCCCCC (Linked2) USD 5000 are oayable by the org account Account ID: AAAAAAAAAAA.

What is the cause and how do we stop the Linked2 account from showing under the Linked1 account?

2 Answers
0

Possible Causes:

Based on this behavior, the issue could be due to one of the following:

  1. AWS Organizations Account Structure Issue • Linked2 (CCCCCCCCCC) may be incorrectly nested under Linked1 (BBBBBBBBBBB) instead of being directly linked to the management account.

  2. Consolidated Billing Configuration • Linked2 may be mistakenly assigned to Linked1 for billing, instead of being billed directly by the management account.

  3. AWS Cost Categories Misconfiguration • If Linked1 and Linked2 are part of the same Cost Category, AWS may be aggregating their charges under Linked1.

  4. Cost Allocation Tags Grouping Costs Together • If Linked1 and Linked2 share the same Cost Allocation Tag, their charges may be combined under Linked1 in billing reports.

  5. AWS Cost Explorer or Cost and Usage Report (CUR) Settings • The report settings might be grouping Linked2’s charges under Linked1.

Next Steps to Resolve the Issue:

Step 1: Verify AWS Organizations Account Hierarchy • Check if Linked2 is mistakenly nested under Linked1 instead of the management account. • Console Steps:

  1. Go to AWS Organizations Console.
  2. Navigate to Accounts and check the hierarchy. • CLI Command: aws organizations list-accounts

• Fix: If Linked2 is under Linked1, move it directly under the management account.

Step 2: Review AWS Consolidated Billing Settings • Ensure Linked2 is billed directly by the management account and not Linked1. • Console Steps:

  1. Go to AWS Billing Console.
  2. Click on Billing Preferences → Check the payer settings. • Fix: Update billing settings so that Linked2 is billed separately.

Step 3: Check AWS Cost Categories • Confirm whether Linked1 and Linked2 are grouped under the same cost category. • Console Steps:

  1. Go to AWS Billing Console → Cost Categories.
  2. Check if Linked1 and Linked2 are in the same category. • Fix: If they are grouped together, remove Linked2 from the shared cost category.

Step 4: Validate Cost Allocation Tags • Check if Linked1 and Linked2 share a tag that is aggregating their costs. • Console Steps:

  1. Go to AWS Billing Console → Cost Allocation Tags.
  2. Check the tags assigned to both accounts. • Fix: If they share a tag that combines costs, remove or modify the tag.

Step 5: Adjust AWS Cost Explorer Settings • Ensure costs are displayed per account without grouping. • Console Steps:

  1. Open AWS Cost Explorer.
  2. Select Group By: Account ID to see individual account costs. • Fix: Change the grouping settings to display accounts separately.

Next Steps for You:

Please review the steps above and let us know if you need further assistance. If the issue persists after these checks, we can escalate the case for deeper analysis.

[1] https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_accounts.html [2] https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/consolidated-billing.html [3] https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/manage-cost-categories.html [4] https://repost.aws/knowledge-center/organizations-no-cost-allocation-tags [5] https://docs.aws.amazon.com/cur/latest/userguide/what-is-cur.html

AWS
SUPPORT ENGINEER

answered 2 years ago

0

Please open billing conductor and review the profile groupings following:

answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.