Recording LawPay deposits in QuickBooks: fees, trust and operating

The short answer

LawPay deposits the full payment amount into the trust or operating account you designated, with no processing fee taken off the top. Fees are debited separately from the operating account at the end of the month, never from trust. LawPay built this split specifically so a credit card fee can never shrink a client's trust balance.

QuickBooks Online doesn't know any of that on its own. LawPay's integration uploads transactions into a LawPay Clearing account and labels them Uncategorized Income by default, so someone still has to tell QuickBooks which deposits are trust, which are earned fees, and that the month-end fee debit is a firm expense, not a trust transaction. Getting that classification wrong is what breaks a three-way reconciliation.

This post walks through how the integration actually moves data, the journal entries for a trust deposit, an operating deposit and the fee debit, and the monthly workflow that keeps the clearing account at zero. It's part of our coverage of law firm accounting and bookkeeping services, and of our complete guide to bookkeeping for law firms. For the account structure behind the trust side of this, see our guide to setting up IOLTA trust accounting in QuickBooks Online.

How the QuickBooks Online integration actually works

Connect LawPay to QuickBooks Online from LawPay's Connections Manager, and LawPay creates a LawPay Clearing account in your chart of accounts. Transactions upload automatically to that account by the following business day (LawPay help center).

Two things about that upload matter for how you work with it:

• Everything lands as Uncategorized Income first. LawPay's own documentation says uploaded transactions are categorized in QuickBooks as Uncategorized Income, specifically so they show up in revenue reports pending review, not because they're actually all revenue. A trust deposit sitting in Uncategorized Income is not yet correctly booked.

• The bank feed side needs matching too. LawPay's instructions have you categorize the bank deposit in your QuickBooks bank feed to the LawPay Clearing account, ideally via a saved rule, so the clearing account can reconcile both sides: what LawPay says it sent, and what the bank actually received.

The clearing account is a holding pen, not a destination. Every transaction that lands there needs to move to its real account, a trust liability, an income account, or an expense, before the books reflect reality. Left alone, the clearing account becomes a growing pile of unclassified deposits that nobody can explain by month three.

Why fees never touch trust

This is LawPay's core design decision, not an accident of how QuickBooks happens to record things. On its own compliance page, LawPay states it directly: "the full payment amount is deposited... At the end of the month, we debit your operating account for all processing fees incurred that month. We never debit your trust account" (LawPay).

That matters because most card processors do the opposite by default: they net the fee off the top before the money ever lands anywhere, which is fine for a business account and a compliance problem for a trust account. If a $3,000 retainer arrives with a $90 fee already subtracted, the client's trust ledger should show $3,000, but only $2,910 actually hit the bank, a reconciling gap of exactly the fee amount, repeated on every card payment. LawPay avoids this by routing fees to operating separately, so the full amount you record as the trust deposit is also the full amount that hits the trust bank account.

Your job in QuickBooks is to preserve that separation, not recreate the netting problem by accident during classification. LawPay doesn't publish a standard processing rate; it's set per merchant account, so don't assume a fixed percentage when you're reconciling.

Recording a trust deposit

A client pays a $3,000 retainer by card, routed to your trust account in LawPay.

Uncategorized Income is only a placeholder here; by the time entry 3 clears it, no part of this has actually touched a real income account. The money isn't the firm's yet; it's a liability you owe the client until it's earned and billed. If you're tracking trust by client, the credit to the trust liability needs to identify which client and matter, whether that's a sub-account, a class, or a customer tag, so the ledger behind your three-way reconciliation actually supports it.

Some firms skip LawPay's clearing-account workflow and post bank feed deposits straight to the trust liability instead, matching entries 1 through 3 into one step. The end result is the same as long as nothing gets missed. The clearing account's real value is catching deposits that stall partway through reclassification, since an uncleared balance there is a visible flag that something is still sitting in Uncategorized Income.

Recording an operating deposit, and the fee debit

An operating deposit follows the same clearing-account path, but lands somewhere different. A client pays a $1,200 invoice by card, routed to operating:

Use the full amount here too. Don't reduce it for the processing fee you know is coming; that fee is unrelated to this specific payment in your books, even though LawPay may calculate it per transaction behind the scenes.

The fee debit arrives separately, usually once a month, as a withdrawal from your operating account:

This entry never references trust, a client, or a matter. It's a firm overhead expense, the same category as any other bank or processor fee. If it shows up in your bank feed, categorize it directly to the expense account; don't route it through the LawPay Clearing account, since clearing exists for payments you received, not fees you paid.

A practical monthly workflow

1. Confirm every LawPay batch landed in the correct real-world bank account, trust or operating, matching what LawPay shows against what the bank shows.

2. In the QuickBooks bank feed, match or categorize each deposit to the LawPay Clearing account, or set up a rule so this happens automatically.

3. Clear each transaction out of LawPay Clearing and Uncategorized Income into its real destination: client trust liability for trust money, income or accounts receivable for operating money, with client and matter detail on the trust side.

4. Record the month's fee debit as a merchant processing expense against operating, never against trust or a client ledger.

5. Reconcile the trust bank account and the operating bank account separately.

6. Run the three-way trust reconciliation (bank statement, trust ledger, sum of client ledgers) and keep the written record your state bar expects.

Done consistently, the LawPay Clearing account returns to zero every month, Uncategorized Income doesn't accumulate stale balances, and the fee expense shows up on the P&L where it belongs.

Common mistakes, and why each one matters

Every one of these surfaces eventually, in a bank reconciliation, a three-way, or a bar review. None of them are LawPay's fault; they're classification steps a person still has to get right after the integration hands off the data.

How Numetix handles this for firms

Numetix runs the monthly workflow above for founder-led law firms using LawPay with QuickBooks Online, directly or through a practice management platform's LawPay integration (PracticePanther's, for example, still supports it alongside its newer PantherPayments option). AI handles matching and categorization; a CPA-overseen finance team confirms every trust deposit lands in the right client's liability and signs off the three-way reconciliation.

We map the LawPay Clearing account and your trust and operating banks correctly from the start, classify every deposit with client and matter detail where it's needed, and book fee debits as pure operating expense. The integration removes the manual entry; the classification judgment is what we own so your firm doesn't have to.

A practical first step: send us your LawPay Clearing account balance and your last trust reconciliation. If the clearing account isn't sitting at zero, we'll show you what's stuck in it and why. Book 30 minutes with our team. More on how Numetix serves law firms.

Frequently asked questions

Does LawPay deduct processing fees from trust deposits? No. LawPay deposits the full payment amount into the account you designated and debits all processing fees from your operating account separately, at the end of the month, by its own design.

What is the LawPay Clearing account in QuickBooks? An account LawPay's QuickBooks Online integration creates automatically to hold uploaded transactions before you reclassify them to their real destination, trust liability, income or accounts receivable.

Why do LawPay transactions show up as Uncategorized Income? LawPay categorizes uploads that way by default so they appear in revenue reports for review. It doesn't mean the money is actually income; a trust deposit still needs to be reclassified to a liability account.

Can a LawPay fee debit ever touch the trust account? It shouldn't, by LawPay's own design and by trust accounting rules generally. If you ever see a fee debit against trust, that's a configuration or classification error to fix immediately, not a normal LawPay behavior.

Does PracticePanther still work with LawPay? Yes. PracticePanther has its own newer payment option, PantherPayments, but existing LawPay integrations continue to work alongside it.

Do I need to use the LawPay Clearing account, or can I reconcile directly? The clearing account is LawPay's recommended workflow and makes stalled or missed deposits easier to spot, but firms that reconcile bank feed deposits directly to their final accounts can get the same result if nothing gets missed along the way.