What-If Analysis / Sensitivity Modeling is where ERP discipline either begins or breaks.
What-If and Sensitivity Analysis looks operational from far away. In a real finance team, it is a chain of assertions: the right actor started the work, the required records existed, the control policy was applied, the state change was preserved, and the outcome can be explained later without rebuilding the transaction from emails and spreadsheets.
The expected business outcome is specific: CFO and business leaders can quantify the P&L sensitivity to key business drivers within minutes, enabling faster and better-informed strategic decisions.
The control flow a finance team actually needs.
Step 1
What-If Workspace Be Isolated From The...
Step 2
Single-Variable Sensitivity Stepping A...
Step 3
Tornado Chart Rank Drivers By Absolute...
Step 4
Multi-Variable Tables At Least 3...
Step 5
Recalculation Complete In Under 5 Seconds
The ERP surface involved.
Module
What-If Analysis / Sensitivity Modeling
Actors
FP&A Analyst, CFO, Business Unit Leader
Tier
Tier 2
Finance area
Budgeting, Planning & FP&A
Region lens
US and UK finance teams
Publication date
April 11, 2026
What-if workspace must be isolated from the approved budget and forecast (changes do not flow to actuals or approved versions unless explicitly promoted); single-variable sensitivity must support stepping a driver across at minimum 10 user-defined values; tornado chart must rank drivers by absolute EBITDA impact; multi-variable tables must support at least 3 simultaneous driver ranges; recalculation must complete in under 5 seconds; named what-if versions must be saveable with title, creator, and date; drill-down from any output cell to its input formula must be available.
US and UK teams have different compliance hooks, but the same control problem.
US teams usually care about clean evidence for audit support, vendor records, payment controls, tax reporting, and management review. UK teams usually care about VAT-ready records, approval evidence, digital-record discipline, and traceable postings. The country-specific details differ, but the operating pattern is the same: the ERP needs controlled records, explicit ownership, defensible state changes, and evidence that survives beyond the person who completed the task.
The control matrix.
| Control area | Requirement | Acceptance proof |
|---|---|---|
| Control 1 | What-if workspace must be isolated from the approved budget and forecast (changes do not flow to actuals or approved versions unless explicitly promoted | Given a what-if workspace seeded from the current approved forecast |
| Control 2 | single-variable sensitivity must support stepping a driver across at minimum 10 user-defined values | when FP&A Analyst runs single-variable sensitivity on win rate stepping across at least 10 values |
| Control 3 | tornado chart must rank drivers by absolute EBITDA impact | then system returns a tornado chart ranking drivers by absolute EBITDA impact and recalculates within 5 seconds |
| Control 4 | multi-variable tables must support at least 3 simultaneous driver ranges | results are saveable as a named what-if version without affecting approved budget |
| Control 5 | recalculation must complete in under 5 seconds | |
| Control 6 | named what-if versions must be saveable with title, creator, and date | CFO and business leaders can quantify the P&L sensitivity to key business drivers within minutes, enabling faster and better-informed strategic decisions. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | FP&A Analyst opens a what-if workspace seeded from the current approved forecast. Analyst selects a set of input assumptions - unit volume, average selling price, cost of goods sold as a percentage, and headcount - and defines a sensitivity range for each. System calculates the P&L impact for each combination of inputs, presenting results as a tornado chart (single-variable sensitivity) and a data table (multi-variable). CFO reviews the analysis to understand which drivers have the largest impact on EBITDA margin. Business Unit Leader uses the workspace to model a specific deal scenario and present the projected margin contribution. Results can be saved as a named what-if version without affecting the approved budget. |
| Control rules | What-if workspace must be isolated from the approved budget and forecast (changes do not flow to actuals or approved versions unless explicitly promoted); single-variable sensitivity must support stepping a driver across at minimum 10 user-defined values; tornado chart must rank drivers by absolute EBITDA impact; multi-variable tables must support at least 3 simultaneous driver ranges; recalculation must complete in under 5 seconds; named what-if versions must be saveable with title, creator, and date; drill-down from any output cell to its input formula must be available. |
| Acceptance proof | |
| Data record | |
| System event | |
| Lifecycle state | |
The useful version of this workflow is not only fast. It is inspectable. A controller, auditor, or operator should be able to move from source event to system record to state transition to final business outcome without guessing.
Implementation contracts.
Reference data model
`whatif_workspace` { id: ww_*, name: string, base_version_id: string, created_by: string, created_at: timestamp, external_id: string }; `whatif_driver` { id: wd_*, workspace_id: string, driver_name: string, current_value: numeric, range_min: numeric, range_max: numeric, steps: int }; `whatif_result` { id: wr_*, workspace_id: string, driver_name: string, step_value: numeric, ebitda_impact_minor: int64, currency_code: char(3) }; (reference, product may differ).API and events
`POST /v1/whatif-workspaces` { base_version_id, name, external_id } -> 201 { id }; `POST /v1/whatif-workspaces/{id}/sensitivity` { driver_name, range_min, range_max, steps } -> 200 { results: [], tornado_ranking: [] }; `POST /v1/whatif-workspaces/{id}/promote-to-budget` requires CFO authorization; emits `whatif.version_saved` event.State transitions
`DRAFT -> SAVED`; guard: what-if workspace is isolated from approved budget; changes do not flow to actuals unless explicitly promoted with CFO authorization; multi-variable tables support at least 3 simultaneous driver ranges.Common implementation traps.
Treating the workflow as data entry
If the ERP only stores the final record, the team loses the decision trail that explains how the record became valid.
Hiding exception logic
Exceptions need owners, reason codes, and time stamps. A vague pending state is not a control.
Posting without recovery design
Retries, duplicate submissions, and partial failures must be explicit so the system does not create inconsistent records.
Skipping evidence design
A workflow that cannot produce evidence on demand will eventually push finance teams back into manual screenshots and spreadsheets.
Where Rivane fits.
Rivane is built for finance workflows where automation must stay tied to source documents, approvals, state transitions, ledger impact, reporting, and audit evidence. Use this guide as a checklist for evaluating whether an ERP workflow is merely digitized or actually controlled.
References and source basis.
These sources provide the standards, regulatory, or government context around the flow. They are included so the guide is useful to finance operators, auditors, and implementation teams, not only buyers reading software copy.