Inside LawAccounting's Overpayment, Credit Memo & Refund Engine: How Law Firms Handle Client Money That Came In Too Big Without Ever Touching Trust (2026 Feature Spotlight)

A client pays $5,000 against a $4,300 invoice. Where does the $700 go? At most firms the honest answer is: into the operating account, onto a sticky note, and into a conversation eight months later. Overpayments, duplicate payments, and credit memos are the least-designed corner of legal accounting and one of the most consequential, because the wrong handling turns a bookkeeping event into a trust violation. Here is how LawAccounting's credit engine handles it.

Published: 2026-08-31T12:44:16.499Z · Category: Legal Accounting · 9 min read

💡 IN SHORT

When a client pays more than the invoice, the excess is unearned money that belongs to the client - which means in most jurisdictions it belongs in trust, not in operating, no matter how it arrived. Generic accounting systems treat an overpayment as a customer credit and park it in a receivable contra account. Legal accounting cannot do that, because a customer credit is a commercial relationship and an unearned client balance is a fiduciary one. LawAccounting's engine routes overpayments, duplicate payments, credit memos, and refunds through a single controlled path that keeps the money identifiable, the ledger balanced, and the trust position defensible.

👥 Who should read this: Bookkeepers & Controllers Firm Administrators Managing Partners Billing Coordinators

💰 The Four Ways Money Arrives That Shouldn't Have

Overpayment is a single word covering four genuinely different events, and conflating them is where firms get into trouble.

➕

Simple Overpayment

Client rounds up, pays $5,000 on a $4,300 invoice. The $700 is unearned and belongs to the client.

👯

Duplicate Payment

Client's AP pays the same invoice twice - once by check, once by ACH. The entire second payment is unearned.

🔁

Post-Payment Adjustment

A billing error is discovered after payment. The invoice shrinks. The difference becomes an existing credit.

🎯

Misapplied Payment

Money posted to the wrong matter or the wrong client entirely. One ledger is over, another is short.

Only the third is a true credit memo in the accounting sense. The other three are unearned funds that arrived in the wrong account. The distinction determines the correct entry, and generic accounting software does not make it.

⚠️ Watch Out

The most common mistake is treating a misapplied payment as a simple journal reclassification between two client ledgers. If one of those ledgers is a trust ledger, moving money between two clients' balances - even to fix an error, even for a moment - is exactly the pattern trust rules exist to prevent. The correction has to route through the operating or trust account itself, with two documented sides, not as a ledger-to-ledger swap.

🏗️ How the Engine Is Built

🔍 Detection at the Point of Application

The engine evaluates every payment against the open invoice balance at the moment of application rather than at month-end. When a payment exceeds the applicable balance, the excess is isolated immediately and held in a distinct, identified state - not swept into a generic customer credit bucket where it loses its identity.

That isolation matters because an unidentified credit is functionally the same as an unreconciled item. Once it is in a pooled contra account, determining months later which client it belongs to is a reconstruction exercise.

🧭 Routing by Fund Character

The engine asks one question that generic systems never ask: has this money been earned?

Scenario	Correct Destination	Common Wrong Answer
Overpayment on a paid-in-full invoice	✅ Client trust ledger, or refunded	❌ Held in operating as "customer credit"
Duplicate payment	✅ Refunded promptly, documented	❌ Applied to a future invoice without authorization
Post-payment billing correction	✅ Credit memo against the invoice, then refund or trust	❌ Silent invoice edit with no audit trail
Payment posted to wrong matter	✅ Reversal and re-application, both sides logged	❌ Ledger-to-ledger transfer between clients
Advance received for future work	✅ Trust deposit with written authorization	❌ Operating deposit as "prepayment"

📝 Credit Memos With Provenance

A credit memo in LawAccounting is a first-class document, not an invoice adjustment. It carries a reason code, the originating invoice and line items, the approving user, a timestamp, and the resulting GL entries. It cannot be created without a reason, and it cannot be created by someone without the permission to create one.

This matters more than it sounds. Credit memo authority is one of the highest-risk permissions in a law firm's accounting system, because the ability to reduce a receivable without cash is the ability to conceal a shortfall. Firms that grant it broadly and log it thinly have removed a control they may not know they had.

🚫 Red Flag

If the same person can receive a payment, issue a credit memo against the invoice it paid, and initiate the refund, you have no segregation of duties on the single most exploitable path in a legal accounting system. At small firms full separation is impossible - but the compensating control is that every credit memo and refund appears on a report a partner reads, by name, every month.

💵 Refund Execution With a Closing Loop

Most systems consider a refund complete when it is issued. The engine treats issuance as the midpoint. A refund carries a status through issuance, clearing, and - if it never clears - dormancy tracking toward the unclaimed property obligation that eventually attaches. Stale refund checks are a real and commonly missed compliance exposure, and they are only visible if the refund record persists past the day it was cut.

💡 Pro Tip

Set a hard firm policy: no client credit balance survives matter closeout, and no credit balance survives ninety days regardless of matter status without a written client instruction to hold it. The instruction is the difference between holding funds at the client's direction and holding funds because it was easier than mailing a check.

🔗 Why It Only Works on a Unified Ledger

Every scenario above crosses boundaries that most firms have split across systems. Detection happens in billing. Routing depends on trust. Correction hits the general ledger. Refunds hit banking and reconciliation. Reporting has to see all four.

When a firm runs practice management in one product and accounting in QuickBooks, an overpayment becomes a manual message between two systems, and every manual message is a place the identity of the money can be lost. LawAccounting keeps the GL, the matter ledgers, the trust ledgers, billing, and bank reconciliation in one double-entry system - so an overpayment on Tuesday shows up correctly on the trial balance, the client ledger, and the trust three-way reconciliation without anyone re-keying it.

⚖️

Trust-Aware Routing

The system knows which balances are fiduciary and refuses entries that would commingle or advance across clients.

🧾

Reason-Coded Credit Memos

Every credit carries approver, reason, source invoice, and GL impact - and reports roll up by reason code.

🔄

Full Reversal, Not Deletion

Corrections are posted as reversing entries with an audit trail. Nothing is silently overwritten.

🏦

Refund Lifecycle Tracking

Issued, cleared, or stale - with dormancy aging that surfaces unclaimed property obligations before they are late.

🔎

Smart Bank Matching

AI-assisted reconciliation across 15,000+ bank connections catches the duplicate deposit before anyone notices the credit.

📊

Open Credit Balance Report

One report showing every client credit, its age, its origin, and whether it sits in trust or operating.

An unearned client balance sitting in an operating account is not a bookkeeping preference. It is the firm using client money as working capital, and the fact that it happened by accident is not a defense.

🧪 The Five-Minute Test

Run this on your current system today. Ask for a single report showing every open client credit balance, how old each one is, which invoice or payment created it, and whether the money is currently sitting in trust or operating.

If producing that requires exporting to a spreadsheet, or if the answer to "trust or operating" has to be determined by someone who remembers, the exposure is not theoretical. It is just unmeasured.

✅ Key Takeaways

"Overpayment" covers four distinct events - simple overpayment, duplicate payment, post-payment adjustment, and misapplied payment - and each requires a different entry.
Unearned client money belongs in trust or back to the client, regardless of which account it landed in. A generic "customer credit" in operating is the wrong destination.
Never correct a misapplied payment as a ledger-to-ledger transfer between two clients; route the reversal and re-application through the account with both sides documented.
Credit memo authority is one of the highest-risk permissions in legal accounting - reason-code it, restrict it, and put it on a report a partner actually reads.
A refund is not complete when issued; track it to clearing or into dormancy, because stale refund checks mature into unclaimed property obligations.

Find Every Open Client Credit in One Report

LawAccounting routes overpayments, credit memos, and refunds through a single trust-aware engine on a unified double-entry ledger - so client money never loses its identity between systems.

Schedule Your Demo →