Financial Planning
FP&A: How Financial Planning and Analysis Works
Learn what FP&A does and build a practical cycle connecting operating plans, forecasts, actual results, variance explanations and decisions.

What you will learn
- Distinguish corporate FP&A from bookkeeping and a single financial model.
- Explain a volume variance using a coherent example.
- Assign assumptions, review dates and decisions to accountable owners.
Financial planning and analysis, or FP&A, connects the operating plan, forecast, actual results and next decision. Its value is a clear answer to three questions: what changed, why does it matter and what should the team do next? Use the cycle below to connect financial figures with the people who own the business drivers.
What exactly does FP&A do?
The Association for Financial Professionals describes integrated planning and forecasting, performance management, and financial analysis as core functions. FP&A works with historical accounting information but uses it to support forward-looking business choices.
Oracle’s FP&A overview also distinguishes the planning cycle from accounting alone. A forecast is an estimate of what may happen, a budget is an agreed planning reference, and actuals describe reviewed results. Label them rather than letting the newest spreadsheet overwrite the earlier promise.
Make the operating cycle explicit
Original plan-to-decision operating cycle
| Stage | Useful output | Accountable question |
|---|---|---|
| Plan | Assumptions and resource commitments | What choices are we making? |
| Forecast | Current expected outcome with changed inputs | What do we now expect, and why? |
| Close actuals | Reviewed results under a stated basis | What happened? |
| Explain variance | Amount, cause evidence and uncertainty | Which difference changes a decision? |
| Decide and follow up | Owner, action and next evidence date | What will happen next? |
A small team may combine roles, but the questions still differ. The person entering actuals should not have to guess which commercial assumption changed. Give each important driver a source, owner and update trigger.
Work a volume variance before adding complexity
Fictional services business, one month, U.S. dollars. The plan expects 100 units at $200 each, variable cost $60 per unit and fixed operating costs $8,000. Actual volume is 90 units; price, unit cost and fixed costs are unchanged. This is a simplified operating example, excluding tax, financing and other items.
Original plan-versus-actual comparison
| Measure | Plan | Actual | Actual minus plan |
|---|---|---|---|
| Units | 100 | 90 | -10 |
| Revenue | $20,000 | $18,000 | -$2,000 |
| Variable cost | $6,000 | $5,400 | -$600 expense |
| Contribution | $14,000 | $12,600 | -$1,400 |
| Fixed cost | $8,000 | $8,000 | $0 |
| Simplified operating result | $6,000 | $4,600 | -$1,400 |
The unit contribution is $200 - $60 = $140. Ten fewer units explain a $1,400 lower result. The $600 cost reduction is not automatically a process efficiency: it follows from delivering fewer units under these assumptions.
Separate explanation from prediction
“Volume was ten units below plan” describes the result. “A delayed customer approval caused it” is a hypothesis needing evidence. “Next month will recover” is a forecast assumption. Keep all three statements separate so an understandable narrative does not become an unsupported promise.
Record the source and confidence of the cause, then ask whether it changes the next forecast. If an approval merely moved into a later month, timing may change without changing the total opportunity. If demand weakened, the expected volume itself may need review. Do not force both into the same variance label.
Use a driver-and-decision register
- Driver: the operating input with a meaningful effect.
- Definition and period: what the number counts and when.
- Plan, actual and latest forecast: separate values, not overwritten versions.
- Evidence: source record and what remains unknown.
- Owner: who can explain and verify the driver.
- Decision: what changed, who acts and when the effect is reviewed.
Prioritize material exceptions rather than reporting every line with equal emphasis. A consistent forecast and a short explanation can be more useful than a dashboard whose measures change every meeting.
Bring the right supporting lessons together
Use the financial-model lesson for constructing scenarios, the weekly business review for the meeting, and the decision journal for recording the choice and later learning. FP&A connects those jobs rather than replacing them.
Carry the financial insight into the next conversation. Keep the planning brief, supporting documents and follow-up context in Finta. Ask Aurora to summarize the supplied variances and draft a focused meeting agenda, while your finance model and accounting system retain the numbers behind the discussion.
Copyable AI prompt
Try this with Aurora AI in Finta, Codex, or Claude. Share only information you are allowed to use, and check the answer before acting.
Using [authorized plan/actual/forecast data] and [driver notes], draft an FP&A exception brief. Define each measure and show the arithmetic of material differences. Separate observations, proposed causes, assumptions and decisions. Assign evidence checks and owners. Do not invent causes, change a model or recommend investments. Prepare a draft for human finance and operating review.Finta Field Guide. By Finta Editorial Team. Sources checked November 15, 2026. Examples and worksheets are original fictional teaching exercises, not customer results or benchmarks. General education, not individualized accounting, financial, investment, legal or tax advice.