Chargeback vs Chargeforward: AWS Billing Conductor vs AWS Invoice Configuration

Note: "charge forward" is not an AWS term. It is an informal label used in this article to contrast with chargeback. The official AWS names are AWS Billing Conductor, AWS invoice configuration, and invoice units.

Scenario

Organizations with consolidated billing often need to separate cost for a subsidiary, a business unit, or a partner customer. Two AWS features address this, and they are easy to confuse because both deal with who pays for what. They act in different places, though. Billing Conductor produces a custom, alternate view of your cost and leaves the real invoice unchanged. Invoice configuration changes the actual AWS invoice, splitting it into separate invoices for the accounts you choose.

A short way to frame the contrast: Billing Conductor is a chargeback tool, because you re-allocate cost internally with a custom pro forma bill. Invoice configuration is the "charge forward" case, because AWS sends the real invoice to the entity that owns the spend.

Billing Conductor: the chargeback tool

Billing Conductor builds pro forma cost data from pricing rules, pricing plans, and custom line items applied to a billing group. It is designed for chargeback and showback. It does not change your real invoice, your credits, or your Reserved Instance and Savings Plans discounts. You use it to show or charge cost back at rates you define, and you can generate a Cost and Usage Report per billing group.

Invoice configuration: the "charge forward" case

Invoice configuration splits the real AWS invoice by business entity. You group accounts into invoice units and assign an invoice receiver for each. There is no custom pricing. It takes the actual AWS charges and routes them to the account you choose, so the right entity is invoiced directly.

Figure 1. Creating an invoice unit in the console.

One caveat on scope: both features work inside a single consolidated billing family, and Billing Conductor crosses organizations only through billing transfer. Neither feature moves money between legal entities by itself.

Side by side

Considerations

• Pro forma data can take up to about 24 hours to appear after you create a billing group, so a new group showing zeros is expected at first.
• Billing Conductor charges a per-account fee for accounts in a billing group. Factor it into the plan.
• An invoice unit's name and its invoice receiver cannot be changed after the unit is created.
• Invoice configuration does not add new accounts automatically. Add them manually or through the AWS Invoicing APIs.

Conclusion

Use Billing Conductor when you need custom rates or margins and internal or partner cost recovery, while keeping the real AWS invoice intact. Use invoice configuration when you need a separate, real invoice per business entity, delivered to the right account. The two are not mutually exclusive: you can split invoices with invoice configuration and layer Billing Conductor on top for the rated view.

Sources

• What is AWS Billing Conductor? https://docs.aws.amazon.com/billingconductor/latest/userguide/what-is-billingconductor.html
• What is pro forma billing data? https://docs.aws.amazon.com/billingconductor/latest/userguide/understanding-proforma.html
• AWS Billing Conductor product page and FAQs https://aws.amazon.com/aws-cost-management/aws-billing-conductor/
• Customizing your invoice preferences with AWS invoice configuration https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/invoice-configuration.html
• Creating invoice units with AWS invoice configuration https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/invoice-configuration-create.html