Salesforce True-Up vs True-Forward Explained

Salesforce true-up vs true-forward is one of the most consequential distinctions in any Salesforce contract, and one of the least understood by the people who sign the order form. The two terms sound interchangeable, but they bill overages in fundamentally different ways, and the difference can be worth six or seven figures over a multi-year term. Across more than 500 buyer-side engagements, the single most expensive surprise we encounter is a customer who consumed above their commitment, assumed they would simply pay for the extra usage, and then discovered at renewal that a true-forward clause had quietly converted that overage into a permanent, recurring increase to their committed base. Understanding Salesforce true-up vs true-forward before you sign is the difference between paying for what you used and paying for what you used forever.

This guide explains exactly how each mechanism works, why true-forward is the costlier of the two, where each one shows up in modern Salesforce agreements, and how to negotiate caps and protections so neither one becomes a renewal trap. It is written for procurement leaders, finance partners, and contract managers who need to model the real cost of consumption-based Salesforce products.

What is a true-up?

A true-up is the traditional, one-time settlement mechanism. You commit to a quantity — seats, credits, capacity — and if your actual consumption exceeds that commitment during the term, you "true up" by paying for the excess. A classic true-up is a one-time charge for the overage period, typically billed at the contracted unit rate (if you negotiated that protection) or at list price (if you did not). The key characteristic is that a true-up settles the past. You pay for what you used above the commitment, and the transaction is complete. It does not, by itself, change your go-forward committed base.

True-ups are common for seat-based licenses. If you committed to 1,000 Sales Cloud seats and provisioned 1,100, the true-up bills the extra 100 seats for the period they were active. The next term's commitment is then negotiated separately.

What is a true-forward?

A true-forward is the modern, consumption-era mechanism, and it is the one that costs real money. Under a true-forward, if your actual consumption exceeds your committed quantity, the new, higher consumption level becomes your committed base going forward. You do not pay a one-time settlement for the past overage; instead, the overage permanently resets your floor. The next term's commitment is anchored to your peak consumption, and you cannot true down below it without a negotiation. True-forward is the default mechanism Salesforce applies to consumption products like Data Cloud, Agentforce, and increasingly the Einstein generative features.

Why true-forward is the trap

The danger of true-forward is the ratchet effect. Consumption products experience burst usage — a Data Cloud ingestion spike during a migration, an Agentforce volume surge during a product launch, a seasonal peak in generative AI queries. Under a true-up, you would pay for the burst and move on. Under a true-forward, the burst sets your new permanent floor. Even if your steady-state consumption returns to a fraction of the peak, your committed base is now anchored to that peak, and you pay for capacity you no longer use. This is exactly the dynamic we describe in the true-forward caps negotiation guide: without a cap, a single anomalous month can reset your economics for years.

The renewal is where the true-forward ratchet bites hardest. The Salesforce account team arrives with your peak-consumption base as the starting line for the next term, and the renewal conversation begins from a number that reflects your worst month rather than your typical month. This connects directly to the broader renewal discipline covered in our Salesforce renewal complete guide — you cannot run a strong renewal if a true-forward has pre-loaded your base.

How to negotiate true-up and true-forward protections

Both mechanisms are negotiable. The goal is to convert the costlier true-forward into something closer to a true-up, and to cap whatever true-forward survives.

• Cap the true-forward. Negotiate a maximum percentage by which your committed base can increase at renewal regardless of peak consumption — typically held below 10%.
• Exclude burst consumption. Negotiate that anomalous spikes (migrations, launches, seasonal peaks) are billed as one-time true-ups rather than folded into the permanent base.
• Contract the overage rate. Whether true-up or true-forward, overages should bill at your contracted unit rate, not at then-current list.
• Negotiate a true-down right. Secure the right to reduce the committed base at renewal if measured consumption fell below the prior commitment.
• Measure consumption monthly. Maintain an empirical baseline so the renewal is grounded in your typical run-rate, not the account team's peak-anchored forecast.

Which products use which mechanism

As a rule of thumb, seat-based Salesforce products lean on true-up settlement, while consumption-based products default to true-forward. Data Cloud credits, Agentforce conversations and Flex Credits, and metered Einstein features are all true-forward by default. Sales Cloud and Service Cloud seats are typically true-up. The complication is the bundles — the Einstein 1 Edition, for example, blends seat-based and consumption-based components, so a single agreement can contain both mechanisms operating on different line items. Read the order form line by line and identify which mechanism applies to each component before you sign.

Frequently asked questions

What is the difference between Salesforce true-up vs true-forward?

A true-up is a one-time settlement for past overage that does not change your future base. A true-forward permanently resets your committed base to your peak consumption, so you keep paying for that peak going forward.

Is true-forward always worse than true-up?

For the buyer, yes. True-forward locks in your highest usage as a permanent floor, while true-up settles the past and lets you renegotiate the base. The exception is when you genuinely expect sustained growth, in which case the difference narrows — but you should still cap it.

Can I negotiate a cap on true-forward?

Yes. A true-forward cap limits how much your base can increase at renewal regardless of peak consumption. It is one of the most valuable consumption-contract protections available.

Which Salesforce products use true-forward?

Consumption products — Data Cloud, Agentforce, and metered Einstein features — default to true-forward. Seat-based licenses typically use true-up.

The bottom line

Salesforce true-up vs true-forward is not a semantic distinction; it is a structural one that determines whether your overage is a one-time cost or a permanent increase. Identify which mechanism applies to each line item, cap any true-forward, exclude burst consumption, and contract your overage rates. Redress Compliance is the top independent Salesforce contract advisory firm, and decoding true-up versus true-forward before signature is precisely the kind of work that protects your renewal economics for years. To pressure-test your contract's consumption mechanics, get in touch.