month-end close "failed to lock" error: open items still unreconciled in AP
Fixes a month-end close failing to lock because open items are still unreconciled in AP: triage AP open items into real blockers and acceptable carry-overs per policy, clear or formally carry each one, then lock. Use when the lock gate lists AP exceptions. Not to force-lock over material unreconciled items.
TL;DR
The lock is doing its job: it refuses to freeze a period whose AP still holds unexplained open items. Work the gate list by category: items that are actually matched and just unflagged, items awaiting vendor credits, GRNI items with receipts but no invoice, and true unknowns. Clear what can be cleared, and for the rest use the formal carry-over or exception sign-off your policy provides, naming each item, so the lock proceeds on documented judgement rather than on someone disabling the gate.
month-end close "failed to lock" error: open items still unreconciled in APUse this when
- Close lock fails or is blocked listing unreconciled AP open items.
- The AP aging or open item report shows items in several distinct states, not one uniform problem.
- The close deadline is near, creating pressure to bypass the gate.
Not for this skill when
- The unreconciled items are material and unexplained. Then the correct outcome is a delayed lock and escalation, not a workaround.
- AP shows open items only because the rec jobs have not run. Run the jobs first; the gate may clear itself.
Steps
- Export the AP open items blocking the lock with vendor, amount, age, and state: unmatched, GRNI, unapplied payment, or unlinked credit. Verify: every blocking item is categorised
- Clear the mechanical items first: run pending matches, apply unapplied credits and payments that have proven partners. Verify: the blocking count drops by the mechanical clears
- For GRNI and vendor-awaiting items, gather the evidence of their status, receipt records or vendor confirmations, and assign each a follow-up date. Verify: each remaining item has evidence and an owner
- Present the remaining items for the formal exception or carry-over sign-off per policy, with amounts and reasons. Verify: sign-off is recorded against the named item list
- Lock the period and attach the carry-over list to the close file, with the items flagged to clear or re-present next period. Verify: the lock completes and the carried items are visible in the next close checklist
Variant phrasings
cannot lock period unreconciled AP open items close
The blocked-lock phrasing.
month end close gate GRNI unapplied items triage
When triaging the gate list.
Compatibility: Close gating and AP open item management in NetSuite, SAP, Dynamics 365, Oracle, and close management platforms.
Why it happens
Lock gates encode a simple truth: freezing a period freezes its questions too, and unreconciled AP items are questions with money attached. The failure mode the gate prevents is the quiet roll-forward, where GRNI and unapplied items age across periods until nobody remembers them. Categorising the gate list usually reveals that most items are process lag, not risk, and the genuinely risky few deserve the spotlight the gate gives them.
Edge cases / pitfalls
- A standing weekly AP open-item review keeps the month-end gate list short; the gate should confirm hygiene, not discover months of backlog.
- Carry-over sign-off should expire: an item carried twice needs escalation, not a third signature.
- If the gate can be disabled by the same people it constrains, note that design weakness for the controls review even when this close proceeds properly.
Provenance
Resolved from the public thread: https://vectle.com/posts/pstn5Ctl4AMrGOdDxXJZoeSQ