Skip to main content

Overview

Cloud Capital uses AWS Billing Transfer to take responsibility for your AWS invoices while you keep full control of your AWS Organizations, accounts, infrastructure and security. This allows you to access discounts, improve visibility, and remove operational overhead without changing how your AWS environment is structured or managed. Billing Transfer is a native AWS feature used by partners and customers to simplify billing and access better commercial terms, without impacting how their AWS environment operates day-to-day. We use this AWS native mechanism so that:
  • Your AWS environment, Organizations structure, IAM, SCPs and root accounts stay owned and operated by you.
  • Cloud Capital only assumes responsibility for billing, discounts and payments on your behalf as a Certified AWS Advanced Partner, reseller.
This page explains how AWS Billing Transfer works with Cloud Capital, what changes, what does not, and how we handle common concerns around control, tax, discounts, security, exit and operational risk.

How AWS Billing Transfer works

At a high level:
  • Cloud Capital’s AWS management account (the bill-transfer account) sends a billing transfer invitation to your AWS Organizations management account (the bill-source account)
  • Your AWS Administrator, with Organizations permissions,  can accept the invite. When you accept this invite, Cloud Capital becomes responsible for managing and paying the consolidated bill for your Organization from the agreed start month onwards. This invite is sent after all of the proper documents sent by Cloud Capital have been signed by your team.
From AWS’s perspective:
  • Only the billing moves to Cloud Capital.
  • Your AWS environment continues to operate exactly as before. Your workloads, accounts, data, services, Reserved Instance commitments and Savings Plans all remain in your own Organization.
  • Your relationship with AWS remains unchanged. You continue to work directly with your AWS account team, support, and services as you do today.
  • For more detail, see the AWS documentation on billing transfer.

What changes versus what stays the same

1. Billing and payments

What changes
  • Once Billing Transfer is active, you will receive your AWS usage invoices from Cloud Capital, with the contracted discounts and benefits under our agreement. You will no longer receive invoices directly from AWS. Any invoices issued to you prior to Billing Transfer must be settled directly with AWS.
  • All payment terms, currency, and payment method will be as set out in the Order Form with Cloud Capital.
  • Cloud Capital receives the AWS invoice(s) for your transferred Organization from the transfer start date onwards and pays AWS directly.
  • Cloud Capital can view the billing and cost data AWS exposes to the bill-transfer account (for example Cost Explorer, CUR, Budgets, Bills), in order to calculate your discount and produce your invoice.
What stays the same
  • Billing Transfer does not move or migrate any AWS accounts.
  • Billing Transfer does not change which account is the management account for your AWS Organization.

2. Infrastructure, security and access

What changes
  • Cloud Capital’s visibility is limited to the billing data AWS exposes to the bill-transfer account. Billing Transfer itself does not change infrastructure or security access.
  • Historical cost data in AWS billing views is reset as part of the transfer, so earlier data may no longer show in Cost Explorer after the switch. Importantly, no data is lost - Cloud Capital preserves and backfills your full cost history in your own S3 bucket and within our Forecasting platform for ongoing reporting and analysis. If you need a longer (3 year) cost history, you may need to open an AWS Support case to have them backfill the CUR data.
  • AWS Cost Anomaly Detection is not supported for bill-source accounts — this is an AWS limitation that applies after any Billing Transfer, regardless of partner. Existing monitors and any newly created monitors will not generate alerts. AWS Budgets and budget alerts continue to work as new cost data accumulates (typically reliable after 36–60 days of fresh data). See AWS Cost Anomaly Detection in the FAQ below for alternatives.
What stays the same
  • Billing Transfer does not grant Cloud Capital any infrastructure-level or security-level control within your AWS environment.
  • Cloud Capital cannot access, create, modify, or delete any  AWS resources in your accounts.
  • Cloud Capital cannot change your AWS Organizations structure.

Onboarding flow with Cloud Capital

  1. Prepare: You and Cloud Capital agree the target start month, and we review your existing setup, discounts, PPAs, SPs/RIs and Marketplace usage. We handle the backfill of your historical cost data as part of onboarding. If extended history (up to 3 years) is required, this can be requested via AWS Support request for a CUR backfill.
IAM policy check required before accepting the invitation. AWS accounts created before March 6, 2023 commonly have legacy aws-portal:* billing IAM actions that block Billing Transfer from being enabled. Use the AWS Bulk Policy Migrator (5–15 min) to identify and update any affected policies in your management account and member accounts before proceeding.Check and migrate legacy IAM billing policies →
  1. Invitation: You receive a Billing Transfer invitation from Cloud Capital in your AWS Organizations management account, specifying the start month and pricing configuration.
  2. Accept: Your management account administrator reviews the details and accepts the invitation in the AWS console.
  3. Go live: From 00:00 UTC on the first day of the agreed month, Cloud Capital becomes responsible for the consolidated bill for your Organization.
  4. Operate: You continue to run your AWS environment as before. You receive Cloud Capital invoices with the contracted discounts and benefits under our agreement.

Common questions

1. Control and lock-in

  • You retain full control of your AWS Organizations, accounts, IAM and infrastructure
  • Billing Transfer does not give Cloud Capital management or root access
  • Billing Transfer can be reversed at any time directly within AWS

2. Security and data access

  • Cloud Capital only receives billing data (e.g. cost and usage data, tags, account metadata)
  • We do not access application data, workloads or logs
  • Any additional access is optional and read-only

3. Discounts and commitments

  • Billing Transfer does not change how your workloads run or how AWS services are used
  • Existing commitments (SPs, RIs, PPAs) continue to apply
  • We work with you and AWS to optimize future commitments and reduce risk

4. Tax and invoicing

  • Cloud Capital becomes the billing entity and seller of record for AWS usage
  • Invoicing, currency and tax treatment are configured during onboarding

5. Data and reporting

  • No historical data is lost — it is preserved and backfilled by Cloud Capital
  • Cost Explorer and AWS Budgets continue to work for ongoing usage as new cost data accumulates
  • AWS Cost Anomaly Detection is disabled after Billing Transfer (an AWS limitation) — see below for alternatives
  • Full data export is available if you ever leave

6. AWS Cost Anomaly Detection

AWS Cost Anomaly Detection (CAD) is not supported for bill-source accounts — this is an AWS-imposed limitation that applies after any Billing Transfer. Existing monitors stop generating alerts immediately, and new monitors created after the transfer will not alert either. This cannot be resolved through reconfiguration. Alternatives that cover most use cases: AWS Budgets — AWS Budgets and budget alerts continue to work after Billing Transfer and are often a good direct replacement. They operate on your pro forma cost data (the discounted rates Cloud Capital configures on your behalf). If you had budgets previously set against undiscounted AWS pricing, you may want to revisit the thresholds downward to reflect your new effective rates. Budgets become most reliable once 36–60 days of fresh post-transfer data has accumulated. Cloud Capital + Claude — if you use Claude Desktop with the Cloud Capital MCP connected, you can ask Claude to check your spend against any condition you care about — service, tag, account, time period — and have it create or update a Cloud Capital alert on your behalf. This works well for custom anomaly-style checks that AWS Budgets thresholds can’t easily express (for example, watching a specific tag combination or a ratio between two services). You can set up a recurring check to run daily or on whatever cadence makes sense. Neither works for your use case? We’d love to understand what you were using Cost Anomaly Detection for specifically — some patterns have solutions we can help set up, and others are good candidates for new Cloud Capital features. Reach out to your Cloud Capital contact or support@cloudcapital.co with a description of what you were monitoring.

7. AWS relationship and support

  • You retain your direct relationship with AWS, including your account team and support
  • You continue to work with AWS exactly as you do today
  • Cloud Capital works alongside AWS, often in partnership with your AWS team

Summary

Using AWS Billing Transfer with Cloud Capital lets you:
  • Keep full control over your AWS Organizations, accounts and security
  • Move billing, discounts and payment operations to a specialist partner
  • Gain richer visibility into past and future cloud spend through our analytics and forecasting platform
  • Maintain a clear, reversible path back to direct billing if you ever need it
If you have questions on how this applies to your specific setup, your Cloud Capital contact and your AWS account team can walk through it with you.