The Step-Down Method, Explained: Allocate Service Department Costs in the Right Sequence

Your HR department recruits the maintenance crew. Your maintenance crew fixes the HR office's air conditioner. So when month-end comes and you need to push both departments' costs into the production departments that actually earn revenue — whose costs move first? Get the order wrong and the answer is thousands of dollars of overhead landing on the wrong product line, quietly distorting every margin and make-or-buy decision downstream.

The step-down method (also called the step allocation or sequential method) is cost accounting's practical answer to that puzzle. It allocates service department costs one department at a time, in a ranked sequence, letting each department's costs flow forward to the departments below it — but never backward. This guide walks through how to rank your service departments, how to normalize the allocation base at each step, and when the simpler direct method or the more exact reciprocal method fits better.

Service Departments vs. Operating Departments: The Setup​

Every cost allocation starts by sorting departments into two buckets:

• Service (support) departments exist to serve other departments, not customers. HR, maintenance, IT, accounting, legal, and facilities are the usual suspects. Their costs are real — salaries, software, parts — but no product or customer invoice absorbs them directly.
• Operating (production) departments make or deliver what customers pay for: assembly, machining, packaging, consulting teams, hospital wards.

For product costing, pricing, and divisional performance reviews, all of the service costs must eventually land in the operating departments. Three methods do that job, and they differ in exactly one thing: how much of the service-to-service traffic they recognize.

The step-down method sits in the middle: more accurate than the direct method because it admits that service departments serve each other, far simpler than the reciprocal method because the flow only ever moves one way.

How the Step-Down Method Works​

The procedure has three moves: rank, allocate, and never look back.

1. Rank the service departments from most to least service provided to other service departments. The top-ranked department goes first.
2. Allocate the top department's full cost to every department below it — the remaining service departments plus all operating departments — using that department's own allocation base (headcount for HR, square footage for facilities, tickets resolved for IT).
3. Step down to the next department. Its allocable cost is its own direct cost plus whatever it received in earlier steps. Allocate that total to the departments still below it. Repeat until the last service department pushes everything it holds into the operating departments.

The iron rule: once a department has allocated its costs, it is closed. No later department ever allocates costs back to it. That one-way flow is what makes the method tractable — and it is also the method's main theoretical weakness, because in reality the maintenance crew really does fix HR's air conditioner after HR already "closed."

Step 1: Rank HR, Maintenance, IT — Who Goes First?​

Ranking is the decision that most affects your final numbers, so it deserves a rule rather than a gut feel. Textbooks and practitioners converge on one primary criterion:

Allocate first the service department that provides the largest share of its services to other service departments (measured by percentage of its output or cost consumed by them).

A common tie-breaker: if two departments serve other service departments in roughly equal proportions, rank the one with the larger total cost first, since its allocation moves more dollars and getting it right matters more.

Suppose a small manufacturer has three service departments:

IT goes first: 40% of what it does serves fellow service departments. Maintenance goes second (20%), and HR goes last (10%). Notice that the ranking follows the share of services to other service departments, not the raw dollar cost — though here IT happens to be biggest on both counts.

Why does this order minimize distortion? The step-down method ignores every behind-you arrow. Putting the department with the heaviest service-to-service traffic first means the largest mutual flows get recognized before anyone closes. Whatever gets ignored later is, by construction, the smallest traffic in the system.

Step 2: Allocate the First Department's Costs​

Each service department allocates on its own base — the driver that best tracks how its services get consumed. Typical pairings:

• HR → number of employees (or new hires) per department
• Maintenance → machine hours, work orders, or square footage serviced
• IT → devices supported, tickets resolved, or storage used
• Facilities / custodial → square footage occupied
• Accounting → transactions processed or labor hours

The first department's percentages are straightforward: divide each receiving department's base units by the total base units across all receivers (every other service department plus every operating department). Multiply the department's cost by each percentage, and those dollars move.

Step 3: Normalize the Base at Every Later Step​

Here is the step everyone gets wrong on the first try. When the second department allocates, one department — the first — is already closed and must be dropped from the base entirely. Its base units come out of the denominator, and the remaining percentages are recomputed (normalized) so they again sum to 100%.

Concretely: suppose Maintenance tracks usage in service hours — 200 hours for HR, 500 for Assembly, 300 for Packaging, 1,000 total. If HR already allocated and closed, HR's 200 hours leave the base. The allocation runs on the remaining 800 hours: Assembly gets 500 ÷ 800 = 62.5%, Packaging gets 300 ÷ 800 = 37.5%. If you forget to normalize and reuse the original 50%/30% split, 20% of Maintenance's cost — the HR slice — simply vanishes from the allocation. Your operating departments end up understated and the books don't foot.

Two accumulations happen at every step after the first, and both are easy to miss:

1. Accumulate incoming costs. The department's allocable total is its own direct cost plus everything allocated to it from departments above. Never allocate just the direct cost.
2. Normalize the base. Recompute every percentage over the still-open departments only.

Worked Example: HR and Maintenance Into Assembly and Packaging​

Let's run a complete two-service-department example so you can see the mechanics reconcile.

Setup. A furniture maker has service departments HR ($90,000) and Maintenance ($60,000), and operating departments Assembly and Packaging.

Usage data. HR serves Maintenance 10%, Assembly 60%, Packaging 30%. Maintenance logs 20% of its hours in HR areas, 50% in Assembly, 30% in Packaging.

Ranking. HR sends 10% of its services to another service department; Maintenance sends 20%. Maintenance ranks first.

Step 1 — Allocate Maintenance's $60,000. All departments are still open, so the original percentages apply:

Maintenance is now closed.

Step 2 — Allocate HR's accumulated $102,000 ($90,000 own cost + $12,000 received). HR is the last service department, so everything goes to operating departments — but HR's own base percentages (10/60/30) included the now-closed Maintenance. Normalize over Assembly and Packaging only: 60 + 30 = 90 base points, so Assembly gets 60 ÷ 90 = 66.67% and Packaging gets 30 ÷ 90 = 33.33%:

Check the footing. Total service cost was $90,000 + $60,000 = $150,000. Assembly received $30,000 + $68,000 = $98,000; Packaging received $18,000 + $34,000 = $52,000. And $98,000 + $52,000 = $150,000. Every dollar landed somewhere — the reconciliation that proves the allocation is complete.

Note what the method recognized and what it dropped. The Maintenance→HR flow (20% of Maintenance's hours) was recognized in full through the $12,000 slice, because it pointed down the ranking. The HR→Maintenance flow (10% of HR's services) was dropped — HR allocated after Maintenance had closed, so those dollars were normalized into Assembly and Packaging instead. The pattern always favors flows pointing down the ranking and drops flows pointing back up it, which is exactly why the ranking rule puts the heaviest mutual traffic at the top: whatever gets ignored is, by construction, the smallest backflow in the system.

When the Direct Method Fits Better​

The direct method skips service-to-service allocation entirely: each service department divides its cost among the operating departments only. Choose it when:

• Service departments barely serve each other. If HR recruits for production and Maintenance fixes production equipment, and neither meaningfully serves the other, the step-down refinement buys you almost nothing.
• Speed beats precision. The direct method needs one percentage set per service department, computed once. For a fast month-end close with immaterial support costs, that simplicity wins.
• Your audience won't trust the ranking. Step-down results shift with the sequence, and a manager whose division looks worse under one ranking will relitigate it every quarter. The direct method has no sequence to argue about.

The cost of that simplicity is accuracy: the direct method systematically understates operating departments that consume heavily through other service departments.

When the Reciprocal Method Fits Better​

The reciprocal method recognizes every mutual flow by solving simultaneous equations — each service department's total equals its direct cost plus its share of every other service department's total. Choose it when:

• Mutual services are large in both directions. A power plant that consumes water and a water plant that consumes power is the textbook case; neither direction is ignorable.
• Regulatory or contractual accuracy matters. Cost-plus government contracts, hospital cost reports, and utility rate cases sometimes effectively require (or reward) the full mutual treatment.
• You have the tooling. A spreadsheet solves two-department reciprocals with a 2×2 system; beyond that you want matrix functions or dedicated cost software. Without tooling, the reciprocal method is where month-end closes go to die.

For most small and mid-size businesses, the honest answer is that the step-down method is the sweet spot: it captures the big inter-service flows with arithmetic a reviewer can verify by hand.

Common Mistakes That Break the Allocation​

1. Allocating back to a closed department. The moment a department's costs are fully pushed out, it leaves the base. Sending it dollars later double-counts its cost.
2. Forgetting to accumulate incoming costs. The second department allocates own cost plus received cost. Allocating only its direct cost strands the received dollars in limbo.
3. Skipping base normalization. Reusing original percentages after a department closes leaks cost — the closed department's slice disappears and the totals won't foot. Always recompute over open departments.
4. Ranking by convenience instead of by service flow. Alphabetical order, department size alone, or "the way we've always done it" can put the heaviest mutual traffic last, maximizing exactly the distortion the method tries to minimize.
5. Stale allocation bases. Headcount, square footage, and machine hours drift every quarter. An allocation base from two reorganizations ago quietly mischarges every product line. Refresh the base readings on the same cadence as the allocation itself.

Tracking It in Your Books​

Whichever method you choose, the allocation is only as good as the cost pools feeding it. Each service department needs its own clean expense grouping — salaries, software, supplies — accumulated through the month so the month-end allocation starts from true totals rather than estimates. In a plain-text ledger that looks like dedicated accounts per service department:

2026-10-01 * "October HR salaries" "Payroll"
  Expenses:Overhead:Service:HR:Salaries  68000.00 USD
  Assets:Cash:Operating                -68000.00 USD
 
2026-10-01 * "October maintenance parts and labor" "Facilities"
  Expenses:Overhead:Service:Maintenance  60000.00 USD
  Assets:Cash:Operating                -60000.00 USD
 
2026-10-31 * "Step-down allocation: Maintenance to HR and production" "Month-end close"
  Expenses:Overhead:Service:HR           12000.00 USD
  Expenses:Overhead:Assembly             30000.00 USD
  Expenses:Overhead:Packaging            18000.00 USD
  Expenses:Overhead:Service:Maintenance -60000.00 USD

With the pools tracked this way, the allocation entries zero out each service account in ranking order, and the operating accounts carry fully loaded costs you can reconcile back to the trial balance. If you want a visual check on where the overhead landed, the Fava dashboard renders the resulting balances per cost center, and the technical docs cover ledger setup in more depth.

Your Next Month-End​

Pull last month's trial balance, list what each support department spent, and sketch the service flows between them as percentages. If one department clearly serves the others more than it is served — IT supporting everyone's systems is the classic — you already know your ranking, and a single spreadsheet pass will give you a step-down allocation before lunch. Get the sequence right, normalize every base, and foot the totals: those three habits are the whole method.