Ask a room of business owners what’s wrong with QuickBooks and you’ll hear about the price. Ask a room of accountants and the price barely comes up. You get audit trails, journal entry visibility, account structure, and the specific things that make a file slow to review or hard to defend.
That gap is worth paying attention to, because the practitioner complaints are the ones that affect whether a set of books stands up when someone examines them.
Here’s the honest version, including the part most articles like this skip: two of the most repeated complaints are largely solved already, and one of the genuine problems is something almost nobody mentions.
“You can’t lock a period in QuickBooks Online”
Largely obsolete, and worth retiring.
The feature exists, is documented, and was renamed Lock your books in 2026 — previously Close the books, which is part of why the complaint persists. It’s in Settings → Account and settings → Advanced → Accounting. Set a lock date, and transactions on or before it can’t be changed without either a warning or a password, depending on how you configure it.
There’s also a report most firms don’t use: the Closing Date Exception Report, under Reports → Accountant Reports. It logs every transaction added, edited or deleted in a closed period. Run it monthly and you catch unauthorized prior-period changes without hunting for them.
Two real limitations remain, and they’re worth stating precisely rather than as “you can’t lock periods.”
It’s a soft lock, not a hard close. Anyone with the password can still edit a locked period. Desktop’s close was firmer. In QBO the control is the password plus the exception report — the lock deters, the report detects.
Locking is cumulative from a single date, not per period. Set the lock to 30 November and everything from January onward is locked too. You cannot lock October, leave November open, and lock September independently. For firms that close monthly and occasionally need to reopen one month, that’s a genuine constraint.
There’s a third problem that only appears with integrations: a connected app posting a back-dated transaction into a locked period can force a restatement. Bill payment and expense tools are the usual culprits. Worth testing on any client with an integration before you rely on the lock.
Related: Sync is not accuracy — the integration cleanup nobody prices for
“The audit log is useless”
Overstated — but there is a real problem underneath, and it isn’t the one people name.
What the audit log does do: records every change with the user, the date and the original transaction details. Tracks sign-ins, settings changes, edits to customers, vendors and employees, and payroll submissions. Captures deleted transactions, so a vanished invoice is findable. Flags indirect edits — changes to a transaction already on the books, such as an edited reconciliation. Drill into a transaction and you see who created it, when, and every subsequent change, with the changes highlighted.
That’s a working audit trail. The blanket dismissal isn’t fair.
What it genuinely can’t do, and these are real:
| Limitation | Consequence |
|---|---|
| History retained for two years only | See below — this is the big one |
| Only the first 300 lines print | Exporting a full log for a large file is awkward |
| No column for original creation date | You can’t easily filter for “changes made to prior-period transactions” |
| No filtering by account | Desktop could do this; QBO can’t |
| Not available via API | No programmatic monitoring of file activity |
| Sign-outs only logged on manual sign-out | Browser close and timeout aren’t recorded |
The two-year problem
QuickBooks Online keeps audit log history for two years. The IRS can look back three, six, or seven — and without limit where no return was filed. The transactions survive. The record of who changed them doesn’t.
This is the finding, and it’s the reason this section exists.
QuickBooks Online retains audit log events for two years.
View data
| Record type | Retention period |
|---|---|
| QBO audit log history | 2 years |
| IRS standard period of limitations | 3 years |
| Employment tax records | 4 years |
| Income understated by more than 25% | 6 years |
| Worthless securities / bad debt claims | 7 years |
| No return filed, or fraudulent return | Unlimited |
The IRS period of limitations is three years for most business records, six years where income is understated by more than 25%, seven years for worthless securities or bad debt claims, and unlimited where no return was filed or a return was fraudulent. Employment tax records should be kept at least four years.
So in every scenario beyond the shortest one, the record of who changed what expires before the records themselves stop mattering. If a question arises about a transaction from three years ago — an audit, a dispute, a suspected irregularity — the transaction is still there. The trail of who touched it is gone.
There’s no setting that extends this. The practical responses are limited and all of them are work: export the audit log periodically and store it outside QuickBooks, replicate the data to an external system on a schedule, or accept that beyond two years your audit trail is the transaction record alone.
Most firms have never checked, and discover it at exactly the wrong moment.
“Undeposited Funds is a dumping ground”
Misunderstood rather than broken — though the product does very little to help.
Undeposited Funds (in some places now labeled Payments to deposit) is a deliberate part of the accounts receivable workflow. Its job is to hold received customer payments until they’re grouped into a deposit matching what actually hits the bank. Three checks received Tuesday and banked together as one deposit should appear in QuickBooks as one deposit, or reconciliation becomes impossible.
The balance piles up for one reason: payments get received but never deposited. The Receive Payment step happens, the Bank Deposit step doesn’t, and the balance grows quietly. The symptom clients report is that the QuickBooks bank balance doesn’t match the bank — and the gap is sitting in an account they never deliberately set up.
The fair criticism isn’t that the account exists. It’s that it’s necessary, poorly explained inside the product, and that the screen for clearing it lacks basic sorting, filtering and grouping. Working through a large Undeposited Funds balance is more tedious than it should be.
What a firm should actually do: check the balance every month as a standing review item, not annually. A growing balance is a leading indicator that the AR workflow is being done wrong, and it’s far cheaper to correct in month two than in month fourteen.
Related: The QuickBooks mistakes that create cleanup work
The complaints that are simply true
Not everything resolves on inspection. These are real absences, not misunderstandings.
What to configure on every client file
Most of the complaints above are either avoidable or detectable if the file is set up properly at the start. This is the list.
- Enable account numbers before any real volume exists. Retrofitting is the expensive version.
- Turn on Lock your books with a password, and set the lock date as part of every close — not once a year.
- Run the Closing Date Exception Report monthly. It’s the detection half of the control and almost nobody uses it.
- Review Undeposited Funds every month. A rising balance means the AR workflow is wrong, not that the account is.
- Export the audit log on a schedule if the client is in a regulated industry, has investors, or has any reason to expect scrutiny beyond two years. Store it outside QuickBooks.
- Test integrations against the lock date before relying on it. A connected app posting into a closed period is a restatement waiting to happen.
- Document who has admin rights and why. The audit log tells you what happened; permissions determine what can happen.
- Set the closing date password separately from general admin access, so closing a period is a deliberate act.
None of it takes long on a new file. All of it is expensive to add to a file that’s been running for three years.
The short version
- Accountant complaints are about traceability and structure, not price.
- “You can’t lock a period” is obsolete. The feature exists, is called Lock your books, and pairs with a Closing Date Exception Report most firms never run. It’s a soft lock and it’s cumulative from one date — those are the real limitations.
- “The audit log is useless” is overstated. It captures users, timestamps, deletions and indirect edits, with drill-down.
- But it retains only two years of history, against IRS periods of three to seven years and unlimited in some cases. Export it if it will ever matter.
- Undeposited Funds isn’t broken, it’s a workflow step people skip. Check it monthly.
- Genuinely absent: multiple A/R and A/P accounts, permanent deletion, several report fields.
- Account numbers are off by default. Turn them on before the file has history.
Frequently asked questions
Can you lock a period in QuickBooks Online?
Yes. The feature is called Lock your books, in Settings → Account and settings → Advanced → Accounting. Set a lock date and transactions on or before it require a warning or password to change. It’s a soft lock rather than a hard close, and it applies cumulatively from a single date — you can’t lock individual months independently.
How long does QuickBooks Online keep audit log history?
Two years. Events older than that are no longer available in the audit log, even though the underlying transactions remain. Since IRS record retention periods run three to seven years and are unlimited for unfiled or fraudulent returns, firms that may need the trail beyond two years should export it periodically and store it outside QuickBooks.
What are the limitations of the QuickBooks Online audit log?
History is retained for two years, only the first 300 lines can be printed, there’s no column showing when a transaction was originally created (so filtering for prior-period changes is difficult), it can’t be filtered by account, it isn’t available via API, and sign-outs are only recorded when a user manually signs out.
Why does my Undeposited Funds balance keep growing?
Because customer payments are being received but never deposited. Undeposited Funds holds received payments until they’re grouped into a bank deposit; if the Bank Deposit step is skipped, the balance accumulates and the QuickBooks bank balance stops matching the actual bank. Review the balance monthly rather than annually.
Does QuickBooks Online have account numbers?
Yes, but they’re off by default. Enable them in Settings → Advanced → Chart of accounts → Enable account numbers. Turn them on before the file has significant history — retrofitting numbers to an established chart of accounts is considerably more work.
Can QuickBooks Online use multiple accounts receivable or accounts payable accounts?
No. QuickBooks Desktop supported multiple A/R and A/P accounts; QuickBooks Online doesn’t. Classes, locations and tags are the available workarounds, but they report differently and don’t behave like separate control accounts.
Why don’t accountants like QuickBooks Online?
The recurring practitioner complaints concern traceability and structure rather than cost: audit log retention and filtering, the soft nature of period locking, the absence of multiple A/R and A/P accounts, missing report fields, and the inability to permanently delete unused records. Several frequently repeated complaints — particularly around period locking — are outdated or resolved in settings.
QuickBooks Online ProAdvisor and Xero Certified Advisor. Leads delivery for US CPA firm engagements at Nimblechapps Finance.
Inherited files nobody set up on purpose?
Account numbers, lock dates and exception reports configured as standard at onboarding.
Book a call