1. Financial Planning & Analysis
  2. Process
  3. Forecast review
Process · Forecast review

Forecast review

A forecast version draws its planning context from a named driver, partner and dated term. Admin maintains the driver’s unit, rate and basis. FP&A Planner checks those assumptions against the version’s forecast amount and actual to date. Finance Leader can inspect held versions and ask for the recorded reason.

Step by step

  1. Maintain forecast drivers Admin

    Check the unit, rate, driver type and default basis used by version owners.

    • Check the unit, rate, driver type and default basis used by version owners.
    • Updates Forecast drivers
  2. Review forecast versions FP&A Planner

    Compare forecast amount with actual to date over the version term and inspect any hold reason.

    • Compare forecast amount with actual to date over the version term and inspect any hold reason.
    • Updates Forecast versions, Forecast drivers, Business partners

Where it usually breaks

And how to keep it from happening.

  • Compare driver code and version reference before discussing a rate change.
  • Keep the version’s partner, organization and start and end dates together.
  • Review the held version’s reason with its owner before using its amount in a planning decision.
Admin
, FP&A Planner and Reviewer participate according to the record and access setup.

Set up Financial Planning & Analysis your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started