Step-Down Method

The step-down method (also called the sequential allocation method) redistributes service-department costs to other departments in a descending order, recognizing that some support functions serve other support functions. A company allocates the most comprehensive service department’s costs first, then moves down to less comprehensive ones, until all overhead reaches production departments. Unlike the direct method, which ignores inter-departmental services, SYD acknowledges that the payroll department’s work benefits not just production but also the maintenance department.

The sequence problem

The defining challenge in step-down is determining which service department’s costs to allocate first. A manufacturing plant with a payroll department, maintenance department, and two production lines must choose: does payroll go down first, or maintenance?

This choice matters. If payroll costs are allocated first, the maintenance department—which also receives payroll services—is charged a portion of those costs before maintenance’s own costs are allocated to production. If maintenance goes first, payroll receives none of maintenance’s benefit allocation, only the primary allocation of payroll’s own direct costs.

The standard practice is to allocate the service department that serves the most other departments (or the most comprehensive one) first, then step down to narrower departments. This logic: the broadest service should bear its own costs, plus appropriate reallocation from narrower support functions, before production departments bear anything. It’s arbitrary, but systematic.

A worked example

A factory has four departments: payroll (support), maintenance (support), assembly (production), and finishing (production). In a given period:

• Payroll direct costs: £100,000
• Maintenance direct costs: £80,000
• Assembly direct overhead: £200,000
• Finishing direct overhead: £150,000

Payroll services are allocated by headcount: 5% to maintenance, 50% to assembly, 45% to finishing. Maintenance services are allocated by machine hours: 60% to assembly, 40% to finishing.

Step 1: Allocate payroll (the most comprehensive, serving both other support and production).

• Maintenance gets: £100,000 × 5% = £5,000
• Assembly gets: £100,000 × 50% = £50,000
• Finishing gets: £100,000 × 45% = £45,000

Step 2: Allocate maintenance (now including the £5,000 from payroll).

• Total maintenance cost: £80,000 + £5,000 = £85,000
• Assembly gets: £85,000 × 60% = £51,000
• Finishing gets: £85,000 × 40% = £34,000

Final result:

• Assembly overhead: £200,000 + £50,000 + £51,000 = £301,000
• Finishing overhead: £150,000 + £45,000 + £34,000 = £229,000

Production departments bear all support costs, and the sequence has been resolved in one direction only: payroll → maintenance → production.

Why the sequence biases results

Notice that if maintenance were allocated before payroll, the payroll department would receive none of maintenance’s cost allocation. This means maintenance’s view of payroll labour would be ignored, understating payroll’s true service value. Conversely, payroll’s view of maintenance would still be captured (since payroll goes last and sees all prior allocations). The sequence advantage tilts toward whichever department is allocated last.

To minimize this bias, practitioners typically identify the service department with the broadest scope—one that serves other support functions extensively—and allocate it first. Departments with more narrow scopes go down the list. The result is not perfect, but it is defensible and reproducible.

Step-down versus direct and reciprocal

The direct method skips this problem entirely by allocating service-department costs straight to production only, ignoring inter-departmental services altogether. It is simple and free of sequence bias but economically inaccurate when support departments meaningfully serve each other.

The reciprocal method captures all mutual services by solving simultaneous equations. It is the most accurate but also computationally complex and less transparent. Modern accounting systems handle the math easily, but step-down remains popular because its sequence logic is intuitive and explainable to non-accountants.

Step-down is the practical middle ground. It acknowledges that service departments serve each other (more realistic than direct), uses a sequential order that can be documented and defended (simpler than simultaneous equations), and produces results consistent across periods if the sequence is held constant.

Common pitfalls in application

Re-allocation error: Some practitioners mistakenly “re-allocate” to departments that have already been stepped down. Once payroll costs are allocated, payroll should not receive further allocations from lower departments. The step is one-way.

Sequence inconsistency: Changing the sequence year to year makes cost comparisons across periods unreliable. Once a sequence is chosen, it should be locked in—documented in the accounting policy—and changed only with auditor approval and clear disclosure.

Forgetting non-reciprocal flows: Step-down assumes that if payroll serves maintenance, maintenance does not meaningfully serve payroll back. If both are true (truly reciprocal), step-down is only an approximation. In such cases, reciprocal allocation is theoretically superior.

Regulatory and practical context

Under Generally Accepted Accounting Principles (GAAP), step-down is an accepted method for allocating overhead to inventory and cost of goods sold, provided the allocation basis is reasonable and applied consistently. Financial statement auditors evaluate both the method chosen and the consistency of its application.

Many regulated industries (utilities, telecommunications, insurance) use step-down in rate-setting, since regulators favour methods that are defensible, transparent, and not subject to simultaneous-equation complexity. It balances accuracy with simplicity.

For management accounting, step-down offers a middle-ground insight: it reveals which service departments depend on others, highlights bottlenecks in support services, and can inform decisions about centralising or decentralising functions.

See also