Revenue Forecasting Basics

This topic gives details of the following:

Custom Objects Used in Revenue Forecasting

The following custom objects in PSA are used to support Revenue Forecasting:

Object

Description

Related Information
Revenue Forecast Stores the revenue forecast for a project or an opportunity. Revenue Forecast Fields
Revenue Forecast Batch Lock Indicates whether the revenue forecast batch job is currently running.
This object is for internal use only.		 Revenue Forecast Batch Lock Fields
Revenue Forecast Batch Log Stores details of any errors that occurred when a revenue forecast was run.
 Revenue Forecast Batch Log Fields
Revenue Forecast Batch Status Stores the status of Revenue Forecasting batch Apex jobs. Revenue Forecast Batch Status Fields
Revenue Forecast Setup Stores the settings for running a revenue forecast. Revenue Forecast Setup Fields
Revenue Forecast Type Stores the revenue forecast for a relevant object, for example Milestone or Est Vs Actuals. Revenue Forecast Type Fields
Revenue Forecast Version Stores the records used in different versions of a revenue forecast. Revenue Forecast Version Fields
Revenue Forecast Version Adjustment Stores adjustments to values on revenue forecast version detail records. Revenue Forecast Version Adjustment Fields
Revenue Forecast Version Batch Log Stores details of any errors that occurred when a revenue forecast version was created. Revenue Forecast Version Batch Log Fields
Revenue Forecast Version Detail Stores the detail records used by different versions of a revenue forecast. Revenue Forecast Version Detail Fields

Revenue Forecasting Permissions

Permission Sets

You can assign the following permission sets to users for access to Revenue Forecasting:

Permission Set Name Description
PSA - Adjust Forecast Version Perform management adjustments to revenue forecast versions.
PSA - Close Time Period for Forecasting Mark time periods as closed for forecasting.
PSA - Configure Recognition Methods for Forecasting Set the recognition method on records used in revenue forecast calculations.
PSA - Configure Forecast Setup Configure the setup for revenue forecasts.
PSA - Delete Forecasts Delete records for the following: revenue forecasts, revenue forecast batch status, revenue forecast versions, and revenue forecast version adjustments.
PSA - Lock Forecast Version Lock revenue forecast versions, so that adjustments can no longer be made.
PSA - Run Forecast Run revenue forecasts.
PSA - View Forecast View revenue forecasts and revenue forecast versions for relevant projects and opportunities. This permission set is suitable for users who need to view forecasts for their own projects and opportunities, for example, project managers.
PSA - View All Forecasts View revenue forecasts and revenue forecast versions for projects and opportunities. This permission set is suitable for users who need to view forecasts for the regions, practices, and groups they cover and for all projects and opportunities, for example, regional managers and services leaders.
Tip:

The PSA - Revenue Forecast - Run custom permission is included in the relevant permission sets above and is required for you to run a revenue forecast. You can use this custom permission in other permission sets, if required.

Permission Set Groups

The following permission set groups include Revenue Forecasting permissions:

For more information, see Overview of Functional Permissions for PSA.

Exchange Rates Used in Revenue Forecasting

For maximum accuracy, Revenue Forecasting calculations use the currency exchange rate that was active on a record’s actual date, such as the timecard end date or expense date. For scheduled records or unscheduled revenue, today’s exchange rate is used.

If no exchange rates exist for a historical actual date, the affected records are omitted from the revenue forecast. You can check the Revenue Forecast Batch Logs related list to view the details.

For historical monthly time periods, the exchange rate that was current at the end of the corresponding monthly time period is used. For current and future monthly time periods, the exchange rate that was current on the date the version was created is used.

If the currency on a record differs from the project currency, Revenue Forecasting uses either PSA or Salesforce currency conversions to calculate the value, depending on your org setup. This might happen, for example, with an expense record if the expense was incurred in another country. In this case, the revenue forecast uses the exchange rate that applied on the expense date.

When reviewing revenue forecast versions, revenue is displayed in the corporate currency by default to enable you to compare values across different currencies. In the Forecast Breakdown grid on the Review Forecast Version page, you can toggle Show Local Currency to switch between viewing values in corporate currency or local currency.

For more information, see Reviewing Revenue Forecast Versions.

How Rounding Works in Revenue Forecasting

Revenue Forecasting uses "half up" rounding to the number of decimal places of the relevant currency. For example:

The difference between the number before and after rounding is carried forward to the next month for recognized revenue. For pending recognition, the difference is carried to scheduled revenue and then to unscheduled revenue within the monthly time period, before being rolled over to the next month's pending recognition.

For time and materials projects recognized on delivery, when you run a revenue forecast, numbers are rounded to the number of decimal places of the relevant currency immediately and Revenue Forecasting adds the revenue to the relevant monthly time period.

For opportunities and for fixed fee projects and milestones, when remaining revenue is rolled over to the next monthly time period due to rounding, Revenue Forecasting adds any remaining amounts to months where the total revenue at that point should round up, as shown in the example below.

For detailed information on how revenue forecast calculations work, see Deliverable Recognition Method, Equal Split Recognition Method, and % Complete Recognition Method.

Example

A fixed fee project spans three months, from April to June. The revenue is split equally between the three months.

Total scheduled revenue over the project duration = $10,000.

The amounts in each month are:

Month Calculation

Amount $

Total Revenue $
April 10,000/3 3,333.33 3,333.33
May 10,000/3 3,333.34 6,666.67
June 10,000/3 3,333.33 10,000.00

Any remaining amount is added on to months where the total revenue at that point should round up. This means the total revenue in May should be $6,666.67 so the remaining $0.01 is added to the revenue amount for May.