Viewing shared costs in the Cost & Usage Explorer

Our Example

We will use this small bill for every example below.

What should happen:

Shared box $80  ── split evenly ──►  Team A gets $40
                                     Team B gets $40

Team A = $300 (EC2) + $40 (from Shared) = $340
Team B = $100 (RDS) + $40 (from Shared) = $140

Views that show the split Cost ✅

1. Group by the business mapping

   This is the easiest way to see the split.

   Group by: business mapping	Cost
   Team A	$340
   Team B	$140
   The Shared box is empty, so it is not shown.

2. Group by the business mapping, then by service

   The split works, but remember the rule: the shared money keeps its "S3" tag. So it gets its own line. It is not added to the EC2 line.

   Business mapping	Service	Cost
   Team A	EC2	$300
   Team A	S3 (from Shared)	$40
   Team B	RDS	$100
   Team B	S3 (from Shared)	$40

3. Filter to one team, group by service

   Filter: business mapping = Team A. Group by: service.

   Service	Cost
   EC2	$300
   S3 (Team A's part of Shared)	$40
   Total	$340

Views where you will NOT see the split ❌

1. The business mapping is not in the view

   If you don't group by the business mapping and don't filter by it, there are no business group. You see the plain cloud bill: EC2 $300, RDS $100, S3 $80. Nothing to split.

2. A filter throws the shared money away

   Filters run first, before the split. If a filter removes the shared money, there is nothing left to split.

   Example: filter service = EC2. The $80 of S3 is gone before the split starts.

   Business mapping	What you expect	What you see
   Team A	$340	$300
   💡Tip: filter by the business mapping (Team A), not by the things the rules look at (service).

3. Budgets

   Budgets do not include split cost. A budget filtered by a business mapping counts each team's own money only.

Extra rules for "group by" mappings

A group-by mapping makes many boxes automatically, one per value. For example, one box per linked account:

Expected: Projects (111) = $340, Projects (222) = $140.

Everything in sections 3 to 5 still applies. On top of that:

⚠️ Group by linked account: the split sits on the account that paid

Same name-tag rule. The support money is tagged "account 999", so that is where it shows up.

This looks exactly like the bill without any mapping. Account 111 does not grow to $340. To see $340, group by the business mapping. The split is also even here even if it was set to "Ratio" (see section 5).

❌ Filter by linked account without the account that paid

Filter: linked account = 111. The support money (account 999) is filtered out before the split.

⚠️ Filter by linked account with the account that paid

Filter: linked account = 111 and 999. Now the support money is there, but the system only sees the boxes in your filter. Account 222 is filtered out, so it is not in the split, and account 111 gets all of it.

💡Tip: with a group-by mapping over linked accounts, don't filter or group by linked account. Group by the business mapping and pick the account's box (for example, "Projects (111)").

Cheat Sheet