Convert law firm operating and IOLTA trust account CSV exports into .qbo Web Connect files for QuickBooks. Build clean registers that reconcile to the penny.
No account needed for your first conversions. We never store your bank login.
Short answer: a law firm's trust account has to reconcile to the penny every month, and a bank feed that silently drops, renames or re-dates transactions is the wrong foundation for that. Export each account, operating and IOLTA, to CSV, convert it with the tool at the top of this page, and import the resulting .qbo Web Connect file into QuickBooks Online or QuickBooks Desktop. You get a complete, dated, auditable register that ties straight to the bank statement, which is the first of the three balances a trust reconciliation has to match. One file per account, no shared bank login. Last updated July 2026.
Trust accounting is the one part of a law firm's books where close enough is a bar complaint. A three-way reconciliation means three numbers agree exactly: the bank statement balance, the trust bank balance in QuickBooks, and the total of every individual client ledger added together. If any one of them is off by a dollar, the reconciliation fails, and in most states you cannot sign off on it. That standard is only reachable when the QuickBooks register is a faithful, complete copy of what the bank actually did, in the exact order and on the exact dates it happened.
Automatic bank feeds work against that. They pull roughly 90 days of history on a first connect, they can post a transaction under a cleaned-up description that no longer matches the check memo, and when a feed breaks it can leave a gap you do not notice until the month does not tie. For an operating account that is an annoyance. For an IOLTA account it is a compliance failure, because the missing item is somebody else's money. Importing a converted .qbo built from the bank's own CSV export removes that variable: every line the bank shows is a line in QuickBooks, with its real date and amount.
The other reason firms convert is history. When the bar auditor asks for the last three years of the trust account, or you take over a matter and need to rebuild a client ledger from the start, a 90 day feed cannot help. A file import has no date limit, so a full prior-year pull goes in as one file. That matters even more for QuickBooks Desktop firms after October 30, 2026, when Intuit retires Direct Connect. Web Connect, the manual .qbo import, is not affected and keeps working, so a converted .qbo remains a supported way to get transactions in.
The converter reads .csv, .txt, .xls, .xlsx and .xlsm in any column order. It handles mixed date formats, strips dollar signs and thousands separators, reads either a single signed amount column or separate debit and credit columns, and writes a valid .qbo with a unique ID on every transaction so QuickBooks can tell a re-import from genuinely new activity. You can also export the same data to XLSX or CSV when a trust ledger has to leave QuickBooks for a reconciliation workpaper or a bar submission.
| Route into QuickBooks | Complete for a trust reconciliation | History depth | Per account effort | Best for |
|---|---|---|---|---|
| Bank feed (QuickBooks Online) | Risky: gaps and renamed lines | About 90 days on first connect | Low once connected | The operating account day to day |
| Direct Connect (Desktop) | Only if the bank enrolled you | Varies by bank | Low | Nothing after October 30, 2026 |
| Native CSV upload (QuickBooks Online only) | Yes, if the file fits | Any dates | Medium, capped at 350 KB and 1,000 rows | One short statement at a time |
| Converted .qbo Web Connect file | Yes, every line the bank shows | Any dates, including prior years | Low, one file per account | Trust audits, backfills, Desktop |
| Manual entry | Yes, but error prone at volume | Any dates | High | A handful of transactions |
Built for the CSV and Excel exports US banks and cards actually send, checked before it exports.
The converter adds up the transactions it parsed and matches that to your file total before you export, so nothing is silently dropped.
Valid OFX 1.02 with QuickBooks Web Connect headers. Online and Desktop import it as a standard bank feed.
Date, description, and amount are detected for you, so you skip QuickBooks' strict 3-column and 4-column CSV layout.
Bulk upload for catch-up and cleanup work. Each file gets its own reconciliation check and its own exports.
Mixed date formats, currency symbols, and stray commas that break a raw CSV import are cleaned up before the .qbo is built.
One conversion, three files: the .qbo for QuickBooks, an XLSX to review, and a CSV for everything else.
Three steps. No column-mapping wizard.
Drag in a CSV, XLS, or XLSX export from your bank, credit card, or accounting tool. Any column order is fine.
Every transaction is parsed and checked against your file total. You see the rows before exporting.
Download the .qbo and import it as a Web Connect bank feed. Excel and CSV are in the same download.
The specifics that decide whether the import is clean. If your case is not here, message us in chat.
Create a dedicated bank account in your chart of accounts for the IOLTA balance, and a matching current liability account for the client funds you are holding. The bank account tracks the cash; the liability account tracks whose cash it is. Keep both entirely separate from operating accounts. QuickBooks has no built-in trust module, so the discipline lives in how you structure these accounts.
A three-way reconciliation proves that three balances match exactly: the bank statement, the trust bank account in QuickBooks, and the sum of every individual client ledger. All three have to agree to the penny. Most state bars require it monthly, a few quarterly, and you keep the signed report for five to seven years in case of an audit.
QuickBooks can, but it has no native trust module, so compliance depends on your setup and habits. You track each client as a customer, hold their funds in a liability account, and never let a client ledger go negative. Firms that want automated three-way reports often add a legal layer such as LeanLaw or Clio on top of QuickBooks, but the underlying bank data still has to be complete and correct.
Record a trust deposit as an increase to the IOLTA bank account and to the client trust liability, tagged to that client. When you disburse, decrease both. Because the money belongs to the client, it never touches an income account, and earned fees move to operating only after you invoice and transfer them. Tagging every line to a customer is what lets you produce a per client ledger later.
Download the IOLTA account's activity from online banking as a CSV, convert it to a .qbo above, and import that file into the trust bank register. On QuickBooks Desktop, use Banking, then Bank Feeds, then Import Web Connect File. On QuickBooks Online, upload the .qbo under the bank account. Then match each line to the correct client before you reconcile.
Use the customer field, not a separate bank account per client. Tag every trust deposit and disbursement to the matter's customer record, then run a report grouped by customer against the trust liability account to see each client's balance. The total of those balances is the third number your three-way reconciliation has to match, so it must be current before you reconcile.
No. QuickBooks Desktop cannot import a bank or credit card CSV in any version or year, including Pro, Premier and Enterprise. Its only banking import is a .qbo Web Connect file, loaded through Banking, then Bank Feeds, then Import Web Connect File. That single limitation is why converting the trust account CSV is the standard route for Desktop based firms.
Most state bars require a three-way reconciliation at least monthly, and a few allow quarterly, but monthly is the safe default. The point of doing it that often is to catch a misposted deposit or a bank fee charged to trust while the trail is still fresh. Keep every signed reconciliation report; retention rules run five to seven years after a matter closes.
Yes. Download the full date range from online banking as one CSV, convert it, and import the .qbo. File imports have no 90 day limit, so a January to December pull goes in as a single file on QuickBooks Desktop. On QuickBooks Online, watch the 350 KB and 1,000 row ceiling on manual uploads and split a busy year by quarter if a file is too large.
Direct Connect stops on that date. Any QuickBooks Desktop account that pulled transactions automatically through Direct Connect goes quiet, and Direct Connect bill pay ends with it. Web Connect .qbo imports are unaffected. In practice firms move to downloading a file each month, either as .qbo if the bank offers it or by converting the CSV the bank does offer.
Not if the date ranges do not overlap. Every transaction in a converted .qbo carries a unique ID, the same field QuickBooks checks against activity it has already seen, so a repeated import is normally recognized and skipped. The safer habit for a trust account is still to import clean, non overlapping periods and reconcile each month before importing the next.
Yes. Conversion is a file format change, not a bank connection, so you never share online banking credentials and no login token is stored. The tool reads the CSV you downloaded and writes a .qbo with the same dates, amounts and descriptions. For a trust account that separation is a feature: the only thing moving is a file you already exported yourself.
Upload a CSV or Excel export, get a QuickBooks-ready .qbo back in seconds. No card to try it.
Where to go next: firms that keep the books for several clients should read the CSV to QBO converter for accountants and bookkeepers page, high volume months are covered on the bulk CSV to QBO converter page, and the two edition specific guides are CSV to QuickBooks Online and CSV to QuickBooks Desktop. If the trust account is at a small institution with no QuickBooks feed, the credit union CSV to QBO converter page covers that case. For the Direct Connect deadline see the Direct Connect alternative page, for step by step conversion see how to convert CSV to QBO, for column layout see the QuickBooks CSV import template, and for a full backfill see importing older transactions into QuickBooks.
For the solo bookkeeper running a monthly close in QuickBooks.
USD / month
billed $288 yearly
For a firm or finance team converting across many clients and currencies.
USD / month
billed $888 yearly
For multi-bookkeeper firms managing many client books at scale.
USD / month
billed $2,988 yearly