Clio QuickBooks Integration for Law Firms: What Syncs and What You Import Yourself

Last updated September 2026.

Clio's QuickBooks Online integration syncs your billing, not your bank. Approved bills, recorded payments, contacts, trust transactions and expenses flow from Clio Manage into QuickBooks Online roughly every 30 to 60 minutes. Bank and credit card transactions are not part of that sync at all, so the statement side of the ledger still has to be imported separately. That single distinction explains most of the confusion firms hit in their first month.

What actually syncs between Clio and QuickBooks Online

Clio publishes the data flow, and it is narrower than most firms expect. Almost everything moves in one direction, from Clio Manage to QuickBooks Online. Contacts are the only two way item, and even then they only sync once the contact has an approved bill in Clio.

One more limit worth knowing before you design a chart of accounts around it: Clio syncs at the account level, not to sub-accounts inside QuickBooks. If your plan was to give every practice area its own sub-account and let the sync sort them, it will not.

Which QuickBooks Online plans does Clio work with?

Clio integrates with QuickBooks Online Essentials, Plus, and Accountant (Advanced). It does not integrate with QuickBooks Online Self-Employed or Simple Start. On Essentials specifically, two features are missing: the timekeeper sync and the import hard costs feature. If advanced client costs matter to how you bill, Essentials is the wrong tier.

What does not sync: your bank transactions

Nothing in the integration reads your bank. Clio sends what happened in Clio, QuickBooks records it, and both systems still need the actual bank activity brought in from the bank itself. In QuickBooks Online that is the bank feed or a manual CSV, QBO or QFX import. In Clio Accounting it is a Plaid connection or a manual CSV upload under Banking.

That is fine while both feeds work. It stops being fine on trust accounts, because IOLTA accounts are frequently held at small community banks and at dedicated trust products that the aggregators do not cover. When the feed is unavailable the only complete record you hold is the monthly PDF statement, and neither Clio nor QuickBooks will read a PDF. The statement has to become rows first. Our Clio bank statement converter page covers the exact CSV layouts Clio accepts, and firms keeping the general ledger in QuickBooks can turn the same statement into a bank file QuickBooks imports directly rather than mapping columns twice.

How trust transactions reach QuickBooks Online

Trust deposits, disbursements and applied trust funds export to QuickBooks Online as journal entries in the Trust Liabilities Account. You pick which Clio trust account syncs, then map it to both a QuickBooks trust bank account and a trust liability account, and set a start date. Clio supports up to 15 trust accounts on the sync.

Because those entries are journal entries rather than bank transactions, they do not clear anything. The trust bank account in QuickBooks still shows whatever the bank feed or your import put there. Reconciling means comparing three things: the bank statement, the trust bank account in QuickBooks, and the client ledger totals. If you would rather do that inside Clio, Clio Manage has a full trust reconciliation that will not let you finish until the difference is zero, and it is restricted to administrators and to current plans. The mechanics of the third leg are in our three way trust account reconciliation guide.

Two QuickBooks settings to change before you connect

Clio asks for both of these up front, and skipping them causes the duplicate bill errors that fill support tickets later. In QuickBooks Online, open Account and Settings, then Sales, edit Sales form content, and turn on Custom Transaction Numbers. Then open the Advanced tab, edit Other preferences, and turn on the warning for a bill number that has already been used for that supplier.

There is a third step that is easy to miss. If you were running QuickBooks Online before Clio, set Clio's first bill number higher than the last bill number already in QuickBooks. Both systems start their numbering at one, so without that adjustment your first synced bill collides on day one.

US firms should also leave the sales tax option "Include tax with corresponding line item" alone. Clio marks it as a Canadian setting and says explicitly not to use it if you are in the United States. Pick either the distinct line item or the aggregated line item option instead.

Import hard costs is the only sync running the other way

Hard costs are the exception. When you enable it, expenses recorded in QuickBooks Online come back into Clio so they can be billed to the right matter. Clio is direct about this being the only integration feature that sends data from QuickBooks Online to Clio.

Two conditions have to hold. In QuickBooks Online you must turn on "Track expenses and items by customer" under Bills and expenses, and only Expense and Check transaction types are imported. A bill or a journal entry will not come across. The contact attached to the cost also needs an existing matter in Clio, otherwise there is nothing for the expense to attach to.

This is where the paperwork behind advanced client costs matters. Court reporter invoices, expert fees and filing receipts are what justify the cost on a client's bill, and they are usually the least organized part of a firm's records. Pulling the line items off those documents into a spreadsheet keeps the backup attached to the number instead of in a folder somebody has to search during a fee dispute.

Clio QuickBooks sync errors and what causes them

Clio publishes the error codes with causes, which saves a support call. These four cover most of what firms actually see.

Code 620 is the one worth preventing rather than fixing, and it is the direct consequence of skipping the numbering step above.

Should a small firm run Clio Accounting or QuickBooks Online?

If the firm has an outside accountant who already works in QuickBooks, keeping the general ledger there and syncing bills and trust entries from Clio is the path of least friction. Your accountant keeps their workflow, tax preparation stays where it has always been, and Clio stays the billing and matter system.

If the firm has no outside bookkeeper and nobody wants to learn two systems, Clio Accounting keeps everything in one place and does the trust reconciliation natively. The trade is that it needs a Plaid supported bank to be effortless, which brings you back to the statement import question on the exact accounts where mistakes are most expensive.

There is no universally right answer, and firms switch. What does not change either way is that the bank statement is the source document, and getting it into columns cleanly is the step both routes depend on. Our law firm bank statement converter handles the IOLTA and operating side regardless of which ledger you land on, and converting statements for QuickBooks covers the QuickBooks route specifically.

What to do this month

Check three things before your next close. First, confirm your QuickBooks Online plan actually supports the features you enabled, because Essentials quietly lacks hard cost import. Second, look at whether every bank and trust account has a working transaction source on both sides, and note the ones that do not. Third, for any account without a feed, convert last month's PDF statement and import it now rather than at year end, when twelve months of it lands at once.