A Bookkeeper's Guide to Preserving QuickBooks Records for Departing Clients

Most firms handle client offboarding well right up to the file. Final invoice, access changes, a handoff email, done. Record preservation, the part that protects you long after the relationship ends, is usually improvised at the last minute, if it happens at all. The fix is to stop treating it as a scramble and make it a standing step in your disengagement workflow, with a defined package you pull for every departing client and a point in the process where you pull it.

Why this protects the practitioner, not only the client

It is easy to frame preservation as a courtesy to the client. The stronger reason is self-interest. The request for old records almost never arrives while the engagement is active. It arrives a year or two later, and it lands on you.

A former client's new accountant calls with a question about how a prior period was handled. A lender doing diligence on a sale wants the workpapers behind a figure. A fee dispute or a board complaint surfaces and someone wants to see what you actually did and when. In an examination, the IRS requests the records that support the return, and if you prepared the books, you are the one who can produce them, or explain why you cannot. Answering any of that from a complete archive is routine. Answering it from memory, after the client's QuickBooks company has been deleted, is the situation you want to design out of your practice.

Your own workpaper obligations point the same direction. How long you must retain client records, and what you hand back versus keep, is set by your engagement letter and your state board's rules, not by QuickBooks or the IRS. Both vary, so the working posture is to check your board's retention requirements and your engagement letter's language and let those define your policy; treat that as an operational note rather than legal advice. A standard preservation package is how you satisfy whatever those rules turn out to require without reconstructing it under pressure each time.

When to pull it: before access is removed

The timing rule is simple and it is the part firms get wrong. Pull the archive before access ends, not after you learn you need it.

An engagement can close off the file two ways. The client removes you as the accountant user, and your view of the company ends that day. Or the client cancels the subscription to stop paying for software they no longer use, which starts Intuit's deletion clock. For a paid subscription, QuickBooks keeps the company in read-only mode for 12 months and then deletes it permanently; a cancelled trial gets only 90 days. That clock runs on the client's schedule, whether or not you are still on the file, and reactivation only works while the window is open. Once it closes, the company is gone for everyone.

So the trigger for pulling the package is any signal the engagement is ending, not the client's cancellation date. By the time cancellation happens you may already be off the file. Our guide on archiving a client's file as you offboard them covers the three ways an engagement ends and why each one argues for pulling early.

The standard preservation package

Define one package and pull the same set every time, adjusting only for whether the client ran payroll. At minimum it contains:

• The full general ledger for the company's entire history, in both cash and accrual basis where the client ever reported on a basis different from how the books were kept.
• Each fiscal year's profit and loss, balance sheet, and trial balance, again in both bases where it applies, with the trial balance as your reconciliation anchor.
• Every attachment, under its original filename, indexed to the transaction it supports.
• The audit log, which records who changed what and when.
• Filed payroll returns and year-end forms with the detail behind them, if the client ran QuickBooks Payroll.
• The master lists: chart of accounts, customers, vendors, employees, products and services, and recurring templates.

Two of these have handling notes worth building into the procedure. The audit log exports as CSV only, 150 rows at a time, and Intuit retains it for just two years, so it is already degrading on any client with real history; pull it first. Attachments are the other trap: the bulk receipt export gives you the files, but Intuit's documentation says they come out separated from the transactions they were attached to, so rebuilding the index that maps each document to its entry has to happen while you can still open the transactions. Keep in mind too that QuickBooks' Export Data feature does not include the audit log, omits attachments, estimates, purchase orders, statements, and recurring templates, and will not send a P&L to CSV, so the package comes together over several exports rather than one. The client-facing version of this pull-list, sequenced by what expires soonest, is in what to pull when a client is closing their business.

The retention windows are what justify capturing all of it rather than the final year. The IRS generally expects records kept three years, up to six where more than 25% of income was omitted and seven for certain bad-debt or worthless-securities claims, with employment tax records on a four-year window and no limit where a return was fraudulent or never filed. Those obligations belong to the client, but you are frequently the one asked to help meet them.

Making it a deliverable

(What that deliverable should contain, pillar by pillar, is the subject of giving a departing client an audit-ready copy of their books.)

A folder of exports is not a deliverable; a package a third party can trust is. Wrap the archive in three things. A cover memo stating what the archive contains, the period it covers, the basis of each report set, and the date it was pulled. Verification counts, so the archive can be trusted rather than just accepted: attachments captured against attachments in the file, the general ledger tied to the trial balance, and a sample of receipts opened to confirm they match the entries they document. And a delivery record: how the client received it and a short sign-off confirming they did, which closes the loop if anyone later asks whether the records were handed over. Keep a copy in your own workpapers per your retention policy at the same time.

Bill it as final work

The last point is a practice-management one. Assembling, verifying, and delivering this package is real professional work, and it is billable as the final line on the engagement rather than something you absorb as unpaid overhead. Framed to the client as a durable archive that protects their retention obligations, it reads as value delivered, and the fee reflects the hours it genuinely takes to pull years of books cleanly and prove they tie out.

If building that package by hand across a client's full history is more than you want inside a closing engagement, that is the archive we build for you: the full ledger, every report in cash and accrual, every attachment still linked to its transaction, the audit log, and payroll reports where they apply, verified against the live company and delivered as a single file with a cover summary you can pass straight to the client, or rebrand and bill as your own final deliverable. It runs off a free accountant-user seat, so you can order it before the read-only window closes on any client you are offboarding. For the underlying tax windows your clients carry, our guide on how long to keep business records after closing breaks them down by situation.