One of the most frustrating moments in manufacturing is when you click Finish on a production order and then immediately notice something is wrong: a missing component, wrong lot number, incorrect output quantity, or time that never got posted. In the past, you were stuck. You had to create awkward workarounds, post reversing journals, or open a new rework order. It was messy for costing and even messier for the audit trail.
With Business Central v26, Microsoft finally gave us a proper Reopen action for Finished production orders. This is a big deal for anyone who works with production orders on a daily basis.
What the Reopen Feature Actually Does

The Reopen feature lets you change a Finished order back to an editable state. You can correct consumption quantities, output, capacity time, item tracking, and then Finish the order again. The best part is that everything stays on the same order, so the history and costing remain clean and traceable.
I have used this many times already with clients in Greece and the UK. It saves a lot of time and reduces the risk of errors that come with workarounds. However, there are some important things to know before you use it.
Two Important Caveats
First, you generally get only one chance to reopen a finished order. Once you reopen and finish again, the option is no longer available. So it is important to plan your corrections carefully before you click Reopen.
Second, posting dates and costing rules still apply as normal. Make sure your Allow Posting From/To dates cover the correction period. If the period is closed, you may need to use a different approach.
Three Ways People Handle Corrections in Practice
In practice, I see three main ways people handle corrections on finished orders.
The cleanest option is to use the new Reopen action when the period is still open and you want to fix the original order. You reopen the order, post the missing consumption or correct the output and time, and then Finish it again. After that, run Adjust Cost – Item Entries so the costs update properly.
If you need to reverse a specific wrong posting first, you can use Undo Output or Undo Consumption, then reopen the order, make the corrections, and finish again. This gives you very clean reversal entries and a clear audit trail.
When the period is already closed or company policy does not allow editing history, the best option is to create a small Rework Production Order. You post only the delta (the missing component or extra time) in the current period. Many times you can even set the quantity to zero on the rework order if you only need to add cost.
Two Gotchas to Watch For
One common gotcha is flushing methods. If components were set to Backward flushing, reopening and finishing again might try to consume the material twice. In those cases, I temporarily change the affected component lines to Manual, post only what is needed, and then Finish the order.
Another thing to watch is item tracking. Fixing lot or serial numbers is one of the most common reasons for reopening. Always undo in reverse order and re-enter the tracking carefully to avoid conflicts.
Final Thoughts from the Field
In my experience, the new Reopen feature has reduced the number of messy rework orders and manual adjustments significantly. It keeps the audit trail much cleaner and makes life easier for both production and finance teams.
If you work with production orders regularly, I strongly recommend testing this feature in your sandbox first. It can save you a lot of time and frustration when those inevitable “oops” moments happen after you have already clicked Finish.
Have you already tried reopening finished production orders in v26? How has it worked for you in practice? Feel free to share your experience. I’m always interested to hear how it behaves in different factories.

Director and Founder of GMSOFT, a Microsoft Dynamics partner serving the UK, Greece, and Italy. Microsoft Dynamics 365 Community Super User, Season 1 2026 — recognised for top-tier community contribution on Business Central manufacturing topics. Independent BC consultant with 15 years on Business Central and NAV (and 30 in ERP overall). Founder of two BC user groups: Business Central Greece on LinkedIn and Dynamics Business Central User Group Greece (Microsoft Community). Publisher of 3 apps on Microsoft AppSource (ABC Classification Manager, Vendor Dispute, BOM Architect) and open-source AL on GitHub (GmsoftLtd).
Discover more from Inside Business Central
Subscribe to get the latest posts sent to your email.
