% Complete Recognition Method

The % Complete revenue recognition method relates to fixed fee projects or milestones recognized on percentage of completion. A revenue forecast record is created for each monthly time period to store the values for these objects for use in Revenue Forecasting.

Revenue Forecasting automatically caps the amount at 100% to prevent over-forecasting if the number of hours logged and scheduled on a milestone or project exceeds the number of planned hours, estimated hours at completion, or expected hours.

Note:

Timecard records without assignments are not included in % Complete revenue forecasts.

Revenue Forecasting uses EVAs to calculate the following in a given month:

  • Actual percentage of completion.
  • Scheduled and unscheduled percentage of completion.
Tips:

If required, you can exclude scheduled hours in closed periods from your revenue forecast calculations for projects and milestones. For more information, see Excluding Scheduled Hours in Closed Periods (% Complete Revenue).

Some calculations described in this topic refer to the Estimated Hours at Completion field, however, you can configure which field is used for calculating the value in the % Hours Completed for Recognition field on a project. For more information, see Scheduling Revenue Forecasts.

In the Total Hours Field on Project field on the active revenue forecast setup record, you can specify the field containing the value you want to use as the denominator to calculate the % Hours Completed for Recognition for projects and milestones. If the total scheduled and actual hours exceeds the value in that field and the Use Sched and Actual Hrs for % Complete setting is selected, the calculation for the % Hours Completed for Recognition field uses the total scheduled and actual hours as the denominator instead. For more information, see Scheduling Revenue Forecasts.

If you are using the integration between PSA and Revenue Management, records looking up to a template in Revenue Management of type % Complete that fall within the monthly time periods spanning the project duration are included.

Tip:

To configure the template in Revenue Management, use the Actuals Template setting in the Revenue Management Settings custom setting. For more information, see Managing Custom Settingsin the Revenue Management Help.

If you run Revenue Forecasting after revenue has been recognized, the revenue is moved from the Revenue Pending Recognition field into the Revenue Recognized to Date field on the revenue forecast record for the monthly time period that corresponds to the date the revenue was recognized in Revenue Management.

If you are not using the integration between PSA and Revenue Management, Revenue Forecasting looks at the Recognition Method field on a record, which must have a value of % Complete.

Warning:

Depending on how you recognize revenue, you must set the Actuals Template or recognition method on either a project or a milestone but not on both.

Milestone

A revenue forecast record is created for each month for milestones whose recognition method is set as % Complete. This record stores the values for EVAs and timecards for use in Revenue Forecasting.

Notes:

These values are rolled up into the revenue forecast type records for the corresponding project that have “% Complete: Milestone” in the Revenue Source field.

The value in the Planned Hours field on a milestone is used in the revenue forecast calculation as the total hours.

If you do not want PSA to use the value in the Milestone Amount field on the milestone record as the total amount in revenue forecast calculations, you can specify an alternative numeric field in the Total Revenue Field on Milestone field on the active revenue forecast setup record. For more information, see Specifying the Field Containing the Total Milestone Revenue (Deliverable, % Complete, and Equal Split Revenue).

If an actual date is recorded on a milestone, when you run a revenue forecast:

  • Only actual hours are included and the revenue is split between the actual hours. Any scheduled or unscheduled hours are discounted. In this case, actual hours are used as the total hours instead of planned hours.
  • The % Hours Completed for Recognition field on the milestone shows a value of 100%, as the actual date indicates the milestone is complete.

EVA records that meet the following criteria are included:

  • The Type field in the Time Period lookup has a value of Month.
  • For EVA records generated for assignments:
    • The assignment record in the Assignment lookup looks up to the corresponding milestone.
    • The assignment record in the Assignment lookup has the Billable checkbox deselected, or has the Billable checkbox selected with a value of zero or null in the Bill Rate field.
  • For EVA records generated for held resource requests:
    • The records look up to the corresponding milestone.
    • The value in the Resource Request Hours field is greater than zero.
    • The value in the Resource Request Bill Rate field is null or zero.
    • The held resource request does not have an associated assignment.
Note:

If there are no EVAs within the project duration, the value in the Milestone Amount field on a milestone is spread evenly over the monthly time periods between the start and end date of the milestone.

Scheduled Hours

For assignments, Revenue Forecasting uses the following calculation to work out the number of scheduled hours:

Estimated Hours - Actual Hours

Note:

If the value in the Actual Hours field is less than zero, it is treated as zero for the purposes of the calculation.

For held resource requests, the value in the Resource Request Hours field on an EVA record represents the number of scheduled hours.

Unscheduled Hours

The following calculation is used to work out the number of unscheduled hours:

Planned Hours - (Actual Hours on Timecards + Scheduled Hours on Resource Requests + Scheduled Hours on Assignments)

Scheduled Revenue

The following calculation is used to work out the Scheduled Revenue percentage for a given month:

(Total Scheduled Hours / Planned Hours) * 100

To work out the Scheduled Revenue amount, the Scheduled Revenue percentage value is multiplied by the value in the Milestone Amount field on the milestone record.

Timecard records that meet the following criteria are included:

  • The Assignment lookup is populated with a value.
  • The value in the Status field matches one of the values displayed in the Timecard Statuses field on the Est Vs Actuals custom setting.
  • The Approved checkbox is selected.
  • The Billable checkbox is deselected.
  • The corresponding milestone is populated in the Milestone lookup.

To work out the Revenue Pending Recognition percentage, the following calculation is used:

(Sum of approved timecard hours / Planned Hours) * 100

To work out the Revenue Pending Recognition amount, the Revenue Pending Recognition percentage is multiplied by the value in the Milestone Amount field on the milestone record.

If you are using the integration between PSA and Revenue Management:

  • Revenue Recognized to Date = Sum of the recognized values in a given month, based on the recognition date in Revenue Management.
  • Pending Recognition = Revenue Recognized to Date value subtracted from the value on the relevant % Complete: Milestone record that has a revenue type of Actuals in PSA.
  • Scheduled Revenue = Value on the relevant % Complete: Milestone record that has a revenue type of Forecast in PSA.

For more information about the fields on a milestone record, see Milestone Fields.

Project

A revenue forecast record is created for each month for projects whose recognition method is set as % Complete. This record stores the values for EVAs and timecards for use in Revenue Forecasting.

Note:

Some calculations described in this section refer to the Estimated Hours at Completion field. You can configure which field is used for calculating the value in the % Hours Completed for Recognition field on a project. For more information, see Scheduling Revenue Forecasts.

When you run a revenue forecast for a project, the following calculation is used to work out the total Revenue Forecast percentage for a given month:

Revenue Pending Recognition percentage + Scheduled Revenue percentage

A project is considered to be closed if the value in the Stage field on a project is "Completed" or the Closed for Time Entry checkbox is selected when you run a revenue forecast:

  • Only actual hours are included and the revenue is split between the actual hours. Any scheduled or unscheduled hours are discounted.
  • The % Hours Completed for Recognition field on the project shows a value of 100%, as the project is complete.
Note:

If you do not want PSA to use the value in the Bookings field on the project record as the total revenue in revenue forecast calculations, you can specify an alternative numeric field in the Total Revenue Field on Project field on the active revenue forecast setup record. For more information, see Specifying the Field Containing the Total Project Revenue (% Complete and Equal Split Revenue).

EVA records that meet the following criteria are included:

  • The Type field in the Time Period lookup has a value of Month.
  • For EVA records generated for assignments, the assignment record in the Assignment lookup has the Billable checkbox deselected, or has the Billable checkbox selected with a value of zero or null in the Bill Rate field.
  • For EVA records generated for held resource requests:
    • The value in the Resource Request Hours field is greater than zero.
    • The value in the Resource Request Bill Rate field is null or zero.
    • The held resource request does not have an associated assignment.
Note:

If there are no EVAs within the project duration, the value in the Bookings field on a project is spread evenly over the project duration.

Scheduled Hours

For assignments, Revenue Forecasting uses the following calculation to work out the number of scheduled hours:

Estimated Hours - Actual Hours

Note:

If the value in the Actual Hours field is less than zero, it is treated as zero for the purposes of the calculation.

For held resource requests, the value in the Resource Request Hours field on an EVA record represents the number of scheduled hours.

Unscheduled Hours

The following calculation is used to work out the number of unscheduled hours:

Estimated Hours at Completion - (Actual Hours on timecards + Scheduled Hours on resource requests + Scheduled Hours on assignments)

Scheduled Revenue

The following calculation is used to work out the Scheduled Revenue percentage for a given month:

(Total Scheduled Hours / Estimated Hours at Completion) * 100

To work out the Scheduled Revenue amount, the Scheduled Revenue percentage value is multiplied by the value in the Bookings field on the project record.

Timecard records that meet the following criteria are included:

  • The Assignment lookup is populated with a value.
  • The value in the Status field matches one of the values displayed in the Timecard Statuses field on the Est Vs Actuals custom setting.
  • The Approved checkbox is selected.
  • The Billable checkbox is deselected.

To work out the Revenue Pending Recognition percentage, the following calculation is used:

(Sum of approved timecard hours / Estimated Hours at Completion) * 100

To work out the Revenue Pending Recognition amount, the Revenue Pending Recognition percentage is multiplied by the value in the Bookings field on the project record.

If you are using the integration between PSA and Revenue Management:

  • Revenue Recognized to Date = Sum of the recognized values in a given month, based on the recognition date in Revenue Management.
  • Pending Recognition = Revenue Recognized to Date value subtracted from the value on the relevant % Complete: Project record that has a revenue type of Actuals in PSA.
  • Scheduled Revenue = Value on the relevant % Complete: Project record that has a revenue type of Forecast in PSA.

For more information about the fields on a project record, see Project Fields.

Calculating with Closed Periods

This section explains how the revenue forecasts are calculated when relevant records are marked as % Complete and there are closed time periods within the project or milestone duration.

Tip:

If required, you can exclude scheduled hours in closed periods from your revenue forecast calculations for projects and milestones. For more information, see Excluding Scheduled Hours in Closed Periods (% Complete Revenue) and Revenue Forecast Setup Fields.

If you are using the integration between PSA and Revenue Management and you run a revenue forecast on an open project, actual revenue is treated in the following way when there are closed monthly time periods:

  • Closed period, full amount recognized: the full amount is displayed in the Revenue Recognized to Date field on the revenue forecast record for the closed time period.
  • Closed period, partial amount recognized: the part that has been recognized is displayed in the Revenue Recognized to Date field on the revenue forecast record for the closed time period. The remainder is displayed in the Revenue Pending Recognition field on the revenue forecast record for the next open time period.
  • No open time period within project or milestone duration: a revenue forecast record is created for the next available open time period and the revenue is displayed in the Revenue Pending Recognition field on this record. If the revenue is subsequently recognized and you run Revenue Forecasting again, the revenue is moved into the Revenue Recognized to Date field on the revenue forecast record for the time period that corresponds to the date the revenue was recognized in Revenue Management.

If a project is open and there are closed periods containing scheduled or unscheduled hours within the project or milestone duration:

  • Closed period: any scheduled hours in the closed period become unscheduled. The revenue from the unscheduled hours is spread evenly between open monthly time periods that do not contain any scheduled or actual revenue, with the exception of empty months that fall between months containing scheduled or actual hours. If all monthly time periods in the project or milestone duration contain scheduled or actual revenue, the revenue that has become unscheduled is moved into:
    • The final monthly time period within the project duration for projects.
    • The monthly time period that contains the target date or, if populated, the actual date for milestones. If the milestone target date or actual date falls outside the project duration, the project end date is used instead.
  • All periods closed in project or milestone duration: any scheduled or unscheduled revenue is ignored by Revenue Forecasting.
Note:

If a project is closed or a milestone is complete, actual revenue is considered to be 100% of the revenue.

If you are not using the integration between PSA and Revenue Management and you run a revenue forecast, the revenue is treated in the following way when a project is open or a milestone is not complete and there are closed periods within the project or milestone duration:

  • Closed period: any scheduled hours in the closed period become unscheduled. The revenue from the unscheduled hours is spread evenly between open monthly time periods that do not contain any scheduled or actual revenue, with the exception of empty months that fall between months containing scheduled or actual hours. If all monthly time periods in the project or milestone duration contain scheduled or actual revenue, the revenue that has become unscheduled is moved into:
    • The final monthly time period within the project duration for projects.
    • The monthly time period that contains the target date or, if populated, the actual date for milestones. If the milestone target date or actual date falls outside the project duration, the project end date is used instead.
  • All periods closed in project or milestone duration: any scheduled or unscheduled revenue is ignored by Revenue Forecasting.
Note:

If a project is closed or a milestone is complete, actual revenue is considered to be 100% of the revenue.

Including Unscheduled Hours

PSA identifies a month as having scheduled hours if it contains at least one Est Vs Actuals (EVA) record.

If there are any unscheduled hours on a project or milestone and there are months that do not contain any scheduled or actual hours, the revenue from the unscheduled hours is spread evenly across those months, with the exception of empty months that fall between months containing scheduled or actual hours.

If there are unscheduled hours on a project or milestone and all relevant months contain scheduled or actual hours, the revenue from the unscheduled hours is added to:

  • The final month within the project duration for projects.
  • The month that contains the target date or, if populated, the actual date for milestones.

If the milestone target date or, if populated, the milestone actual date falls outside the project duration, the project end date is used instead.

Unscheduled revenue is displayed in the Unscheduled Revenue field on the revenue forecast and revenue forecast type records.

On projects, the following calculation is used to work out the number of unscheduled hours:

Estimated Hours at Completion - (Actual Hours on timecards + Scheduled Hours on resource requests + Scheduled Hours on assignments)

On milestones, the following calculation is used to work out the number of unscheduled hours:

Planned Hours - (Actual Hours on Timecards + Scheduled Hours on Resource Requests + Scheduled Hours on Assignments)

Calculating Accurate Mid Month Forecasts

On the active revenue forecast setup record, you can select Use Mid Month Forecast Calculations and specify a cutoff day. Revenue Forecasting then excludes past scheduled hours that are not covered by timecards from calculations for the current monthly time period (forecasts run for other months are not affected). This means:

  • Scheduled work that never took place is excluded.
  • Forecast calculations exclude such scheduled work on a weekly basis instead of on a monthly basis, aligning with the typical timecard submission cadence.
    • Note:

    Forecasts are still generated monthly.

This setting brings the following benefits:

  • There is a smoother progression through the month, with no sudden change in forecasting values at month end.
  • You have a more accurate representation of the remaining planned work and the completed planned work for the current month. Forecasts run for other months are not affected.

The following rules apply:

  • Revenue Forecasting excludes scheduled hours that fall on or before the actuals cutoff day you select.
  • If the actual hours recorded for a day exceed the scheduled hours, Revenue Forecasting excludes all scheduled revenue for that day.
  • If an assignment uses a daily bill rate and there are actual hours from timecards for that day, Revenue Forecasting includes the day in the forecast as an actual day.
Tip:

For even greater accuracy, you can also select Exclude Actuals After Cutoff Day if you do not want actual hours that are after the cutoff day to be included in % Complete forecast calculations.

For more information, see Configuring Mid Month Forecasting Calculations (Deliverable and % Complete Revenue).

An active fixed fee project has the following attributes:

  • Start Date = December 4.
  • End Date = December 29.
  • Bookings = $20,000.
  • Planned Hours = 160.
  • Recognition method is set to % Complete.

There is one assignment with the following attributes:

  • Assigned to resource: Mateo Smith.
  • Bill Rate = $0 per hour.
  • Start Date = December 4.
  • End Date = December 29.
  • Total scheduled hours = 160.
  • Schedule or schedule exceptions are:
    • 40 hours in Week 1.
    • 40 hours in Week 2.
    • 40 hours in Week 3.
    • 40 hours in Week 4.

Today's date is Tuesday, December 12.

The following timecards have been approved for Mateo Smith:

  • 10 hours in Week 1.
  • 30 hours in Week 2.

The following diagram shows what happens when you select the following on the active revenue forecast setup record:

  • Use Mid Month Forecast Calculations.
  • Exclude Actuals After Cutoff Day (this means Revenue Forecasting excludes scheduled hours that fall after Sunday, 10 December).
  • Sunday from the Actuals Cutoff Day field.

Example of Accurate Mid Month Forecast for % Complete Revenue Forecast

The following table shows the difference between selecting and deselecting Use Mid Month Forecast Calculations.

Effect When Use Mid Month Forecast Calculations Is Selected or Deselected

 

Fields

Use Mid Month Forecast Calculations
Selected

Deselected
Revenue Recognized To Date $0 $0
Revenue Pending Recognition $1,250 $1,250
Scheduled Revenue $15,000 $18,750
Unscheduled Revenue $3,750 $0

Notes

Unused scheduled hours that are not reflected by timecards up to the latest cutoff day (Sunday, December 10) are removed from the scheduled revenue. This means 30 hours from Week 1 are no longer included in the forecast.

Unused scheduled hours in current and future weeks are still forecast until the next cutoff day of Sunday, December 17 is reached.

The 10 unused hours in the current week will be removed from the forecast if not covered by suitable timecards by the end of the day on Sunday, December 17.

Note:

The Timecard Statuses field on the Est Vs Actuals custom setting determines the status of timecards that are included in the forecast, for example, Submitted, Approved. For more information, see Est Vs Actuals Settings.

Using Weighting

Weighting enables you to forecast based on cost rate or other attribute so that the monetary value of each hour on a project or milestone differs depending on the resource the hours are assigned to. For example, if the cost rate amount for resource A is twice the cost rate amount for resource B, an hour of resource A's time accounts for twice as much revenue as an hour of resource B's time.

Notes:

Unscheduled hours are not included when applying weighting. For projects and milestones, the total hours are the sum of the actual and scheduled hours.

For records in different currencies, you must convert the values using the appropriate exchange rate to ensure that the relative weightings are correctly applied. For example, if resource A has a cost rate amount of 100 USD and resource B has a cost rate amount of 100 GBP and the project currency is USD, in this scenario we recommend that you create a custom formula field that converts the cost rate amount into the project currency.

You can enable this feature from the active revenue forecast setup record and can specify the fields on the Assignment and Resource Request objects that determine the relative value of the hours. For more information, see Applying Weighting (% Complete Revenue).

Tip:

If you want to validate the weighted values returned in revenue forecasts, you can view the Actual Weighted Effort and Scheduled Weighted Effort fields on the revenue forecast record for the relevant monthly time period. If the fields are not visible, ask an administrator to add them to the page layout.

An active fixed fee project has the following attributes:

  • Start Date = April 12.
  • End Date = June 23.
  • Bookings = $20,000 (total project revenue).
  • Total Hours = 240 (taken from field specified in Total Hours Field on Project picklist in Revenue Forecast Setup).
  • Recognition Method = % Complete.
  • The monthly time period records for March and April have the Closed for Forecasting checkbox selected.

There are two assignments on the project.

Assignment A has the following attributes:

  • Assigned to resource: Sally Jones.
  • Bill Rate = $0.
  • Cost Rate Amount = $100.
  • Start Date = April 12.
  • End Date = June 23.
  • Total scheduled hours = 120.
  • Schedule, including schedule exceptions:
    • 40 hours in April.
    • 40 hours in May.
    • 40 hours in June.

Assignment B has the following attributes:

  • Assigned to resource: John Smith.
  • Bill Rate = $0.
  • Cost Rate Amount = $150.
  • Start Date = April 12.
  • End Date = June 23.
  • Total scheduled hours = 120.
  • Schedule, including schedule exceptions:
    • 40 hours in April.
    • 40 hours in May.
    • 40 hours in June.

The following diagram gives details of the dates, time periods, and records included in the forecast.

Example of Weighting on a Fixed Fee % Complete Revenue Forecast

When Revenue Forecasting is run on the project, the following fields are updated on the revenue forecast records relating to each monthly time period.

Fields Updated

 

Field		 $ Revenue
April May June
Revenue Recognized To Date $6,033.33 $0 $0
Revenue Pending Recognition $0 $7,300 $0
Scheduled Revenue $0 $0 $6,666.67
Unscheduled Revenue (not supported when applying weighting) $0 $0 $0

The following revenue forecast type records are created.

Revenue Forecast Type Records and Values in Relevant Fields
  $ Value in Revenue Forecasting Fields
Revenue Source Revenue Forecast Type April May June
% Complete: Project Actual

Revenue Recognized To Date: $6,033.33

Revenue Pending Recognition: $0

Scheduled Revenue: $0

Unscheduled Revenue: $0

Revenue Recognized To Date: $0

Revenue Pending Recognition: $7,300

Scheduled Revenue: $0

Unscheduled Revenue: $0

Revenue Recognized To Date: $0

Revenue Pending Recognition: $0

Scheduled Revenue: $0

Unscheduled Revenue: $0
% Complete: Project Forecast

Revenue Recognized To Date: $0

Revenue Pending Recognition: $0

Scheduled Revenue: $0

Unscheduled Revenue: $0

Revenue Recognized To Date: $0

Revenue Pending Recognition: $0

Scheduled Revenue: $0

Unscheduled Revenue: $0

Revenue Recognized To Date: $0

Revenue Pending Recognition: $0

Scheduled Revenue: $6,666.67

Unscheduled Revenue: $0

Notes

In a weighted % Complete calculation, each resource’s scheduled hours are multiplied by their weighting, such as cost rate, to give a total value for their effort on the project. The sum of this value for all resources gives us a total value of the effort on the project as a whole.

Sally Jones has 120 hours on the project at a cost rate of $100
Value of effort on the project: 120*100 = $12,000

John Smith has 120 hours on the project at a cost rate of $150
Value of effort on the project: 120*150 = $18,000

Total revenue, such as Bookings: $20,000
Total value of the effort on the project: 12,000+18,000 = $30,000

The total revenue of the project is divided by the value of the total effort to give a value per hour on the project: 20,000 / 30,000 = $0.6666667

Each actual and scheduled hour a resource has on the project is multiplied by their own weighting, and then by the value per hour to give the revenue forecast (Hours * Weighting) * Value per hour.

For April:

  • Sally Jones worked 38 hours with a cost rate of $100, which is (38*100)*0.6666667 = $2,533.30
  • John Smith worked 35 hours with a cost rate of $150, which is (35*150)*0.6666667 = $3,500.00

As April is closed for forecasting, there is no scheduled revenue and the total revenue forecast for April is 2,533.33 + 3,500.00 = $6,033.33.

For May:

  • Sally Jones worked 42 hours (42*100)*0.6666667 = $2,800
  • John Smith worked 45 hours (45*150)*0.6666667 = $4,500

The total revenue forecast for May is 2,800.00 + 4,500.00 = $7,300. As the actual hours exceed the scheduled hours, there is no scheduled revenue in May.

For June:

  • Sally Jones has 40 hours scheduled (40*100)*0.6666667 = $2666.67
  • John Smith has 40 hours scheduled (40*150)*0.6666667 = $4,000.00

Unscheduled revenue is not supported when using this calculation method.

Example for % Complete Recognition Method

  • Start Date = March 12.
  • End Date = May 23.
  • Bookings = $18,000.
  • Total Hours = 120 (taken from field specified in Total Hours Field on Project picklist in Revenue Forecast Setup).
  • Recognition Method = % Complete.
  • The monthly time period records for February and March have the Closed for Forecasting checkbox selected.

There is one assignment with the following attributes:

  • Assigned to resource: Sally Jones.
  • Bill Rate = $0.
  • Start Date = March 12.
  • End Date = May 23.
  • Total scheduled hours = 100.
  • Schedule or schedule exceptions are:
    • 40 hours in March.
    • 40 hours in April.
    • 20 hours in May.

The following diagram gives details of the dates, time periods, and records included in the forecast.

Example of Fixed Fee % Complete Revenue Forecast.

When Revenue Forecasting is run on the project, the following fields are updated on the revenue forecast records relating to each monthly time period.

Fields Updated

 

Field		 $ Revenue
March April May
Revenue Recognized To Date $5,700 $0 $0
Revenue Pending Recognition $0 $6,300 $0
Scheduled Revenue $0 $0 $3,000
Unscheduled Revenue $0 $0 $3,000

The following revenue forecast type records are created.

Revenue Forecast Type Records and Values in Relevant Fields
  $ Value in Revenue Forecasting Fields
Revenue Source Revenue Forecast Type March

April

May
% Complete: Project Actual

Revenue Recognized To Date: $5,700

Revenue Pending Recognition: $0

Scheduled Revenue: $0

Unscheduled Revenue: $0

Revenue Recognized To Date: $0

Revenue Pending Recognition: $6,300

Scheduled Revenue: $0

Unscheduled Revenue: $0

Revenue Recognized To Date: $0

Revenue Pending Recognition: $0

Scheduled Revenue: $0

Unscheduled Revenue: $0
% Complete: Project Forecast

Revenue Recognized To Date: $0

Revenue Pending Recognition: $0

Scheduled Revenue: $0

Unscheduled Revenue: $0

Revenue Recognized To Date: $0

Revenue Pending Recognition: $0

Scheduled Revenue: $0

Unscheduled Revenue: $0

Revenue Recognized To Date: $0

Revenue Pending Recognition: $0

Scheduled Revenue: $3,000

Unscheduled Revenue: $3,000

Notes

In March, only 38 of the 40 scheduled hours were submitted and approved in timecards. The amount in Revenue Pending Recognition is (38 / 120) * 18,000 = $5,700. As the full amount is recognized, no revenue rolls into April when the March time period is closed.

The scheduled revenue for the remaining two hours in March is ignored when the period is closed.

In April, Sally Jones works two hours more than scheduled to make up for March. 120 hours is still the total hours for the project, so in Revenue Pending Recognition there is (42 / 120) * 18,000 = $6,300. As the number of timecard hours exceeds the number of scheduled hours, there is no scheduled revenue in April.

In May, there are 20 scheduled hours, which means the amount in Scheduled Revenue is (20 / 120) * 18,000 = $3,000.

The whole project has only 100 hours out of the total planned 120 hours in timecards or schedules. The remaining 20 hours corresponds to $3,000 of revenue, which goes into the first period that does not contain any actual or scheduled hours, or the last period in the project if there are no periods without any actual or scheduled hours. In this example, the $3,000 goes into Unscheduled Revenue in May.