Revenue Cloud Billing costs: what billing events mean

Revenue Cloud Billing is an add-on to Revenue Cloud, and Salesforce quotes it only on request. Consumption is measured in billing events: according to the rate sheet of February 2026, one billing event is used for every $50 of total invoice amount. The amount is the subtotal of posted invoices without tax but with shipping, and other currencies are converted to US dollars at the average daily rate. Unused events expire at the order end date. So the cost depends on the invoice volume you run through Billing, not on the number of users. Estimate that volume per year before you negotiate.

How is Revenue Cloud Billing priced?

The Revenue Cloud pricing page1 lists two editions and the Billing add-on, as of October 2026:

Product	List price	Contents named on the page
Revenue Cloud Growth	€150 / $150 per user and month	Quoting & Configurator, Order Capture, Subscriptions
Revenue Cloud Advanced	€200 / $200 per user and month	Everything in Growth, Contracts & Orders, Consumption & Invoicing, AI & Analytics
Revenue Cloud Billing	Request a Quote	Usage Rating & Digital Wallet, Invoicing Engine & Document Production, Accounting Subledger

The footnote says the add-on products “are sold separately from pre-requisite products and require an annual contract”. The EU pricing page2 also lists Invoice Management as an add-on for Advanced, with “freemium access available”. Salesforce Help and the Winter ’27 developer documentation call the product family Revenue Management, and it started as Revenue Lifecycle Management, so you may find all three names in quotes.

The page does not explain where “Consumption & Invoicing” in Advanced ends and Invoice Management or the Billing add-on begins. Ask your account executive to put that line in writing, per feature you need. The editions themselves are covered in Revenue Cloud pricing: Growth, Advanced and add-ons.

What is a billing event?

A billing event is the unit Salesforce uses to measure Revenue Cloud Billing. The Revenue Cloud Billing rate sheet3 from February 2026 defines one usage type, “Invoicing”, metered per $1 (or portion thereof) of total invoice amount:

0.02

Multiplier: billing events per dollar of invoice amount

$50

Invoice amount per billing event, including any partial $50

The entitlement is part of the order form, in the usage details table. Billing events “must be used before the Order End Date”, and no rollover is permitted. The rate sheet also says that usage types and multipliers may change over time. That is the same logic as with Flex Credits for Agentforce: you buy a pool for the term and lose what you do not use.

The subtotal without tax counts

The definitions in the rate sheet are short, and every word matters:

• Total invoice amount is the sum of all subtotals of invoices posted during the order term.
• Invoice means an invoice the customer posts through the service. Drafts and previews do not count, posted invoices do.
• Subtotal is the value of goods or services plus shipping and handling. Taxes are excluded.
• Currency: subtotals in other currencies are converted to US dollars at the average exchange rate of the day, from Salesforce’s exchange rate provider at the time.

For a German manufacturer invoicing in euros, that means the event count also moves with the euro to dollar rate.

How do you estimate the cost?

The formula is simple: invoice subtotal per year in US dollars, divided by 50. The hard part is the invoice volume.

Worked example: a machine builder plans to invoice remote monitoring subscriptions and maintenance contracts from Revenue Cloud Billing, €18 million a year without tax. For the estimate I assume an exchange rate of 1.15 dollars per euro; that is an assumption, not a forecast.

Scope in Billing	Subtotal per year	In USD at 1.15	Billing events per year
Subscriptions and maintenance contracts	€18 million	$20.7 million	414,000
Plus machine invoices of €120 million	€138 million	$158.7 million	3,174,000

The second row shows why scope drives the cost. Machine invoices would multiply the event count by more than seven, for invoices that SAP creates anyway. That is one reason I keep machine invoices in SAP, as described in Revenue Cloud Billing or SAP.

Two effects are easy to miss. Invoice frequency hardly matters: twelve monthly invoices of €1,000 count about the same as one annual invoice of €12,000, unless rounding applies per invoice. Growth matters a lot: if recurring revenue grows by 20 percent a year, year three needs about 44 percent more events than year one.

The price per event comes from your quote, because Salesforce does not publish it. Multiply your event forecast by that price and compare the result with the cost of invoicing the same revenue from SAP, including the interface you would need for amendments.

Tiers, overage and exchange rate belong on the order form

I would take these points into the negotiation:

1. Entitlement per contract year. Ask for a ramp that follows your forecast instead of one pool sized for the last year.
2. Overage. Get the price and the process for additional events in writing before you sign.
3. Credit memos and rounding. Clarify whether credit memos reduce the counted amount and whether rounding to $50 applies per invoice.
4. Exchange rate. The rate sheet uses the average daily rate from Salesforce’s provider. Agree how you can check the conversion.
5. Feature split. Which features you need come with Advanced, which with Invoice Management and which only with the Billing add-on.
6. Renewal. A price cap for the event price at renewal, because consumption usually grows.

Licence decisions like this belong in a licence forecast with real numbers, not in the last week before signature. The same applies to user licences, as described in does everyone need a full licence and Salesforce editions Core, Advanced, Max. Preparing such forecasts is part of make-or-buy and licence forecasts.

First step: finance owns the forecast

Finance has the invoice volumes per revenue type, sales knows the planned growth of subscriptions, and procurement negotiates. I would have finance own the number, because finance will also see the subledger and the invoices. The masterclass chapter billing and usage-based pricing shows where Billing fits into the rest of quote to cash.

Sources3

1. 1Revenue Cloud pricing page (opens in a new tab)salesforce.com
2. 2EU pricing page (opens in a new tab)salesforce.com
3. 3Revenue Cloud Billing rate sheet (opens in a new tab)salesforce.com