The complete guide to predetermined overhead rate

Most teams treat the predetermined overhead rate like a New Year’s resolution: they calculate it once, pat themselves on the back, and promptly ignore it until the accountant flags an issue twelve months later.

That ‘set it and forget it’ mindset is exactly why your product cost data is losing its edge (even if you don’t realize it yet). The formula itself, in all likelihood, isn’t the problem. But when you allow the numbers to drift even slightly, they can compound over time and you’re left guessing why your budget looks different than your actuals. 

If you’re tired of the guesswork, this guide is for you. We’re going to walk through how to build a rate that’s actually defensible, scalable, and—most importantly—accurate enough to rely on all year.

If you want to know how to calculate the predetermined overhead rate, check out our article that explains the formula and gives some basic examples.

What’s the formula?

Here’s the predetermined overhead rate formula, for reference:

Estimated total manufacturing overhead cost ÷ allocation base = predetermined overhead rate

You set the rate before the accounting period begins, using a budgeted overhead amount and an estimated total for the activity you’re allocating. You then apply this rate to jobs or units as you produce them, well before you know the actual overhead cost. That’s the main idea.

The math is, thankfully, straightforward. 

The challenges present themselves in other parts of the process.

Picking a defensible allocation base

The allocation base, also known as the cost driver, is the activity you use to spread overhead. If you choose the wrong one, every product cost after that will carry the mistake.

Three bases cover most situations:

• Machine hours: best when production is automated and capital-intensive, where depreciation, power, and maintenance are the bulk of your manufacturing overhead.
• Direct labor cost: useful when overhead tracks roughly with payroll (this is common in assembly-heavy work and easy to pull from records you already keep).
• Direct labor hours: a middle ground when wage rates vary across workers but overhead follows time spent instead of dollars paid.

The key is to identify the cause of the indirect cost. If most of your overhead comes from machine depreciation and electricity, but you allocate by direct labor cost, a product that uses little labor but a lot of machines will be undercosted. You might think it has the best margin, but the math would disagree. The overhead allocation gave you the wrong picture.

This type of mistake is the biggest to watch out for. Teams often use direct labor cost because the payroll data is easy to find, not because it matches how overhead works in their plant. 

Choosing an allocation rate for convenience is a bad idea. Take some time to figure out where your total overhead cost comes from before you decide on a base.

One rate, or several?

Using a single plant-wide rate is the simplest approach. You have one pool of estimated overhead cost, one allocation base, and one number used everywhere. This works if your production process is pretty uniform and your departments use overhead in similar ways.

But departments usually do differ. For example, a finishing department with expensive CNC (Computer Numerical Control) equipment and a hand-packing department have very different costs. If you use one rate for both, you can end up overcharging the cheaper work or undercharging the more expensive work.

Departmental overhead rates solve this problem. 

You create a separate predetermined overhead rate for each department/cost pool, match each one to the correct cost driver, and apply them separately. Yes, having multiple rates takes more work to set up and maintain, but it pays off if you want accurate overhead numbers.

When activity-based costing earns its keep

Activity-based costing (ABC) takes the departmental approach even further. Instead of using one rate per department, you find the specific activities that use overhead, like machine setups, quality inspections, or processing purchase orders, and assign costs to each with its own driver. This way, a product that needs X setups and Y inspections gets charged for its fair share of those costs.

If your product mix varies a lot in complexity, activity-based costing is the most accurate method. It reveals the hidden costs of low-volume, high-touch SKUs that a simple plant-wide rate would miss.

The tradeoff, though, is that ABC is costly to set up and maintain. Every activity needs its own driver, each driver needs data, and you have to keep that data updated as your business changes. 

It’s difficult to keep this type of model up to date and accurate. A good set of departmental rates often gives you most of the accuracy with much less work. End of the day, choose the method you can keep up with, not just the one that looks best on paper.

Applied versus actual

Throughout the year, you apply overhead using your predetermined rate. By definition, applied overhead is just an estimate. Actual manufacturing overhead costs are what you actually spend. Generally, they won’t match exactly. The important thing is to see how big the difference is and decide what to do about it.

Walk a real number through it. Say you estimated $480,000 in total manufacturing overhead cost for the year and an allocation base of 24,000 machine hours:

• Predetermined overhead rate: $480,000 ÷ 24,000 = $20 per machine hour
• But you actually run 22,500 machine hours, so applied overhead is 22,500 × $20 = $450,000
• Your actual overhead cost comes in at $470,000

In this case, applied overhead ($450,000) is less than actual overhead ($470,000), so you underapplied overhead by $20,000. Simply put, you charged less overhead to your products than they used, so your product costs were too low all year. Your margins looked a bit better than they really were.

At the end of the period, you clear out that difference. Usually, you add the underapplied amount to cost of goods sold, which increases COGS and fixes the understatement. If the numbers are large or you have a lot of inventory, you would spread the difference across work in process, finished goods, and COGS instead. If applied overhead was higher than actual, you would have overapplied overhead, overstated your product cost, and then reduce COGS by the difference.

See the variance as a warning. A small difference means your estimates were good. A large or repeated difference means your budget, estimated units, or allocation base is off, and you need to adjust next year’s predetermined rate. Teams that reconcile every quarter rather than every year catch problems early. Teams that only calculate once and never review are relying on outdated assumptions.

Where the numbers come from

A predetermined overhead rate is only as reliable as the estimates you use to create it. If your estimate is bad, you’ll end up with a rate that looks right, but isn’t.

Your estimates for total units and production volume should be based on more than just last year’s numbers and a guess. Demand patterns, seasonality, and channel growth all affect the total, and getting it wrong can throw off your whole rate. 

This is where good forecasting is valuable. For example, sellers using Linnworks stock forecasting to project volume across channels get a much more accurate activity estimate than a manual spreadsheet can provide.

You need the same careful approach for overhead. You can’t allocate indirect costs accurately unless you can see them clearly at the SKU and channel level. SKU-level reporting in Linnworks helps operations teams separate true overhead from direct costs, which makes the difference between a solid allocation base and one based on guesses.

Run the reconciliation this quarter

Don’t wait until year-end. Check your applied overhead and actual overhead cost for the last quarter and compare them. If the difference is bigger than you expected, you’ve found next year’s correction early, and you have two quarters to adjust the rate before it affects more pricing decisions. For more details on overhead, see our breakdown of manufacturing overhead costs.

If you want cleaner volume estimates and SKU-level cost visibility to build your rate on, book a Linnworks demoand see how it fits into your overhead process.

FAQ

What is the predetermined overhead rate formula?

The predetermined overhead rate formula is: estimated total manufacturing overhead cost ÷ allocation base = predetermined overhead rate. You set the rate before the accounting period begins, using a budgeted overhead amount and an estimated total for the activity you’re allocating, then apply it to jobs or units as you produce them.

How do I choose the right allocation base?

Start by identifying what actually drives your indirect costs. Machine hours work best when production is automated and capital-intensive, where depreciation, power, and maintenance make up the bulk of your overhead. Direct labor cost suits assembly-heavy work where overhead tracks roughly with payroll. Direct labor hours are a reasonable middle ground when wage rates vary across workers but overhead follows time spent rather than dollars paid. The mistake most teams make is defaulting to direct labor cost because the data is easy to pull, not because it reflects how overhead actually behaves in their operation.

What is the difference between a plant-wide rate and departmental overhead rates?

A plant-wide rate uses one pool of estimated overhead and one allocation base applied across your entire operation. It works when your production process is fairly uniform. Departmental overhead rates create a separate rate for each department, matched to the cost driver that actually applies there. A finishing department running expensive CNC equipment has very different costs than a hand-packing line, and a single rate applied to both will either overcharge the cheaper work or undercharge the more expensive work.

What does it mean when overhead is underapplied or overapplied?

Applied overhead is the amount you charged to products throughout the year using your predetermined rate. Actual overhead is what you really spent. If applied overhead is lower than actual, you underapplied overhead and your product costs were too low all year, making margins appear better than they were. If applied overhead is higher than actual, you overapplied and overstated product costs. At year-end, the difference is typically cleared through cost of goods sold, or spread across work in process, finished goods, and COGS if the variance is large.

How often should I reconcile applied and actual overhead?

Every quarter, not every year. Teams that only compare applied and actual overhead at year-end are working with outdated assumptions for most of the year. A quarterly reconciliation surfaces problems early, while you still have time to adjust before the variance affects more pricing decisions.

When does activity-based costing make sense?

Activity-based costing is worth the setup cost when your product mix varies significantly in complexity. It assigns costs based on the specific activities each product consumes, such as machine setups, quality inspections, or purchase order processing, which reveals the hidden costs of low-volume, high-touch SKUs that a plant-wide or departmental rate would miss. The tradeoff is that ABC is expensive to maintain. Every activity needs its own driver and that data needs to stay current. A well-constructed set of departmental rates will give you most of the accuracy with considerably less ongoing effort.