Bottom-up budgeting: process, example and tradeoffs

Bottom up budgeting builds the company plan from department estimates of the work to be done and the resources required. Finance combines those submissions, checks their assumptions and resolves overlaps before leadership approves spending. A detailed request becomes useful only when its totals reconcile and its operating commitments are clear.

What moves upward through the process

The submission should contain a calculation and an accountable owner. A payroll request needs staffed months and a cost per month. A service request needs workload and cost per unit. A fixed contract needs the applicable period and amount.

OpenStax describes bottom-up budgeting as department estimates moving upward after management communicates goals. It connects the approach with operating knowledge and participation. That does not mean every request becomes an approved budget.

For a cost submission, the basic calculation is:

Department budget = Sum of activity quantities × corresponding unit costs + separately identified fixed costs

Company departmental cost budget = Sum of department budgets − duplicated or internal charges

This example covers selected departmental costs. A full company plan also needs revenue, other expenses and cash requirements. The business budget template provides the broader schedule; keep the submission process focused on the assumptions each manager can support.

Start from records managers can recognize

Give every department the same submission columns: period, cost center, account, driver, quantity, unit, rate, amount, assumption owner and version. Add a source reference that identifies the payroll schedule, contract, invoice history or workload report behind each assumption.

Keep dated staffing information separate from a simple employee count. A role filled late in the quarter costs less in that quarter than a role filled at its start. Express that timing as staffed months before multiplying by a monthly cost.

Use the same treatment for shared costs. If finance budgets the company-wide contract, departments should identify their usage without submitting the full contract again. If departments receive allocations, mark those rows so consolidation does not count both the corporate charge and its departmental distribution.

OpenStax's operating-budget guidance connects sales assumptions with required production, materials and labor. Apply that dependency check to your own business: the workload assumed by the service team should agree with the demand assumed by sales.

A quarterly submission worked from its drivers

Consider an illustrative US field-service company preparing a quarterly departmental cost budget. Managers submit the quantities and rates below. Payroll rates include the employment costs included in this company's planning policy. Actual amounts are later taken from the general ledger for the same quarter and accounts.

Each submitted cost is quantity times rate. Sales payroll is 12 × $8,000 = $96,000; the facilities contract is 1 × $18,000 = $18,000. The fixed items use one applicable contract period rather than an invented workload driver.

If quantity is column B, rate is D and submitted cost is E, the first data-row formula is:

=B2*D2

Fill down through row 10. The submitted total is =SUM(E2:E10). Amounts are whole dollars; the percentage below is rounded to one decimal place.

Reconcile the company total before approving it

Summarize the same rows by department. The example assumes leadership accepts the submitted plan without adjustments, so the submission and approved budget are equal.

The checks are explicit:

• Department budgets sum to $453,600, the same as the detailed submission rows.
• Department actuals sum to $460,900, the ledger total for the defined accounts and quarter.
• Variances sum to $7,300, which also equals $460,900 − $453,600.

The company cost variance is $7,300 / $453,600 = 1.6% over budget. A positive value means higher expense throughout these tables.

If the submitted total exceeds the spending limit, keep both amounts visible. Ask which workload, rate or scope assumption must change. The top-down versus bottom-up comparison covers that negotiation in detail.

Explain the actual result using the original assumptions

The department view identifies the owner; the driver rows identify the question. Sales travel is $30,000 − $27,000 = $3,000 over plan. Service job support is $29,700 − $27,000 = $2,700 over plan. Those differences need different operational explanations from an audit engagement that finished below its allowance.

Suppose the service report shows 660 completed jobs, against the planned 600, and the support rate remained $45 per job. Expected support cost at actual workload is 660 × $45 = $29,700. The entire $2,700 difference comes from workload; actual cost equals the amount expected for that workload.

This is the purpose of a flexible-budget comparison described by OpenStax: evaluate variable cost at actual activity. Preserve the approved budget when doing this calculation. The budget-versus-forecast guide explains why an updated outlook needs its own identity.

The service manager owns the workload explanation. Finance checks the ledger tie and rate calculation. Leadership decides whether higher activity supports more resources, a pricing change or a service-process change.

Where bottom-up budgets go wrong

• Duplicate shared costs. A corporate contract appears in both the central file and department submissions. Assign its owner before consolidating.
• Unstated units. Seats, seat-months and quarterly licenses produce different amounts. Require a unit beside every quantity.
• Requests include hidden cushions. Ask managers to separate expected cost from a named contingency with a specific trigger.
• Different demand assumptions. Sales plans additional work while service staffing assumes unchanged volume. Reconcile the common operating driver before debating costs.
• A submission replaces the approved version. Retain the original request, approved adjustments and actuals so the variance analysis answers the right question.

Compare your department submissions in Covirage

Bring a department submission file and the matching actual-cost export, with periods, accounts and assumption references. Covirage maps the columns; its tools compute and check the figures, 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 how this work fits FP&A reporting.