What we do
Tools
Industries
Department
How we workLet's talk →
Home/QuickBooks/Clio QuickBooks Integration and Trust Mapping
Clio + QuickBooks Online

Clio QuickBooks Integration: Mapping Trust Accounts So the Books Agree With Clio

The integration is switched on, the first retainer has synced, and it shows up in QuickBooks as income. That's a mapping problem, not a sync problem, and it's worth fixing before a second deposit follows it. Clio's own integration sends contacts, approved bills, payments, expenses and trust transactions from Clio to QuickBooks Online. Very little comes back the other way, which is why trust money has to be entered in Clio and only in Clio.

What Clio sends to QuickBooks Online, and what stays in Clio

Clio to QuickBooks Online

Sent across by the sync

  • Contacts.
  • Approved bills and credit notes, and payments recorded in Clio.
  • Expenses.
  • Trust transactions, for each Clio trust account you map, up to 15.
Not synced, or one way only

Kept in Clio, or by hand

  • Client-level trust ledgers. QuickBooks receives transactions at the account level, not into per-client sub-accounts.
  • Anything typed straight into QuickBooks, with one exception: hard-cost expenses recorded in QuickBooks can be imported into Clio.
  • Three-way trust reconciliation, which runs in Clio Manage itself.
  • QuickBooks Desktop. There's no live sync; Clio exports IIF files you import by hand.

Treat Clio as the place trust money is recorded and QuickBooks Online as the place the firm's books are reported. A trust disbursement entered in QuickBooks first is how the two start to disagree.

Setting up trust accounts for the Clio sync

QuickBooks Online first, then Clio's QuickBooks Online sync settings.

  1. 1

    Create the trust bank account in QuickBooks Online

    Add it as a Bank account with the detail type Trust account. One per real trust bank account the firm holds.

    Watch for: the detail type. Clio only lists QuickBooks accounts set to Trust account when you go to map them, so a plain checking account won't appear.

  2. 2

    Create the matching trust liability account

    Add an Other Current Liabilities account with the detail type Trust Accounts - Liabilities. This is where money held for clients sits, and it's what deposits should post against, not income.

  3. 3

    Pair each Clio trust account with its two QuickBooks accounts

    In Clio's QuickBooks Online settings, pick the Clio trust account, then the QuickBooks bank account and the trust liability account that go with it. Repeat for each trust account, up to 15.

  4. 4

    Test with one small deposit

    Record a small trust deposit in Clio and wait for it to sync. In QuickBooks it should raise the trust bank account and the trust liability account together, with nothing touching income.

  5. 5

    Agree who enters what

    All trust receipts, transfers and disbursements go into Clio. QuickBooks Online is for the operating side: overhead, payroll and the firm's own bank accounts.

Trust entries that put Clio and QuickBooks out of step

Retainers posting to income

How you'll know: The Profit and Loss shows a jump in revenue the month large retainers came in, before any work was billed.

Fix: Remap the Clio trust account to the trust liability account in the sync settings, then have your accountant correct the entries already posted.

Disbursements typed into QuickBooks

How you'll know: The trust bank balance in QuickBooks is lower than Clio's, and Clio's client ledgers don't show the payment.

Fix: Record the disbursement in Clio so it reaches the client ledger and syncs across, then remove the QuickBooks-side entry once you've confirmed the synced one.

Expecting per-client detail in QuickBooks

How you'll know: Someone is keeping client sub-accounts in QuickBooks by hand, and they never quite match Clio.

Fix: Clio holds the client ledgers and runs the three-way reconciliation, while QuickBooks gets account-level totals. Trust rules vary by state, so confirm with your state bar's rules and your accountant what your records must show, and where.

Running QuickBooks Desktop

How you'll know: There's no Desktop option in Clio's sync settings.

Fix: Use Clio's IIF export: in Clio Manage, Accounts > Export transactions, choose the bank account, date range and QuickBooks format, then import the file into Desktop. Desktop won't stop you importing the same file twice, so keep a log of what's been imported.

Clio and QuickBooks, before and after the sync is on

Does Clio integrate with QuickBooks?

Yes, with QuickBooks Online, through Clio's own integration rather than a third-party app. It sends contacts, approved bills, payments, expenses and trust transactions from Clio to QuickBooks. QuickBooks Desktop is handled by IIF export instead.

Is Clio itself accounting software, or do I still need QuickBooks?

Clio Manage is practice management with billing and trust accounting, including client ledgers and trust reconciliation. Clio also offers Clio Accounting on some plans. Firms that keep their general ledger, payroll and tax reporting in QuickBooks run it next to Clio, with the integration carrying Clio's side across.

How does Clio's QuickBooks trust accounting sync actually work?

Each Clio trust account is paired with a QuickBooks Online trust bank account and a trust liability account. Trust transactions entered in Clio then sync across to those two accounts. The client-by-client detail stays in Clio's trust ledgers; QuickBooks holds the totals.

Does Clio's QuickBooks integration work with QuickBooks Desktop?

Not as a live sync. Clio exports transactions and bills as IIF files from Clio Manage, and you import them into QuickBooks Desktop yourself, once per period.

Who builds reporting that puts Clio matters next to QuickBooks numbers?

That reporting is an n-frames build. Because the sync posts at the account level, QuickBooks Online can't break fees down by practice area, attorney or matter type. We read matters and billing from Clio's API and the firm's figures from QuickBooks Online's, and combine them in one report, leaving the native sync exactly as it posts today.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.