Skip to content
K
GoBD: n/a §203 StGB-compliant Q3-Q4

Forecast Agent

Calculate rolling forecast - extrapolate trends, model scenarios, analyse sensitivities.

Prepares historical data, extrapolates trends, models best/base/worst scenarios, performs sensitivity analyses and compares the forecast with the budget.

Analyse your process
Airbus Volkswagen Shell Renault Evonik Vattenfall Philips KPMG

Rule-based trend extrapolation and scenarios, assumptions and judgement stay with humans

The agent prepares historical data deterministically, calculates best/base/worst-case scenarios and sensitivities by rules, and hands assumptions and strategic assessment to the planning owner.

Outcome: Forecast cycle reduced from 3 weeks to 4 working days, scenario coverage from 1 to 3 per planning run, and a reproducible calculation basis instead of hidden spreadsheet logic.

62% Rules Engine
0% AI Agent
38% Human

The clean assignment of the 8 steps between calculation and judgement relieves the controller specifically:

142 million euro point forecast, outdated the day it is issued

Fifty-one percent of CFOs name forecast accuracy as one of their five top priorities (Gartner CFO Survey 2025). Yet most FP&A teams still work with point forecasts in spreadsheets - a single number that is already outdated on the day it is produced. The problem lies not in the calculation. It lies in the missing separation between what an algorithm can deliver and what requires human judgement.

Forecast accuracy fails on processes, not models

When a forecast misses its mark, the instinctive reaction is to question the model. More variables, more complex regressions, more data points. But KPMG research shows that companies with high data quality are 3.5 times more likely to produce reliable forecasts than companies with better models but worse data.

The bottleneck runs deeper: in most finance departments, the forecast process mixes mechanical work with judgement calls. The same person who cleanses historical data is expected, in the same step, to define growth assumptions. The result is projections that are neither truly data-driven nor strategically grounded - but a compromise of both.

A Forecast Agent solves this by decomposition. Data preparation, trend extrapolation, scenario calculation and sensitivity analysis run rule-based. Defining assumptions, assessing plausibility and strategic interpretation stay with the CFO or Head of FP&A. Not because automation would be impossible there, but because these steps demand business knowledge that no model can replicate.

Scenario analysis replaces the deceptive point forecast

A revenue forecast of EUR 142 million (USD 156 million) conveys a precision that does not exist. Reality is a range - depending on market developments, exchange rates, raw material prices and dozens of other variables. According to an EPM Channel study, only 42 percent of companies use a rolling forecast, even though companies with rolling forecasts achieve 25 percent more accurate projections.

The Forecast Agent calculates three fully modelled scenarios: best case, base case, worst case. Each scenario rests on a defined assumption set - not on optimism or pessimism, but on parameterised variables. Exchange rate assumption plus two percent, raw material costs minus five percent, sales volume constant: that yields a concrete scenario with traceable logic.

For corporate steering, this represents a step change in decision quality. The board no longer debates a single number but discusses ranges and their probabilities. The question shifts from “Is the forecast right?” to “Under which conditions do we land in the worst case - and what do we do then?”

Sensitivity analysis identifies the one variable that matters

Not all assumptions carry equal weight. A forecast may hinge on ten variables, but often a single one dominates the outcome corridor. For an export-oriented manufacturer, the EUR/USD rate can produce more earnings volatility than all internal cost levers combined.

The Forecast Agent’s sensitivity analysis systematically calculates how much the result changes when each variable shifts by a defined percentage. The output is a ranking: which assumption has the greatest leverage? Where does hedging pay off? Where is monitoring sufficient?

This transparency changes board conversations. Instead of twenty slides of detailed figures, a clear statement enters the room: “Our EBIT reacts three times more strongly to the copper price than to personnel costs. That is where our risk sits - and where our action option lies.”

The Decision Layer separates calculation from strategic judgement

The Forecast Agent operates at Decision Layer tiers 1 and 2. Five of the eight decision steps are rule-based: data preparation, trend extrapolation, scenario calculation, sensitivity analysis and budget comparison. Three steps remain with the human: defining assumptions, checking plausibility, strategic assessment.

This architecture is deliberately conservative. For listed companies, forecasts flow into the outlook section of the annual report. The assumptions behind each scenario must be traceable - not only for management but also for statutory auditors and the supervisory board. The Decision Layer documents for every forecast cycle which assumptions were defined by whom, which data served as the basis and how the scenarios were calculated.

The result for FP&A teams: instead of spending weeks on data cleansing and spreadsheet maintenance, they invest their time where they actually create value - in interpreting the numbers and delivering strategic recommendations to the board.

Micro-Decision Table

Who decides in this agent?

8 decision steps, split by decider

62%(5/8)
Rules Engine
deterministic
0%(0/8)
AI Agent
model-based with confidence
38%(3/8)
Human
explicitly assigned
Human
Rules Engine
AI Agent
Each row is a decision. Expand to see the decision record and whether it can be challenged.
Prepare historical data Which data forms the basis for the forecast? Rules Engine

Database query and data cleansing

Decision Record

Rule ID and version number
Input data that triggered the rule
Calculation result and applied formula

Challengeable: Yes - rule application verifiable. Objection possible for incorrect data or wrong rule version.

Calculate trend extrapolation How do metrics develop if the trend continues? Rules Engine

Linear trends = R, non-linear patterns = A

Decision Record

Rule ID and version number
Input data that triggered the rule
Calculation result and applied formula

Challengeable: Yes - rule application verifiable. Objection possible for incorrect data or wrong rule version.

Define assumptions Which growth, cost and FX assumptions apply per scenario? Human

Strategic assumptions require human judgement

Decision Record

Decider ID and role
Decision rationale
Timestamp and context

Challengeable: Yes - via manager, works council, or formal objection process.

Calculate scenarios What do best, base and worst case yield? Rules Engine

Arithmetic calculation per scenario

Decision Record

Rule ID and version number
Input data that triggered the rule
Calculation result and applied formula

Challengeable: Yes - rule application verifiable. Objection possible for incorrect data or wrong rule version.

Sensitivity analysis Which variable has the greatest impact on the result? Rules Engine

Calculation = R, interpretation of relationships = A

Decision Record

Rule ID and version number
Input data that triggered the rule
Calculation result and applied formula

Challengeable: Yes - rule application verifiable. Objection possible for incorrect data or wrong rule version.

Compare forecast vs. budget How does the forecast deviate from the budget? Rules Engine

Arithmetic comparison

Decision Record

Rule ID and version number
Input data that triggered the rule
Calculation result and applied formula

Challengeable: Yes - rule application verifiable. Objection possible for incorrect data or wrong rule version.

Plausibility check Are the forecast results plausible? Human

Experience and industry knowledge

Decision Record

Decider ID and role
Decision rationale
Timestamp and context

Challengeable: Yes - via manager, works council, or formal objection process.

Strategic assessment Which strategic options emerge from the forecast? Human

Judgement in strategic interpretation

Decision Record

Decider ID and role
Decision rationale
Timestamp and context

Challengeable: Yes - via manager, works council, or formal objection process.

Decision Record and Right to Challenge

Every decision this agent makes or prepares is documented in a complete decision record. Affected parties (employees, suppliers, auditors) can review, understand, and challenge every individual decision.

Which rule in which version was applied?
What data was the decision based on?
Who (human, rules engine, or AI) decided - and why?
How can the affected person file an objection?
How the Decision Layer enforces this architecturally →

Does this agent fit your process?

We analyse your specific finance process and show how this agent fits into your system landscape. 30 minutes, no preparation needed.

Analyse your process

Governance Notes

GoBD: n/a §203 StGB-compliant

Not GoBD-relevant: the Forecast Agent does not process tax-relevant data - it creates projections and scenarios. However, the results can have significant impact on investment, financing and personnel decisions.

The assumptions and strategic assessment remain with the controller. The agent delivers the calculation - responsibility for assumptions and recommendations lies with the human. This must be transparently documented.

§203 StGB-relevant data is encrypted end-to-end and never passed to AI models in plain text.

Process Documentation Contribution

The Forecast Agent documents: which historical data was used as the basis, which trend models were applied, which assumptions were defined per scenario and how the sensitivity analysis was calculated.

Assessment

Agent Readiness 41-48%
Governance Complexity 26-33%
Economic Impact 66-73%
Lighthouse Effect 48-55%
Implementation Complexity 46-53%
Transaction Volume Monthly

Prerequisites

  • ERP system with at least 24 months of historical financial data
  • Planning system for budget data (SAP BPC, Jedox, Anaplan or equivalent)
  • Defined scenario parameters and assumptions framework
  • Access to external data for market and FX assumptions

Infrastructure Contribution

The Forecast Agent uses the variance analysis engine of the Budget Variance Analysis Agent and the KPI library of the Management Reporting Agent. The scenario modelling framework becomes the standard for all planning and projection processes. The sensitivity analysis engine is reused by the Cash Forecasting Agent.

Builds Decision Logging and Audit Trail used by the Decision Layer for traceability and challengeability of every decision.

What this assessment contains: 9 slides for your leadership team

Personalised with your numbers. Generated in 2 minutes directly in your browser. No upload, no login.

  1. 1

    Title slide - Process name, decision points, automation potential

  2. 2

    Executive summary - FTE freed, cost per transaction before/after, break-even date, cost of waiting

  3. 3

    Current state - Transaction volume, error costs, growth scenario with FTE comparison

  4. 4

    Solution architecture - Human - rules engine - AI agent with specific decision points

  5. 5

    Governance - EU AI Act, GoBD/statutory, audit trail - with traffic light status

  6. 6

    Risk analysis - 5 risks with likelihood, impact and mitigation

  7. 7

    Roadmap - 3-phase plan with concrete calendar dates and Go/No-Go

  8. 8

    Business case - 3-scenario comparison (do nothing/hire/automate) plus 3×3 sensitivity matrix

  9. 9

    Discussion proposal - Concrete next steps with timeline and responsibilities

Includes: 3-scenario comparison

Do nothing vs. new hire vs. automation - with your salary level, your error rate and your growth plan. The one slide your CFO wants to see first.

Show calculation methodology

Hourly rate: Annual salary (your input) × 1.3 employer burden ÷ 1,720 annual work hours

Savings: Transactions × 12 × automation rate × minutes/transaction × hourly rate × economic factor

Quality ROI: Error reduction × transactions × 12 × EUR 260/error (APQC Open Standards Benchmarking)

FTE: Saved hours ÷ 1,720 annual work hours

Break-Even: Benchmark investment ÷ monthly combined savings (efficiency + quality)

New hire: Annual salary × 1.3 + EUR 12,000 recruiting per FTE

All data stays in your browser. Nothing is transmitted to any server.

Forecast Agent

Initial assessment for your leadership team

A thorough initial assessment in 2 minutes - with your numbers, your risk profile and industry benchmarks. No vendor logo, no sales pitch.

30K120K
1%15%

All data stays in your browser. Nothing is transmitted.

Frequently Asked Questions

How often should the rolling forecast be updated?

Most companies update monthly or quarterly. The agent supports both rhythms. A monthly forecast is more accurate but requires more effort in maintaining assumptions. The choice depends on the volatility of the business model.

Can the agent also incorporate non-financial drivers into the forecast?

Yes, if data is available. Sales volumes, headcount, production capacity and other drivers can be included as variables in scenario modelling. Defining the relationships between drivers and financial metrics is a one-time configuration.

How is forecast accuracy measured?

The agent automatically calculates forecast accuracy by comparing past forecasts with actual results. Systematic analysis of forecast errors improves model quality over time.

What Happens Next?

1

30 minutes

Initial call

We analyse your process and identify the optimal starting point.

2

1 week

Discover

Mapping your decision logic. Rule sets documented, Decision Layer designed.

3

3-4 weeks

Build

Production agent in your infrastructure. Governance, audit trail, cert-ready from day 1.

4

12-18 months

Self-sufficient

Full access to source code, prompts and rule versions. No vendor lock-in.

Implement This Agent?

We assess your finance process landscape and show how this agent fits your infrastructure.