Top-down vs bottom-up budgeting: reconcile the two plans

To budget top down and bottom up, compare the company spending limit with the cost of department operating plans. Top-down budgeting asks what the company can fund; bottom-up budgeting asks what the agreed work requires. The practical job is to reconcile those answers into one approved budget with supported assumptions.

What each approach establishes

Neither method is a performance ratio. Each establishes a planned amount, but its starting point and evidence differ. OpenStax's budgeting guidance distinguishes management targets passed downward from department estimates passed upward, and describes a combination of both.

The detailed bottom-up budgeting process covers building submissions; the top-down budgeting process covers deriving the central envelope. Here the focus is the gap between their outputs.

Put both versions on the same rows

Start with the company's department list and chart of accounts. Each row needs a period, department, account, cost type, version and amount. Keep quantities and rates for driver-based rows, plus an assumption owner and a source reference.

Confirm the scope before subtracting versions. An allocation that excludes centrally funded benefits cannot be compared directly with a department request that includes them. An annual allowance cannot be compared with a quarterly submission. A payroll expense plan cannot be reconciled to cash payments without identifying the timing differences.

The business budget template supplies a common planning layout. Preserve the central allocation and the department request as separate versions within that layout, so a later approval does not erase the original difference.

Work the same department costs both ways

An illustrative US software-services company sets a quarterly departmental operating-cost limit of $1,000,000. Leadership initially allocates it using explicit planning weights: customer success gets 50%, sales 30% and finance 20%. These weights are planning inputs, not an estimate of what the work should cost.

At the same time, managers prepare these operating requests. Loaded payroll rates include the employment costs covered by the company's planning policy.

Each request is quantity × rate. Summing the rows by department produces the right-hand amounts below. Applying the weights to the same company limit produces the central allocations.

The methods answer different questions about the same work. Customer success has an allowance of $500,000 but a supported request of $528,000. Finance requests less than its allowance. Company-wide, the requests exceed the limit by $54,000.

For a summary with weight in B, central limit in C and department request in D, put the company limit in H1. Enter this in C2:

=$H$1*B2

Enter the request-minus-limit calculation in E2:

=D2-C2

Fill down for each department. The gap check must return zero:

=SUM(E2:E4)-(SUM(D2:D4)-SUM(C2:C4))

All dollar amounts in this example are exact whole dollars. No rounded allocation percentages are used in the calculations.

Resolve the gap through named operating changes

Leadership keeps the company limit. Procurement confirms a support-service rate of $8 per ticket instead of $12 for the same scope. Sales agrees to run three campaigns instead of four. These are illustrative decisions; they require evidence and approval in a real budget.

The revised bottom-up total is $1,054,000 − $54,000 = $1,000,000. It meets the company limit while changing the initial departmental allocation:

The approved customer-success amount is $432,000 + 8,000 × $8 = $496,000. Sales is $240,000 + 3 × $22,000 = $306,000. Finance remains $171,000 + $27,000 = $198,000.

Sales must also revisit the operating outcome promised by its campaign plan. A lower campaign count cannot retain its original demand commitment without explanation. The sales projection guide covers checking the assumptions behind that revenue expectation.

Choose the process that fits the decision

Use a central limit first when the binding decision is affordability, a profit requirement or a strategic spending shift. Require managers to explain feasibility before final approval. An allocation that adds up can still be impossible to execute.

Start with department drivers when staffing, contracts or service workload determine the resource requirement. Require consistent assumptions and consolidation checks before treating the combined request as a company plan.

Use both when those needs coexist. Freeze the approved amounts and assumptions, then compare actuals with that version. For variable spending, OpenStax explains why a flexible budget uses actual activity to make the cost comparison meaningful. Keep an activity-adjusted explanation separate from a change to the approved budget.

Where the comparison goes wrong

• Identical totals are treated as agreement. Department allocations can differ even when both versions meet the company limit. Reconcile each owner and account.
• The gap is divided evenly. Equal cuts can remove required capacity while leaving lower-priority work funded. Change named assumptions instead.
• A lower cost keeps an unchanged commitment. Record the service, staffing or revenue consequence beside the approved change.
• Versions use different scope. Align periods, shared charges and cost definitions before calculating differences.
• A request becomes the reporting baseline. Actual results should be compared with the approved version, with the original submission retained for reference.

Reconcile your budget versions in Covirage

Bring a file containing the central allocations, department submissions and approved amounts, with the matching account and period fields. Covirage maps the columns; its tools compute and check the differences, and the external AI model explains the result with every figure traced to its rows. Create a free Covirage account and bring a sample of your own data; creating an account takes about a minute.

See the supporting FP&A reporting page.