Publicité
ERP IMPLEMENTATION
🇫🇷 Lire en français →

Year-End Inventory Count and Stock Cut-Off in Your ERP: A December-to-Close Checklist

A D-15 to D+10 method for the annual stock count in your ERP: movement freeze, cut-off, counting, variance handling, SAP, Odoo, Sage X3 and Business Central.

Year-End Inventory Count and Stock Cut-Off in Your ERP: A December-to-Close Checklist

At midnight on December 31, the book value of your stock must match what is physically in your warehouses, and every movement must sit in the right period. On paper, that is simple. In practice, the last days of the financial year are when receipts arrive in bursts, shipments leave without being invoiced, and teams count stock while the system keeps moving underneath them.

This guide lays out an operational method around the year-end close, from D-15 to D+10, with the ERP settings you need in order to freeze, count, validate and post. It is written for CFOs, logistics managers and financial controllers in mid-sized companies. It complements our guide on initial inventory and cycle counting without repeating it: here we cover the annual close-out appointment.

Why the Annual Stock Count Is Still a Pain Point

The requirement is old and clear. Most accounting frameworks (IFRS, US GAAP, local GAAP) expect inventory to exist and to be measured correctly at the balance sheet date, and many jurisdictions explicitly require a physical verification at least once a year. In France, for instance, Article L. 123-12 of the Commercial Code requires companies to verify “the existence and value of the assets and liabilities of the business” by inventory at least every twelve months. Check the rules that apply to your own entities before writing them into your procedure.

Even with a real-time ERP, three frictions remain:

  • Reconciling book stock with physical stock. The ERP’s theoretical stock is only a hypothesis until it has been confronted with a count. The difference becomes a year-end adjustment with a direct hit on profit.
  • The external auditor. Under ISA 501, auditors typically review the count procedure, observe some or all of the counts and test period separation. An undocumented procedure or a badly held freeze costs you follow-up questions and adjusting entries.
  • Overlapping flows. Logistics teams do not stop on principle. Every exception to the freeze is a risk of double counting or omission.

The right approach is to treat the annual count as a small project: calendar, owners, system configuration, retained evidence. The rest of this guide follows that structure.

Preparing the ERP at D-15: Freeze, Statuses, Locations, Dry Run

Fifteen days before the count date, four workstreams start in parallel.

  1. Clean up master data: non-existent or duplicated locations, obsolete items still active, units of measure that differ between purchasing and stock.
  2. Settle open documents: purchase orders received but not closed, inter-site transfers open for weeks, production orders never closed.
  3. Clarify lot statuses: a blocked or quarantined lot must appear as such in the count and must not be counted as available.
  4. Run a dry count in a pilot zone: it validates count sheets, labels, access rights and the real duration of the count.

Movement Freeze: Window, Exceptions, Goods in Transit

The freeze is the most structuring decision. It means prohibiting (or strictly controlling) stock movements between the start of the count and the end of results entry. Four points must be decided and written down:

  • The window: from what time to what time, for which warehouses. A shorter freeze reduces commercial impact but requires a faster count.
  • The exceptions: for example, urgent shipments approved by the logistics manager. Each exception is logged with its reference so it can be neutralized in the reconciliation.
  • Goods in transit: goods that have left one site and not yet reached the other. They are in no warehouse on count day and must be listed separately.
  • The technical mechanism in the ERP: a movement block per warehouse, freezing of book stock on the inventory document, or a simple organizational instruction. A system block is better than an instruction.

In SAP, the physical inventory document can freeze the book inventory of the item concerned, which lets you compare the count against the frozen book quantity while still allowing certain movements. Check the exact behavior in the documentation for your release (SAP Help, physical inventory).

Equipment and Data Entry: Scanning, Tablets, Count Sheets

The entry method determines reliability. Three options, from simplest to most robust:

MethodAdvantageLimitation
Printed count sheetsNo hardware, good fallbackRe-keying, transcription errors
Tablets or smartphonesDirect entry into the ERPNetwork coverage in the warehouse
Barcode-scanning terminalsItem, lot and location are read, not typedInvestment, prior labeling

Whichever method you choose, always print backup sheets. Sheets are also an audit trail for the auditor. On the count sheet, hide the theoretical quantity for blind counts: a counter who sees the expected figure tends to confirm it.

Cut-Off: Assigning Every Movement to the Right Period

Cut-off (period separation) means verifying that each physical flow is recorded in the period in which the transfer of risks and ownership took place. It is the point auditors like to test most, because errors move profit directly from one financial year to the next.

Four situations need explicit handling:

Shipped but not invoiced. Goods shipped on December 30 and invoiced in January have left stock: they must no longer appear in the count. Depending on the terms of sale, the revenue may belong to the year just ended. The check is to list the delivery notes of the last week and verify that they were invoiced, or that an accrued revenue entry (invoice to be issued) was recorded.

Received but not invoiced. Goods received on December 29 whose supplier invoice only arrives in January are in stock and must be counted. You therefore need an accrual, or a “goods received not invoiced” (GR/IR) entry: the GR/IR clearing account in SAP, an equivalent uninvoiced-purchases account depending on how other ERPs are configured. A receipt that was never posted distorts both stock and payables. The link with the annual close and its cut-off entries is direct.

Consignment and held-on-behalf stock. Ownership rules depend on the contract: stock held at a customer’s premises still belongs to your company until the customer withdraws it, while consignment stock at your site belongs to the supplier. Both are counted physically but are not valued the same way. Our article on consignment stock and vendor-managed inventory in the ERP covers the configuration. Plan to send a stock confirmation request to third-party holders.

Stock held by third parties. Subcontractors, carriers, repair workshops: the company remains the owner. Each third party should confirm quantities in writing as of the count date. Without confirmation, the difference can only be handled by estimate, which auditors do not appreciate.

A methodological tip: keep the last and first document numbers (last goods receipt of the year, first of the new year, same for shipments) and have the warehouse manager sign them. These are the “bookends” of your cut-off.

The Count: Plan, Teams, Double Counting, Test Counts

A good count owes more to its organization than to the tool.

  • The count plan divides the warehouse into numbered zones, with one sheet or one task per zone. No zone should be left without an owner, and none should be counted twice by mistake.
  • Teams ideally pair a counter with a verifier who is independent of the storekeeping function. Logistics staff count better in zones they do not normally manage, for an obvious reason: they do not know the expected figures.
  • Double counting: two independent counts of the same zone, one of them blind. A discrepancy between the two triggers a third count.
  • Test counts (auditor or independent re-counts): the financial controller, internal audit or the external auditor selects items and re-counts them. This validates the quality of the process rather than the figure.

Record the following: damaged or unusable items (for write-downs), third-party goods present in the warehouse (to be excluded) and returnable packaging.

Handling Variances: Thresholds, Recount, Approval, Adjustment

Once the count has been entered, the ERP calculates the difference between counted quantity and book quantity. Handling follows a consistent path:

  1. Tolerance thresholds. Define a threshold in quantity and in value, possibly differentiated by item class. Below the threshold the variance is accepted; above it, it triggers a recount.
  2. Recount. It is performed by a different person, before any posting. Most large variances disappear at this stage (unit error, neighboring location, mistyped lot).
  3. Root-cause analysis for variances that persist: unfrozen movement, forgotten customer return, transfer not received, unit-of-measure error, theft or breakage.
  4. Two-level approval: the logistics manager validates the explanation, and finance validates the accounting impact above a set amount. The counter never approves their own variances.
  5. Adjustment posting. The ERP generates an adjustment movement (positive or negative) valued according to the item’s costing method, with a stock variance as the counterpart. Valuation depends on the method chosen: see our guide on inventory valuation with FIFO, weighted average and standard cost.

Unposted variances do not go away: they come back at the next count, bigger. And the obsolete or damaged stock identified during the count feeds the inventory write-down at year-end.

ERP-Specific Details

The terms change, the sequence stays the same: create the count document, freeze the comparison baseline, enter, validate, post.

StepSAPOdooSage X3Business Central
Prepare the countMI01, physical inventory documentInventory adjustments, “Request a Count”Inventory function in the Stock module (menu to be checked per version)Physical inventory journal, “Calculate Inventory”
Enter the countMI04Counted quantity column, Barcode appEntry of counted quantitiesQty. (Phys. Inventory) in the journal
Post the variancesMI07Apply the adjustmentInventory validationPost the journal

Reference points, with the usual caveats:

  • SAP: MI01 creates the document, MI04 enters the count, MI07 posts the differences, and MI08 / MI10 combine several of these steps (Guru99, SAP MM physical inventory). Exact transaction codes vary between ECC, S/4HANA and Fiori: confirm them in your release.
  • Odoo: inventory adjustments can be validated line by line or in bulk, and the default scheduled date is December 31 (Odoo 18 documentation). Check the accounting date of the generated movements so the adjustment lands in the right financial year.
  • Sage X3: the inventory function sits in the Stock module. Menu labels depend on the version and folder: validate them with your integrator rather than relying on a generic list.
  • Business Central: Microsoft recommends keeping the lines calculated at the start rather than recalculating expected stock during the count, since it may change in the meantime (Microsoft Learn, count, adjust and reclassify inventory).

In every case, test the full sequence in a test environment before the real date, including the posting date of the variance, which must stay within the financial year being closed.

After the Count: Unfreeze, Root Causes, KPIs

The unfreeze happens when validated variances have been posted and the last blocked movements have been processed in order. Do not reopen the flows before that: a movement posted too early invalidates the calculated variance.

Once the period is reopened:

  • Release the queued flows (receipts and shipments accumulated during the freeze), checking their dates.
  • Analyze variance causes by family: entry error, unfrozen movement, forgotten return, theft. Every cause must lead to an action.
  • Track reliability indicators: variance rate in quantity and value, number of items with a variance, share of explained variances, freeze duration. Set your own thresholds from your history rather than adopting an unsourced benchmark.
  • Link to valuation: a recurring negative variance on a product family may hide a cost or bill-of-materials error, not just a physical problem.

Classic errors to watch for: unfrozen movements, forgotten customer returns, blocked lots counted as available, in-transit transfers counted twice, third-party stock included in the count.

Printable Checklist: D-15 / D-1 / D / D+10

D-15: prepare

  • Count date, scope and owner decided and communicated
  • Master data cleaned (locations, units, inactive items)
  • Open documents settled (receipts, transfers, production orders)
  • Lot statuses verified (blocked, quarantine)
  • Count plan, teams and equipment ready, dry count performed
  • Confirmation requests sent to third parties holding stock
  • Sequence tested in a test environment (document, entry, variance, posting)

D-1: freeze

  • Movement freeze activated in the ERP (or written instruction if a block is impossible)
  • Last receipt and shipment numbers recorded and signed
  • Goods in transit listed
  • Count sheets and labels printed, backup sheets included

D: count

  • Blind count, double count in high-risk zones
  • Freeze exceptions logged with their reference
  • Damaged, blocked or third-party items identified separately
  • Test count performed by finance or audit

D+1 to D+10: validate and close

  • Quantities entered and variances calculated
  • Variances above thresholds recounted
  • Two-level approval and adjustment entries (correct accounting date)
  • Cut-off checked: shipped-not-invoiced, received-not-invoiced, accruals
  • Inventory write-downs assessed
  • Unfreeze, root-cause analysis, KPIs updated
  • Count file archived (sheets, bookends, approvals)

Going Further

To structure the overall close calendar, read our year-end ERP configuration and 2027 fiscal-year switchover checklist (in French), then download our ERP evaluation scorecard: 30 criteria and 100 points to benchmark your current ERP or a future vendor.