What Is FP&A? Role, Process, and Tools

Accounting produces the auditable record of what happened in the period. Financial planning and analysis (FP&A) works from that same record to explain why the numbers moved and what the business should do next. When the two views run on different versions of the actuals, the forecast becomes a second set of books. Leadership then has to decide which one to believe before it can decide anything else.

FP&A stands for financial planning and analysis. You'll also see it written as FPA without the ampersand, and it refers to the same function.

The term covers both the people and the work. Analysts and managers own the plan. The work itself is the annual budget, the rolling forecast, the variance pack, and the scenario models that sit behind a decision. Software supports all of that, though no tool defines what the function is accountable for.

An FP&A analyst sits between the books and the business, which means turning a closed period into something an operating leader can act on. Most of the role comes down to five recurring jobs:

• Build and maintain the budget and the rolling forecast.
• Explain actual against plan and actual against forecast.
• Model scenarios for drivers such as volume and price, hiring, or a deal.
• Partner with unit leaders on the story behind the numbers.
• Prepare packs for monthly reviews and the board.

Analysts don't post journals, and they don't own the general ledger. What they own is an outlook they have to defend in front of the chief financial officer (CFO) and the board. That outlook only holds up when the actuals underneath it are the same actuals the close just signed.

Both functions need the same data model underneath them. If FP&A re-keys the profit and loss statement into a workbook, the explanation of a variance won't match the close that produced it. The monthly review then turns into an argument about whose number is right.

Most teams run some version of the cycle below, whether the calendar is monthly or quarterly. The sequence matters more than the cadence because each step depends on the one before it holding up.

Set the targets

Leadership sets the goals for growth, margin, cash, and headcount. FP&A turns those goals into a plan structure the business can actually own, built on drivers that unit leaders recognize from their own operations.

Build the annual plan

The plan gets built by driver, using volume, rate, and headcount rather than last year plus a percentage. Lines of business submit their numbers, and FP&A challenges the assumptions before consolidating everything into one version the CFO can present.

Update the forecast

A rolling forecast updates the outlook as actuals land through the year. Good forecasts move when the business moves, rather than waiting for the calendar to reach the end of a quarter.

Explain the close

Once the period closes, FP&A explains the variance across price, volume, mix, timing, and one-time items. That commentary is the part of the pack leadership actually reads, and it's where the function either earns credibility or loses it.

Test the scenarios

Before a hiring wave, a price change, or an acquisition, FP&A models the impact on the profit and loss statement, the balance sheet, and cash. Three scenarios with assumptions a board can trace are worth more than one precise number nobody can explain.

Make the recommendation

The output that matters is the recommendation rather than the model that produced it. Leadership wants to know which option FP&A would choose and why, and that answer is only credible when every figure traces back to trusted actuals.

Teams generally work across three layers, and the problems tend to show up where those layers meet.

1. The enterprise resource planning (ERP) system and the close produce the actuals.
2. Planning and forecasting software holds versions, drivers, and workflow.
3. Spreadsheets and slides handle the last mile of the story.

A spreadsheet works well for a single model built by one analyst who knows every cell in it. The same file struggles as the system of record for a multi-entity plan. That's because version control, security, and the audit trail all depend on someone remembering to enforce them. When the plan, forecast, and close share the same accounts and entities, that work belongs in software running planning on the same model as reporting.

Explore budgeting and forecasting software to see how versions, drivers, and workflow stay governed.

AI has become part of the toolkit for first-pass variance commentary and for cutting the data behind it. The forecast still has a human owner who signs the number. The practical question is which steps a team is willing to hand over and what evidence it needs back before approving the result.

Explore agentic AI in FP&A for what Finance leaders are handing to agents today.

FP&A is one process inside enterprise performance management (EPM), the management layer that also covers close, consolidation, and reporting. Teams that run planning as a separate system spend every month reconciling the forecast back to the close. FP&A wants to stop doing exactly that work.

Gartner defines financial planning software as enabling Finance organizations to plan and analyze business financial strategy across all three statements. The definition also covers modeling, collaboration, analytics, and performance reporting. Gartner has also named OneStream a Leader in the Magic Quadrant for Financial Planning Software for 5 years. Planning, close, and reporting run on the same data model, so a forecast can be explained against last month's actuals without an export.

Nasdaq runs a deliberately small Finance function on that model, using OneStream across four areas of the cycle:

• Consolidation and financial reporting
• Forecasting, including revenue forecasting
• Allocations
• People planning

Because all of that work sits on one data set, Nasdaq can apply AI to forecasting without assembling the inputs first. Analysts then spend the cycle on scenarios instead of collection.

FP&A is financial planning and analysis, the people and the process that turn actuals into a plan, a forecast, and a recommendation. The role is partnership with the business, and the cycle runs from setting targets through building the plan, forecasting, explaining, modeling, and advising. Whatever software sits underneath that cycle only works when it shares a set of numbers with accounting. That's because an outlook built on a different version of the actuals can't be defended in the room where it matters.

Explore FP&A software for how planning runs on the same model as the close.

What is FP&A?

FP&A is financial planning and analysis, the Finance function that plans, forecasts, explains performance, and advises leadership on what to do next.

What does FP&A stand for?

FP&A stands for financial planning and analysis. Teams that write it as FPA without the ampersand are describing the same function.

What does an FP&A analyst do?

FP&A analysts build plans and forecasts, explain variances, run scenarios, and partner with the business on the story behind the numbers. The general ledger stays with accounting.

What is the FP&A process?

The FP&A process runs in six steps: set the targets, build the plan, update the forecast, explain the close, test scenarios, and recommend a next step. Most teams run that cycle monthly or quarterly.

How is FP&A different from accounting?

Accounting produces the auditable actuals for a period that has closed, and FP&A uses those same actuals to plan, forecast, and advise leadership. Problems start when the two functions work from different versions of the numbers.

Is FP&A the same as EPM?

No. FP&A is the planning and analysis process, and the team that runs it. EPM is the wider management layer that also covers close, consolidation, and reporting.