The Annual POHR as a Cost Transfer
The textbook presents the annual predetermined overhead rate (POHR) as the standard approach. But viewed through the lens of Simplicity Moves Cost, It Doesn’t Reduce It, the annual POHR is a simplification that moves complexity rather than eliminating it.
The Simplification and Where the Cost Goes
| What Annual POHR Simplifies | Where the Complexity Moves |
|---|---|
| No need to calculate seasonal rates | Product costs in high-overhead months are understated |
| Stable month-to-month reporting | Year-end variance adjustment absorbs accumulated distortion |
| One rate for all pricing decisions | Some products subsidize others without visibility |
The annual POHR doesn't eliminate seasonal variation—it hides it until year-end, then dumps it into COGS as a lump adjustment.
Who Benefits, Who Pays
| The Simplification | Who Benefits | Who Bears the Cost |
|---|---|---|
| Annual POHR instead of seasonal | Accountants (less work), executives (stable reports) | Production managers in high-overhead seasons judged on “variances” |
| Year-end variance dump to COGS | Monthly reports look clean | Shareholders absorb surprise adjustment; decisions made on distorted data all year |
| Single allocation base (e.g., DLH) | Products aligned with that base | Products that don’t fit the base (cross-subsidization) |
This maps directly to The People Around You Bear the Cost of Your Shortcuts—the finance department takes the simple path, and production managers absorb the consequences.
The Hidden Baseline
From Every Comparison Has a Hidden Baseline:
“Underapplied overhead” sounds like a fact. But it’s underapplied compared to the estimate. A different estimate would produce a different variance—and tell a different story about performance.
| If Estimated Overhead Was… | The Variance Would Be… | The Narrative Becomes… |
|---|---|---|
| 325,000) | $5,000 underapplied | ”We spent more than expected” |
| 325,000) | $5,000 overapplied | ”We came in under budget” |
Same reality. Different baseline. Different conclusion.
Seven Lenses Applied to Annual POHR
The claim: “Using an annual predetermined overhead rate is appropriate for costing jobs.”
1. Actors
Who designed this? Who benefits? Whose voices were absent?
| Question | Answer |
|---|---|
| Who decides to use annual POHR? | Cost accountants, finance department |
| Who benefits? | Accountants (less work), executives (stable reports) |
| Who loses? | Production managers judged on variances; seasonal products mispriced |
| Whose voices absent? | Workers in seasonal departments, customers paying distorted prices |
2. Conditions
What assumptions must be true for this to work fairly?
| Assumption | What If False? |
|---|---|
| Overhead is stable across the year | Seasonal businesses get distorted product costs |
| Allocation base drives overhead | Products get mis-costed; cross-subsidization |
| Estimates are accurate | Large year-end variances; wrong decisions all year |
3. Trade-offs
What’s sacrificed for simplicity?
| Gained | Sacrificed |
|---|---|
| Administrative simplicity | Accuracy of individual product costs |
| Stable monthly reports | Visibility into seasonal patterns |
| Easy pricing | Understanding of true cost drivers |
4. Scope
Does this claim universality it doesn’t have?
The textbook presents annual POHR as universal best practice. It’s actually context-dependent:
- Works well: Stable, year-round manufacturing
- Works poorly: Seasonal businesses, project-based firms, high-variation environments
5. Scale
Accurate in aggregate, unfair to individuals?
| Level | Performance |
|---|---|
| Company-wide annual profit | Reasonably accurate |
| Individual product cost | May be significantly distorted |
| Monthly manager evaluation | Seasonal managers judged on timing, not performance |
6. Mechanism
How does methodology translate to consequences?
Annual POHR chosen
↓
Overhead applied evenly across months
↓
Winter products under-absorb (heating costs not reflected)
Summer products over-absorb
↓
Winter products appear less profitable → pricing/resource decisions shift
↓
Year-end: variance dumped to COGS
Nobody traces which decisions were distorted
7. Sequence
When was choice made? Can it be revised?
- Decided at year start by finance
- Affected parties not consulted (treated as “technical”)
- Practically locked in—mid-year changes look like manipulation
When Seasonal Rates Make Sense
| Business Context | Why Seasonal Rates Help |
|---|---|
| Ski resort | Overhead concentrated in winter |
| Ice cream manufacturer | Production peaks in summer |
| Retail fulfillment | Holiday surge changes cost structure |
| Agricultural processing | Harvest vs. off-season are different operations |
The Meta-Lesson
The textbook presents "how it's done."; the frameworks ask "who decided, and who benefits?"
Annual POHR is a trade-off.
The problem is presenting it as neutral best practice rather than a choice with distributed consequences.
This connects to Methodology as Power:
“There is no neutral measurement. Every method answers a different question, embeds different assumptions, and distributes consequences differently.”
North: Where this comes from
- FMGT-2294 Chapter 5 - Notes from the Textbook (textbook treatment of POHR)
- Methodology as Power (framework for analyzing design choices)
- Simplicity Moves Cost, It Doesn’t Reduce It (cost transfer principle)
East: What opposes this?
- Practical Constraints Justify Simplification (sometimes annual POHR really is good enough)
- Administrative Cost of Precision (seasonal rates have real overhead)
South: Where this leads
- Activity-Based Costing (more refined allocation, but same trade-offs at finer grain)
- Variance Analysis (managing the consequences of estimation error)
West: What’s similar?
- CPI Basket Decisions (same pattern—methodology choice distributes consequences)
- Performance Metrics Design (same pattern in organizational context)