Skip to main content

Overview

Consolidated billing lets an enterprise or holding company purchase one plan that covers multiple subsidiary teams or entities. Each child customer generates usage independently, but all usage aggregates under the parent subscription, producing a single invoice for the parent. subscription_type results:
  • Parent subscription: parent
  • Each child: inherited (auto-created skeleton, no line items)

How it works

When to use consolidated billing

  • Enterprise with subsidiaries: Global HQ purchases an enterprise plan. Regional divisions (APAC, EMEA, Americas) each generate usage independently. HQ receives one consolidated invoice.
  • Holding company: A holding company owns multiple brands. Each brand operates as a customer. Finance at HQ handles all invoices.
  • Internal chargeback: A company tracks usage per department for internal reporting, but the central IT team is invoiced.

Prerequisites

  • Parent customer created in Flexprice
  • Each child customer created in Flexprice (with a known external_id)
  • A plan created in the product catalogue
  • Child customers must not already have an active inherited subscription under another parent
On create, you cannot combine inheritance.external_customer_ids_to_inherit_subscription with invoicing_customer_external_id or subscriptions_ids_for_grouped_invoicing in the same request.

Configure

Step 1: Create customers

Create the parent customer and each child customer through the Dashboard or API. Customer records have no hierarchy fields; they stay flat.

Step 2: Create the parent subscription with child inheritance

1

Start a new contract

In the dashboard, subscriptions are called contracts. Go to Contracts and click New contract.
Contracts list with the New contract button
2

Choose the parent customer and plan

In the Contract step, select the parent customer in Customer and choose a Plan. Adjust the billing period, currency, and dates if needed, then click Next.
Contract step with the parent customer and plan selected
3

Add the child customers

Click Next through Charges & add-ons and Commitments & benefits to reach the Billing step. In the Customer hierarchy card, keep Billing customer on Same customer, then add each child customer in Inherited customers.
Customer hierarchy card on the Billing step with two inherited customers
The list shows only customers with an external ID. A customer that has its own contract, or inherits another customer’s contract, is greyed out.
4

Review and create

Click Next. On the Review step, check that Billing customer shows Same customer and that Inherited customers lists every child, then click Create contract.
Review step listing the inherited customers

Step 3: Verify

Open the parent subscription’s detail page. Child skeleton subscriptions appear under it.

Post-creation changes

You can add additional child customers to an existing parent subscription using the modify API.
Replace {parent_subscription_id} with the id of the parent subscription.You can preview the modify operation without committing changes using POST /subscriptions/{id}/modify/preview with the same request body.

Analytics: per-child and aggregated

Inherited children do not appear in billing usage summaries. All billable usage is attributed to the parent subscription. For analytics (non-billing), use POST /events/analytics. Aggregate all children under the parent:
Per-child usage breakdown:
include_children: true aggregates all inherited children’s usage into the parent’s response. Query each child’s external_customer_id individually to see per-child contribution.
Get customer usage summary for a child that only has an inherited subscription returns no billable usage on that child. This is expected. Confirm totals on the parent customer or use analytics as above.

Validations and constraints

Child already has an inherited subscription. A customer that already has an inherited subscription under another parent cannot be added as a child here. Error: "customer already has an inherited subscription". Resolve: cancel the existing inherited subscription or use a different child customer.
Inherited subscriptions cannot be cancelled directly. Calling cancel on an inherited subscription returns an error: "inherited subscription cannot be cancelled directly". Cancel the parent subscription instead. All inherited children are cancelled automatically at the same time.
Cascade behavior. When the parent subscription is paused, resumed, or cancelled, all inherited children are updated to match automatically.
Wallet balance. The parent customer’s wallet is used for all settlement. Inherited children have no independent wallet balance for this subscription.
Mutual exclusion. The inheritance.external_customer_ids_to_inherit_subscription field cannot be combined with invoicing_customer_external_id or subscriptions_ids_for_grouped_invoicing in the same request.

Frequently asked questions

No. Currency is set on the parent subscription and applies to all invoices. Inherited children use the parent’s currency.
Plan changes apply to the parent subscription only. Inherited skeleton subscriptions keep routing usage events to the updated parent.
Billable usage for inherited subscriptions is attributed to the parent subscription. A child with only an inherited subscription has no independent billing usage ledger. This is expected. Use POST /events/analytics for per-child breakdowns.

Delegated Invoicing

When children need their own subscriptions but a third party pays

Grouped Invoicing

When separate subscriptions should merge into one invoice