Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
DictionaryRRevenue Forecasting
SalesBeginner

Revenue Forecasting

Revenue Forecasting in Salesforce is the type of forecast that projects sales based on the dollar amount of opportunities, rolling Opportunity Amount values up the forecast hierarchy and grouping them into the Forecast Categories (Pipeline, Best Case, Commit, Closed).

§ 01

Definition

Revenue Forecasting in Salesforce is the type of forecast that projects sales based on the dollar amount of opportunities, rolling Opportunity Amount values up the forecast hierarchy and grouping them into the Forecast Categories (Pipeline, Best Case, Commit, Closed). It is one of the two forecast types Collaborative Forecasting supports; the other is Quantity Forecasting, which projects based on the Quantity field on Opportunity Products.

Revenue Forecasting is the default for most Salesforce orgs because revenue is the metric most sales organisations report on. Quantity Forecasting becomes relevant only when the business sells in units that matter as much as price (manufacturing seat counts, oil and gas barrels, agricultural tonnage). Both forecast types can be enabled simultaneously in the same org so an organisation can roll up both revenue and units side by side. The Forecast Categories map Opportunity Stages to forecast buckets that managers adjust week to week.

§ 02

How Revenue Forecasting projects Opportunity Amount up the hierarchy

How Revenue Forecasting rolls up Opportunity Amount

Revenue Forecasting takes the Amount field on each Opportunity and aggregates the values up the forecast hierarchy. Each user sees their own forecast (the sum of their owned opportunities) plus the rolled-up forecast of every user below them. The hierarchy used for forecasting is the Forecast Hierarchy, which mirrors the Role Hierarchy by default but can be customised so the forecasting structure differs from the org's reporting structure. The roll-up is real-time; an Opportunity Amount edit is reflected in the manager's forecast view immediately, without an overnight batch.

Forecast Categories and stage mapping

Every Opportunity Stage maps to one of the Forecast Categories: Pipeline, Best Case, Commit, Closed, or Omitted. The mapping is configured at the Opportunity Stage level in Setup. When a rep moves an Opportunity from Stage 2 (Discovery) to Stage 5 (Proposal), the Opportunity moves from the Pipeline category to the Commit category if the stage mapping says so. Forecast views aggregate amounts by category, so the rep and manager see how much pipeline is in each forecast bucket without manually filtering by stage every time.

Manager adjustments to the rolled-up forecast

Managers can override the rolled-up amount with a manual adjustment that reflects their judgment about which deals will actually close. The adjustment is a number entered against a specific category in the forecast view. The platform records the adjustment with the user, date, and original rolled-up amount, which lets the org audit forecast accuracy after the period closes. Adjustments cascade up the hierarchy: a manager's adjustment to their team's forecast is visible to their own manager, who can further adjust the consolidated number before reporting upward. The adjustment history is preserved on the forecast snapshot for the period, which is what finance teams compare against actuals when measuring forecast accuracy.

Revenue Forecasting vs Quantity Forecasting and when each fits

Revenue Forecasting projects dollar amounts; Quantity Forecasting projects unit counts from Opportunity Products. Industries that price per unit (manufacturing, transportation, distribution) often run both side by side: dollars matter for finance, units matter for capacity planning and production scheduling. Software and services orgs typically only need Revenue Forecasting because their unit is the deal itself. Both types share the same Forecast Hierarchy and Forecast Categories, so the same management process works for either type once the basic setup is in place.

Currency handling in multi-currency orgs

Multi-currency orgs roll up Revenue Forecasting amounts using the org's corporate currency. Each Opportunity's Amount is converted to corporate currency using the dated exchange rate at the time of the forecast view. Managers see one consolidated revenue forecast in the corporate currency regardless of which currency each Opportunity was created in. The conversion is automatic; admins do not need to maintain conversion logic per forecast. However, the conversion rate at the time of forecast view differs from the rate at deal close, which can produce small variances between the forecast and the actual booked revenue. Mature finance teams reconcile these variances at quarter close and document the impact so the next period's forecast factors in expected FX movement against budgeted exchange rates.

Forecast Categories vs Probability and the most-common confusion

Forecast Categories and Probability are independent fields on Opportunity Stages. Probability is a percentage that drives the Expected Revenue formula on the Opportunity. Forecast Category is a bucket label that drives Revenue Forecasting roll-up. The two are typically aligned (Stage 5 Proposal usually has high Probability and falls in Commit), but they can diverge. A custom Stage with 70 percent Probability could still fall in Best Case rather than Commit depending on the org's sales process. This independence is the most-common source of confusion for new sales operations admins.

Common pitfalls in Revenue Forecasting setup

Three patterns produce broken Revenue Forecasting setups. The first is missing stage mapping: a custom Opportunity Stage with no Forecast Category mapping silently falls into the Pipeline category, which inflates the pipeline number and produces a misleading view of the deals managers should be paying attention to. The second is over-adjusting managers: forecast adjustments are useful when the rep's judgment is wrong, but cumulative adjustments at every hierarchy level produce a manager-led forecast that diverges from the underlying CRM data. The third is enabling both Revenue and Quantity Forecasting without aligning the sales process; sales reps then maintain Amount and Quantity inconsistently and the two forecast types disagree by enough to make leadership distrust both numbers.

§ 03

Enable and configure Revenue Forecasting

Revenue Forecasting is part of Collaborative Forecasting. The steps below cover enabling the feature, mapping stages to categories, and configuring the Forecast Hierarchy.

  1. Enable Collaborative Forecasting

    In Setup, go to Forecasts, Settings. Tick Enable Forecasts. The platform provisions the Forecast Hierarchy mirrored from the Role Hierarchy.

  2. Enable Revenue Forecasts

    On the Forecast Settings page, tick Enable Revenue Forecasts. This activates the dollar-amount roll-up. Quantity Forecasting is a separate checkbox if you also need unit counts.

  3. Configure Forecast Categories on Opportunity Stages

    In Setup, go to Opportunity, Fields, Stage. For each stage, set the Forecast Category. Stages with no mapping default to Pipeline; explicit mapping is required for accurate Commit and Best Case rollups.

  4. Customise the Forecast Hierarchy if needed

    Open the Forecast Hierarchy from Setup. By default it mirrors the Role Hierarchy. Enable forecasting on specific users (often the people-managers), assign forecast managers, and verify the tree matches the way the sales organisation reports.

  5. Test by creating opportunities and viewing the forecast

    Create test opportunities at different stages and amounts. View the Forecasts tab as a manager and confirm the rollup totals match the underlying opportunities. Adjust a forecast number and verify the adjustment cascades correctly up the hierarchy.

Key options
Revenue Forecastremember

Dollar-amount roll-up. The default forecast type for most orgs.

Quantity Forecastremember

Unit-count roll-up. Use when units matter for capacity planning.

Cumulative Forecast Rollupsremember

Setting that determines whether Commit includes Best Case and Closed (cumulative) or just the Commit category (non-cumulative).

Gotchas
  • Opportunity Stages with no Forecast Category mapping default to Pipeline, which can silently inflate the pipeline bucket. Audit every active stage to confirm its mapping aligns with the sales process.
  • Forecast Categories and Probability are independent. Custom stages can have high Probability but still fall in Best Case rather than Commit. Confusion between the two is the most-common source of bad forecast accuracy.
  • Multi-currency orgs convert all forecasts to the corporate currency at the time of the forecast view. Exchange rate fluctuations between the forecast and the deal close produce small variances; finance teams need to know this when comparing forecast to actuals.
§

Trust & references

Sources

Cross-checked against the following references.

Official documentation

Straight from the source - Salesforce's reference material on Revenue Forecasting.

Keep learning

Hands-on resources to go deeper on Revenue Forecasting.

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 Revenue Forecasting?

Q2. What drives forecast quality?

Q3. Why is forecasting foundational?

§

Discussion

Loading…

Loading discussion…