Skip to main content

Capacity and Overhead Now Post to the Correct Location WIP Account

 

Quick reference

Feature

Wave

GA Date

BC Version

Location-based capacity and overhead posting

Wave 1 2026

April 2026

BC 28


Introduction

If you run manufacturing in Business Central across multiple locations — and you use location-specific WIP accounts in your Inventory Posting Setup — there is a good chance your finance team has been quietly chasing an unexplained WIP imbalance for longer than they realise.

It was not a data entry error. It was not a misconfigured posting group. It was a system behaviour that caused capacity and overhead costs to post to the common inventory posting group based WIP account.

BC 28, generally available April 2026 as part of 2026 Release Wave 1, fixes this. This post explains exactly what was happening, what changed, and what you need to do before and after upgrading.


The problem — what was happening before BC 28

  • Material costs → correct location WIP account
  • Capacity and overhead costs → blank location WIP account

This created WIP account imbalances that were genuinely difficult to diagnose. The total WIP balance across all accounts might be correct in aggregate — but the split between location-specific accounts was wrong. Your production facility in one city was showing lower WIP than it should, and your blank-location account was absorbing costs that belonged somewhere else.

There was a secondary consequence too. If you added overhead to routings and posted a production journal, BC threw an error unless you maintained an Inventory Posting Setup line for blank location. This forced every multi-location manufacturer to keep a blank-location posting setup line purely as a workaround — even when it served no legitimate accounting purpose.


Who was most affected

Not every BC manufacturing environment hit this issue equally. The impact was most significant for:

Multi-site manufacturers with location-specific Inventory Posting Setup If your Inventory Posting Setup has rows for specific locations — typically because your chart of accounts separates WIP by facility — you were affected. The larger the capacity and overhead component of your production cost, the larger the WIP imbalance.

Finance teams doing site-level P&L reporting If your management accounts report WIP and cost of production by facility, the blank location posting directly distorted those reports. The fixes applied were legitimate reconciliation entries for a system error, not real cost variances.


What BC 28 fixes — the exact changes

Microsoft has made two precise corrections in BC 28:

1. Value entries now carry the correct Location Code

Value entries that are linked to capacity ledger entries now have a Location Code value that comes from the related production order line or item journal line. Previously, these value entries had no Location Code — or carried the blank location — regardless of where production actually occurred.

2. Capacity and overhead now use location-specific Inventory Posting Setup

When you post capacity or overhead, Business Central now looks up the Inventory Posting Setup for the specific production location — not the blank location. This means your location-specific WIP accounts receive all production costs from that location: materials, output, capacity, and overhead.

3. Blank location Inventory Posting Setup line no longer required

You are no longer forced to keep an Inventory Posting Setup line for blank location as a workaround for the overhead posting error. Once you confirm the BC 28 fix is working correctly in your environment, that workaround line can be reviewed and removed from your configuration if it serves no other purpose.


Practical guidance — what to do before and after upgrading

Before upgrading to BC 28

Step 1 — Document your current WIP account balances by location

Pull a balance by location for all WIP accounts in your chart of accounts. Note the balance on each location-specific WIP account and the blank-location WIP account. This is your baseline — you will compare against it after the upgrade to understand the impact.

Step 2 — Identify your blank-location Inventory Posting Setup line

Go to Inventory Posting Setup and find the row with a blank Location Code. Note which WIP account it points to. This is the account that was incorrectly absorbing capacity and overhead costs. After the upgrade, you will want to verify this account is no longer receiving production cost postings.

Step 3 — Estimate the historical impact

If you want to understand the size of the misstatement in your historical WIP reporting, pull the value entries for capacity ledger entries over the past 12 months and filter by blank location. The total of these entries is the amount that was posted to the blank location. Depending on your materiality threshold and your audit requirements, you may want to discuss with your finance team whether a correcting journal is appropriate for historical periods.

Step 4 — Test in a sandbox before going live

This fix changes posting behavior that directly affects your financial accounts. Always test in a sandbox environment against your actual Inventory Posting Setup before upgrading production. Post a test production journal with routing operations and verify the value entries carry the correct Location Code and hit the correct WIP account.

Step 5 — Complete posting of existing orders already posted under the current setup

Before upgrading, identify all production orders that have been partially posted under the current (old) posting behavior — meaning they already have capacity and overhead value entries sitting in the blank-location WIP account. Where operationally possible, complete and fully post these orders before the BC 28 upgrade. This ensures each order's cost entries are consistent — all posted under the same logic — and avoids a mixed audit trail where some value entries carry blank location and others carry the correct location on the same production order. Orders that cannot be completed before the upgrade should be flagged for a careful post-upgrade reconciliation review.

 


Final thought

This BC 28 fix removes one of the genuine sources of that imbalance in multi-location manufacturing environments.

If your finance team has been reconciling unexplained differences between location WIP accounts, this post is worth sharing with them alongside your BC 28 upgrade plan.

 

Comments

Popular posts from this blog

Manufacturing Costing — What Changed in recent versions (BC26 & 27) and Why It Matters

  Introduction Manufacturing costing has always been one of the most technically demanding areas of a Business Central implementation. Get it right and you have a reliable, real-time view of what it actually costs to make your products. Get it wrong and your P&L tells a story that doesn't match your shop floor. In 2025, Microsoft has made meaningful improvements to manufacturing costing across both Wave 1 and Wave 2 — which targeted fixes to gaps that practitioners like me have been navigating in our implementations. This post walks through what changed, what it means in practice, and what you should do about it. Quick reference — what's available and when All four features covered in this post are already generally available. Here's the version map so you know exactly what you need to be running: Feature Wave GA Date BC Version Non-inventory items in production cost Wave 1 20...

Subcontracting in BC 2026 Wave 1 — A Manufacturer's Guide to the New Native Framework

  Introduction Subcontracting has been one of the most common pain points I encounter in Business Central manufacturing implementations. The question I've heard dozens of times is some version of this: "We send components to a vendor for painting / galvanizing / heat treatment — how do we handle that in BC without building a workaround?" Until now, the honest answer was: with some creative configuration, a fair bit of discipline, and an acceptance that BC's native subcontracting capabilities only handled the cost side of the equation, not the physical movement of goods. It is worth noting that subcontracting logistics functionality has existed in BC but only within specific localizations, namely India and Italy. Manufacturers running those localizations have had access to logistics flows for subcontractor transfers as a regional capability. With 2026 Wave 1, Microsoft is promoting this to a W1 — worldwide — solution, meaning any BC customer on any localization c...

BC vs Traditional ERP — A Manufacturer's Perspective

  BC vs Traditional ERP — A Manufacturer's Perspective Introduction After 11 years implementing ERP systems — first as a production planner on the shop floor, then as a functional consultant— I've sat on both sides of the table. I've felt the frustration of a clunky legacy ERP as a user, and I've guided manufacturers through the transition to Microsoft Dynamics 365 Business Central as a consultant. The question I get most often from manufacturers considering a move is simple: "Is BC really different, or is it just another ERP with a new logo?" The honest answer is: It depends on how you implement it; flexibility that actually fits the way a factory works. Here are the most practical differences I've observed, and the tips that make the difference in real-world manufacturing implementations. 1. Traditional ERP was built for Accounting, Extended to Manufacturing Most legacy ERP systems were designed from the financial ledger outward. Manufa...