Lock accounting period: What a period lock stops, who can still post, and when to reopen

Locking an accounting period means turning on the setting that stops users from changing transactions dated in that period, so reported results stay fixed. When you close an accounting period, you finish the month's work, and the lock is the control that protects the result.

Three terms come up in every system:

• Lock date or closing dateThe date on or before which transactions can't change without approval. QuickBooks calls it a closing date, and Xero calls it a lock date.
• Closed periodA month whose posting is finished. In NetSuite, a closed period blocks general ledger postings by anyone, while in Business Central, closing a period doesn't block posting at all.
• ReopenLifting a lock or close so an approved entry can post to the original month, then locking it again.

You lock right after sign-off for three reasons. A late bill or backdated journal entry can't quietly change numbers the board, lenders, or auditors already have. Reconciliations finished during the close stay reconciled, and every later change has to go through a visible, approved path. The lock is the last step of the month-end close, after reconciliations, adjusting entries, and review.

A soft lock stops ordinary users but lets named people post with a password or override. A hard lock stops everyone until an authorized user lifts it. Closed status and posting restrictions are separate settings: in Business Central, a closed period or fiscal year doesn't block posting at all.

These labels aren't vendor terms, so check each system's behavior in the next section rather than its menu name. A soft lock is also different from a soft close. A soft close is a faster monthly close that leans on estimates, followed by a full hard close at quarter-end or year-end.

Each system locks differently: QuickBooks Online uses one closing date, Xero two lock dates, NetSuite module locks and a period close, and Business Central posting date ranges. Sage Intacct closes subledgers and then the books, and SAP opens posting periods by account type. This table shows what each lock stops, checked against vendor help pages on November 9, 2026.

Who can still post in each system, whether payables and receivables lock on their own, and the vendor page behind each row:

QuickBooks Online and QuickBooks Desktop

In QuickBooks Online, choose "Allow changes after viewing a warning and entering password," not the warning-only option, which anyone who can edit transactions clicks through. There's one closing date for the company, so move it forward after each monthly close. QuickBooks Desktop works the same way, with a closing date and password the admin sets.

Xero

Xero gives you two lock dates: one that stops all users except administrators (Dext's help calls the role adviser), and one that stops every user. Set the first when each month closes, and set the second once year-end accounts and tax returns are final. Dext's help center notes that a bill dated before the lock can still reach Xero as a draft or awaiting approval. Clear those before you lock.

NetSuite

NetSuite's checklist locks run from the subledgers up. Lock A/P and Lock A/R stop ordinary users posting those transaction types, and Lock All stops every other transaction that hits the general ledger. Closing the period "prevents posting to the general ledger for any dates included in the period, by anyone," in Oracle's words. To stop typos like 2027 for 2026, turn on Enable Accounting Period Window, which locks future periods beyond a window of 1–1,000 open periods.

Business Central

Microsoft Learn says "accounting periods don't control posting dates." It adds that "although a fiscal year is closed, you can still post general ledger entries to it." Your lock is the Allow Posting From and Allow Posting To range on General Ledger Setup, which applies to all users. Ranges on User Setup "overrule" it for named users. Date formula fields can roll the window forward each month, with one catch covered in the leak table below.

Sage Intacct

Sage Intacct closes in layers: AP, AR, and Expenses summaries and Cash Management periods first, then the books. After the books close, "you cannot post transactions in any application" for earlier dates. Sage notes you can still book adjusting entries to a closed period. To stop those too, lock the closed period. Sage says a locked period "cannot be reopened, and information for the period cannot be changed, even by adjustments" until it's unlocked.

SAP S/4HANA

In SAP S/4HANA, OB52 opens posting periods for each posting period variant, with the + line checked first for every document. Interval 2 is the normal interval for all users. Interval 1 can carry an authorization group, so only your closing team can post to last month. Interval 3 controls postings from Controlling to Financial Accounting.

Which accounting software lets you lock periods by subledger, not just a single closing date?

NetSuite, Sage Intacct, and SAP S/4HANA lock by subledger or account type, so you can lock payables while the general ledger stays open for adjusting entries. Business Central restricts posting dates by user and journal template, not by module. QuickBooks Online, QuickBooks Desktop, and Xero lock the whole file to one date, so in those systems you set the date once, at sign-off.

Not directly: a manager can ask for a recode, but accounting decides and posts it. Small recodes go in the current month as a reclassification, and recodes that change reported results go in the closed month after an approved reopen. Separating the request from the posting keeps department results reliable.

A recode changes the account, department, class, or entity on an expense. An override edits the original transaction in place, which is exactly what the lock is there to stop, so no manager should hold override access.

Total software expense doesn't change, and September's company P&L stays as reported. October's Sales expense is $3,200 lower and Engineering's is $3,200 higher, so note the reclass in the October department reports. Reopen September instead when department results drive commissions, bonuses, or a budget decision that has already been made. The guide to month-end journal entries covers how reclassification entries are built and reviewed.

Book it in the current month unless it was never accrued and late items for that month cross your materiality threshold or change a figure someone relies on. A written rule keeps every late item from becoming a debate.

Work through four questions in order:

1. 1Does the cost belong to the locked month?Check the service or delivery date, not the invoice date
2. 2Was it accrued?If it was, match the invoice to the accrual in the current month and leave the locked month alone
3. 3Is it under your threshold, alone and with other late items for that month?If it is, book it in the current month with a memo naming the original month
4. 4Does it trip a qualitative trigger?Reopen for any item that affects a loan covenant, a bonus, a tax filing, a loss turning into income, or a figure already sent to investors or the board

No single percentage settles materiality. The SEC's Staff Accounting Bulletin No. 99 (1999) describes a common 5% rule of thumb. It then says "exclusive reliance on this or any percentage or numerical threshold has no basis in the accounting literature or the law." It lists qualitative factors such as whether a misstatement "affects the registrant's compliance with loan covenants" or "has the effect of increasing management's compensation." Treat your threshold as the point that triggers a controller review, not a bright line.

Outcome A: September already has an accrual. The team accrued $4,500 for the work on September 30, so September already carries the cost. The invoice clears the accrual in October, and the $300 difference is October expense.

Outcome B: No accrual, under the threshold. $4,800 is 4.0% of September's pre-tax income and under the $6,000 threshold, so the invoice is booked in October and logged as a late September item.

Memo: September services, booked late per lock policy

September's expense is understated by $4,800 and October's is overstated by the same amount. The late-item log keeps that visible, so the next late September item is tested against the running total.

Outcome C (an alternative to B): No accrual, and the late items cross the threshold. Suppose instead that a $2,000 September freight bill turns up the same day, before the $4,800 invoice is booked. Together the two are $6,800, or 5.7% of September's pre-tax income, so the controller reviews them and approves a reopen.

The team reopens September, posts the entry, reruns the accounts payable reconciliation, and relocks the month the same day. The revised September package shows pre-tax income of $113,200 ($120,000 − $6,800). If the $4,800 invoice had already been booked in October under outcome B, reverse that October entry when you post it to September, or the cost is counted twice.

Accruing well turns late invoices into outcome A, which is why the guide to accrued expenses is the first fix for repeat reopens. The same rule covers backdated journal entries. Backdating inside the open month is normal. After the lock, date the entry in the current period and name the original month in the memo. If your team reopens prior months for every small item, enforce the threshold, because each reopen changes reports you already sent. The guide to adjusting entries covers an entry booked to the wrong period.

Usually yes: an authorized user can reopen or unlock a closed period in most systems, but treat it as an exception. Business Central differs, because a closed fiscal year can't be reopened and you control changes with posting date ranges instead. Approve every reopen in writing, post the entry, rerun the affected reconciliations, and relock the same day.

1. 1RequestThe preparer submits the entry, the reason, the amount, and the accounts affected
2. 2ApproveThe controller approves in writing before anyone unlocks, and the CFO approves items above the policy threshold
3. 3UnlockOne named person reopens the period or widens their own posting range, using the steps in the table above
4. 4PostPost only the approved entry, dated in the original month
5. 5RerunRerun the account reconciliation for every account the entry touched, and the trial balance for the month
6. 6Relock and recordLock the period again, and save the request, approval, entry, and before-and-after trial balance together. In NetSuite, redo the required checklist tasks and close every reopened period again, oldest first

Two system behaviors catch teams out. In NetSuite, reopening a period automatically reopens every later closed period, and you may need to redo checklist tasks for each before you can close them again. In Sage Intacct, a locked period must be unlocked first. Sage says access to Open books is usually restricted to the accounting manager, controller, or CFO.

Reopening the ledger vs correcting issued financial statements

Reopening a month in your ledger is a bookkeeping step you take before results are final. Once statements for that period are issued, ASC 250 governs the correction. A material error means restating the earlier statements as a prior-period adjustment, with the cumulative effect in opening retained earnings. An immaterial error is corrected in the current period if it's also immaterial to that period, or by revising the prior period. Booking a late accrual into a reopened month before anything is issued isn't a prior-period adjustment in the ASC 250 sense, so don't label it as one.

Depending on the lock, the system blocks the entry, warns and asks for a password or override, or moves the entry to an open period. If an entry did land in a closed month, someone had an override, moved the lock date, or used a setting that bypasses the lock.

NetSuite shows both behaviors. When a period is locked for a subsidiary, it drops out of the Posting Period list. The Allow Transaction Date Outside of Posting Period preference decides what happens when a transaction's date and posting period don't match: Disallow stops the user from saving until they match, Warn lets them save after a warning, and Allow saves without one. For a backdated transaction from a closed period, the Default Posting Period When Transaction Date in Closed Period preference picks the current period (the default) or the first open period. In SAP, an error saying the posting period isn't open means the posting date falls in a period OB52 hasn't opened for that account type.

Why transactions still land in a locked period

Each leak below has a setting behind it and a report that catches it, so you can close the gap before your next audit.

Integrations follow the same rules as people, so an integration user with admin rights or Override Period Restrictions posts through the lock. Some spend and billing tools move a backdated item to the first open period, and others stop the sync with a closed-period error. Test each connector against a locked month before you depend on it.

No one in a day-to-day role should post to a closed month. Only the controller, or the owner at a small company, approves changes. One or two named people make them, with access that ends at relock.

In QuickBooks Online, limit admin rights before you share the password, because Intuit says admins can change the closing date and password. Avoid shared logins for anyone who can post to a closed month, so every change traces to a person.

Run your system's change report, then compare the signed-off trial balance with today's for the same month: any difference is a change after close. A monthly review gives you visibility before your auditors find the change.

In Business Central, include the Allow Posting From and Allow Posting To fields in the change log so you can see who widened a posting range. A flux analysis of the signed-off and current balances shows which accounts moved and by how much.

Auditors want to see that few people can post to or reopen a closed period and that every change was approved before it happened. They also match the system's log of lock and reopen events to your approved list, so keep the evidence for each exception together.

Keep these for every period:

• Lock timestampsWhen each period was locked, closed, reopened, and relocked
• Access reportWho held admin rights, the closing date password, an override permission, or a wider posting range
• Each reopenThe request, the approval dated before the unlock, the entry with its support, and the before-and-after trial balance
• Full populationA system report of every change to a closed period
• Late-item logEvery item booked in the current month for a prior month, with its amount and running total

If you're subject to SOX, these are the records your auditors will sample, so produce them from the system rather than from memory.

A period lock policy states when each lock happens, who approves later changes, and which late items wait for the current month. It also lists the evidence you keep, so every late item gets the same answer. Copy the tables below and replace the example values with your own.

Lock calendar (example, business days after month-end)

Policy rules

Reopen request form fields

• Period and entity to reopen
• Entry, amount, and accounts affected
• Reason, with the source document
• Test result: accrual status, amount vs threshold, and any qualitative trigger
• Whether results for the period have gone outside the finance team
• Approver, approval date, and the person who will post
• Unlock time, relock time, and the reconciliations rerun

Add the lock step and the late-item review to your month-end close checklist, and place it after review in your month-end close process.

Your ERP or accounting system is the only tool that blocks a posting, and close software adds detection and workflow around that lock.

When you compare tools, ask each vendor to show a late entry posted into a locked month after sign-off. Then ask how it's flagged, who is notified, and what approval trail ends with the period relocked.

Our Close Agent works around your ERP's lock: a month can't lock in the agent until every task is signed off, and once it's locked, the agent can't change it. It reads from and posts approved entries to NetSuite, Oracle, SAP S/4HANA, Microsoft Dynamics 365, Business Central, and QuickBooks, so a late entry it prepares posts only after a named approver signs off. It runs in a dedicated AWS account we manage for you, in your own AWS account, or on-premises; explore our Close Agent to see how it fits your close.