Who owns the client’s QuickBooks file?

The client’s financial data is the client’s. That part isn’t seriously disputed.

What gets disputed — and what turns into the standoffs that fill accounting forums — is that “the QuickBooks file” isn’t one thing. It’s three, and they have different owners:

Almost every “my bookkeeper won’t give me my books” dispute is a collision between the first and the second. The client is right that the data is theirs. The bookkeeper is right that the subscription is in their name. Both can be true simultaneously, and the disagreement isn’t really about ownership at all — it’s about access.

This page works through what professional standards actually require, what Intuit will and won’t do, the mechanics of transferring a QBO company cleanly, and the engagement-letter terms that stop the question arising.

What do professional standards say about returning client records?

For CPAs, this is settled and has been for years. The AICPA Code of Professional Conduct treats withholding client records after a demand as an act discreditable to the profession under Rule 501, and Interpretation 501-1 sets out how to respond to a records request.

Records fall into categories, and the obligation differs by category:

Three points do most of the work in a real dispute.

An unpaid fee is not a reason to withhold client records. The professional standard is explicit: the obligation stands regardless of an outstanding balance. Even where a state statute grants a lien over records in the firm’s possession, that doesn’t alter the ethical position. Withholding records as leverage in a fee dispute is precisely what the interpretation exists to prevent.

State boards are often stricter than the AICPA. Many prohibit withholding any client record over a fee dispute. Where the rules differ, the more restrictive one governs, and a state board can suspend or revoke a license over it.

The firm generally can’t charge for the initial retrieval and return. Locating and releasing records the client is entitled to isn’t billable professional time.

There is a narrower point worth knowing: a firm is generally not obliged to hand over a specific work product — a completed audit report, say — where fees for that specific engagement are unpaid. That’s a different thing from withholding the client’s own books, and the distinction is where most of the confusion sits.

But what if the bookkeeper isn’t a CPA?

This is the part the professional-standards discussion usually skips, and it’s the reason so many of these disputes go nowhere.

Rule 501 binds AICPA members and, by extension, licensees in states that have adopted the AICPA Code. A non-CPA bookkeeper — no license, no membership, no state board oversight — is not bound by it. There is no ethics complaint to file and no license to put at risk.

For that relationship, the only enforceable terms are whatever the engagement letter says. If there isn’t one, or it’s silent on records and access, the client’s position rests on contract and property law rather than professional conduct rules, and that is a slower and more expensive road.

Will Intuit step in?

Almost certainly not, and planning on the assumption that it will is how people lose weeks.

Guidance in Intuit’s own community forum puts it directly: where the current bookkeeper holds the primary admin role, the route is to ask them to transfer it, because Intuit will not interfere in the dispute. That’s a support-channel answer rather than a published policy document, so treat it as a strong indication of how these requests are handled in practice rather than as a contractual term.

The underlying logic is straightforward regardless of where it’s written down. Intuit administers accounts. It has no way to adjudicate a commercial dispute between two parties it isn’t part of, and no basis on which to strip a role from the person who currently holds it. Support can explain how a transfer works. Executing one over the current holder’s objection is a different thing entirely.

Where accounts do get recovered, it tends to be on documentary proof of authority over the entity — evidence that the person asking controls the business — rather than on an argument about who deserves access. That is a slower route than a cooperative transfer, and it depends on having the corporate documentation to hand.

The practical conclusion: the leverage is in the setup, not the escalation. Once someone else holds primary admin and won’t release it, the available routes are their cooperation, a legal one, or rebuilding the books elsewhere.

What Intuit itself says about firms holding primary admin

Worth quoting the position plainly, because it settles the argument. From Intuit’s own accountant documentation, on firms holding the primary admin role on a client’s company:

Intuit describes it as not a recommended state to be in, warns that a firm holding primary admin can cause unforeseen and wide-reaching issues in the client account, and states that it is not recommended for firms to be the primary admin.

That’s the vendor telling firms not to do the thing that causes these disputes.

The right configuration is straightforward:

• The client is primary admin. It’s their entity and their data.
• The firm is added as an accountant user, which grants the access needed to do the work.
• Billing can sit wherever commercially suits — it’s a separate setting, covered next.

A firm holding primary admin gains nothing operationally. Accountant-user access already covers the work. What it does create is a single point of failure at exactly the moment a relationship ends badly.

Admin rights and billing are two different things

These get conflated constantly, and untangling them resolves a good share of disputes on its own.

Primary admin controls users, permissions and data management. Billing determines who pays Intuit. They transfer separately, by different routes, and either can sit with either party.

Transferring primary admin to the client

From QuickBooks Online Accountant, as primary admin on the client’s company:

The transfer isn’t complete until the client accepts. If they don’t act on the email, the role stays where it was.

Transferring billing

Separate route, and note the deadline. If the client currently pays and wants the firm to take over, the client initiates: Settings, then Subscriptions and billing, then Allow billing transfer to your accountant, then select the firm and confirm. Once permission is given, the firm has 48 hours to complete the transfer before it lapses.

Moving billing the other way — firm-billed back to client — the client needs removing from the firm’s wholesale billing account, after which they enter their own payment details.

One detail worth knowing if a client is moving between firms: if the new firm adds them to ProAdvisor Preferred Pricing within 60 days of the previous firm ceasing to pay, they keep the program pricing. Outside that window, standard rates.

Desktop is a different problem

Everything above concerns QuickBooks Online, where the dispute is over an account and a role. Desktop is a different shape.

A Desktop company file is a file. It sits on a machine or a server. Whoever has the file has the data, and it can be copied. There is no primary admin to transfer and no vendor account to argue about.

That makes Desktop simultaneously easier and harder. Easier because a client with a copy of the .QBW is in possession of their books and needs nobody’s permission. Harder because if the bookkeeper holds the only copy on their own hardware, there is no administrative route at all — no Intuit setting to change, nothing to escalate.

The Accountant’s Copy adds a further wrinkle. It is a restricted working file, not a full company file — it exists so an accountant can work on a period while the client keeps operating, and it limits what can be changed and over which dates. Receiving one is not the same as receiving your books. If a handover produces an Accountant’s Copy rather than a company file, ask for the company file.

For any Desktop client, the practical protection is simply that the client holds a current backup, refreshed on a schedule, stored somewhere the bookkeeper cannot reach. That single habit renders the whole dispute moot.

Related: QuickBooks Desktop is being sunset — your migration plan starts now

What the engagement letter should cover

Cheapest possible insurance. Every clause below exists because its absence has produced a dispute somewhere.

If you’re a client rather than a firm, those eight points are also your checklist for reading someone else’s engagement letter before signing.

Related: How engagement models work

If you’re the client and access is being withheld

In order, and pausing at each step.

The short version

• The data is the client’s. The subscription and the workpapers may not be. Most disputes are that collision.
• Under AICPA Rule 501, withholding client records after a demand is an act discreditable. An unpaid fee is not a defense. State boards are frequently stricter.
• Workpapers are the firm’s property and don’t have to be handed over.
• A non-CPA bookkeeper isn’t bound by any of it. Only the engagement letter is.
• Intuit will not arbitrate. It administers accounts; it doesn’t decide who’s entitled to one.
• Intuit itself says firms shouldn’t hold primary admin. Client as primary admin, firm as accountant user.
• Admin rights and billing transfer separately. Billing permission expires after 48 hours.
• Desktop has no admin to transfer — the protection is a client-held backup.
• Eight clauses in an engagement letter prevent nearly all of this.

Frequently asked questions