Finance · Forecast
Route /finance/revenue-forecast Flag revenueForecastEnabled

Revenue Forecast

Forward look composed from POs, plans, and pipeline — a forecast view, not a second set of contracts.

Scroll to Flowcharts. Scenario: Read forecast vs pipeline and open a gap.

Forward look

Forecast from contracts and pipeline you already have

Revenue forecast looks ahead using bids, POs, and plans. It does not create a parallel contract book.

Finance → Revenue forecast Route /finance/revenue-forecast Org flag revenueForecastEnabled Finance Manager · Executive · Admin

The job of this console

Pick a horizon, see what is driving the number, open that bid or PO if it is wrong.

Seat at the table

Finance and executives. Sales operators update bids; finance owns the lens.

The working rhythm

Set horizon, read, drill, fix source.

Moments that bring you here

Quarter commit. Board pack. After a slipped PO. A bid that should not be weighted.

ⓘ
View of commercial sources
Bids are pursuit. POs are contracts. Recognition books revenue.

Flowcharts

1 — Horizon then source

Read the forecast, open the bid or PO that drives it.

flowchart TD
  A[Open Revenue forecast] --> B[Pick horizon]
  B --> C[See drivers]
  C --> D[Bid / PO / plan]
  D --> E[Forecast follows]
            
  1. 1
    OpenFinance → Revenue forecast.
  2. 2
    HorizonPeriod.
  3. 3
    DriversPipeline and contracts.
  4. 4
    Fix sourceNot the chart.

Overview

Forecast composes bids, POs, and billing plans. Booked revenue still needs invoices/recognition per policy.

How to use

1. Won ≠ recognized
Recognition console posts.
2. Pipeline weighting
Understand the product’s rules.
3. Do not sandbox in Excel as source
Change the bid/PO.