Skip to main content

Billing Plans

Billing plans help you set up billing rules for your customers. You can group customers (child organizations) together and apply the same rules to all of them. This makes billing analysis and invoicing easier to manage across multiple accounts.

Once you've created a billing plan, you can:

  • Edit, delete, or duplicate a plan
  • Change the order of the rules inside the plan
  • Add an adjustment to the plan
  • Track bill processing status in billing history
  • Define the day of the month that the monthly billing reports are automatically locked in the lock settings

Before you can use billing plans for the first time, make sure you have created at least one customer and the bill split rule-based dimension:

Create a billing plan​

  1. Make sure you have a customer defined, and the bill split rule-based dimension.

  2. Go to the Billing Plans page (Customers > Customers > Billing Plans).

  3. Click New Plan and enter a name (and description) for the plan.

  4. Find and select the customers to include in the plan, then click Save.

    A customer can only be included in one billing plan.

  5. Click Add Rule, select the rule type, and click Next.

  6. Configure the billing rule or billing rule adjustment, then click Save.

  7. You can change the order of the rules in a plan by clicking Reorder.

    note

    Commitment rules (reserved instance, reservation, and savings plan reallocation rules) are always applied first. You cannot reorder commitment rules.

    The order of the remaining rules affects the final billing calculations.

Add an adjustment to a billing plan​

Use this method for recurring adjustments that are part of your standard service offerings. These adjustments only affect customers in the billing plan.

  1. Go to the Billing Plans page (Customers > Customers > Billing Plans).
  2. Open the billing plan you want to add an adjustment to.
  3. Click Add Rule, select the adjustment type, and click Next.
  4. Configure the adjustment settings, then click Save.
  5. You can control the order in which adjustments are applied by clicking Reorder.
  6. Reprocess the bills.

Create a standalone adjustment​

Use this method for one-off adjustments like end-of-month credits, special charges, or billing corrections. Standalone adjustments can apply to customers across different billing plans.

Standalone adjustments are applied in the order they were created. You can schedule them to run across multiple billing periods.

  1. Go to the Billing Plans page (Customers > Customers > Billing Plans).
  2. Click Adjustments > New Adjustment.
  3. Select the adjustment type and configure the settings:
    • Find and select the customers to apply the adjustment to, then click Next.
    • Choose to apply the adjustment before or after the billing rules. This affects the final calculation.
    • Choose either basic or advanced rule-based dimensions.
  4. Click Save.
  5. Reprocess the bills.

Reprocess bills after updating a plan or adjustment​

After you change a billing plan or add an adjustment, you need to reprocess existing bills to apply the new rules. This recalculates the bills with your updated settings.

  1. Go to the Billing History page (Customers > Customers > Billing History).
  2. Find the bills for the customers you want to reprocess.
  3. Click Manage, then select:
    • Reprocess to recalculate the bill using existing data and the new adjustment.
    • Unlock & Reprocess to pull in any new data from the cloud provider and recalculate the bill. This makes sure margins and totals are accurate.
  4. Click Proceed.

Billing rules​

When you create a plan, you add rules that change how billing works for your specific needs. Billing rules handle many scenarios, from applying discounts to basic cost allocation.

Commitment rules​

Savings plan reallocation: distribute AWS or Azure savings plan benefits across customers

Savings plans have discounted rates compared with on-demand, but are purchased at the account or organizational level. For MSPs, one account may underutilize savings plans, while another has high on-demand costs. This rule lets you distribute the savings plan benefits according to your strategy to minimize your overall utilization.

You can choose to:

  • Retain vendor-shared benefits. This keeps the default vendor allocation logic. Benefits are automatically shared across linked accounts according to the cloud provider rules.
  • Restrict benefits to the owner account only. This limits savings plan benefits strictly to the purchasing account, ensuring no spillover to other accounts.
  • Remove all benefits. This excludes savings plan benefits from billing. It treats all usage as on-demand for transparency or customer-specific models.
Reserved instance reallocation: distribute AWS reserved instance or Azure reservation benefits across customers

Reserved instances and Azure reservations lock in lower prices for committed usage. When purchased centrally, MSPs need flexibility to distribute these benefits fairly across multiple customers. This rule helps you avoid underutilization and makes sure benefits are aligned with business agreements.

You can choose to:

  • Retain vendor-shared benefits. This keeps the default vendor allocation logic. Benefits are automatically shared across linked accounts according to the cloud provider rules.
  • Restrict benefits to the owner account only. This limits benefits strictly to the purchasing account, ensuring no spillover to other accounts.
  • Remove all benefits. This excludes reserved instance/reservations benefits from billing views. You can only see raw on-demand usage for transparency or alternative pricing models.
Cloud Commitment Management cost sharing: allocate reservation and savings plan costs to customers who benefit from them

This distributes the costs of reservations and savings plan benefits across customer accounts managed by Cloud Commitment Management. This rule enables fair allocation of those costs to customers who benefit from shared reservations.

You can choose:

  • Reservations
  • Savings plans

Rerating rules​

Rerating rules help MSPs bill each customer based on their actual usage, rather than the aggregated usage across all linked accounts. This provides accurate cost allocation, maintains your margins, and reduces manual adjustments.

Rerate AWS support tiers: customize or suppress AWS support charges per customer

Customize how support charges are calculated for each customer. You can suppress native support charges or apply a custom support level to each customer account.

  • Suppress AWS Support charges—Removes all AWS Support charges from your customer's bill, so no native support costs are included.
  • Apply Custom Charges Based on Support Tiers—Removes AWS Support charges and applies your selected support tier logic per customer:
    • Developer—Applies a support fee of 3% to the total monthly AWS spend. If this calculated fee is less than $29, the minimum charge of $29 applies, unless the minimum charge is specifically excluded.
    • Business—Applies tiered support fees based on monthly AWS spend: 10% for the first $0–$10,000, 7% for $10,001–$80,000, 5% for $80,001–$250,000, 3% for over $250,000. If the total calculated support fee is less than $100, a minimum charge of $100 applies, unless the minimum charge is specifically excluded.
    • Enterprise On-Ramp—Applies a support fee of 10% to the total monthly spend. If this calculated fee is less than $5,500, the minimum charge of $5,500 applies, unless the minimum charge is specifically excluded.
    • Enterprise—Applies tiered support fees based on monthly AWS spend: 10% for the first $0–$150,000, 7% for $150,001–$500,000, 5% for $500,001–$1,000,000, 3% for over $1,000,000. If the total calculated support fee is less than $15,000, a minimum charge of $15,000 applies, unless the minimum charge is specifically excluded.
  • Apply Pricing Tiers Based on Spend Per—Determines how support fee tiers are calculated:
    • Customer—Pricing tiers are applied separately for each customer's monthly AWS spend. Each customer's support fee is calculated based on their individual usage.
    • Vendor account—Pricing tiers are applied to the combined monthly AWS spend of all customers managed by the vendor. The total spend determines the support fee tiers, and the resulting charges are allocated to each customer.
Rerate AWS pricing tiers: recalculate pricing tiers based on individual customer usage

Recalculate AWS pricing tier charges based on each customer's individual usage, rather than the total spend across all accounts. This ensures each customer is billed accurately for their own usage.

  • Enable—AWS pricing tiers (such as for data transfer or storage) are applied separately for each customer.
  • Disable—AWS pricing tiers are calculated based on the total spend across all accounts, following the default AWS logic.
Rerate AWS volume discount: recalculate RI volume discounts based on individual customer usage

Recalculate AWS reserved instance (RI) volume discounts based on each customer's individual usage, rather than the total usage across all accounts.

  • Enable—AWS RI volume discount tiers are calculated separately for each customer.
  • Disable—AWS RI volume discounts are calculated based on the total usage across all accounts, following the default AWS logic.

Adjustments​

Adjustments handle non-typical billing changes like credits, incident refunds, or special charges that don't appear on your normal provider bill. There are two ways to create adjustments:

These are the types of adjustments you can use:

  • Adjust existing cost by percentage: Adjust existing costs by applying a markup or markdown percentage for a specified period. You can apply a percentage-based adjustment to existing usage charges. This is useful for adding management fees or offering discounts based on contractual terms.

  • New line item based on a percentage: Create new charges calculated as a percentage of the customer's spend. You can apply pricing tiers based on each customer's usage instead of total cloud spend. This is ideal for platform fees or tiered service charges.

  • New line item using a flat value: Add a fixed-value charge to the billing. You can apply a flat-value charge or discount, such as monthly platform fees or service subscriptions.

  • Custom credit memo: Issue credits to customers, represented as negative line items. You can create a credit memo represented as a negative charge applied based on the selected filters. This is useful for refunds, service level agreement (SLA) breaches, or promotional credits.

  • Vendor credit visibility: Manage visibility and application of vendor credits. When enabled, all vendor credits published in the usage file are removed from the custom cost metric. Credits can be reassigned or excluded from custom cost metrics. This is only available as part of the billing plan adjustment rules.

    • Enable—Remove all vendor credits from the custom cost metric.
    • Disable—Keep vendor credits in the usage file.

Sample billing plans​

Here are some examples of how you can use billing plans for different scenarios:

  • You can create a Bronze Tier billing plan for five small customers. The plan applies a flat discount rule and a basic support tier condition. All customers in this plan automatically receive the same pricing logic without manual setup for each account.
  • A Gold Tier plan with advanced rule-based dimensions (RBD) to apply different charges based on usage and support level. For example, customers with premium support get an extra 20% charge, while others remain at base rates.
  • During the billing lock period, you can apply a 10% discount to a single unhappy customer outside the billing plan. This adjustment is configured to run after the plan rules to make sure the discount applies to the final invoice.