AWS Billing Transfer lets one AWS payer account take over billing management for another payer account’s entire AWS Organization, without either side migrating a single account. For MSPs, that means you can finally bill customers who want pricing oversight and program benefits but won’t give up ownership of their AWS Organization. MontyCloud DAY2 now supports Billing Transfer Billing Groups alongside Standard Billing Groups, in one platform.
What is AWS Billing Transfer?
Standard billing groups, built on AWS Billing Conductor, work within a single AWS Organization. The MSP’s management account owns the Organization, links the customer’s accounts under it, and applies a pricing plan across those linked accounts. That model has worked well for years, but it assumes the customer is willing to bring their accounts into the partner’s Organization.
AWS Billing Transfer removes that assumption. It lets one AWS payer account (the receiver) take over billing management for another payer account’s Organization (the source), without either side migrating accounts anywhere. The MSP sends a Billing Transfer request from its management account, selects the pricing plan that should apply, and the customer accepts from their own management account. Once accepted, AWS automatically creates a billing group tied to that transfer, and the selected pricing plan applies across the entire source Organization. The commercial relationship changes. The technical boundary does not.
How is Billing Transfer different from a Standard Billing Group?
The distinction comes down to who owns the AWS Organization:
- Standard Billing Group: The customer’s accounts are linked inside the MSP’s Organization. One Organization, one owner: the MSP.
- Billing Transfer Billing Group: The customer keeps their own AWS Organization. The MSP’s payer account manages pricing and billing for that entire Organization through an accepted transfer, and AWS Billing Conductor applies the plan.
For MSPs and distributors, that opens a customer segment that was hard to serve under the traditional linked-account model: customers who want billing oversight and program benefits without giving up ownership of their AWS Organization.
Why does AWS Billing Transfer matter for your billing practice?
Billing is a core revenue function for most MSPs, not a back-office task. A customer segment you cannot bill cleanly is a segment you cannot fully monetize, no matter how good the underlying managed services are.
Now you can:
- Serve customers who retain ownership of their AWS Organization while you still manage pricing, margin, and billing oversight.
- Run this alongside every Standard Billing Group you already manage, from the same platform, instead of tracking Billing Transfer relationships in a spreadsheet or a separate tool.
That second point is the one that matters most operationally. If DAY2 is already where you manage Standard and Billing Transfer Billing Groups, adding a second billing model outside the platform creates exactly the kind of fragmented workflow a no-code CloudOps platform is supposed to eliminate.
What’s new in DAY2 for Billing Transfer Billing Groups?
Billing Transfer Billing Groups are now visible and creatable in DAY2 with the same clarity and control as Standard Billing Groups.
See both group types clearly: Standard and Billing Transfer Billing Groups now live in separate views within the Billing Groups page, each with the columns that actually matter for that model. Standard groups show management account, primary account, and linked account counts. Billing Transfer groups show transfer status, receiver and source accounts, and whether the source customer is already onboarded in DAY2.
Create either type from one workflow: The Create Billing Group wizard now supports both paths. Choose Billing Transfer, and DAY2 walks you through selecting the receiver tenant and management account, picking a pricing plan (including the AWS-managed Passthrough plan built for this model), and attaching the specific Billing Transfer the group belongs to.
Know where every customer stands: If a source management account hasn’t been onboarded into one of your DAY2 tenants yet, the group says so plainly, so you always know the real state of the relationship instead of guessing.
What’s next for Billing Transfer in DAY2?
This release is the foundation, not the finish line. MontyCloud is continuing to expand what’s possible in DAY2 so you can manage more of your customers’ billing needs in one place, with the same clarity and control. Billing is too important to your bottom line to run outside the platform you already trust for cost, compliance, and operations. See how Billing Transfer Billing Groups fit into your DAY2 workflow.
Request a demo to see it in action.
FAQs
What is AWS Billing Transfer?
AWS Billing Transfer is a feature that lets one AWS payer account (the receiver) manage billing for another payer account’s entire AWS Organization (the source), after the source account accepts the transfer request. Neither side moves accounts between Organizations.
How is AWS Billing Transfer different from AWS Billing Conductor?
AWS Billing Conductor is the underlying pricing and billing-group engine. AWS Billing Transfer is a way to apply Billing Conductor pricing across an entire external AWS Organization, instead of only to accounts linked inside your own Organization.
Does AWS Billing Transfer require the customer to move their AWS accounts?
No. The customer keeps their AWS Organization exactly as it is. Only billing management and the applied pricing plan change hands, and only after the customer accepts the transfer from their own management account.
Does DAY2 support AWS Billing Transfer today?
Yes. DAY2 now supports Billing Transfer Billing Groups alongside Standard Billing Groups, including a dedicated view, a guided creation workflow, and onboarding status for each source customer.
Who should use Billing Transfer Billing Groups instead of Standard Billing Groups?
MSPs serving customers who want pricing oversight and program benefits but are unwilling to link their accounts inside the MSP’s AWS Organization. Standard Billing Groups remain the right fit when the customer is comfortable joining the MSP’s Organization directly.