Prepare month-end close

We need the month-end close completed for June by the close calendar: all subledger reconciliations, accruals posted, inventory variances investigated, and final P&L closed by end of business on the third business day. Run the close checklist, escalate any unreconciled items over $25,000 to me and to Javier in supply chain, and confirm with payroll and tax that no outstanding tickets remain before I declare the books closed.

Before I declare the month closed, make the reviewer’s job simple: surface the five largest outstanding reconciling items at top, show which accurals changed the most since last month, flag any inventory counts not signed off by the warehouse manager, and attach the supporting documents for each flagged item so the controller can approve or escalate in one pass.

On Day Two of the month close, inventory variance reports show $132,000 unexplained increases but operations insists counts matched. I’m stuck between delaying close and declaring the books. I can’t prove whether it’s a counting error, a posting lag, or a valuation problem. What is the most likely cause given our recent cycle, what should I ask the warehouse and the operations lead right now, and what is the safest short-term decision to protect reporting integrity?

Every month we’re firefighting reconciling items in the final two days which causes overtime, late disclosures, and strained relations with operations. Where are we losing time and control during close? Recommend three habit changes across finance, supply chain, and IT to compress the close, who must own each change, and what metric will show we can reliably close two days earlier within three cycles.