prior-month adjustments posted to the current month: "close lock missed" error

Not specified by the original author.

TL;DR

First separate two questions: what actually posted into the wrong month because the lock missed, and what should happen about it. List every prior-month-dated item that posted after the close, with amounts and posters. Material items argue for reopening and correcting properly; immaterial ones can stay with a disclosure note. Either way, find why the lock missed: a role with override rights, an interface that bypasses locks, or a lock scheduled but never applied, and close that hole before the next close.

prior-month adjustments posted to the current month: "close lock missed" error

Use this when

• Journals dated in the prior month appear as posted after the prior close completed.
• The close checklist shows the lock step as done, late, or missing.
• Reported prior-month numbers changed after they were issued internally.

Not for this skill when

• The items were deliberately posted forward with memos naming the original period. That is approved practice, not a missed lock.
• The dates are wrong because of a posting-date default in one user's import. Correct the process for that user; the lock may be fine.

Steps

1. Extract all entries dated in the prior month that were created or posted after the close timestamp, with amounts, accounts, and creators. Verify: the late-posted population is complete and quantified
2. Check the lock's actual state history: when it engaged, for which entities and modules, and whether any role or interface can post through it. Verify: the bypass path is identified from settings or logs
3. Assess materiality of the late items in total and per account with the controller. Verify: a documented decision exists per item group: reopen and correct, or retain with disclosure
4. Execute the decision: reopen briefly and repost correctly, or attach the disclosure to the close file and the issued reports' working papers. Verify: prior-month balances now match the decision record
5. Repair the lock process: fix the schedule, restrict overrides, or block the bypassing interface, and test with a dummy backdated entry. Verify: the test entry is refused by the lock

Variant phrasings

adjustments posted after period close lock failed

The missed-lock phrasing.

prior month numbers changed after close postings

Searching by the changed-numbers symptom.

Compatibility: Period locking in NetSuite, Sage Intacct, Dynamics 365, Oracle, and multi-module close processes.

Why it happens

Locks fail in the gaps between modules and identities: the GL locks but the AP subledger keeps posting into it, an interface account holds standing override rights, or the lock task itself is manual and was missed in a busy close. Numbers issued from the close then drift as late items land, and trust in the close erodes. Proving which path admitted the entries is what turns an embarrassment into a control fix.

Edge cases / pitfalls

• Subledger closes and GL closes are separate locks in most ERPs. A complete lock checklist names each module explicitly.
• Interfaces that post on schedules, such as revenue or payroll feeds, need lock-aware configuration or a post-close pause.
• Keep a post-close change report as a standing close artefact; if it is empty by design, any entry on it is a finding.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_J3u4lcS0-w6Beo1XikU2Iw

Resolved from the public thread: https://vectle.com/posts/pst_J3u4lcS0-w6Beo1XikU2Iw

Thread query: prior-month adjustments posted to the current month: "close lock missed" error

TL;DR: First separate two questions: what actually posted into the wrong month because the lock missed, and what should happen about it. List every prior-month-dated item that posted after the close, with amounts and posters. Material items argue for reopening and correcting properly; immaterial ones can stay with a disclosure note. Either way, find why the lock missed: a role with override rights, an interface that bypasses locks, or a lock scheduled but never applied, and close that hole before the next close.