Cross-Account Duplicate Detection Behavior
Who this is for
Organizations with multiple cloud accounts connected to CloudAIPilot who want to understand how costs are attributed and whether any cost is counted twice.
What you will complete
Understand how CloudAIPilot handles multiple cloud accounts from the same provider, and when duplicate cost detection applies.
The multi-account cost scenario
If you have connected multiple AWS accounts (for example, a production account and a staging account from the same organization), CloudAIPilot pulls billing data from each account separately. The FinOps total reflects the sum of all accounts.
This is correct behavior: Each account's costs are real and separate. They are not duplicates.
When duplicate detection matters: consolidated billing
Some organizations use consolidated billing (also called management accounts or payer accounts):
- AWS Organizations: A management account that receives a consolidated bill for all member accounts
- GCP Billing Account: One billing account covering multiple projects
- Azure Enterprise Agreement: One billing account covering multiple subscriptions
The risk: If you connect both a management/payer account AND the individual member accounts to CloudAIPilot, the same costs may appear in both — once in the management account's billing data and again in each member account's data.
CloudAIPilot detects this pattern and warns you when duplicate billing data is detected. When duplicate detection triggers:
- A warning banner appears in the FinOps dashboard
- The affected accounts are listed
- You are asked to choose: keep the management account data, or the member account data (not both)
Best practice: which account to connect for FinOps
| Setup | Recommended for FinOps |
|---|---|
| Single account per provider | Connect that account |
| AWS Organizations (consolidated billing) | Connect the management account only |
| Multiple independent AWS accounts | Connect all — they are not duplicates |
| GCP with one billing account, multiple projects | Connect via the billing account, not individual projects |
| Azure Enterprise Agreement | Connect at subscription level — EA management account data is not always available via API |
What success looks like
- The FinOps dashboard total matches your expected spend without double-counting.
- No duplicate detection warning appears.
- The By Account breakdown shows each account with its individual spend (not combined management account + member account).
Common errors and fixes
"FinOps shows double the spend I expect" Cause: Both a consolidated billing account and individual member accounts are connected. Fix: Go to Cloud Accounts and disconnect either the consolidated billing account or the individual member accounts — keep only one level.
"Duplicate detection warning appears but I want to keep both accounts" Cause: CloudAIPilot detected overlapping billing data. Fix: If you genuinely need data from both account levels, email support@cloudaipilot.com — some advanced configurations support per-account budget tracking alongside consolidated totals.