·
3 minute read
If you've ever implemented a CPQ tool and watched your pipeline numbers change overnight, you've met this problem. The Opportunity Amount field suddenly shows a number that's bigger than what your team is used to seeing — and the first reaction is usually: "Can we make it show MRR again?"
The short answer is: you can, but there is a price to pay.
How the Amount Field Works
When products are added to a Salesforce Opportunity, the Amount field becomes read-only. Salesforce calculates it automatically through a chain that's worth understanding:
- Each Opportunity Product has a TotalPrice field:
TotalPrice = Quantity × Sales Price - The Opportunity Amount is then:
Amount = SUM(TotalPrice)across all line items
That's it. Amount is the sum of every product on the deal — subscriptions, one-time charges, implementation fees, hardware, everything. This total is what Salesforce considers the deal value. It's Total Contract Value (TCV).
This isn't a configurable behavior. It isn't a setting. When Opportunity Products exist, Amount is a roll-up of everything on the deal.
Why Organizations Want MRR in Amount
Many subscription businesses run on MRR or ARR as their primary metric. Reps are compensated on it. Leadership reports on it. So when Amount shows something different, it feels wrong.
Before adopting a CPQ tool, many organizations worked around this by having reps manually enter MRR in the Amount field — often by simply setting the term to 1 so that Quantity × Sales Price produced a monthly figure. One-time charges were sometimes tracked separately, sometimes not tracked at all. The data was imprecise, but it was familiar.
Then a CPQ tool arrives. Products have real prices. Quotes have line items with quantities, terms, and discounts. When that quote syncs to Salesforce, the Amount field calculates accordingly — and the number is bigger than what anyone expected.
The CPQ tool didn't create this mismatch. It revealed it.
The Tradeoffs at a Glance
| Approach | Amount Shows | What You Lose |
|---|---|---|
| Salesforce approach (recommended) | TCV — full deal value | Nothing. Add MRR/ARR as custom fields. |
| MRR in Amount | Monthly recurring only | One-time charges vanish from the deal total. Pipeline and forecasts understate actual revenue. Standard reports lose meaning. |
| ARR in Amount | Annualized recurring only | Same as above, plus multi-year deals are understated. |
| TCV ÷ Term | An averaged monthly figure | Blends recurring and one-time charges into a meaningless average. A $10K implementation fee spread over 36 months looks like $278/mo of "recurring" revenue. |
What Actually Breaks When You Force It
To make Amount show MRR, you'd need to do one of the following — and none of them are clean:
Exclude non-recurring line items from the Opportunity. Implementation fees, setup costs, and professional services disappear from the deal. They can't be reported on. Revenue recognition has no line-item basis for them. The Opportunity no longer represents the full deal.
Manipulate prices to represent monthly values. Divide recurring totals by the term and post that as the unit price. But a $5,000 implementation fee has a term of 1 — it can't be meaningfully divided into monthly amounts. Now Salesforce's math produces numbers that don't correspond to what the customer will actually pay.
Divide TCV by term after the fact. A deal with $120,000 in software licenses and a $36,000 implementation fee over 36 months produces an "average monthly" of $4,333. That's neither the MRR ($3,333) nor the first-month billing ($39,333). It's a number that describes nothing real about the business.
This is not a software limitation — it's a math and data problem. No CPQ tool, no integration, and no workflow can change the fact that a single field cannot simultaneously represent a total and a subset of that total.
The Salesforce Approach: TCV in Amount, Everything Else in Custom Fields
The simplest architecture is also the most maintainable. Let Amount be what Salesforce designed it to be — the total deal value. Then add the fields you actually need:
| Field | What It Represents |
|---|---|
| MRR | Sum of recurring line items ÷ term in months. Excludes one-time charges. |
| ARR | MRR × 12. |
| One-Time Revenue | Sum of line items flagged as one-time. |
| Year 1 Billing | First-year recurring charges + all one-time charges. |
With this structure, a sales leader can build a dashboard showing ARR by rep. Finance can pull one-time revenue by quarter. The CEO can see TCV pipeline by stage. Every report pulls from a field that means exactly one thing. Nobody has to ask "wait, does Amount mean MRR here?"
What About Forecasting on ARR?
This is the most common follow-up question. Salesforce Collaborative Forecasting can be configured to forecast on custom currency fields, not just Amount. If you enable Opportunity Splits, you can add your ARR field as a forecast type. This gives you a native ARR forecast without touching the Amount field.
The Bottom Line
The Amount field can only hold one number. TCV is the only value that captures the entire deal without excluding or distorting anything. Every other metric — MRR, ARR, one-time revenue — should live in its own field where it can be clearly defined, independently reported, and correctly understood.
The goal isn't to track fewer metrics. It's to track each metric in the right place.
Have questions about how this applies to your Salesforce and DealHub integration? Get in touch — this is exactly the kind of thing we help with.
