# How do I close and lock a period so nobody can change the books behind it?

Applies to: United States · Updated 2026-09-18

Finish the period's close work first, then, in systems that offer one, set a lock date at the strongest protection the system has, such as a password rather than a warning. Give the power to move that date or pass the lock to one person who does not make day-to-day entries. Handle any genuine change through a recorded, time-limited exception, and check each period that the closed figures still match what you saved at close.

## Is closing a period the same as locking it?

No. Closing is accounting work: the last invoices and bills are entered, the accounts are reconciled, the numbers are reviewed and reported. Locking is an access control that keeps those finished numbers from moving afterwards. A month can be closed perfectly and still be fully editable, and the business usually finds out only when a figure it already gave to a lender or a tax preparer has changed.

So a close checklist is not the control. The control has four parts: a boundary date set in the system, a protection level on that date, a named person who can pass or move it, and a check that it held.

QuickBooks Online describes it this way: locking the books sets a lock date, and transactions on or before that date can't be changed without approval.

## How do you set the lock, and what does each setting do?

Where the lock lives, how strong it is and what it refuses all differ by system and change between versions. Each description below is from the vendor's current U.S. help for the product named. If your edition differs, check its own help before relying on the lock.

**QuickBooks Online.** Go to Account and settings, open the Advanced tab, edit the Accounting section, turn on Close the books and enter a Closing date. Then pick one of two security options:

- *Allow changes after viewing a warning.* Users see a warning but can still make the change. This is a prompt, not a lock.
- *Allow changes after viewing a warning and entering password.* Users must enter a password to make the change, and Intuit calls this the more secure option.

Intuit's page says that if someone tries to change or delete a transaction dated on or before the lock date, QuickBooks either gives a warning or asks for a password, depending on your setting, and that you can't edit transactions before the closing date. The page does not say whether a new transaction dated into the protected period is refused. Try one in your own file before you rely on the lock for new entries. Only a primary admin or company admin can change the closing date or the password, and an admin changes the password just by entering a new one. Use the password option. The warning option stops nobody who clicks through it.

**QuickBooks Desktop (Windows and Mac).** Sign in as the admin, choose Set Closing Date from the Company menu (on Mac it is under Company, then Users and Passwords), and enter both a Closing Date and a Closing Date Password. The page covers one special case. If you void a check that is dated before the closing date and uses an expense account, QuickBooks shows a message. If you select Yes, it creates two journal entries to balance the accounts the check affected, and you can still void the check either way. Neither Intuit page says which choice leaves the closed period's figures unchanged, so run the saved-report comparison described below after any such void.

**Zoho Books.** The help page lists the plans that include Transaction Locking, starting with Standard. If you can't find the screen, check your plan. Go to Accountant on the left sidebar and select Transaction Locking. You can lock individual modules, each with its own lock date, or lock all transactions at once. Each lock asks for a reason, and the screen lets you edit the lock date and the reason later. Transactions recorded before the lock date cannot be modified or deleted. If you lock module by module, any module you left unlocked is still open. Zoho Books will not lock a period that contains transactions with negative stock, meaning an item sold before it was bought, unless you change the restriction setting to allow locking with negative stock.

**Sage 50 U.S. 2026.** The Change Accounting Period command moves the current accounting period. A user who can't see the command lacks security access to it, and the current period can be moved to any period in the one or two open fiscal years. That makes access to this command override authority, so grant it on that basis. Before you rely on the current period as protection, test what your edition refuses for entries dated earlier.

**Wave.** Wave's help on editing transactions says a warning pop-up appears when an edit will affect a reconciled period. That is a warning, not a refusal, so it does not protect a period on its own. Without a lock, the parts of the control you can still run are the override and exception policy below, the saved-report comparison, and the last-modified date Wave shows on each transaction.

## What can still reach a locked period?

The routes that get around a lock are the ones people forget, because they don't pass through the screen where the lock is set.

**Override holders.** In QuickBooks Online, anyone who knows the password can get past the lock, and any admin can move the date or reset the password. For Zoho Books, the API documentation shows that a lock can carry a list of users exempted from it and a list of accounts exempted from it. Keep both lists empty unless you have decided otherwise, and check them.

**Temporary openings.** Zoho Books can partially unlock a chosen date range, and transactions in that range can be created, modified or deleted until partial unlock is disabled. Once it is disabled, the locked transactions can't be changed again. Organizations that have transactions involving inventory-tracked items cannot use partial unlock at all.

**Connected apps that can change the lock.** The Zoho Books API has endpoints to update transaction lock settings and to delete a lock, and the update endpoint uses the ZohoBooks.accountants.UPDATE scope. Give an app accountant-level scopes only if it truly needs them, and review which connected apps hold them.

**Connected apps that post transactions.** Connex, an ecommerce integration, documents in its own help article that a transaction dated inside a closed QuickBooks Online period cannot post, quoting the error QuickBooks returns, and that the order then fails to export. This can happen when a transaction syncs late or after the period is closed. What breaks is that the sale is missing from your books until someone deals with the error. Connex's suggested fixes include reopening the period, or changing the transaction's date in the integration to a date in the open period. Don't switch the lock off to clear a sync backlog. Treat each rejected posting as a request to change a locked period and send it through the exception route below.

**Recurring entries, imports, bank-feed matching and bulk-edit tools.** Test each one in your own file. With the lock on, try one of each dated before the boundary and note whether it is refused, warned or accepted. Any route that gets through goes on your monthly check.

**Reconciliation changes.** Edits that touch a reconciled period deserve the same scrutiny. The vendor pages checked do not settle whether undoing a reconciliation or editing a reconciled transaction gets past the lock, so include both in your own test. Undoing a completed reconciliation is a separate procedure.

## Who should be able to override the lock?

Two separate powers are involved. One is passing the lock for a single change, which in QuickBooks Online means knowing the password. The other is moving the boundary or changing the password, which in QuickBooks Online is limited to admins. In Zoho Books the equivalent powers are locking, unlocking, partially unlocking and adding exemptions. Zoho's help page does not say which users can do these, so check your own file's roles before you decide who holds them. The person who records transactions every day should hold none of these powers. Set up their user role accordingly (see the related question on users and permissions).

Choose one of these arrangements, write it down and name the person:

- **The owner holds it and the bookkeeper does not.** This is the strongest arrangement when the owner is not doing the entries.
- **The bookkeeper holds it under a written policy.** This works only if someone else reviews the monthly check, because the control now records changes rather than preventing them.
- **An outside accountant holds it** for post-close adjustments. This works when they are independent of the day-to-day entries.
- **Nobody holds a standing override.** The boundary moves only when it is formally advanced, and every correction is recorded in the open period.

Hold the override more tightly once a period's figures have gone out to a lender, investor or tax preparer.

Never leave the password blank, share it in a group chat or let everyone who works in the file know it. When someone who knew it leaves, have an admin set a new one.

**If one person does everything.** When a single person keeps the books and holds every credential, the override can't be separated from the person making the entries, so prevention alone can't work. Keep the password option anyway, because it forces a deliberate step. Then build the control on independent review: an outside accountant, a co-owner or a trusted adviser reviews the exceptions report and the saved-versus-current comparison described below, monthly or at least quarterly. The related question on checks for a business where one person records, pays and reconciles covers this in more depth.

## What is the right way to make a change behind the lock?

Decide which route applies before anyone touches the period:

1. **Refuse the override and correct in the open period.** Record the fix in the current period under your correction policy. Whether an error belongs in the old period or the current one is an accounting question to settle separately, and the lock should not decide it.
2. **Grant a recorded, time-limited override.** Someone requests it in writing, stating the transaction, the amount, the reason and the dates affected. The override holder approves it, and a named person makes the change. The boundary goes back on the same day, and the approval is filed with the next exceptions report.

**When an outside accountant needs to adjust a closed period:** if you control who holds admin rights, don't give the accountant admin rights or the password. The pages checked don't state what rights an invited accountant user holds in QuickBooks Online, so confirm that in your own file. The accountant sends the proposed entries. The override holder then either posts them or opens the narrowest possible window.

In Zoho Books, that window is a partial unlock for just the dates needed, with a reason entered, disabled once the entries are in. Zoho says to unlock every module the changes may affect. Partial unlock isn't available to organizations with inventory-tracked items. In QuickBooks Online, the admin moves the closing date back only as far as needed and restores it right after.

Either way, the window is not limited to the accountant. The password prompt applies only to transactions dated on or before the lock date. So while the date is moved back, every transaction after the new date is open to every user with edit rights, with no password prompt. A Zoho partial unlock likewise opens the range to every user. Keep the window short, and have the override holder confirm the result on the next check.

Every authorized change should leave a record of who asked, who approved, what changed and when the lock went back on. Without that record, a later reviewer can't tell a sanctioned correction from tampering. Zoho Books keeps a reason with each lock action and shows who locked the period, which helps, but it does not replace your own approval record.

## How do you check that a locked period has not moved?

Prevention can fail quietly, so run a detection check every period, before you advance the lock.

- **Compare against what you saved.** At close, export the closed period's trial balance, balance sheet and profit and loss. Each month, run the same reports for the same dates and compare them. Any difference means something moved behind the boundary.
- **QuickBooks Online.** Open Reports, then Standard reports, search for Exceptions to Closing Date and open it. It shows changes made after you closed your books. The audit log tracks all account activity, including changes to QuickBooks settings, and its events are available for two years.
- **Zoho Books.** Open Transaction Locking and confirm each lock date is where it should be. The help page describes that screen as showing Lock, Unlock and Edit for the lock date and reason. It does not describe an exemption list. The exempted-user and exempted-account lists appear only in the API documentation, where the lock details also name who locked the period and give the reason. To confirm those lists are empty, pull the lock details through the API.
- **Wave.** The Edit transaction pop-up shows the date a transaction was last modified.
- **Sage 50.** The current accounting period is shown at the top of the main Sage 50 window. Confirm it is where your policy says it should be.

If the check shows a change, find out what moved and who moved it through the audit trail. That investigation is its own procedure.

## When should the lock date move forward, and who moves it?

Advance the lock every period, at the same rhythm as your close, and only after that period's work is finished. QuickBooks Online lists reconciling your accounts up to the lock date as one of the review steps before you lock. Sage notes that you typically change accounting periods at the end of each period. A business that closes monthly advances the lock monthly. A lock set once and never moved leaves every recent period open while everyone believes they are protected.

Name the person who advances the lock, normally the override holder, and give it a fixed deadline, such as five business days after month end.

**Using a lock for the first time on a file with history:** place the first boundary at the end of the most recent period that is fully reconciled and has already been reported, such as your last filed tax year or your last reviewed month. Don't lock periods that still have open work. In Zoho Books, check for negative-stock transactions first, because they can block the lock. Then advance the lock one period at a time as each close finishes.

## What does a working period-protection routine look like?

An example for a small business that closes monthly. The owner is the QuickBooks Online admin and the only person who knows the closing-date password. The bookkeeper works under a non-admin role, and an outside accountant reviews quarterly.

1. **Close work finished** (bookkeeper, by business day 4). Reconciliations and review are done for the month.
2. **Reports saved** (bookkeeper, same day). Export the month's trial balance, balance sheet and profit and loss to the close folder.
3. **Check before advancing** (owner, business day 5). Rerun the prior months' reports and compare them with the saved copies. Open Exceptions to Closing Date and review settings changes in the audit log. Check the integration's error list for closed-period rejections.
4. **Lock advanced** (owner, business day 5). Move the closing date to the last day of the month and confirm the password option is still selected.
5. **Override holder.** The owner only. The password is changed whenever someone who knew it leaves.
6. **Exception record.** For each exception, log the date, requester, transaction and amount, reason, approver, the window opened and closed, and the exceptions report showing the result.
7. **Independent review** (outside accountant, quarterly). The accountant reads the exception record, the exceptions report and the saved-versus-current comparison, and signs off.

## Sources

1. Intuit Inc. — *Lock your books in QuickBooks Online*, updated 8/5/2026. https://quickbooks.intuit.com/learn-support/en-us/help-article/close-books/close-books-quickbooks-online/L59LelyPM_US_en_US
2. Intuit Inc. — *Edit your closed books in QuickBooks*, updated 8/5/2026. https://quickbooks.intuit.com/learn-support/en-us/help-article/customer-company-settings/edit-closed-books/L76xHuaZ5_US_en_US
3. Intuit Inc. — *Use the audit log in QuickBooks Online*, updated 8/4/2026. https://quickbooks.intuit.com/learn-support/en-us/help-article/audit-log/use-audit-log-quickbooks-online/L2WoVnW6I_US_en_US
4. Intuit Inc. — *Set or change the closing date and password in QuickBooks Desktop*, updated 8/4/2026. https://quickbooks.intuit.com/learn-support/en-us/help-article/close-books/set-change-closing-date-closing-date-password/L2uKHmMhZ_US_en_US
5. Zoho Corporation — *Transaction Locking, Zoho Books Help*, US edition, current release; undated. https://www.zoho.com/us/books/help/accountant/transaction-lock.html
6. Zoho Corporation — *Transaction Locking, Zoho Books API Documentation*, API v3; undated. https://www.zoho.com/books/api/v3/transaction-locking/
7. Wave Financial Inc. — *Edit a transaction*, undated. https://support.waveapps.com/hc/en-us/articles/41357148807700-Edit-a-transaction
8. The Sage Group plc — *Change Accounting Periods*, Sage 50 U.S. 2026 help, published June 17, 2026. https://help-sage50.na.sage.com/en-us/2026/Content/Banking_General_Ledger/Change_Accounting_Periods.htm
9. Connex Ecommerce — *QuickBooks Online Error - "The account period has closed and the account books cannot be updated through through the QuickBooks Services API."*, undated. https://help.connexecommerce.com/hc/the-account-period-has-closed-error-qbo

## Related questions

- [How do I set up users and permissions in my accounting file so people only see and change what they should?](https://uppago.com/resources/how-do-i-set-up-users-and-permissions-in-my-accounting-file-so-people-only-see)
- [What checks can a very small business put in place when the same person records, pays and reconciles?](https://uppago.com/resources/what-checks-can-a-very-small-business-put-in-place-when-the-same-person-records)