FP&A 202 · CAPABILITY
How do FP&A planning and budgeting work?
Planning translates strategy into operational and financial assumptions; budgeting converts an approved plan into an accountable baseline and, where applicable, a spending boundary.
FP&A ROLE
What this capability is for
A useful plan is driver-based enough to explain, integrated enough to reconcile, and simple enough for accountable owners to maintain. FP&A coordinates the cycle, challenges assumptions, consolidates submissions, and protects the approved baseline.
WORKING FLOW
Move from question to controlled result
Set the planning contract
Agree horizon, calendar, versions, granularity, currency, materiality, responsibilities, submission workflow, and approval rules.
Prepare a controlled starting point
Use actuals, run rate, contracts, headcount, demand, price, capacity, projects, and policy assumptions without treating last year plus a percentage as the only truth.
Collect and challenge inputs
Business owners enter assumptions and values; FP&A tests internal consistency, affordability, dependencies, risks, and the evidence behind material changes.
Freeze and communicate the baseline
Publish the approved budget, retain rejected and adjusted assumptions, distribute targets, and define how future forecasts will compare with the baseline.
CONTROL POINTS
What makes the result trustworthy?
Plan versus budget
The plan describes an expected operating path. The budget is the formally approved baseline and may connect to spending controls. A forecast should not overwrite either history.
Driver and account integration
Volume × price, headcount × rate, activity × cost, project timing, working-capital days, and capital spend should flow coherently into P&L, balance sheet, and cash views.
Top-down and bottom-up balance
Leadership targets need operational feasibility; local submissions need strategic and funding discipline. Reconciliation should expose—not hide—the gap between them.
DECISION EVIDENCE
Retain the assumptions behind the number
A result is reusable only when another person can understand its source, version, ownership, and decision context.
Driver name, definition, owner, source, baseline, seasonality, sensitivity, and approval.
Entity or responsibility scope, completeness, validation errors, commentary, workflow status, and timestamp.
Approved version, exchange rates, allocations, eliminations, retained adjustments, and sign-off.
WORKED EXAMPLE
An annual operating plan
A manufacturer plans unit demand, price, material inflation, labor capacity, maintenance, headcount, capital projects, inventory days, and customer-payment timing. FP&A challenges whether output fits capacity and whether the resulting P&L, balance sheet, and cash flow tell one story before the budget is approved.
- Drivers reconcile
- Capacity is feasible
- Cash impact is visible
- Baseline is locked
OFFICIAL SAP REFERENCES
Continue into product-specific detail
Capabilities and navigation vary by SAP edition, release, licensed scope, and role. Verify against the approved target landscape.
Run the complete cycle from management question through governed action.