Nine times out of ten, the culprit is the same: inventory recalculation and inventory close weren't being run consistently — or at all. It's one of those things that nobody thinks about during implementation until it's a problem. And by then, you're doing damage control instead of just closing the books.
So let's talk about it before you're in that situation.
Let's define what we're actually talking about
Before we get into the why and the how, let's make sure we're using the same vocabulary.
Inventory recalculation is a periodic process that re-evaluates the cost of your inventory transactions based on your configured costing method. Think of it as D365 F&O doing a rough draft — it recalculates what costs should be assigned to issues based on the receipts available, and posts adjustment transactions to reflect that. It's not final. It's an estimate. But it gets your GL a lot closer to where it needs to be.
Inventory close is the process that actually settles inventory issues against the receipts that supplied them — permanently. When close runs, D365 F&O creates offsetting settlement transactions, locks the period so no further cost adjustments can be made, and marks those transactions as fully settled. Once a period is closed, it's done. You cannot go back and change inventory values in a closed period.
Value open is a status flag on inventory transactions. If a transaction shows Value open = Yes, it hasn't been fully settled yet. That means the cost assigned to it is still subject to change. Until that flips to No and the period is closed, your inventory costs are still estimates — even if they look reasonable.
How they work together
Here's a helpful way to think about the relationship between these two processes.
Inventory recalculation is like editing a document. You can run it as many times as you want during the period — daily, weekly, whenever — and each time, D365 F&O will refine the cost estimates based on the most current data available. Every run produces adjustment transactions that flow to the GL, getting your numbers closer and closer to final.
Inventory close is like hitting submit. It's the final pass. D365 F&O settles every open issue against the receipts that supplied it, posts any remaining adjustments, locks the period, and marks everything as settled. After close, no new cost adjustments can be made for that period. The numbers are locked, unless you reverse the close completely.
You can think of recalculation without close as doing all the work and never turning it in. Your GL will look better than it would with nothing at all, but it's not final. Costs are still moving. Settlements haven't happened. The period is still open to manipulation — intentional or otherwise.
The intended workflow is: run recalculation to refine your numbers throughout the period, then run close at period-end to finalize everything and lock it down.
Which methods require it — and which don't (but should)
Not every costing method requires recalculation and close to function. But that doesn't mean you should skip it.
Methods that require recalculation and close. These five methods depend on periodic settlement to assign accurate costs. Without close, your inventory values will never be finalized:
- FIFO
- LIFO
- LIFO date
- Weighted average
- Weighted average date
Methods that don't require it:
- Moving average — costs update perpetually with each receipt, so there's no period-end settlement needed.
- Standard cost — every transaction posts at the predefined standard cost, so there's nothing to settle.
But here's the thing. Even if your method doesn't technically need close, there are still very good reasons to run it consistently:
- Microsoft's guidance is to run inventory close monthly — and the only costing method its month-end guidance explicitly lets off the hook is moving average.
- Closing the period locks it — meaning no one can sneak in a backdated transaction or retroactive adjustment after the fact.
- D365 F&O's inventory archiving feature requires inventory close to have been run before archiving can happen.
- Teams that skip close regularly tend to end up with GL balances that drift unexpectedly mid-month. It's not catastrophic — until someone asks you to explain it.
Make it a habit. It's a lot cheaper than the alternative.
What actually happens during inventory close
Let's lift the hood a little.
When you run inventory close for a period, D365 F&O works through your inventory transactions and attempts to settle each issue against the receipts that supplied it. What "settle" means depends on your costing method — FIFO settles against the oldest receipts first, LIFO against the most recent, weighted average pools everything together — but the outcome is the same: each issue gets a final, settled cost assigned to it.
To record these settlements, D365 F&O creates new offset transactions (sometimes called closing transactions). These aren't physical inventory movements — they're accounting entries that represent the difference between the estimated cost that was posted originally and the final settled cost. Those differences flow to your GL as cost adjustments.
Once the period is closed:
- The Value open flag on fully settled transactions flips to No
- The period is locked — no inventory value adjustments can be posted to it
- Anything late — like a vendor invoice that shows up with a different price — can't be posted into the closed period. It has to land in an open period, or you reverse the close first
The frequency question
One of the most common questions I get: How often should we run recalculation? How often should we close?
The honest answer is: it depends on your business. But here are some useful guardrails.
For recalculation, the question to ask is: How often do you want cost adjustments hitting the GL?
If you run recalculation once a month right before close, you'll see one big batch of cost adjustments hit the GL at the end of the period. If you run it weekly, those adjustments spread out over the month. If you run it daily, your GL stays current almost in real time.
For inventory close, Microsoft's guidance is monthly. Most organizations align this with their financial close process — run recalculation during the period as often as you need, then run close as part of month-end.
One scenario worth knowing about: the zero-quantity reset. You won't find that phrase in Microsoft's documentation, but the effect is real. When an item's on-hand quantity drops to zero, there's nothing left to carry cost forward — the next receipt starts the item's cost story fresh. If your items frequently hit zero during a period — think just-in-time environments or fast-moving SKUs — your recalculation frequency and costing method work together in ways that can produce unexpected results. The more frequently you recalculate in those scenarios, the more accurate your mid-period GL will be.
A practical note on performance. Recalculation and close are resource-intensive processes, especially for high-volume environments. If you have millions of inventory transactions per month, running recalculation daily might not be realistic. Work with your team to find a frequency that balances GL accuracy with system performance. For most mid-market organizations, weekly recalculation and monthly close is a solid starting point. And whenever possible, schedule the recalculation batch job to run during off-peak hours — evenings or overnight work great — so it's not competing with active users and slowing the system down mid-business-day.
What goes wrong when you don't
Let me paint you a picture of what life looks like when recalculation and close get deprioritized. Because I've seen it, and it's not fun.
Unexplained GL swings. When recalculation hasn't been run in a while and you finally kick it off, a large batch of cost adjustments hits the GL all at once. Finance sees a big number move and has no context for why. Cue the support tickets — and the riled-up auditors.
Costs that don't match expectations. If your costing method requires settlement (FIFO, LIFO, weighted average, etc.) and close hasn't run, your COGS and inventory values are still based on estimated costs — not final settled ones. Finance is making decisions on numbers that aren't real yet.
Backdating chaos. An open period is an invitation for someone to post a transaction with a date three weeks ago. Without regular close, those backdated entries can ripple through your cost calculations in ways that are very hard to untangle after the fact.
Audit surprises. Auditors look at inventory valuation closely. If your costing method requires periodic settlement and you can't demonstrate that close was run consistently, you're going to have a longer conversation than you want.
None of these are unsolvable. But they're all avoidable.
Practical tips before you run close
Running inventory close isn't complicated, but a little prep goes a long way. Here's what I recommend checking before you kick it off:
- Confirm all purchase invoices for the period are posted. Unposted invoices mean unfinalized receipt costs. If a purchase order receipt came in at an estimated cost and the invoice still hasn't been posted, that receipt will settle at the wrong number. Post your invoices first.
- Confirm all sales invoices for the period are posted. Same logic on the issue side. If a shipment went out but the sales invoice is still sitting unposted, D365 F&O may not have the financial issue transaction it needs to settle against.
- Check for negative inventory. Negative inventory — where issues have been posted against an item with no corresponding receipt — causes problems during settlement. D365 F&O will do its best, but it can't settle a receipt that doesn't exist yet. Resolve negative inventory situations before running close whenever possible.
- Run recalculation first and review the adjustments. Don't run close cold. Run recalculation first, look at the adjustment amounts, and make sure nothing looks wildly off. If you see a cost adjustment that doesn't make sense, investigate it before locking the period.
- Don't close a period you're not ready to lock. This sounds obvious, but it's worth saying. Once close runs, that period is done. If your finance team is still working through invoice exceptions or there are open PO receipts you're waiting on, wait. Close when you're actually ready — not just when the calendar says month-end. You can always reverse a close, make adjustments, and re-run close; it just adds more steps you don't really need (or want).
The bottom line
Inventory recalculation and inventory close aren't just technical processes you hand off to someone on the IT admin team. They're part of your accounting discipline. They're how D365 F&O turns a month's worth of estimated costs into final, settled, auditable numbers.
Teams that run them consistently have cleaner GL balances, easier reconciliations, and a much smoother time at audit. Teams that skip them or treat them as optional tend to spend a lot of quality time explaining numbers nobody can fully account for.
It doesn't have to be that way. Build recalculation into your regular cadence. Lock inventory close into your month-end checklist — or even better, the Financial period close workspace — alongside your other financial close steps. Make it routine.
Frequently asked questions
What's the difference between inventory recalculation and inventory close?
Recalculation is a periodic process that re-estimates the cost of inventory issues based on your costing method and posts adjustment transactions to the GL. It can run as often as you like, and the results are still estimates. Close is the final pass: it settles issues against receipts, posts the remaining adjustments, and locks the period so no further inventory value adjustments can be posted to it.
Which costing methods require inventory close?
FIFO, LIFO, LIFO date, weighted average, and weighted average date all depend on periodic settlement, so they require recalculation and close to produce final costs. Moving average and standard cost don't. Even so, Microsoft's guidance is to run inventory close monthly — the only method explicitly exempted is moving average. It locks the period against backdated adjustments and is required for inventory archiving.
How often should you run inventory recalculation?
It depends on how often you want cost adjustments hitting the GL. The ending inventory value at month-end is the same regardless of frequency — what changes is when the adjustments show up in your books. For most mid-market organizations, weekly recalculation and monthly close is a solid starting point, with the batch job scheduled during off-peak hours under a dedicated admin account.
Can you reverse an inventory close?
Yes. An inventory close can be cancelled, which reopens the period so adjustments can be made, and then close can be re-run. But it adds steps you don't want, so the better practice is to close only when the period is actually ready — all invoices posted, negative inventory resolved, and recalculation adjustments reviewed.
What should you check before running inventory close?
Confirm all purchase and sales invoices for the period are posted, resolve negative inventory, run recalculation first and review the adjustments, and make sure the period is genuinely ready to lock. Unposted invoices mean receipts and issues settle at estimated costs instead of final ones.
Caf2Code implements and tunes Dynamics 365 Finance & Operations inventory costing, recalculation, and close across manufacturing, distribution, and retail clients. If your month-end inventory numbers are producing more questions than answers, we can help you find out why.