Getting Client Consent Before Connecting Apps to QuickBooks Online

A familiar question in bookkeeping communities: should a practice get client consent before connecting third-party apps to a client’s QuickBooks Online file? One small firm raised it recently while planning read-only connections for error checking and quarterly client snapshots. Our short answer is yes. Put it in writing before the first connection goes live.

Do you need client consent before connecting an app?

We think you do. The company file and everything in it belongs to the client. Connecting an app sends that data to another company’s servers, which is a disclosure even when the app only reads. Professional standards for accountants and bookkeepers generally expect informed consent before client data is shared with a third party. Privacy law in many jurisdictions points the same way. A signed record also protects the firm if a client later asks why an outside tool ever touched their books.

Consent form or engagement letter?

Either approach can work. An engagement letter clause covering categories of tools survives app changes without re-papering each client. A standalone consent form signed at onboarding is more precise: it names the app, the purpose, and the access level. A middle path tends to wear best. Keep a general clause in the engagement letter, then attach a short schedule of current tools that the client reviews and approves.

What should the consent cover?

Aim for one page that records five things:

• The tool’s name and vendor, plus the job it does, such as error scanning or quarterly reporting.
• The data it can reach: transactions, customer and vendor records, payroll where relevant.
• The access level, stated in writing, with read-only as the default for review work.
• Who at the firm may connect and manage the app.
• How long the connection stays active, and how the client can ask for removal.

QuickBooks Online shows authorized apps inside the company’s own app settings. The client can review that list at any time and disconnect anything they did not agree to. This visibility helps trust. It also means silent connections are not really possible, so the paperwork should match reality.

Should you connect through your accountant login or the client’s?

An app is authorized per company file, through an Intuit sign-in screen that spells out the data the app wants. Whoever completes that authorization needs sufficient permissions on the company. It is cleaner to have the client, or an admin on the client’s side, click the final authorize button. The paper trail then matches the technical one. If your firm authorizes on the client’s behalf, say so in the consent. Whichever route you use, pick the narrowest access the tool offers.

Does E&O insurance need a look first?

Ask before the first connection, not after an incident. Put three questions to your broker or carrier. Does the policy cover work performed through third-party tools? Must the tools be disclosed or named? If a vendor suffers a breach, does your coverage apply, or is it excluded? Some policies treat data incidents differently from ordinary bookkeeping errors. One short note to your broker now can prevent an unwelcome surprise later.

What if a client says no?

Refusals happen, and they are workable. Explain the purpose plainly: a read-only connection that scans for errors and builds the quarterly summary. Offer alternatives where that is not enough. You can review manual exports instead, or seek approval app by app rather than a blanket grant. Document whatever the client decides, and honor it. A client who feels steamrolled on data access rarely stays a client.

Where to start

One page is enough to begin. List the tools you plan to connect, the data each one reads, the read-only access level, and a simple disconnect request process. Have your attorney review the wording once, so the same language serves every client. Then fold it into onboarding for new clients, and send it to existing ones before the next connection goes live.