Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
DictionaryFForecast Amount
SalesBeginner

Forecast Amount

Forecast Amount is the projected revenue contribution of an Opportunity (or Opportunity Product line) as it rolls into Salesforce Forecasts.

§ 01

Definition

Forecast Amount is the projected revenue contribution of an Opportunity (or Opportunity Product line) as it rolls into Salesforce Forecasts. Each in-flight deal contributes a Forecast Amount that aggregates up the forecast hierarchy into every manager's number. The amount that lands in any given forecast cell depends on the Opportunity's Forecast Category, its Close Date, and the forecast period the user is looking at.

Forecast Amount is not the same as Opportunity Amount. Opportunity Amount is one field on one record. Forecast Amount is a calculation that sums opportunity-level or product-level amounts grouped by category and period, then adjusts for overlay splits, manager adjustments, and currency conversion. A 100k Best Case deal contributes 100k to the rep's Best Case row, 100k to their manager's Best Case row, and 100k to the VP's, because the forecast hierarchy chains the rollup together.

§ 02

How Forecast Amount turns Opportunity data into a number sales leaders actually trust

Forecast Amount versus Opportunity Amount

Two amounts, two purposes. Opportunity Amount is the gross deal size stored on the Opportunity record, calculated from line items or entered manually. Forecast Amount is what shows up in the Forecasts tab after Salesforce applies forecast splits, overlay credit, and any per-line product adjustments. For a clean deal with no splits, the two match. For a deal split 60/40 between two reps, Rep A's Forecast Amount is 60k against a 100k Opportunity, and Rep B's is 40k. The Opportunity itself still reads 100k.

How Forecast Category drives the bucket

Forecast Category is a picklist on Opportunity Stage with five values: Pipeline, Best Case, Commit, Closed, and Omitted. Stage maps to category via the Stage picklist's hidden Forecast Category column. A deal in Stage 3 of 7 might map to Pipeline; Stage 5 to Best Case; Stage 6 to Commit. Forecast Amount flows into the category column matching the deal's current stage. Move the deal from Best Case to Commit and the same amount jumps columns in the manager's view.

Revenue forecasts versus quantity forecasts

Salesforce supports two forecast measure types. Revenue forecasts use Opportunity Amount (or a custom currency field) as the source. Quantity forecasts use Opportunity Quantity or a custom number field. You can run both at once via Forecast Types. A volume-driven sales team often forecasts by quantity for units sold and by revenue for ACV, side by side in the same tab. Forecast Amount is the revenue side; Forecast Quantity is the unit side.

Rolling up through the forecast hierarchy

The Forecast Amount that any user sees is the sum of their own opportunities plus everyone reporting to them in the forecast hierarchy. The forecast hierarchy is a parallel structure to the role hierarchy, configured under Setup, Forecasts Hierarchy. A user can be in the role hierarchy without being in the forecast hierarchy, or vice versa. If a rep is missing from the forecast hierarchy, their deals roll up to nobody. This is the second-most-common forecast support ticket after split confusion.

Manager adjustments and overlay credit

Managers can adjust the Forecast Amount they show their own boss without changing the underlying Opportunity data. Adjustments are tracked on the ForecastingAdjustment object and are visible to the manager who made them, plus their own manager. The rep does not see the adjustment. Overlay splits work the opposite way: a Sales Engineer can receive a percentage of every deal they support, and that percentage shows up as their Forecast Amount in a separate overlay forecast.

Product-level forecasting and OpportunityLineItem

Enable product-level forecasting and Forecast Amount sources from OpportunityLineItem rather than Opportunity. Each line item contributes its TotalPrice (or a custom currency field) into the forecast independently, grouped by Product Family. Forecasting becomes Product Family by category by period instead of Opportunity by category by period. A deal with three product families lands in three rows of the rep's forecast, with each line's amount in its own family's row.

Multi-currency conversion timing

In multi-currency orgs, Forecast Amount is converted to the corporate currency using the dated exchange rate active on the Opportunity's Close Date, not the rate active today. Change the rate retroactively and forecasts recompute on the next refresh. The forecast cache lags Opportunity edits by a few minutes; a closed deal that disappears from the rep's number for ten minutes is usually the cache, not a bug.

§ 03

Turning on Forecasts and configuring how Forecast Amount calculates

Forecasts has to be enabled at the org level before any Forecast Amount exists. Then you pick which measure (revenue or quantity), which source field, which period (monthly or quarterly), and which users sit in the forecast hierarchy.

  1. Enable Forecasts

    Setup, Forecasts, Forecasts Settings. Check Enable Forecasts. Pick the default forecast period (monthly or quarterly) and the start month for fiscal-year alignment. This unlocks the Forecasts tab and the underlying ForecastingItem object.

  2. Define forecast types

    Setup, Forecasts, Forecasts Settings, Add a Forecast Type. Pick the object (Opportunity or OpportunityLineItem), the measure (revenue, quantity, or custom), and the date field (Close Date is standard). You can run up to four forecast types simultaneously, one per measure-source combination.

  3. Map Stage to Forecast Category

    Object Manager, Opportunity, Fields, Stage. Edit each picklist value and set its Forecast Category. Most orgs map early stages to Pipeline, mid-funnel to Best Case, late stages to Commit, and only Closed Won to Closed. Map Lost stages to Omitted so they disappear from the forecast.

  4. Configure the forecast hierarchy

    Setup, Forecasts, Forecasts Hierarchy. Enable forecasting for each user role from leaf-level reps up to the VP. The hierarchy is a separate structure from the role hierarchy, even though it usually mirrors it. Missing users mean deals roll up to nobody.

  5. Set quotas and refresh

    Load monthly or quarterly quotas via Data Loader on the ForecastingQuota object. Quotas show as a target line on the Forecasts tab. The forecast view refreshes on a five-minute cache, so changes to Opportunity Amount lag briefly.

Key options
Forecast measureremember

Revenue (sums Amount or a custom currency field) or Quantity (sums Quantity or a custom number field). Custom currency forecasts let you forecast ARR, ACV, or any other revenue cut without using the standard Amount field.

Forecast periodremember

Monthly or quarterly. Cannot mix; pick one per forecast type. Most enterprise orgs go quarterly for the manager view and monthly for the rep view via two forecast types.

Adjustmentsremember

Allow Manager Adjustments lets people above the rep adjust forecast numbers without touching Opportunity data. Allow Owner Adjustments lets reps adjust their own number.

Cumulative vs incremental categoriesremember

Cumulative categories show Commit + Best Case + Pipeline together (sales-leader view). Incremental show each bucket alone (rep view). Toggled per user view on the Forecasts tab.

Gotchas
  • A deal owned by a user outside the forecast hierarchy contributes zero to every forecast cell, even if its category is Best Case or Commit.
  • Closed Lost opportunities should map to the Omitted category, not Closed. Closed is for Closed Won only and shows as actuals on the Forecasts tab.
  • Reports filtered by Close Date and grouped by stage will not match Forecasts grouped by category. Reports use stage; Forecasts use category. Same data, different bucket.
  • Multi-currency forecasts use the dated exchange rate of the Close Date, not today's rate. Changing rates retroactively shifts historical forecasts.
  • The forecast cache lags edits by about five minutes. A closed deal that has not yet moved to Closed in the forecast view is almost always cache, not a bug.
§

Trust & references

Sources

Cross-checked against the following references.

Official documentation

Straight from the source - Salesforce's reference material on Forecast Amount.

Was this entry helpful?
Help us write better definitions. Quick reactions or detailed edit suggestions.

About the Author

Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.

§

Test your knowledge

Q1. What is Forecast Amount?

Q2. Can forecast amounts be adjusted?

Q3. How do forecast amounts roll up?

§

Discussion

Loading…

Loading discussion…