Staying on Your QuickBooks Version When Your Accountant Upgrades
A newer QuickBooks install rewrites your company file when it opens it, and there is no way back: protect your year before handing anything over.
Your accountant's new QuickBooks install is more than a cosmetic change. The moment it opens your company file, it rewrites the file to its own format, and your year will not take it back. You can still stay on your version. The file simply has to never meet the newer program, and there are three clean ways to arrange that.
Why can't the file simply come back down?
QuickBooks keeps the books in a database whose internal layout is stamped with the version that last wrote to it. When a newer program opens the file, it offers to upgrade, then rewrites the data structures to its own layout and updates the stamp. The old program sees the new stamp and refuses, with a message that the file came from a newer version.
Nothing in the product reverses that stamp. There is no Save As to an older format and no compatibility mode. One consolation exists: the newer program forces a backup before it upgrades, and that backup predates the rewrite. It restores cleanly into your year, so it is worth keeping even after a mistake.
Confirm what you are both running
Press F2 while QuickBooks is open, and the Product Information screen shows the year, edition, release, and country flavor you run. Send the accountant those four facts in writing before anything changes hands. Edition matters as much as year here: a Pro or Premier file opened in Enterprise converts to Enterprise, and that conversion is one-way too. The release, shown as an R number, is worth matching whenever a spare install comes into play.
Take a full backup regardless of the route you choose. Use File, then Back Up Company, then Create Local Backup, with complete verification turned on. Store the .QBB somewhere dated, keep the .TLG beside the working file, and restore the backup once as a test. A handoff you cannot roll back is not a handoff; it is a bet.
A version-matched accountant's copy
This is the built-in answer, and it keeps your file in your version by design. From your own install, choose File, then Accountant's Copy, then Client Activities, then Save File. Set the dividing date at the end of the period under review, typically the fiscal year end. QuickBooks verifies the data and writes a .QBX transfer file. Send that file, never the working .QBW.
The .QBX opens inside the accountant's newer Accountant's edition, which supports client copies from earlier years within a limited span. They work on transactions dated on or before the dividing date and return a .QBY change file. You import it through Import Accountant's Changes, still inside your own year. The company file itself never changes version.
The mechanism has edges. While the copy is out, you cannot edit anything dated on or before the dividing date, and you cannot condense the file or upgrade it yourself. Certain list changes also stay off limits to the accountant. Agree the dividing date before creating the copy, because cancelling the restrictions mid-engagement gets messy.
A portable file when review is all you need
When the accountant only needs to look, send a portable file. Choose File, then Create Copy, then Portable company file, and QuickBooks writes a compact .QBM. They can restore it in any version they like, including the new one, because the restore makes a separate copy. Your original never moves.
The trade is that nothing flows back. The accountant reviews, sends notes or a list of journal entries for you to key in, and the restored copy is discarded. A portable file also drops non-financial extras such as letters and logos, which is fine for review. Use this route when adjustments will be few and clearly described.
A spare install of your year on their machine
Desktop editions from different years install side by side without conflict. The accountant adds your exact year and edition to their machine, you send a .QBB, and they open it without any upgrade prompt because the version matches. Work happens in your year, and they return a .QBB that restores on your machine without ceremony.
Three cautions apply. The spare install must match the edition flavor and country edition, not just the year, or you get a different one-way conversion. A licence for the old year has to be available. And installers and patches for past years become hard to obtain once Intuit retires the download pages, so archive the setup files you would need while you still can. Remote access onto your own machine sidesteps the question entirely, since the file never travels; it only asks that your machine be on and the session secured.
If the rewrite has already happened
Stop working in the upgraded copy if returning to your year is the goal, because every day of entries deepens the hole. Hunt for the backup the newer program forced at upgrade time, and for your own scheduled backups; either restores into your old install. Re-key only what was entered after the rewrite. When no usable backup exists, the remaining route is a conversion that walks the file back down, which our engineers handle as a QuickBooks downgrade between versions. The clean outcomes all start earlier: match the method to the engagement, and keep the file away from any program newer than your own.