Skip to content

    AWS Billing and Cost Management Merges Conductor and Transfer Views Into One

    AL
    Aria Lin

    November 11, 2026

    AWS Billing and Cost Management began accepting three source view types in custom billing views on Nov 10, 2026: billing group views, billing transfer views, and transfer showback views. The headline is the consolidation, but the buried lead is that nothing about who can see

    AWS Billing and Cost Management Merges Conductor and Transfer Views Into One

    AWS Billing and Cost Management began accepting three source view types in custom billing views on Nov 10, 2026: billing group views, billing transfer views, and transfer showback views. The headline is the consolidation, but the buried lead is that nothing about who can see what has changed. This is a plumbing upgrade for data you already hold, and it arrives at no additional cost.

    For FinOps teams, AWS Partners and any organization running chargeback, the practical question is whether one filtered view can replace the pile of per-customer views they maintain today. Per AWS, it can, and this article covers what changed, who benefits, and what the announcement leaves unanswered.

    What's new

    According to AWS, AWS Billing and Cost Management now supports AWS Billing Conductor and AWS Billing Transfer views as source views for custom billing views. A custom billing view (a saved, filterable slice of your cost data) previously could not draw on these AWS-maintained views. Now it can, and several can be combined into a single view with filters applied.

    The three source view types are these:

      • Billing group views: the cost of each AWS Billing Conductor billing group, which can be combined for chargeback and showback across business units.
      • Billing transfer views: the cost transferred to you for each end customer.
      • Transfer showback views: the cost that end customer sees.

    Read together, the three types describe one chain: what each billing group costs, what is transferred to you for each end customer, and what that customer is shown. Aggregating each type gives your total transferred cost and the total bill your end customers see. AWS maintains these views per billing group and per billing transfer relationship, so the new capability layers on views that already exist rather than creating new data.

    Lined notepad, blank calculator and three small stacks of copper, silver and gold coins arranged on a wooden desk, suggesting cost tracking and billing.

    For context, AWS documentation describes AWS Billing Conductor as a custom billing service for AWS Channel Partners and organizations with chargeback requirements. It builds pro forma cost data (a second version of your costs, derived from pricing plans, pricing rules and custom line items), and that data is accessed through billing views.

    The combined view works in Cost Explorer, AWS Budgets, and the Billing and Cost Management console. It is available in all commercial AWS Regions at no additional cost. To get started, open Billing Views in the AWS Billing and Cost Management console, or see the user guide.

    Why it matters

    AWS frames the benefit as one consolidated view instead of one per customer or group. For an organization using billing groups for pro forma billing, that means rolling business-unit groups into a single view for chargeback and showback. For an AWS Partner reselling AWS services, it means comparing total transferred cost against the total bill end customers see in one place, rather than reconciling separate views by hand.

    Filters add a second lever. Because filters can be applied to the combined view, one view can be narrowed to the slice a given team cares about, and that slice can then be used in Cost Explorer, AWS Budgets and the console.

    Two hands pass a brass key to each other across a wooden desk, suggesting access being handed over between partner and customer.

    The sharing model extends the reach. A custom billing view can be shared through AWS Resource Access Manager (RAM, the AWS service for sharing resources across accounts) with accounts inside or outside your organization. AWS gives two examples: a finance team, or a downstream seller, working with the data in their own account.

    The access rule is the caveat to read twice. AWS states that you can use an AWS-managed view as a source only where you can already access it. The feature consolidates visibility; it does not widen it.

    Billing Conductor itself does not alter invoices. AWS documentation says its configurations do not affect customers' existing AWS invoices or billing configurations, and that billable and pro forma costs may differ during the month but usage values match at month end once the invoice is issued. Teams building showback on combined views should treat the numbers accordingly.

    Competitive Landscape

    The AWS announcement makes no competitor comparisons, and the available peer material is thin. Third-party roundups of AWS cost tools list Amnic first and Economize third in "The 9 best cost optimization tools for AWS in 2026," though the snippets give no positioning beyond those rankings. A separate roundup describes CloudHealth by VMware as "Best for Multi-Cloud Cost Management and Centralized Billing."

    What can be said is narrower: this capability is first-party, sits inside the Billing and Cost Management console, and costs $0 extra. AWS Cost Explorer and the AWS Cost and Usage Report are AWS's own tools, not rivals.

    A person in a white shirt squares a stack of red, blue and green folders on a white desk beside a silver laptop.

    What's next

    AWS's announcement names no roadmap, performance metrics or customer counts, so next steps are practical ones:

      • Open Billing Views in the AWS Billing and Cost Management console, or read the user guide.
      • Check which billing group, billing transfer and transfer showback views you can already access, since those are the only ones usable as sources.
      • Consider whether a combined view should be shared through RAM with a finance team or downstream seller.

    Open questions remain.

    Billing tooling rarely makes headlines, yet it decides how quickly a finance team can answer "who spent this." AWS has spent years generating the views; this release finally lets them be stacked in one place. The tidy part is the consolidation.

    For a partner finance lead managing transferred cost across many end customers, the near-term change is one filtered view in Cost Explorer and AWS Budgets, shareable by RAM with a downstream seller, in place of one view per customer. The cost is $0 and the access rules stay as they were.

    -- Aria Lin, Enterprise Technology Analyst

    Sources: AWS · AWS What's New announcement · AWS Billing Conductor documentation

    More on Revuzia