Reconcile your trust account, and keep the audit trail.
LedgerGuard runs an independent, fail-closed reconciliation of your client trust account against the bank statement, matches every transaction, names every unmatched item, and stamps a tamper-evident receipt on every run. Not a spreadsheet you have to defend to a bar auditor, a reconciliation record with a receipt attached.
Book a trust-reconciliation pilot See a sample reconciliation record
THE PROBLEM
Every month your client trust account has to reconcile, to the penny, against the bank statement, and unlike the rest of your books this one is not a bookkeeping question, it is a bar-discipline question. A deposit that never cleared, a disbursement that was recorded but not cashed, a client balance that quietly went negative, a fee moved out of trust a day too early, these are the errors that turn into a shortfall, and a shortfall in an IOLTA account is a reportable event, not a rounding note. The trust module in your practice-management tool records the ledger and then lets you type in a reconciliation, but it does not re-derive the number for you and it does not leave a receipt, so when a bar auditor or a client asks you to prove the account is clean, what you have is a spreadsheet nobody independently checked. And the newer wrinkle is the same one everyone else is living with, software (and increasingly AI) now touches the ledger, so a confidently wrong reconciliation can sail through with every box green.
HOW IT WORKS
LedgerGuard does not replace your bookkeeping, and it does not ask you to change your workflow, it sits on top of the trust ledger you already keep. It pulls the trust ledger transactions and the bank statement for the period, matches them, derives the reconciled balance from the source data (the outstanding deposits and outstanding disbursements included), and then persists a reconciliation record and flags every unmatched item for your review. It never moves money, it never disburses from trust, it only reads, reconciles, and records. Every run is wrapped in an audit-trail entry (retained, and redacted of anything sensitive), so the reconciliation and the proof that it ran are one artifact. And it is fail-closed by construction, if it cannot complete a reconciliation it reports the account as not reconciled, it never green-stamps a balance it could not actually derive.
WHAT YOU GET (the reconciliation record)
For every trust account, every period, an auditable artifact: - the reconciled result, balanced or not, with the bank balance, the ledger balance, and the adjusted balance shown side by side, - every unmatched item named, the outstanding deposits and the outstanding disbursements, so the follow-up is obvious rather than a hunt, - the difference, if the account does not tie, stated plainly rather than buried, - an audit-trail receipt stamped on the run itself, so the record and the proof it was produced travel together.
A reconciliation you can hand to a bar auditor or a client, not a spreadsheet you have to reopen and re-explain.
WHO IT'S FOR
Solo and small-firm attorneys and their bookkeepers who hold client money in an IOLTA trust account and are personally on the hook for reconciling it, firm administrators and legal-accounting staff who run the monthly three-way reconciliation, and fractional legal-bookkeepers reconciling trust across several firms. Not for firms that hold no client funds in trust, and not for anyone who does not already run a formal monthly trust reconciliation.
PRICING
Prices are hypotheses we want to test with you, not commitments, and we price the ladder rather than a single number.
- Pilot, a fixed-price paid proof on your own recent monthly reconciliations, so you see the records, the flagged items, and the receipts before you commit. - Per reconciliation, once the pilot proves the receipt, priced per trust account per month while your ledger keeps running. - Platform, license the reconciliation-with-audit-trail into a practice-management or legal-bookkeeping stack, priced by volume.
IP is licensed, never assigned. The workflow stays ours, the proof is yours. Any step that would take your money is gated and confirmed before it runs, nothing charges silently, and nothing ever touches or moves the trust funds themselves.
THE PROOF (dogfood)
We run this discipline on ourselves before we sell it. The reconciliation engine underneath LedgerGuard is the same one AYA's own SCE ledger patterns use, so it reconciles our own ledger fixtures the same way it would reconcile your trust account, it is producer-agnostic at the ledger seam. And this product's own build left a receipt of exactly the kind it sells, the deliverable already existed as a live pattern (we reused it, we did not rebuild it), the four atoms it composes were confirmed to resolve on disk, the pattern JSON validates, and the one change we made (marking it auditable so the audit-trail receipt attaches on every run) is a visible edit anyone can inspect. The product is a reconciliation with a receipt, and building it produced a receipt.
HONEST NOTE
We would rather under-promise. LedgerGuard's deliverable is a real, live workflow that reconciles a trust ledger against a bank statement, flags the unmatched items, persists the record, and now stamps an audit-trail receipt on every run, and its parts are all confirmed on disk. What it has NOT done yet is run inside a booted system or against a real firm's trust ledger and bank statement, the workflow is wired at the pattern layer and structurally verified, but a live ledger connection and a first real batch of a firm's monthly trust reconciliations are still owed, and we will say so plainly rather than imply a proof we have not run. It is fail-closed on purpose, where it can reconcile it gives you a decisive record, and where it cannot it tells you the account is not reconciled rather than manufacturing a green tick. That refusal to fake certainty, in the one account where a wrong number is a bar matter, is the whole point.
Book a trust-reconciliation pilot
*This page is a specification. The capability it describes is not built yet, and nothing here is a claim that it runs today.*