What Each Role in Planning and Forecasting Knows, and Where the Gaps Bite

Budget holders know what they plan to spend and why. Planning analysts know the model and its assumptions. Accountants know what has actually posted and when. Treasury knows when cash will move. Trouble starts when each group treats its own view as complete, mostly around timing and unrecorded commitments.

Budget holders know the commitments nobody has booked

The department head carries a mental ledger. It holds the contractor who agreed to start next quarter, the software renewal that will arrive with a price increase, and the hire who accepted verbally but has no start date in the system. None of this exists in the general ledger yet. Some of it never reaches a purchase order until the invoice lands.

This is the most valuable knowledge in the process and the least visible. When a forecast misses, it is often because the person who knew about the commitment was never asked in a form that captured it.

Budget holders also know which lines they padded and which they cut too thin to survive. They rarely volunteer that.

Planning analysts know the assumptions, not always the mechanics

The analyst understands why the model says what it says. Growth drivers, headcount phasing, allocation keys: these live in their spreadsheets and their heads. They know which figures came from a conversation and which came from a system.

What they often lack is a clear picture of how costs actually hit the books. An analyst may phase a cost evenly across months when accounting recognises it on delivery. The budget looks right in total and wrong in every single month, which wrecks variance analysis before anyone has started it.

Accounting knows what posted, and what it means

The controller's team knows the difference between a real overspend and a timing artefact. They know an accrual was reversed, a cost was reclassified, or revenue was recognised for work that is earned but not yet billed. They know which balances reconcile and which are being chased.

They are also the people who can confirm that budget reporting traces back to ledger balances. When planning reports and the ledger disagree, accounting usually knows why within minutes. Planning may spend days building an explanation that turns out to be a late journal.

The gap here runs the other way too. Accountants seldom see the forward plan in enough detail to anticipate what is coming, so they cannot warn anyone that a proposed phasing will never match how costs are recorded.

Treasury and payables know when money actually leaves

A budget is about when cost is incurred. Cash is about when it is paid. The payables team holds invoices approved but not yet due, and they build the payment runs. Treasury turns that into cash projections and watches for unusually large receipts or payments that need advance arrangement.

Planning tends to assume cash follows the budget with a neat lag. It does not. Supplier terms change, payment runs get held, and large customer receipts slip. Treasury knows this first, yet its view often sits apart from the forecast the executive team reads.

Where the gaps turn into problems

Variance commentary is where it shows most. An analyst writes that marketing is underspent. Accounting knows the agency invoice is sitting unapproved. The budget holder knows the campaign was delayed, not cancelled. Leadership reads the commentary and reallocates money that is already committed.

Reforecasting carries the same risk. If the forecast is rebuilt from ledger actuals plus an extrapolation, every unbooked commitment drops out. The number looks better than reality until the invoices arrive together.

Policy causes quieter damage. Budget policies are usually written by finance and read by almost nobody outside it. Approval thresholds, carry forward rules and transfer limits are understood differently in each department. Some managers spend early because they believe unspent money is lost. Others hoard because they think transfers need board approval when they do not.

Revenue has its own version. Sales leaders know which deals are genuinely closing. Accounting knows what can be recognised. The forecast sits between two definitions of the same word.

Questions to ask the people who run it

Written procedure and daily practice drift apart. These questions tend to surface the difference.

• Which commitments does each budget holder track outside the system, and where do they keep that list?
• How does the analyst decide monthly phasing, and has anyone in accounting checked it against how those costs are actually recognised?
• When a variance appears, who is asked first, and who actually knows the answer?
• Which accruals or reclassifications are routinely posted after planning has already pulled the actuals?
• What does payables hold back from a payment run, and does treasury's projection reflect it?
• Which budget policies do department heads believe exist, and do those match the written ones?
• When the forecast was last badly wrong, what did someone know beforehand that never reached the model?
• Who reconciles the planning report to the ledger, and what happens when they do not agree?

The answers usually point to a handful of informal conversations that hold the process together. Any redesign that removes those conversations without replacing them will make the forecast less accurate, however much cleaner the workflow looks.

APQC's Process Classification Framework® (PCF) is an open standard developed by APQC, a nonprofit that promotes benchmarking and best practices worldwide. To download the full PCF or to view definitions and measures, please visit www.apqc.org/pcf.