Clio + QuickBooks Integration: Trust Accounting Workarounds Every Legal Bookkeeper Needs

Hey everyone, welcome back to the Accountant's Law Lab. This is your go-to channel for smart, compliant law firm bookkeeping. So if you're a legal bookkeeper and you're already working with Clio Manage and QuickBooks Online, you already know this powerful combo can transform a law firm's financials, but it's rarely plug and play. Today I'm going to break down the main workarounds that you're going to need for your Clio QuickBooks integration, especially when it comes to trust accounting. Exactly why these extra steps exist due to built-in program shortfalls. Stick around because skipping these can really lead to reconciliation nightmares, maybe some duplicate entries. You ever look in the undeposited fund account and see them there? Or worse, state bar compliance issues. And don't forget to hit that like button if you're dealing with Clio and QuickBooks right now. Let's dive in. Clio is built specifically for legal practice management. It's time tracking, matter-specific billing, rock-solid client trust ledgers that follow IOLTA rules. QuickBooks Online is a general accounting powerhouse, great for profit and loss statements, balance sheets, tax prep. I like to call it the whole enchiladas where all of your data lives for your business. So the practice management tool is Clio, and Clio sits on top of it, which takes a program like QuickBooks, which is really for all types of businesses, and it makes the business legal specific. And primarily it's handling all the client-specific tasks. So when you connect them, the data flows in, but it's a one-way sync, so it doesn't always flow perfectly. The integration handles contacts, it handles invoices, some payments, but it isn't designed to fully automate legal-specific requirements like client trust level subledgers. Doesn't do that. And it does have some automatic safeguards against overdrawing trust funds. So that's a good thing. I always like to tell bookkeepers working with law firm clients that they can type whatever they want in Clio, but you have to really follow what happened at the bank level. That's really what happened. And then you have to make sure that Clio matches what happened at the bank. If you don't, then it throws it out of compliance. So— Okay. This is the real reason why legal bookkeepers end up with manual processes. Without these workarounds, you risk commingling funds, phantom revenue, we've seen that, and maybe a failing 3-way bank reconciliation during a bar audit. Yes, Clio does have a reconciliation feature. It does work. It's one of those things that has to work from the very, very beginning of using Clio and using QuickBooks, and it has to be that step-by-step starting point. If you're coming into it mid-time, maybe you had another practice management tool, you switched to Clio, it's very hard to follow and to keep track. So the three-way bank reconciliation within Clio Manage— I'm not talking about Clio Accounting here. Clio Accounting is a totally separate product. Hopefully you're not in it right now because it's not ready for prime time yet for bigger firms. It's great for one specific type of client. But if you're in Clio Manage and QuickBooks, you know what I'm talking about. So let's start with the number one pain point, which is trust accounting, right? Trust accounting in Clio and QuickBooks. Clio has some built-in protections. It won't allow you to apply more trust money than the client has, and it auto-shows trust balances on invoices. So you have that going for you. QuickBooks doesn't have these legal-specific controls. So if you try to use QuickBooks without Clio and just use it as standalone, you have to mimic all of these tasks that are handled by the software. It becomes very time-consuming. And anytime you make something that's a manual process, you're going to find that it's going to take you more time than the value— the cost of the software. It's really crazy to skip out on the software. I always say that to attorneys. I think they're saving a few dollars by not having the software, but in the long run, you're saving because the manual processes always seem to lead to problems, right? In the long haul, when you start to look at it, and whenever there's manual steps, if one step gets missed, it can really mess everything up. So even when you enable the trust transaction syncing, it often pushes everything into the trust liability account, the parent account, and it doesn't break it out into the individual matter. So that's something that we do manually. We use the reclass tool, we reclassify it down. You have to create the accounts. If you have a lot of accounts, it's better just to use the import feature in QuickBooks and import the name. So then you can populate it really quickly. Many states require that you have this separate client subledger under the trust, and it's to prove no commingling. The native syncing in Clio doesn't handle that perfectly without the extra steps. And even bank fees and IOLTA interest have to be treated as a subledger. But you can create a subledger called IOLTA interest clearing account, and then you put the interest in and out through there. It's just a clearing. Sometimes it doesn't clear out, so you wanna know that. I also make one for wire and bank fees that have to be reimbursed. I'll call it wire and bank fees to be reimbursed so that the client knows that this account has to be zero and they may have to move operating fees to cover that because you can't use other people's money to pay these fees. So if you don't use the workaround of actually syncing and moving things down into the separate trust ledgers, and we know a lot of bookkeepers that don't do this, but in some states it's required to have that visual look of it. Some states demand that, Florida being one of them. You're gonna need to have a clean 3-way bank reconciliation. So that will be the extra step, which is gonna be tying your bank statement with all the transactions in transit accounted for, your Clio trust ledger, simple report you can pull outta Clio, and your QuickBooks trust account. That if you aren't doing the subledger method, you are gonna have to filter by customer. To manage it, to show, improve the client ledgers. So the best way to do it and how we recommend doing it is to set it up and do it right. You have set up your QuickBooks chart of accounts before even connecting Clio. And if you are connecting Clio along the way at a certain date and you're going to be bringing in opening balances, you really want to put a password protect on the prior periods of QuickBooks so you don't pull in a lot of garbage when you do that migration. And then if you are using classes or locations, you want to address that as well. And then you want to put in those subaccounts. So the easiest way in the first go-round to do this is to actually bring an import in and import in all the sub-liability account names so that way you don't have to do them on the fly. It saves you a lot of time, and then you're able to push them in with the reclass tool. And then always enter your trust activity first in Clio. And that's your source of truth for your clients. And then you can come through and you're gonna sync it over and reclassify those transactions in QuickBooks. So you're gonna have a mirror image of what would the trust ledgers in QuickBooks and a mirror image of what in Clio. That's what you're going for. And then you also have to perform that 3-way bank reconciliation. Right now we're using a Google Sheet to do that. You can use Excel and create that form so that it's got the view that— If you take the time as a bookkeeper to look up where your attorney's practicing law and what the bar rules what the rules are. You want to mirror what the bar rules say to do. So depending on your state, you want to make sure that everything is tied back to exactly what they want to see. So if there ever is a random audit or an audit because somebody complained, you're like ready on the fly because they don't give you a lot of time when your client gets audited. But this extra step of pushing the data down into the liability account, the sub-liability account, is going to keep your records compliant and audit ready. So next up we're gonna talk about sync issues. So QuickBooks and Clio, the integration isn't real-time. And know that this can take up to 30 to 60 minutes, sometimes 24 hours for the initial sync. It's a slow process. That was one of the fascinating things after working with LeanLaw all the time, then I started working with Clio and I didn't realize that the sync didn't automatically happen. Some days it does, some days it doesn't. I really don't know the reason why. Sometimes it takes a bit of time before it refreshes, but then you'll know that it will show. So know that if you make edits in one, in one system, if your client makes edits, for example, Clio changes something on the invoice or something like that, it'll throw a duplicate transaction over. And if you don't have your preserved date, your data that you've already done a 3-way bank reconciliation, you don't have a password in it. You don't even have to put the password. You can just put the warning that it warns you that you have it. You don't have to put a password in, but you could have the warning in QuickBooks. And that's found under the gear and under the advanced settings. At least if you have that in place, Clio won't push in anything old. We had a client one time, we didn't have the password on, and the client made a change to an invoice, corrected it to make it look like it had been paid in a prior year. So she not only changed the data in QuickBooks, she changed the data in Clio, and she caused a lot of problems with the prior year stuff. So you really want to make sure that— Yeah. You just protect your work. It's gonna save you time in the long run. You'll be thanking me that you put those passwords on. So you wanna do the corrections and do the data cleanup in both systems before connecting them. You wanna make sure that both systems are preset and ready to go. And then when you do sync Clio to QuickBooks, you wanna make sure that the names match exactly, emails are matching. If you're gonna use batch invoice syncing instead of real-time, you wanna use the unique pre— fix to the Clio bill numbers if you're doing multiple bill types. You want to run a sync health check. Broken sync transactions, when you look into that area in Clio, you're going to see that those things are usually because the name is truncated and it doesn't— the name has too long of a name. And I've seen that it's actually not a Clio thing, it's actually a QuickBooks thing, but Clio will not push a transaction in because in Clio you can make the name pretty long,, but in QuickBooks it can only be so many characters. So it will throw a sync error and then that piece of transaction won't come through and you'd be like, what's missing here? Why didn't my 3-way match? You'll find the offending transaction. So I always go to those Clio sync errors to start and then make sure you can sync them over. So bank feeds and reconciliations can be another headache. Once connected, QuickBooks auto rules can make a nightmare. So this really isn't a Clio problem, it's the QuickBooks problem, but it can also miscategorize Clio sync transactions. And you just have to really pay attention to this. So when you connect the bank feeds in QuickBooks, make sure you've got the bank rules not so aggressive. Try not to use the auto rules for anything that has to do with a Clio payee, and try to manually match the transactions that Clio brings over. It's one of the things when they— if a client does a monthly billing and they do a monthly amount to move out of trust, It will maybe, if you have your settings set up the way they're set up, you might find that they're individually throwing each transaction into QuickBooks individually when you actually want them grouped, like the client grouped the trust transfer and put one over. So you really want to take a look at that setup and make sure that it's correct. For expenses and hard costs, you want to enter the firm expenses directly into QuickBooks and have all that set up in the Clio settings, and then import only the ones, the ones that are going to go into Clio would be the ones that are tagged to advanced client costs. And then you want to track all of that. Make sure that if you are working in a state or your client works in a state where you really need to track multiple locations, make sure in QuickBooks you have the location tracking on. Make sure if you're using it, you're also using class tracking. If you have multiple attorneys and you want to track data by the attorneys, you really want to have class tracking turned on too. So it's important to make sure you've got the filtering set up so you can pull reports of that nature. So it's important to really take a look at all of these settings. And these are just a few of the workarounds. And there's some other, sometimes if somebody's moving a transaction from Matter to Matter, you got one client, multiple Matters, and you move them Matter to Matter, it's going to throw a transaction that you just need to simply zero out in Clio. This is just some of the things you might find that you're going to have to deal with when you do this kind of integrating of Clio. We recommend you integrate Clio. I think it's important to. I don't think it's a great practice not to have them. I know a lot of people People like to leave it standalone, then they end up doing redundant work because it's not connected. And they bring in all their data as deposits in a cash basis way. I think it's better to have QuickBooks and Clio synchronized and Clio invoices coming in and the payments coming in. It's tracked that way. I think it's a better, more pure way, more accurate, accurate way to present the data to a client. And I don't think you should be afraid of that. And if you are, come and join us at the Law Lab. We'll help you out. We take once a month, we do an Ask Me Anything, and we've helped our members by logging in and actually working on their data files and help them get things set up the right way. Clio QuickBooks synchronization or integration is one of those topics that gets brought up over and over again 'cause people really struggle with it. So I hope this video helped. And until next week, we'll see you all. More Clio this month, so don't miss out. Bye. Bye now. Bye.