The stock close starts before the last day of the month

Use one cutoff, with exceptions recorded explicitly

Define which physical events belong to the period and how late entries are identified. Record event time and posting time separately where the system supports it. A delivery received before cutoff should not become invisible merely because its document is entered later; finance must determine the appropriate treatment from the evidence.

Stock reconciliation tools such as ERPNext's include a posting date and time. That makes timing explicit in the record, but the business still needs a procedure for movements during counting and corrections discovered afterwards.

Source: Frappe / ERPNext · Posting date, time and stock reconciliation. Reference details

Prepare a short exception schedule

Give each unresolved item an amount or quantity, a responsible team and a next action. Avoid an undifferentiated list of every open document.

• Receipts with missing invoices or unresolved quantity differences.
• Production material issued but not yet reflected in output, return or measured WIP.
• Transfers dispatched but not confirmed at the receiving location.
• Returns awaiting a disposition or commercial decision.
• Charges and corrections that affect the agreed costing period.

Use a boundary checklist for the final shift

The last shift needs to know which events to record before handover and how to identify unfinished work. A tank in process, material at a packing line and a vehicle awaiting outlet confirmation should not disappear because no final transaction has posted. Record the physical state and reference so the next team can complete the account.

The finance close can then distinguish an event that occurred before cutoff but was entered late from an event that genuinely occurred afterwards. Preserve both times where possible. A blanket instruction to backdate all late paperwork is not an adequate policy, because the underlying physical events may belong to different periods.

An illustrative transfer crosses midnight

A central kitchen dispatches 200 trays at 23:30 on the last day of the month. The outlet receives 196 at 00:20 the following day, with four still unexplained. The operational records should preserve the dispatch, in-transit quantity, actual receipt and remaining exception. The business's finance policy determines how those events affect the period accounts.

If the system immediately books 200 as received when dispatch occurs, the outlet count may appear short by 200 at midnight. If it waits until final receipt to record any event, the kitchen can appear to retain stock that already left. A transit model makes the physical handover visible without forcing both sites to pretend the same event happened at the same time.

Separate missing evidence from an unresolved judgement

A missing receiving record requires someone to find or reconstruct the evidence. A known damaged lot awaiting an authorised disposition requires a decision. Those tasks should not share one vague pending status. The close schedule should identify the type of work, quantity or value affected, evidence available and responsible owner.

Finance may use estimates or other treatments under its approved policy. Label them and retain the basis. Do not let an automation turn an empty field into zero or an unknown stock status into unrestricted inventory. When later evidence arrives, link it to the earlier exception so the adjustment is explainable.

Review the close as a process, not only a deadline

After the close, choose a small number of recurring exceptions to resolve at source. Repeated late receipts may require a practical dock-entry step; repeated WIP differences may require a clearer production boundary. Record who owns the change and how the next period will demonstrate improvement. Closing faster is useful only if the shortened process leaves fewer unexplained balances, rather than moving them into later corrections.

Close the loop on repeated adjustments

If the same item requires an unexplained adjustment every month, investigate its units, receiving process and production postings. A recurring journal can make the ledger balance while allowing the operating problem to continue. Keep a distinction between a documented correction and an estimate made under finance policy.

An automation can assemble the exception schedule and link its evidence. It should not decide materiality, backdate transactions or close an accounting period without the authorised workflow. Test the report against one completed period and compare how much evidence the controller still needs to request outside the system.

Summary

A dependable inventory close explains the unfinished work around the cutoff as well as the physical count. Operations supplies the evidence; finance determines the approved accounting treatment. Automation can make the exception schedule complete and traceable, while authorised people retain the closing decisions.

What to do next

1. Publish the cutoff and correction procedure before the next count.
2. Prepare a shared schedule of open receipts, WIP, transfers, returns and relevant charges.
3. Investigate the most repeated adjustment from the previous close and assign a prevention action.