Blog · Territory, capacity and quota planning · Finance and FP&A teams
Collaborative FP&A gives departments common assumptions and a consistent submission process. Reconcile selected versions, identify assumption differences and prove the company rollup before finance takes the plan to review.
Collaborative FP&A aligns department plans before finance compares them or rolls them into a company total. Give budget owners common definitions and assumptions, select one submission version for each required scope, and reconcile its reported total to the underlying drivers. The useful outcome is a checked plan with visible exceptions and clear approval responsibility.
Start with the ledger and planning files people already use. Require a department ID, fiscal period, version, selection status, account or planning line, amount and assumption owner. Keep the company's currency and sign convention in the instructions so that a positive expense means the same thing in every file.
The process sits within the broader cycle described in what FP&A does. Its specific job is to make separately prepared submissions comparable. It does not require every owner to use the same worksheet design, provided the required fields and definitions arrive intact.
Finance owns the common assumption register and reconciliation. Department leaders own demand, staffing and spending inputs. HR or procurement may supply supporting schedules; authorized leaders approve exceptions and the final plan. Keep those responsibilities explicit when a proposed adjustment crosses departmental boundaries.
For each shared assumption, record its value, unit, effective date, owner and evidence. A wage adjustment applying for a full year differs from one starting partway through the year. Both may be reasonable, but they cannot silently share the same label.
This invented US company is collecting FY2027 annual budgets. Its intake register has one summary record per department and version. Enter these rows on a Raw sheet in A:F, with headers in row 1:
| Department | Period | Version | Selection | Owner role | Submitted annual cost (USD) |
|---|---|---|---|---|---|
| Sales | FY2027 | v2 | Current | Sales director | 1,040,000 |
| Operations | FY2027 | v1 | Superseded | Operations director | 761,600 |
| Operations | FY2027 | v2 | Current | Operations director | 768,800 |
| Finance | FY2027 | v2 | Current | Finance director | 252,200 |
Summing all four amounts returns $2,822,600. That is an intake total, not a company budget, because it includes the superseded Operations submission. Selecting only Current records returns 1,040,000 + 768,800 + 252,200 = $2,061,000.
On a separate Inputs sheet, put department names in A2:A4 and FY2027 in L2. Check the selected summary count for each department:
=COUNTIFS(Raw!$A$2:$A$5,$A2,Raw!$B$2:$B$5,$L$2,Raw!$D$2:$D$5,"Current")
The expected result is one for each department. Microsoft documents COUNTIFS as counting records that meet all supplied criteria. A result above one requires investigation; zero means the expected submission is missing. Detailed account exports need an expanded key, because multiple expense lines within a department are legitimate.
Pull the selected annual amount into Inputs I2 and fill down:
=SUMIFS(Raw!$F$2:$F$5,Raw!$A$2:$A$5,$A2,Raw!$B$2:$B$5,$L$2,Raw!$D$2:$D$5,"Current")
Microsoft's SUMIFS guidance explains the matching-criteria sum and the need for equally sized ranges. The formula selects a version; it does not prove that the version's assumptions are consistent. Covirage is not affiliated with Microsoft.
The selected files contain these inputs. FTE means average full-year equivalent staffing, not a closing headcount. The example covers base wages and the displayed other costs only; benefits and payroll taxes would require additional lines in a complete budget.
Enter department, FTE, annual base pay, submitted raise and other annual costs in Inputs A:E:
| Department | Average FTE | Base pay per FTE (USD) | Submitted raise | Other annual costs (USD) | Rebuilt submission (USD) |
|---|---|---|---|---|---|
| Sales | 10 | 100,000 | 3% | 10,000 | 1,040,000 |
| Operations | 8 | 90,000 | 4% | 20,000 | 768,800 |
| Finance | 2 | 120,000 | 3% | 5,000 | 252,200 |
| Total | 20 | 35,000 | 2,061,000 |
Calculate the rebuilt submission in F2, then compare it with the selected imported amount in I2:
=B2*C2*(1+D2)+E2
=F2-I2
Fill both formulas down. Each difference is zero, and the rebuilt total equals the selected intake total. This proves the submitted arithmetic and selection agree. It does not yet settle the raise assumption.
The common planning raise is 3%, effective for the full year. Operations used 4%. Put the common rate in J2 and calculate a comparison candidate in G2, with the change in H2:
=B2*C2*(1+$J$2)+E2
=G2-F2
| Department | Selected submission (USD) | Candidate at common assumption (USD) | Candidate change (USD) |
|---|---|---|---|
| Sales | 1,040,000 | 1,040,000 | 0 |
| Operations | 768,800 | 761,600 | -7,200 |
| Finance | 252,200 | 252,200 | 0 |
| Total | 2,061,000 | 2,053,800 | -7,200 |
The Operations difference is 8 × 90,000 × (3% - 4%) = -$7,200. All displayed dollar figures are exact; no rounding is needed. The candidate check is 2,061,000 - 7,200 = 2,053,800, which must also equal the sum of G2:G4.
Ask the Operations owner whether the exception reflects a documented staffing need or an input mistake. Record the response, approver and chosen treatment. The comparison candidate becomes an accepted plan only after that decision; a calculation cannot supply approval.
Use FP&A modeling for the wider driver structure. Once submissions are accepted, FP&A consolidation covers the next rollup, and FP&A goals connects the agreed plan with the questions reviewed afterward.
Give finance the selected files, assumption exceptions, arithmetic checks and unresolved decisions together. The review pack should distinguish a missing submission from a complete submission with a legitimate exception. Those conditions need different responses.
After approval, preserve the accepted version and compare actuals against that specific baseline. A later forecast should receive its own version rather than replacing the original budget. Owners can then explain operating changes without rewriting the target they were measured against.
Bring a sample of your own department submissions and common assumptions as files or a Google Sheet. Covirage maps the columns; its tools compute and check the figures, and the external AI model explains differences with every figure traced to its rows. Create a free Covirage account and bring a sample of your own planning export.
See FP&A reporting for the supporting finance workflow.
Include finance, the owners of departmental budgets and the leaders authorized to approve decisions. Add people who own material assumptions, such as hiring dates or purchase commitments. Participation should follow responsibility for an input or decision, rather than access to every planning discussion.
Give each submission a department, period, version and selection status. Preserve earlier versions for comparison, but identify exactly which version enters the rollup. Check the expected count of selected submissions before summing amounts, and reject an ambiguous selection instead of guessing.
Finance should show the difference and its financial effect, then route the exception to the appropriate owner. A common assumption is a comparison baseline. Changing the approved budget requires the company's approval process, even when the proposed correction is mathematically straightforward.
Collaborative FP&A coordinates the inputs and explanations supplied by budget owners. Consolidation combines entities or units under consistent reporting rules. A reconciled departmental submission helps the later rollup, but it does not replace entity accounting, eliminations or formal reporting requirements.