AWS Organizations and consolidated billing

AWS consolidated billing means that an organisation's management account receives and pays one bill for all member accounts, that AWS treats the usage of all accounts as one for volume tiers, the free tier, reservations and Savings Plans, and that the members' bills are information only; Organizations and consolidated billing cost nothing. What sits on the bill is the usage per account, the discounts AWS spreads over the accounts, the payer's credits and taxes, and where wanted Billing Conductor's pro forma bills per account and month; what makes it complicated is the spreading: a discount one account bought lands in another, and the report shows both.

Pricing dimensions

The organisation itself has no price, and the table shows what it changes about the prices and what AWS sells for billing beyond that. Every line of the bill carries its usage type and the account that caused it.

Consolidated billing turns the organisation into one account for pricing: the volume tiers of S3, data transfer and other services with falling rates count the usage of all accounts together, and AWS spreads the benefit over the member accounts in proportion to their usage; the free tier of the first twelve months applies to the sum of all accounts, so a new account in an old organisation gets none of its own. Reservations and Savings Plans work across account boundaries: the discount covers the matching usage in the account that bought first, then the usage in the organisation's other accounts, and the management account can switch sharing off per account, for which the buying account must be active in the preferences. The bill comes per seller: accounts with a European address are billed by AWS EMEA SARL, with VAT by the account's country, and an organisation with accounts at several sellers receives several bills. How accounts, bills and hierarchies relate across all providers is in billing accounts and hierarchies; what credits are and how they appear on the bill, in credits, refunds and corrections.

Two services build on consolidated billing. Billing Conductor produces pro forma bills per billing group with pricing plans, markups or discounts of their own, as a service provider or an internal chargeback needs, at a price per account and month; the real bill stays as it is. Billing transfer lets an account outside the organisation manage and pay the bill, with the consequence that reservations and Savings Plans apply only in the organisation that bought them, that the payer does not manage the cost allocation tags and categories, and that Cost Anomaly Detection is unavailable for the paid account. What private prices and enterprise agreements change about the bill is described in enterprise agreements and private pricing.

Invoices, exports and APIs

The management account's Cost and Usage Report holds all accounts: bill/PayerAccountId is the management account, lineItem/UsageAccountId the account that caused the usage, bill/BillingEntity tells AWS from AWS Marketplace, bill/InvoicingEntity names the seller, such as AWS EMEA SARL, and bill/InvoiceId the invoice once it is issued. What the organisation changes about the line sits in lineItem/LineItemType: Usage for usage at list price, DiscountedUsage for usage a reservation covers, with lineItem/UnblendedRate zero and the reservation's ARN in reservation/ReservationARN, whose account ID is the buying account; SavingsPlanCoveredUsage for usage under a Savings Plan with SavingsPlanNegation as the offsetting entry and SavingsPlanRecurringFee for the plan's fee in the buying account; RIFee for a reservation's recurring fee, even at zero; Fee for upfront payments; Credit, Refund and Tax at the payer; BundledDiscount, Discount, EdpDiscount and PrivateRateDiscount for discounts an organisation negotiated. lineItem/BlendedCost is the organisation's average rate for the same usage, lineItem/UnblendedCost the account's rate, and lineItem/NetUnblendedCost the rate after private discounts, only when the account has any; which figure a chargeback takes is in list, billed, effective and amortized cost. In CUR 2.0 the columns are called bill_payer_account_id and line_item_usage_account_id, and discount and total_discount gather the discounts; the structure is described in the AWS Cost and Usage Report.

In the FOCUS export, BillingAccountId is the management account and SubAccountId the member account, InvoiceIssuerName the seller, ChargeCategory separates Usage, Purchase, Credit, Tax and Adjustment, CommitmentDiscountId names the reservation or the Savings Plan, and BilledCost against EffectiveCost separates the bill from the amortized costs (FOCUS columns). A member account sees only its own usage in Cost Explorer and can create a report only on it; the organisation's discounts sit with it as the management account spread them, and the member's bill is information, not a claim. Billing Conductor delivers a pro forma report per billing group with the same columns and the group's prices. The Organizations API, ListAccounts and DescribeOrganization, delivers the accounts and their organizational units, and the Cost Explorer API the usage per account at USD 0.01 per request. How accounts serve allocation is in allocation by account, subscription and project; which tags and categories the management account activates, in cost allocation tags and Cost Categories.

Levers

Configuration: the first lever is the sharing of reservations and Savings Plans, which stays on, because every sharing switched off lowers coverage and the usage in the account falls back to list price; whoever wants to credit discounts to an account does it in the chargeback, not in the billing. The second is buying in the management account or an account of its own for commitments, because the discount covers first where it was bought, and a purchase in a team account favours that team's usage (AWS Reserved Instances, AWS Savings Plans). The third is the seller: accounts with addresses in different countries receive separate bills with currencies and taxes of their own (invoice currency and exchange rates).

Purchase option: none for the organisation; the services' volume tiers and commitments apply across all accounts (sustained use and tiered discounts).

Architecture: one account per team and environment makes lineItem/UsageAccountId the first-order allocation that needs no tags; the shared services, data transfer and support stay with the payer and are spread. Billing Conductor only where a pro forma bill per customer or business unit is demanded, because it costs per account and month and a chargeback in a tool outside the bill does the same; billing transfer only where several organisations actually need one bill, because it ends the sharing of commitments across organisations.

Where it goes wrong

• The discount sits in the wrong account. A reservation from the platform account covers usage in the team account, and the team sees DiscountedUsage at zero. The fee sits with the buyer; the chargeback computes amortized, not by the bill.
• Sharing is switched off. An account without sharing pays list price while another's reservation stays unused. The setting per account shows it; the reservation's utilisation falls.
• The new account has no free tier. The free tier applies to the organisation, not per account. A development account in an old organisation pays from day one.
• The volume tier is missing from the chargeback. AWS spreads the tier discount over the accounts by usage, and an account alone would have paid a higher tier. Whoever charges back per account at list price charges more than the bill shows.
• Two bills, one organisation. Accounts at different sellers receive separate bills with separate taxes. The sum in the report is right, the bill does not match one figure.
• The credit vanishes at the payer. A credit is applied to the management account's bill, not to the account that earned it. Credit lines sit with the payer; the chargeback assigns them.
• Billing transfer ends the sharing. Reservations and Savings Plans apply only in the organisation that bought them, even when another account pays the bill. There is no reservation for all organisations.

Example

List prices in USD for Frankfurt (eu-central-1), read on 2026-10-21 from the AWS price list: Organizations and consolidated billing cost nothing; Billing Conductor USD 8.25 per account and month for the first 500 accounts; data transfer to the internet USD 0.09 per GB for the first 10 TB a month and USD 0.085 up to 50 TB; an m7g.large instance on demand USD 0.0978 per hour.

Two accounts of an organisation transfer 8 TB and 4 TB to the internet in a month: alone they would pay 8,192 × 0.09 = USD 737.28 and 4,096 × 0.09 = USD 368.64, USD 1,105.92 together; consolidated, AWS counts 12 TB, 10,240 × 0.09 = USD 921.60 plus 2,048 × 0.085 = USD 174.08, so USD 1,095.68, and spreads the USD 10.24 saving over both accounts by usage, leaving the organisation's 100 GB free allowance aside. An m7g.large that runs 730 hours in the team account costs USD 71.39 on demand; with a reservation from the platform account it sits in the team account as DiscountedUsage at USD 0, and the reservation's fee sits as RIFee with the platform account, so the team's bill falls by USD 71.39 and the platform's rises by the fee while the organisation saves the difference. Billing Conductor for 50 accounts in billing groups costs USD 412.50 a month, for 600 accounts 500 × 8.25 + 100 × 6.75 = USD 4,800.00. The figures show that volume tiers across accounts save percentage points, that commitments move the bill between accounts without costing the organisation more, and that Billing Conductor costs per account what a chargeback tool does per organisation.

Sources

Read on 2026-10-21. Billing: consolidated billing for AWS Organizations, effective billing date, account activity and volume discounts, Reserved Instances in Organizations, Reserved Instances and Savings Plans discount sharing, applying AWS credits, transfer billing management to external accounts. Prices: AWS Billing Conductor pricing, AWS Cost Explorer pricing, Amazon EC2 on-demand pricing. Billing data: Cost and Usage Report columns: lineItem, Data Exports: CUR 2.0, FOCUS 1.0 with AWS columns.