BizBlocz
Finance Financial Planning & Budgeting FA01
Operations reference

Finance: Financial Planning & Budgeting

You own this process. What the work is and where its difficulty sits — then how much better it could run, who can run it, where AI fits, and how to choose.

The short answer

8-step finance work whose binding step is target vs bottom-up reconcile — the part you can’t fully automate away. Best-fit AI is ML / Predictive (~45%); best-in-class teams reach 61% cfos adopted fp&a software (2024).

Tasks
8
The bottleneck
target vs bottom-up reconcile
Improvement potential
61% · CFOs adopted FP&A software (2024)
Best-fit AI
ML / Predictive · 45%
01
Section 01 / 05
Overview · understand the work

What the work actually is

Financial planning and budgeting builds and maintains the company plan: it defines the plan structure (entities, accounts, periods, scenarios), collects inputs from business owners with workflow and documented assumptions, models revenue, headcount, opex, and capex with driver-based logic, runs scenario analysis (best / worst / most-likely, what-if), applies AI-assisted time-series forecasting, consolidates the plan across entities reconciling top-down targets against the bottom-up build, approves and freezes the baseline with an audit trail, and rolls forward to forecasts on a continuous re-forecasting cadence.

Inputs · documents in
GL actuals / ERP data extractPrior-year actuals & prior budgetHeadcount / HRIS roster (fully-loaded cost)Sales pipeline / CRM & operational drivers
Outputs · documents out
Annual budget / master budget (3-statement)Board deck / plan packageVariance analysis report (budget vs actual)Rolling forecast / reforecast
Volume
moderate
Risk / control
high
Shape of the work
Mostly predicting · gated by judging

The 8 tasks — the nature of each, and the oversight it needs

Tag each task in plain terms — what kind of work it is and how hands-off it can run — before any mention of AI. The kind of work is what later decides which tool, if any, fits.

Naturerule-basedreadingpredictingjudgingpeople / hands-on
01
Define plan structure (entities, accounts, time periods, scenarios)
defining plan structureexceptions
02
Collect inputs from business owners with workflow + assumptions documentation
collecting business inputsexceptions
03
Model revenue, headcount, opex, capex with driver-based logic
driver-based modelingunattended
04
Apply scenario analysis (best/worst/most-likely, what-if)
scenario analysisunattended
05
Apply AI-assisted forecasting (time-series, anomaly surfacing)
AI-assisted forecastingunattended
06
Consolidate plan across entities with target vs bottom-up reconciliationthe bottleneck
target vs bottom-up reconcileapproves
07
Approve and freeze baseline plan with audit trail
approving & freezing baselineapproves
08
Roll forward to forecasts with continuous re-forecasting cadence
rolling re-forecastunattended

A prediction-and-narrative process. Most of the build is forecasting — projecting revenue, headcount, and cost from drivers is a prediction problem — and a large share of the output is language: variance commentary, board narrative, and assumptions writeups. The binding step is the reconciliation: closing the gap between executive top-down targets and the bottom-up build is a negotiation and a judgment, not a calculation, and it is where the plan is actually committed. AI forecasts and drafts; the target-vs-bottom-up call and the freeze stay with FP&A leadership and the executive team.

The budget sets everyone's targets and the board's expectations — the target-vs-bottom-up reconciliation and the baseline freeze are owned by FP&A leadership and the executive team; AI forecasts and drafts, a person commits the number.

02
Section 02 / 05
Improvement potential · how much better it could run

How much better this process can run

The question isn’t only “is there savings” — it’s can I run this better: cheaper, faster, higher quality, better service? Here’s what best-in-class looks like, and how teams get there. (How much of it AI specifically drives — and how proven that is — is Section 04.)

Best-in-class · what “better” looks like
61%
CFOs adopted FP&A software (2024)
CFO Dive
3.2x
Adoption jump vs 2023
CFO Dive
57%
Faster forecasts (World Class)
Hackett 2025
56%
Call FP&A tech extremely important
CFO Dive
How best-in-class teams get there

Process discipline first, then automation — AI is one slice of the second column, not the whole answer.

Process & standardization
  • Driver-based plan structure & assumptions
  • Top-down target vs bottom-up governance
  • Baseline freeze & audit trail
  • Rolling re-forecast cadence
Automation & AI
  • ML driver-based & time-series forecasting
  • GenAI variance & board narrative drafting
  • Automated multi-entity plan consolidation
  • Scenario & what-if modeling
Planning tooling is being adopted fast: 61% of CFOs had implemented FP&A software by 2024, up from 19% in 2023, and 56% call FP&A technology "extremely important" (CFO Dive / CFO.com, independent editorial). The value shows up in speed and cost: Digital World Class finance organizations deliver forecasts 57% faster and spend materially less on planning and forecasting than typical peers (The Hackett Group, 2025 — a finance-function-wide benchmark, not FP&A-only). Gartner's 2025 Magic Quadrant for Financial Planning Software names Anaplan, Board, SAP, Oracle, Workday, and Jedox as Leaders (vendor-published recaps of a paywalled report).
03
Section 03 / 05
Executor · who can run it

Your levers — five ways to run this work

“Who runs the work” is its own question, separate from AI. AI shows up across these options — sometimes heavily, sometimes not at all. Vendor-neutral; the real options mapped to FA01.

Lever 01
Internal staff
Your own team runs it — the status quo.
AI: optional copilotdata: in-house
Your people, on your ERP, optionally AI-assisted.
Best when volume is low, formats vary wildly, or you need full control and a person accountable on every step.
Lever 02
ERP / platform
Your system of record runs it natively.
AI: some nativedata: vendor-cloud
Workday
Best when you're already on SAP/Oracle and want least integration — data never leaves the ERP.
Lever 03
Specialized SaaS
Buy a best-of-breed product; run it in-house.
AI: usually coredata: vendor-cloud
OneStream · Wolters Kluwer · Anaplan · Pigment · Vena Solutions · Cube · Datarails · Mosaic · Jirav
Best when you want capability your ERP lacks and will run another system; data processed in the vendor cloud.
Lever 04
AI agents
Autonomous AI runs the pipeline; you handle exceptions.
AI: it IS the executorcross-cuts the delivery models
Cube · Accenture · Genpact · WNS
Best when volume is high and formats are stable — you want touchless and only manage exceptions.
Lever 05
BPO / managed service
Hand the whole process to a partner.
AI: people + toolingdata: service-mediated
EXL Service · Accenture · Genpact · WNS
Best when you want an outcome and an SLA, not a tool to operate — partner works on your ERP, data stays with you.
Note on AI agents: they aren’t bought separately — you get them through a delivery model (your ERP, a SaaS product, or the BPO). Listed on their own because “should an agent run this autonomously?” is a distinct decision (Section 05), not because it’s a separate kind of vendor.
04
Section 04 / 05
AI · where it fits this work

Match a solution to each kind of work

Recall the tasks and their nature from Section 01. AI is one lever, not the whole story — the mix below is simply the result of matching the right kind of solution to each kind of work, weighted by where the work concentrates.

Nature of the work → the solution that fits
Read a document you didn’t designDocument AI
Deterministic routing, validation, postingAgentic / RPA
Anomaly detection & predictionML / Predictive
Draft, summarize, correspondGenerative AI
Answer questions in natural languageNLP / Conversational
See / digitize images & scansComputer Vision
The AI mix · weighted by where the work concentrates
45%
ML / Predictive leads the mix — matched to where this work concentrates and to its binding step.
ML 45%
Generative 25%
Agentic 15%
NLP 10%
ML / Predictive45%
Generative AI25%
Agentic AI / RPA15%
NLP / Conversational10%
Document AI5%

ML/Predictive leads (45%) because planning is fundamentally driver-based forecasting — projecting revenue, headcount, and cost from drivers is prediction (time-series and regression). Generative AI is unusually high (25%) because a large part of the FP&A deliverable is language: variance commentary, board-deck narrative, and assumptions writeups are generation work. Agentic/RPA (15%) orchestrates data collection and consolidation; NLP (10%) supports plan query and search; Document AI (5%) ingests submissions. No Computer Vision.

AI target value
61% — AI the dominant lever toward Section 02’s targets
AI’s contribution toward the best-in-class targets · personalized in the assessment
Medium
evidence
The grade is for the AI value/results, not the mix (which is directional). AI target value: ~35-55%, with ML the dominant lever for driver-based forecasting and GenAI strong for narrative. Confidence: Medium — planning AI is maturing fast (61% CFO adoption in 2024), but the target-vs-bottom-up reconciliation and the executive freeze stay human. Sources: CFO Dive / CFO.com, The Hackett Group (2025), Gartner MQ Financial Planning 2025, AFP / BPM Partners.See your number →
05
Section 05 / 05
How to choose · which lever fits you

Matching the approach to your situation

The right lever fits your volume, variability, control needs, and appetite to operate a system. Start here.

If your situation is…
Lean toward
High, stable volume; you want touchless
AI agentvia your ERP or a SaaS platform — runs itself, you handle exceptions
Formats vary widely, exceptions frequent, or a person must stay accountable
Copilotyour team, AI-assisted — the human still presses enter
Already standardized on SAP/Oracle; data must stay in the ERP
ERP-embeddedleast integration, platform-resident data
Need capability your ERP lacks; willing to run another system
Specialized SaaSbest-of-breed; data processed in vendor cloud
You want an outcome & SLA, not a tool to operate
BPO / managed serviceoffload the function; partner works on your ERP

The autonomy question: agent or copilot?

Whichever delivery model you pick, one choice cuts across them — who presses enter.

It acts

AI agent

Runs the steps end-to-end, completes the clean cases on its own, and routes only the exceptions to a person.

Best: high volume, stable inputs, a clear accountability surface.
vs
It assists

AI copilot

Sits beside the person and speeds up each step; the human acts on every decision.

Best: high variability, frequent exceptions, or a need for a person in the loop.

What to evaluate — whichever you choose

  • Accuracy on your own inputsvendor benchmarks are on clean data; test your messiest cases.
  • Straight-through / touchless ratethe real efficiency number, not “AI-powered.”
  • Exception-handling experiencemost of your team's time goes here, not the happy path.
  • ERP write-back & integration depthdoes it post cleanly to your system of record?
  • Data residencydoes data leave your environment, and is that acceptable to compliance?
  • The accountability surfacewhat happens, and who owns it, when the model is confidently wrong?
Related blocks

See every lever across your processes

Run your portfolio through the assessment — work profile, improvement potential, confidence, and executor options across all your blocks, scored against 127 enterprise subprocesses.

Open the AI Value Assessment →