Frequently asked questions
Will I have to verify my identity every time I switch between client files?
We're working on longer-lasting sessions on trusted devices, so you'll eventually verify less often when moving between client files. Intuit Accountant Suite allows accountants to see all of their client files without switching between them.
What if I get locked out of my QuickBooks account?
We're also improving account recovery to make it more straightforward if you get locked out.
Can I control which staff can undo a reconciliation?
Undo Reconcile is now available to any Primary Admin on a company file. If your firm assigns different access levels to staff, review your admin role assignments to confirm this matches your internal controls.
What actually prevents a reconciliation from breaking after it's done?
New guardrails flag edits or deletions to previously reconciled transactions before they're saved, rather than allowing silent changes that surface later as an unexplained discrepancy.
Does QuickBooks Online flag conflicting categorization rules across a client's transactions?
Yes, the rules engine now detects when two rules would apply to the same transaction and flags the conflict instead of applying one silently.
Will migrating a client from QuickBooks Desktop bring over their categorization history?
Not yet, but groundwork toward it is underway. Full support for categorization history transfer in Desktop-to-Online migrations is one of the top priorities on the roadmap, not something shipping in this release.
What breaks when you migrate a client from QuickBooks Desktop to Online in 2026?
Reports and bank rules are the two things to plan around. Reports often need to be rebuilt rather than transferring as-is, and some bank rules don't carry over—budget time for a manual review of both after migrating. It's an active area of investment, not yet a clean one-click process.
How does the new bank matching logic work?
Matches are ranked by confidence so the likeliest match surfaces first, the search window widens automatically when no nearby match is found, and duplicate warnings appear before a transaction is posted.
Why did bill payments stop defaulting to check?
Roughly 90% of payments processed aren't check payments, so the previous default required extra correction on nearly every bill. Payment type now reflects how bills are actually being paid.
Is bank connection reliability actually fixed now?
Not entirely—this release targets the highest-volume error codes and adds earlier expiration warnings, but the underlying disconnect/reconnect cycle with some banks is a multi-quarter effort. If you manage connections across many client banks, expect continued incremental improvement rather than a single fix.
What should I watch for immediately after this release?
Review Primary Admin assignments in light of the Undo Reconcile change, and check any rule sets you've built across multiple clients for newly surfaced conflicts—both are behavior changes that affect existing setups, not just new features.