FP&A 202 · CAPABILITY
How does FP&A build an integrated plan?
FP&A translates strategy into connected operational and financial assumptions, then publishes a decision baseline; B2R separately owns budget authorization, release, and spend control.
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 publishes the management baseline. Where that baseline becomes a spending boundary, B2R owns the authorization and availability-control process.
Coordinate drivers, challenge submissions, publish the management baseline, and maintain the forecast and scenario versions used for decisions.
Turn an approved management plan into a formal budget baseline, release, availability rule, and controlled change only where a spending boundary is required.
Provide closed actuals, accounting definitions, reconciliation boundaries, and period status; it does not approve the forward plan or budget.
WORKING FLOW
Move from question to controlled result
Set the planning contract
Agree horizon, calendar, versions, granularity, currency, materiality, responsibilities, submission workflow, and management sign-off rules. Planning sign-off is not budget authorization.
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 planning baseline
Publish the integrated management baseline, retain rejected and adjusted assumptions, distribute targets, and define how future forecasts will compare with it. Hand any spending boundary to B2R for separate authorization and release.
CONTROL POINTS
What makes the result trustworthy?
Planning baseline versus spend authority
FP&A publishes the integrated plan and explains its assumptions. B2R separately authorizes, releases, and controls a budget where spend control is required. 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 FP&A publishes the plan and B2R separately authorizes any spending boundary.
- 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.