Blog · Territory, capacity and quota planning · Finance and FP&A teams
An FP&A operating model assigns ownership of planning inputs, checks, analysis and decisions. Build a monthly review from business-unit submissions and actuals, with spreadsheet formulas and a reconciliation that proves the result.
An FP&A operating model assigns responsibility for the inputs, checks, explanations and decisions in the planning cycle. Start with the monthly review the business needs, then work backward to the files and handoffs that make it reliable. A team chart helps only when it makes those responsibilities clear.
Suppose a US distributor reviews September revenue and operating costs by business unit. The finance leader needs to decide whether a profit shortfall requires a spending change, a commercial action or a correction to the reporting inputs.
The general FP&A role covers planning and performance analysis. An operating model goes further: it says who must deliver which evidence, who can reject incomplete inputs, and who can approve a response.
Write the handoffs before selecting a reporting format:
| Handoff | Responsible person | Evidence passed forward | Recipient's acceptance check |
|---|---|---|---|
| Business assumptions | Business-unit leader | Approved plan with period and version | FP&A confirms common definitions |
| Accounting actuals | Controller | Ledger export and control totals | FP&A ties amounts to the controller's totals |
| Performance explanation | FP&A analyst | Variances, source rows and open questions | Budget owner confirms operational context |
| Operating response | Business leader | Decision, action owner and due date | Finance leader confirms authority and follow-up |
A small team may combine roles. Record that explicitly and arrange another person's review of material changes. Analysis does not itself authorize a ledger adjustment, a new hire or a spending commitment.
Use a common reporting period, currency, account grouping and approved plan version. Ask each unit to identify its submission owner and explain changes since the previous version. Keep an unresolved mapping visible rather than forcing it into an unrelated account.
Department-level assumption alignment belongs in collaborative FP&A. Here, the important handoff is acceptance: FP&A either accepts a complete submission or returns it with a specific reason and owner. The controller separately confirms when accounting actuals are ready for comparison.
For this example, the Inputs sheet has the following rows. Amounts are positive for both revenue and operating costs; the profit calculation subtracts costs. September is represented by the text value 2026-09, consistently across the sheet.
| Period | Unit | Line | Version | Amount (USD) | Source row ID |
|---|---|---|---|---|---|
| 2026-09 | East | Revenue | Plan | 600,000 | P1 |
| 2026-09 | East | Operating cost | Plan | 420,000 | P2 |
| 2026-09 | West | Revenue | Plan | 400,000 | P3 |
| 2026-09 | West | Operating cost | Plan | 300,000 | P4 |
| 2026-09 | East | Revenue | Actual | 570,000 | A1 |
| 2026-09 | East | Operating cost | Actual | 430,000 | A2 |
| 2026-09 | West | Revenue | Actual | 420,000 | A3 |
| 2026-09 | West | Operating cost | Actual | 295,000 | A4 |
These are already grouped finance rows. Preserve the detailed source references supporting each amount. For multiple entities, complete the required FP&A consolidation checks before treating a group total as ready.
On a separate summary sheet, put Unit in column A, Line in B, Plan in C and Actual in D. Put the selected period in J1. Enter this in C2, then copy across to D2 and down through row 5:
=SUMIFS(Inputs!$E$2:$E$9,Inputs!$A$2:$A$9,$J$1,Inputs!$B$2:$B$9,$A2,Inputs!$C$2:$C$9,$B2,Inputs!$D$2:$D$9,C$1)
The version heading changes as the formula moves across. Microsoft's SUMIFS documentation describes summing values that meet multiple criteria. Matching period, unit, line and version prevents an unfiltered total from looking like a valid comparison.
In E2 calculate actual minus plan. In F2 convert that variance to its effect on profit:
=D2-C2
=IF(B2="Revenue",E2,-E2)
The second formula applies only to this example's two line types. Do not apply its cost treatment to every nonrevenue account in a full statement.
| Unit | Line | Plan (USD) | Actual (USD) | Variance (USD) | Profit effect (USD) |
|---|---|---|---|---|---|
| East | Revenue | 600,000 | 570,000 | -30,000 | -30,000 |
| East | Operating cost | 420,000 | 430,000 | 10,000 | -10,000 |
| West | Revenue | 400,000 | 420,000 | 20,000 | 20,000 |
| West | Operating cost | 300,000 | 295,000 | -5,000 | 5,000 |
All dollar figures are exact; no rounding is needed.
The control totals follow directly from those rows:
| Control | Plan (USD) | Actual (USD) | Actual minus plan (USD) |
|---|---|---|---|
| Revenue | 1,000,000 | 990,000 | -10,000 |
| Operating cost | 720,000 | 725,000 | 5,000 |
| Operating profit | 280,000 | 265,000 | -15,000 |
Calculate plan operating profit from summary rows 2 through 5:
=SUMIF(B2:B5,"Revenue",C2:C5)-SUMIF(B2:B5,"Operating cost",C2:C5)
Use column D instead of C for actual profit. The proof is that the profit effects sum to the change in profit: -30,000 - 10,000 + 20,000 + 5,000 = -15,000, equal to 265,000 - 280,000.
Check repeated source rows on Inputs, using period, version and source ID together:
=COUNTIFS($A$2:$A$9,A2,$D$2:$D$9,D2,$F$2:$F$9,F2)
Each displayed row returns 1. A result above 1 requires investigation before accepting the file. Microsoft documents COUNTIFS as counting rows where all supplied criteria match. Covirage is not affiliated with Microsoft.
FP&A should ask East's owner for evidence behind the revenue shortfall and additional cost. The leader then decides what action is justified. West's favorable results deserve a durability check before anyone assumes they will offset East next month.
Record the explanation, decision, action owner, due date and evidence to revisit. Keep a disputed explanation open. FP&A goals can define the intended outcome, but the monthly record proves whether the assigned action happened.
Bring your business-unit plans and actuals as a file or Google Sheet; Covirage maps the columns, and its tools compute and check the comparisons. The external AI model explains the results with every figure traced to its rows, while your team retains responsibility for approvals and decisions. Create a free Covirage account and bring a sample of your own data.
See Covirage for finance teams for the supporting finance workflow.
The finance leader should own the overall process and resolve responsibility gaps. Controllers own the integrity of accounting actuals, budget owners own their assumptions, and FP&A owns consistent comparison and explanation. Business leaders retain authority for operating decisions.
Either arrangement can work if definitions and handoffs are explicit. A central team can maintain common reporting rules while finance partners work with individual units. Choose responsibilities around business complexity and review needs, then test whether submissions reconcile without repeated clarification.
Include the reporting period, approved plan version, actuals cutoff, account mapping, source references and unresolved exceptions. Add a reconciled variance table and an action record. Each proposed action needs a decision owner, a due date and evidence required for the next review.