Cost management and inventory closing in F&O

Where Business Central runs Adjust Cost — Item Entries as a routine, Dynamics 365 Supply Chain Management has a deeper, more configurable inventory costing engine centred on the inventory closing process. Understanding it is essential for anyone running F&O at scale.

The cost-management module

F&O's Cost Management workspace coordinates:

• Item models — costing methods per item (FIFO, LIFO, Weighted Avg., Date, Standard Cost, Moving Average).
• Closing runs — periodic recalculation of inventory costs to ensure inbound costs flow to outbound transactions.
• Adjustments — manual corrections to specific item ledger entries.
• Inventory recalculation — without locking inventory, recalculate cost without closing the period.
• Marking — manually link specific outbound transactions to specific inbound layers (for serial-tracked or specific costing scenarios).
• Cost rollups — for standard-cost items, roll up component costs to finished goods.

Inventory closing

The headline operation. Inventory closing is a date-bound process that:

1. Identifies all open inventory transactions up to a chosen closing date.
2. Matches outbound transactions to inbound transactions based on the item's costing method (FIFO matches earliest open inbound; LIFO matches latest; Weighted Avg. computes the moving average).
3. Posts adjustment entries to reconcile cost.
4. Locks inventory transactions before the closing date — they cannot be edited without explicit reopening.

This is more powerful than BC's adjustment routine: it produces a closed period of inventory transactions that auditors can trust, with locked records.

Per-item closing

Closing can run for selected items only — useful when investigating discrepancies on one item without disturbing the whole inventory.

Inventory recalculation

A lighter-touch alternative that re-runs cost matching without locking transactions. Used for mid-period sanity checks or for ongoing operations where closing would be premature.

Marking

Manual marking lets users explicitly bind a specific outbound transaction to a specific inbound layer. The classic use case: a unique high-value purchase (a specific machine) sold to a specific customer — the user marks the sale against the specific purchase, regardless of FIFO/LIFO order. Marking overrides the standard costing logic for that pair.

The standard-cost item model

Standard cost items work differently. Each item has a configured standard; inbound and outbound post at the standard; variances post to designated variance accounts. The annual standard-cost roll updates the standards (similar to BC's standard cost worksheet but more deeply integrated with manufacturing). Closing reconciles standard inventory to actual when actual deviates substantially.

Moving average

An incremental Weighted Avg. variant where each receipt updates the moving average and outbounds post at the current moving average. Less precise than Weighted Avg. at closing but provides real-time cost visibility on every transaction.

FIFO with date

FIFO with explicit date control — combines date and FIFO order, so deliveries late but recorded earlier still match correctly.

The GL impact

Closing posts adjustment entries to:

• Inventory account (asset side).
• Cost of Goods Sold account (P&L side).
• Variance accounts (for standard cost items).
• Inventory revaluation accounts (when standards change).

Period-end reconciliation between the Inventory GL account and the Inventory Valuation report should match to the penny after closing.

Common pitfalls.

• Closing not run regularly — inventory cost drifts; COGS becomes unreliable.
• Marking abused — too many manual marks make audit complex.
• Standard cost variances unallocated — large variances accumulate in variance accounts without analysis.
• Closing run during operations — locks inventory, disrupts shipping. Schedule during quiet windows.

Operational discipline

Run inventory recalculation weekly; run inventory closing monthly (or quarterly for low-volume operations). Reconcile inventory to the GL every close. Don't let unallocated variances accumulate; investigate large ones each close.