Automating Billing Transfer Operations at Scale for AWS Partners
Learn how partners can automate CUR exports, pro forma billing adjustments, reporting, and margin analysis to operate Billing Transfer efficiently at scale.
Executive summary
Setting up Billing Transfer to centrally manage billing and payments across multiple AWS organizations is multi-step process, which includes configuring Cost and Usage Report (CUR) exports to gain granular spend visibility centrally, and pro forma billing data adjustments to surface the desired cost data to end-users whose accounts are transferring billing management.
The Billing Transfer Automation Portal is an open-source reference implementation ( https://github.com/aws-samples/sample-billing-transfer-workflow-automation), that helps you streamline the end-to-end Billing Transfer configuration process by adding an automation layer that uses AWS SDK calls for operational workflows. The portal also features the integration with AWS Billing & Cost Management Model Context Protocol (MCP) Server for AI-assisted natural language queries via Amazon Bedrock, providing an intelligent assistant for ad-hoc billing questions about the accounts managed with Billing Transfer.
The portal supports multi-account management through cross-account AWS Identity and Access Management (IAM) roles, and an Amazon DynamoDB backed account registry, enabling distributor partners who operate multiple billing-transfer accounts (BTAs) to view and manage their entire BTA portfolio from a single deployment.
By integrating with your existing billing systems, you can reduce manual effort, improve consistency, and operate billing transfer more efficiently at scale.
As you move from supporting a subset of your customer portfolio, to adopting Billing Transfer at scale, this solution will help you operate more efficiently.
Introduction: Operating billing transfer at scale with automated workflows
Billing Transfer enables a management account (the bill-transfer account) to manage and pay for the consolidated bill of another management account (the bill-source account). The bill-transfer account uses AWS Billing Conductor to control the pricing and cost data visible to bill-source accounts.
After a transfer starts, the bill-transfer account gains access to two billing views for each bill-source account:
- My View shows the billing data that the bill-transfer account is financially responsible for
- Showback/chargeback view shows billing data configured through AWS Billing Conductor for the bill-source account
AWS Cost and Usage Report (CUR) exports are scoped to these billing views. As a result, the Billing Transfer relationship must become active before CUR exports can be configured with the correct billing view Amazon Resource Name (ARN). The Billing Transfer Automation Portal automates this workflow by discovering the billing view ARN after the transfer becomes active and provisioning the required CUR exports, eliminating the need to manually monitor transfer status before completing CUR configuration.
AWS Billing Conductor is the custom billing engine service that produces pro forma billing data, shown in the showback/chargeback view, which reflects what customers see in their account. AWS Billing Conductor pro forma data reflects the configuration enabled through AWS Billing Conductor Pricing Plans. AWS Billing Conductor supports two types of pricing plans: AWS managed pricing plans and Customer managed pricing plans. AWS managed pricing plans are predefined by AWS and cannot be modified or deleted. They include BasicPricingPlan, which generates pro forma billing data while excluding credits, taxes, Premium Support charges (such as Business and Enterprise Support), and non-public discounts, and PassthroughPricingPlan, which reflects AWS invoice data without applying custom pricing logic. Customer managed pricing plans are fully managed by the user and can be created, modified, or deleted as needed. Building on the same baseline billing model as BasicPricingPlan, they allow partners to define custom pricing rules that modify public pricing rates by applying markups or discounts. They also provide full configurability for Custom Line Items (CLIs), enabling you to tailor pro forma billing information to your business requirements, including modeling charge types that aren't included in the default pro forma view.
The Billing Transfer Automation Portal addresses a common operational scenario encountered when using BasicPricingPlan. Because certain charge types, including credits, premium Support charges, taxes, and refunds aren't included in the pro forma view by default, Partners often choose to model these charges as CLI to present the desired billing information to their customers. The portal automatically identifies these gaps and generates the appropriate CLI either as a one-time operation or through scheduled daily reconciliation.
Architecture: Billing operations layer

The Billing Transfer Automation Portal introduces a lightweight operational layer between partner systems and AWS billing services.
Operational endpoints: Uses the AWS SDK (boto3) directly for both read and write operations: querying Cost Explorer, listing billing groups, managing CUR exports, creating Custom Line Items, running Athena queries, and tracking credits.
AI billing assistant: Uses the AWS Billing & Cost Management MCP Server via Strands Agents on Amazon Bedrock, enabling natural language queries against billing data through tool calling.
A FastAPI backend orchestrates these interactions and exposes REST API endpoints that integrate directly into partner billing portals.
This approach lets you standardize workflows and extend your existing systems without managing multiple service integrations.
Workflow 1: CUR 2.0 export management at scale
AWS Cost and Usage Report (CUR) 2.0 provides the detailed cost and usage data required for billing analysis and reporting across billing groups.
This solution automates the end-to-end lifecycle of CUR export configuration for Billing Transfer environment. It dynamically discovers billing view ARNs using the Billing Views API, inventories existing CUR exports across billing groups, identifies missing or unhealthy configurations, provisions exports with the correct billing view, schema, and format settings, and continuously validates export health after Billing Transfer activation. By replacing repetitive manual configuration with API-driven workflows, you can consistently provision, maintain, and remediate CUR exports across their entire Billing Transfer portfolio while reducing operational overhead.
The portal exposes REST API endpoints that enable partner billing platforms to inventory existing exports, provision individual or batch exports, remove stale or unhealthy configurations, and automate CUR export management as part of their existing operational workflows.
Endpoint | Method | Function |
|---|---|---|
/cur-manager | GET | Inventory all existing CUR exports and identify gaps |
/cur-manager/create | POST | Create a single export with correct schema and billing view ARN |
/cur-manager/create-all-missing | POST | Batch-provision Showback and My View exports for all uncovered billing groups |
/cur-manager/delete | POST | Delete a stale or unhealthy export |
/cur-manager/run-crawler | POST | Trigger Glue Crawler to update the catalog after new exports land |
Table: CUR Export Manager REST API Endpoints
Workflow 2: Pro forma gap analysis
The Showback/Chargeback view reflects pricing models applied through AWS Billing Conductor. As mentioned above, when using the BasicPricingPlan certain charge types don’t appear in pro forma billing data by default: support plan charges, AWS credits, refunds, tax, and non-public discounts. These charge types can be explicitly modeled using Custom Line Items (CLI) in AWS Billing Conductor.
The portal’s Pro Forma Gap Analyzer feature, uses the Billing Views API and Cost Explorer to compare what you pay AWS (My View) against what your customer sees (Showback/Chargeback). It discovers BILLING_TRANSFER and BILLING_TRANSFER_SHOWBACK view ARNs for each customer, then queries Cost Explorer grouped by RECORD_TYPE and SERVICE. This gives you per-customer actuals for support, credits, refunds, tax, and discounts broken down by individual AWS service.
To simplify pro forma reconciliation, the portal classifies excluded charge types into three categories based on the recommended action:
- Actionable – Charge types that you typically pass through to your customers, such as Premium Support charges (for example, Enterprise Support).
- Detected – Charge types that the portal identifies for your review because whether you pass them through depends on your business policy, such as credits and refunds.
- Informational – Charge types that the portal surfaces for visibility but that you don't typically pass through to your customers, such as taxes and non-public discounts
The portal matches existing CLIs against the detected charge types and identifies which items are already covered, helping you quickly determine what still requires action.
You can configure pass-through charges using flat CLIs scoped either at the RECORD_TYPE level (for example, passing all Premium Support charges at 100%) or at the individual AWS service level (for example, passing Enterprise Support charges at 100% while absorbing Developer Support charges). When you use BasicPricingPlan, flat CLIs appear under the AWS Billing Conductor service on the customer's Bills page. If you want flat CLIs to appear under a specific AWS service (for example, AWS Support), you can migrate to a Customer managed pricing plan and update the CLI configuration in the AWS Billing Conductor console.
The portal supports two modes for creating CLIs:
- Save and schedule (recommended) – Saves your pass-through configuration and runs a nightly reconciliation workflow using Amazon EventBridge and AWS Lambda. The workflow queries AWS Cost Explorer for the latest month-to-date amounts, replaces previously created CLIs, and creates updated flat CLIs. This keeps your customer's pro forma view synchronized as charges accumulate throughout the billing period.
- Create now – Creates flat CLIs immediately for the current billing period using the latest values returned by AWS Cost Explorer

What previously required manual CLI creation every billing period for every billing group becomes a configure-once workflow with automated daily reconciliation.
Other functionalities: Partner Dashboard and Margin Visibility
The Partner View Dashboard aligns My View and Showback into a single perspective. It provides portfolio-level visibility (i.e., across multiple BTAs) into cost, billing, and margin, with the ability to drill down into individual billing groups and track trends over time.
This gives you clear financial insight across your entire portfolio.

Integration with Your Existing Billing Platform
A key design principle: you should not need to replace your existing billing infrastructure. If you have an existing billing platform built in Node.js, Java, .NET, or any other stack, you can run only the FastAPI backend and consume its REST API endpoints from your own frontend. This backend-only deployment mode means you can integrate the automation capabilities into any existing workflow without disrupting current operations.
The REST API endpoints cover the full spectrum of billing transfer operations — from CUR export inventory and provisioning to pro forma analysis and CLI configuration, pro forma margin reporting, and multi-account management. You can call these endpoints from your existing systems using standard HTTP requests, adding to your existing stack.
Deployment Mode | Description | Best For |
|---|---|---|
Full-Stack | FastAPI backend + React frontend running together via uvicorn and pnpm dev | Partners who want a ready to deploy interface for managing Billing Transfer workflows across their portfolio |
Backend-Only | FastAPI backend exposing REST API endpoints, consumed by partner's existing frontend | Partners who want to embed Billing Transfer automation into their existing billing platforms |
Local Development | Run everything locally for evaluation, testing, and customization before production deployment | Partners evaluating the solution or building custom extensions before committing to a production deployment |
Table: Deployment Options for the Billing Transfer Automation Portal
Getting Started
The Billing Transfer Automation Portal is available as an open-source reference implementation on GitHub. To deploy the solution in your environment, clone the repository and follow the setup instructions in the README:
sample-billing-transfer-workflow-automation ( https://github.com/aws-samples/sample-billing-transfer-workflow-automation )
The repository supports full-stack and backend-only deployment modes. Prerequisites, IAM permissions, and configuration steps are documented in the repository.
Conclusion
The operational workflows that accompany it – such as pro forma adjustments, CUR management, reporting, and margin analysis – are areas where automation delivers additional value. The Billing Transfer Automation Portal enables you to automate key workflows using AWS SDK integration and the AWS Billing & Cost Management MCP Server for AI-assisted billing queries.
By integrating with your existing systems, you can scale billing operations efficiently while maintaining consistency and visibility across your entire customer portfolio.
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article