Skip to main content
Self-Serve Billing Rules are in private preview. Self-Serve Billing Rules let you create billing rules in a Vantage account that you manage yourself. They must be enabled for your account by Vantage. To request access, contact support@vantage.sh or your account team.Billing rules for Vantage for MSPs Management Accounts are generally available. If your account is a Managed Account under an MSP, your MSP manages billing rules for you.
Billing rules change the cost amounts Vantage shows after it imports your provider billing data. Use them when the costs imported from your providers don’t reflect the rates, discounts, and fees your business actually pays. For example:
  • You buy cloud services through a reseller whose discount doesn’t appear in your AWS Cost and Usage Report.
  • You buy cloud services through an MSP that doesn’t provide your billing data at your agreed rate.
  • You include support fees or other charges in the costs you report on.
  • Your discount rate changes from one contract period to the next.
Billing rules change only the costs Vantage processes and displays. They do not change your provider’s invoice, your negotiated agreement, or the billing files from your provider.
Billing rules change cost amounts. Virtual Tags change cost attribution (how costs are grouped and filtered). Use a billing rule when the number is wrong, and a Virtual Tag when the number is right but needs a different label.

Billing Rules by Account Type

Which steps you follow depends on your type of Vantage account.

How Billing Rules Work

Each time Vantage processes cost data for an account, it applies the account’s billing rules before anything else uses that data:
  1. Vantage imports cost and usage data from your provider integrations.
  2. Billing rules run in a fixed execution order.
  3. Virtual Tags are evaluated on the cost data that billing rules produced.
  4. Cost Reports, budgets, forecasts, and other features use the result.
Because billing rules run first, every feature downstream sees the adjusted amounts. You don’t need to rebuild Cost Reports. Existing reports that include affected costs show the adjusted data once reprocessing completes.

Supported Providers

Billing rules that change line items are not supported today for standard GCP usage costs or most other providers.

Who Can Manage Billing Rules

Users with the Organization Owner or Integration Owner role can create, edit, and delete billing rules. See Role-Based Access Control for details. Users with other roles can’t open Billing Rules in Settings, but they see costs with billing rules applied in Cost Reports and across Vantage. Managed Accounts cannot create or edit billing rules. If your account is a Managed Account, your MSP manages billing rules for you.

Create a Billing Rule

Select the tab for your account type. If you’re not sure which type you have, see Billing Rules by Account Type.
1
Log in to your Vantage for MSPs Management Account.
2
From the top navigation, click Settings.
3
From the left navigation, under Partner Settings, select Billing Rules. Your existing billing rules are displayed.
4
Click New Billing Rule, then select Adjustment, Charge, Credit, Custom, or Exclusion.
5
Enter a Title and the fields for the rule type. See Billing Rule Types.
6
Optionally, enter a Start Date and End Date. Charge and Credit rules require a start date. See Rule Dates.
7
Optionally, choose to apply the rule to all existing and new Managed Accounts, then click Save.
8
If you didn’t apply the rule to all Managed Accounts, assign it to individual Managed Accounts. See Assign Billing Rules to a Managed Account.
The rule changes only the costs of the Managed Accounts it’s assigned to, never the Management Account’s own costs. See Billing Rules for MSPs.

Billing Rule Types

Each billing rule has a type that determines what it does to your cost data: Adjustment, Charge and Credit, Exclusion, or Custom. The fields are the same for self-serve and MSP accounts.

Adjustment

Adjustment rules change the amount of existing cost line items. Select one of the following adjustment types.
You choose the adjustment type when you create the rule and cannot change it afterward. Re-Rate to Public Price and Remove RI/SP Discounts rules are saved as Custom rules against the aws dataset, so they are listed with the SQL Rule type and open in the SQL editor when you edit them.

Per Service Adjustment

Changes matching line items to a percentage of their original amount. Use it for discounts, markups, and negotiated rates that do not appear in your provider bill. On a self-serve account, Percentage of Cost Shown to Customer is the share of cost shown in your own account.
To see Category names, open a Cost Report, expand Group By, and select Category.
Example: Apply a 10% AWS reseller discount If you buy AWS through a reseller whose discount does not appear in your Cost and Usage Report, create a Per Service Adjustment, set Service to all AWS services, and enter 90 as the percentage. Vantage keeps 90% of each matching AWS line item, so Cost Reports show AWS costs with the 10% discount applied. Scope the rule so it applies only to the costs your agreement covers. If the discount changes over time, create one rule for each contract period and give each rule its own Start Date and End Date, rather than editing a single rule. See Rule Dates.

Re-Rate to Public Price

Shows AWS usage at public on-demand rates, removing the effect of Enterprise Discount Programs (EDPs), Private Pricing Agreements (PPAs), and other negotiated pricing. Use it when you need to report or charge back AWS costs at list price. This adjustment has no additional fields. It supports AWS costs only. Vantage replaces lineItem/UnblendedCost with pricing/publicOnDemandCost and lineItem/UnblendedRate with pricing/publicOnDemandRate from the AWS Cost and Usage Report.

Remove RI/SP Discounts

Removes Reserved Instance and Savings Plan discounts from usage when the commitment was purchased in a different AWS account than the one that used it. Use it when commitments are bought centrally, such as in a payer account, and you want each account’s costs to reflect on-demand pricing instead of the shared discount. This adjustment has no additional fields. It supports AWS costs only. Vantage rewrites matching SavingsPlanCoveredUsage and DiscountedUsage line items as Usage, so they appear at on-demand rates. Usage covered by a commitment purchased in the same account keeps its discount.

Charge and Credit

Charge and Credit rules insert a new line item. Use a Charge for fees, such as a support or platform fee, and a Credit for amounts that reduce cost, such as a negotiated service credit. Charges and credits run in the second execution stage, so later Adjustment and Exclusion rules can act on them.

Exclusion

Exclusion rules remove line items with a specific charge type from your cost data. Use them to remove items you do not want to report on, such as Reserved Instance fees, taxes, or distributor discounts. The Charge Type must exactly match a raw charge type value, including capitalization. The display names shown when you group a Cost Report by Charge Type, such as Reserved Instance Fee, do not match. Expand the section below for the exact values.
Each AWS discount type in the table above, such as BundledDiscount, EdpDiscount, and PrivateRateDiscount, can also have amortized and unamortized variants that use the raw costs.cost_type value with a prefix. For example, EdpDiscount can also appear as AmortizedEdpDiscount or UnamortizedEdpDiscount.
  • Amortized variants such as AmortizedEdpDiscount appear when amortization and discounts are both enabled. These represent the discount amount on fee rows, such as Marketplace or Enterprise Support charges, that has been spread across the billing period.
  • Unamortized variants such as UnamortizedEdpDiscount appear when amortization is disabled and discounts are included. These represent the discount amount on unamortized fee or commitment rows, such as Reserved Instance fees or Savings Plan recurring fees.
The AWS discount types with these variants are: EdpDiscount, BundledDiscount, SppDiscount, RiVolumeDiscount, PrivateRateDiscount, and DistributorDiscount.

Custom

Custom rules run a SQL UPDATE, INSERT, or DELETE statement against Vantage cost data (the costs dataset) or raw AWS Cost and Usage Report data (the aws dataset). Use them when no other rule type expresses the logic you need, such as a discount that excludes certain charge types, or a fee calculated from total monthly spend. The editor includes Format, which auto-formats your SQL, and Validate, which checks it for syntax errors, schema mismatches, and common issues. See Validate a Rule Before You Save. Example: Apply a discount that excludes Marketplace purchases When a discount or fee covers cloud consumption but not Marketplace purchases, use a Custom rule to define which line items it applies to. Excluded line items stay unchanged:
To remove Marketplace costs entirely instead, see Exclude Marketplace Costs. See SQL Billing Rules for datasets, supported syntax, and examples.

Validate a Rule Before You Save

Check a rule before you save it, because every save reprocesses your cost data:
  • Validate in the editor: For Custom rules, click Validate above the SQL editor. Validate checks your SQL for syntax errors, unsupported operations, unknown columns, and schema mismatches without saving the rule.
  • Ask the docs assistant: On the SQL Billing Rules page, use the AI assistant prompts to draft a rule from a plain-language description, validate a rule you paste in, or troubleshoot a rule that isn’t working.
  • Use the Docs MCP: Connect the Vantage Docs MCP to your AI tool so it can check a rule against the billing rules documentation while you write it.

Rule Dates

Start and end dates are inclusive calendar dates in YYYY-MM-DD format:
  • Start date only: The rule applies from that date forward.
  • End date only: The rule applies from the beginning of your cost data through that date.
  • Both: The rule applies only within that window.
  • Neither: The rule applies to your entire cost history.
Charge and Credit rules require a start date. To use different rates for different contract periods, create one rule for each period with its own start and end dates. For example, one rule can apply the discount from a previous contract year, and another can apply the current rate. Avoid overlapping date ranges unless you intend both adjustments to apply, because overlapping rules compound. Use dates instead of date conditions in SQL. A rule with an empty start date reprocesses your entire history, so set a start date when you only need the rule for a recent period.

Reprocessing

When you save, edit, or delete a billing rule, Vantage reprocesses the affected cost data within the rule’s date range. Creating or editing a rule recalculates matching costs with the change, and deleting a rule recalculates them without it.
  • Reprocessing runs in the background and can take several hours, depending on the amount of cost data. The console does not show a progress indicator. Vantage processes the most recent data first, so recent results are usually available before reprocessing finishes.
  • Saving a rule again restarts reprocessing. Finalize the rule before you save it, then check the results after reprocessing completes.
  • How far back a rule applies depends on the historical cost data available in your account.

Limits

  • Each account can have up to 20 billing rules. If you need more, contact support@vantage.sh.
  • Each rule has one set of conditions. For adjustments with different conditions or rates, create separate rules.

Billing Rule Execution Order

Billing rules run as a fixed pipeline of four execution stages. The stages always run in the order below, and each rule’s stage is determined by its type and schema. This applies to every rule type, including Custom (SQL) rules. Within a stage, rules run in order. On a self-serve account, that is the order the rules were created, and a new rule is added to the end of its stage. On a Vantage for MSPs account, you can reorder rules for each Managed Account.

Why Order Matters

Every rule that matches a line item applies to it, in order, so rules compound. Within a stage, each rule operates on the cost data left by the rule before it, not on the original data, and each stage operates on the output of the stage before it. Review rule conditions, order, and date ranges together to make sure the result matches the pricing you intend.
  • Overlapping percentages compound: Two 10% discounts (two rules set to 90) turn $100 into $90, then $81, not $80. A rule set to 90 followed by a rule set to 95 turns $100 into $85.50.
  • Percentages alone are order-independent: Stacking percentage adjustments produces the same result in either order. A 10% discount and a 5% markup on a $100 line item yield $94.05 either way (100 × 0.90 × 1.05 = 100 × 1.05 × 0.90).
  • Mixed operations are order-dependent: Mixing a percentage with a fixed amount or an exclusion does not. If Rule A sets a line item to $100 and Rule B applies a 90% rate, running A then B produces $90. Running B then A produces $100, and the discount is lost.
  • Monthly Insert rules run last: Aggregate rules calculate from the adjusted costs. If a stage 3 rule removes AWS Marketplace costs, a Monthly Insert rule that charges 10% of AWS spend calculates the fee without those Marketplace costs.
Create broad, foundational rules first and narrower corrections afterward. Check totals after reprocessing completes.

Manage Billing Rules Programmatically

You can also create, list, update, and delete billing rules with the Billing Rules API, the Terraform provider, and the billing rules tools in the Vantage MCP, which the FinOps Agent can also use.
Self-Serve Billing Rules are in private preview, including through the API, Terraform, and MCP. On a self-serve account, these tools work only after Vantage enables Self-Serve Billing Rules for the account. Rules created on a self-serve account always apply to that account’s own costs, and apply_to_all is ignored.
The following examples create a 10% reseller discount.
An Adjustment rule without a service or category applies to all services. Add service and category to scope it to the costs your agreement covers. See the vantage_billing_rule resource and vantage_billing_rules data source for all attributes.

Billing Rules for MSPs

On a Vantage for MSPs Management Account, billing rules work the same way, with these differences:
  • A rule applies to the Managed Accounts you assign it to, not to the Management Account’s own costs. Select Managed Accounts, or apply the rule to all current and future Managed Accounts.
  • Within a stage, you can reorder rules for each Managed Account.
  • On Managed Accounts, billing rules also record Build Hours.
See Billing Rules for Vantage for MSPs for assignment, reordering, and what customers see in their Managed Accounts.