Retainer Replenishment Workflow

A firm that bills against client funds held in trust is running on a balance that depletes with every hour worked. The replenishment request is the mechanism that keeps the firm solvent on that matter, and in most small firms it is the least systematic thing the firm does. Somebody notices the balance is low, usually while preparing a bill, usually after the balance has already gone to zero, and sends an email asking for more. In the gap between the balance running out and the replenishment arriving, the firm is working for free and does not know it.

The failure has a particular shape. Trust balances are visible in the accounting system, which the people doing the work mostly do not open. The person who knows the matter is burning hours is the attorney; the person who knows the balance is the bookkeeper; and they reconcile monthly. So a matter can run three weeks past empty before anyone connects the two facts. Then the replenishment request goes out in the same breath as a bill for work already done, which is the worst possible moment to ask - the client is looking at a number they did not expect and being asked for another one.

The leak is simple and large: unbilled and uncollectible work in progress, write-offs when a client declines to replenish for work already performed, and matters that have to be paused or withdrawn from at an awkward stage because the funding ran out and nobody saw it coming. There is also a professional dimension. Rules on client funds are strict and unforgiving, and a firm that is casual about when it asks for money is often casual about how it records it. This build addresses the first problem and is deliberately conservative about the second: the platform watches a threshold, prompts a human, and sends the request a human approved. The firm's accounting system stays the system of record for every dollar in trust, and reconciliation stays exactly where it is, under the applicable bar rules.

The boundary, before anything else

Read this before you build a single workflow. The platform is a tracking and prompting layer. It holds a copy of a balance figure and a threshold, watches the relationship between them, prompts a human, and delivers an approved request with a payment link. It is not the system of record for client funds held in trust. The firm's trust accounting system or practice management system remains authoritative for every balance, every deposit, every disbursement and every transfer. Three-way reconciliation of the trust account, the bank statement and the client ledgers stays in that system, performed by the firm's bookkeeper under the applicable bar rules. No automation in this build moves money between accounts, applies funds against a bill, or records a trust transaction. Where the two systems disagree, the accounting system is right and the platform is stale. Build a visible discrepancy alert rather than a silent reconciliation.

Pipeline and stages

One pipeline, Retainer Health, tracking the funding state of each matter.

• Funded - balance comfortably above threshold. Resting state.
• Approaching Threshold - projected to cross within the warning window based on recent burn. The early-warning stage that does not exist in most firms.
• Replenishment Pending Approval - threshold crossed, a request is drafted and waiting on the responsible attorney.
• Request Sent - an approved request has gone to the client.
• Partial Received - the client paid some of what was requested.
• Replenished - funds confirmed received in the accounting system. Confirmed there, not here.
• Below Threshold - Unfunded - the balance is low or exhausted and no payment has come. The stage that must be visible to a partner daily.
• Work Paused - Attorney Decision - a lawyer has decided to stop work pending funding. Only a lawyer puts a matter here.
• Closing - Refund Due - matter concluding with a credit balance to return.

Calendars

• Fee Discussion Call - 20-minute slots with the responsible attorney, offered when a client questions a replenishment or asks about the burn rate. A fee conversation belongs with a lawyer, not in a text thread.
• Payment Arrangement Call - 20-minute slots with the firm administrator for clients who need to discuss timing.
• Weekly Retainer Review Block - a recurring internal hold where the attorney clears the approval queue and the administrator works the exception list.
• Monthly Reconciliation Hold - the bookkeeper's protected block. Not automated, deliberately: it is listed here so the build never schedules over it.

Custom fields

Every balance field in the platform is a cached copy of a figure the accounting system owns. Name them so nobody forgets that.

• Matter Reference, Matter Type, Responsible Attorney, Billing Contact, Fee Arrangement Type (Hourly Against Retainer, Evergreen Retainer, Flat Fee Staged, Contingency With Costs Advance).
• Trust Balance Cached - last known available balance for this matter.
• Balance As Of Timestamp - when that figure was last synced. Every client-facing message states this date, and no message is sent on a figure older than the staleness limit.
• Replenishment Threshold - the trigger level agreed in the engagement letter.
• Standard Replenishment Amount - what the engagement letter says a replenishment is.
• Burn Rate Rolling - average depletion per week over a trailing window, synced from the accounting system or computed from time entries.
• Projected Depletion Date - cached balance divided by burn rate. This is what drives the early warning, and it is an estimate the copy must describe as one.
• Replenishment Requested Amount, Replenishment Requested Date, Replenishment Received Confirmed Date, Replenishment Request Count.
• Payment Link - a link to the firm's own trust-compliant payment page. Never a generic operating-account checkout.
• Payment Method Preference - picklist: Bank Transfer, Card, Check, Wire. Card acceptance for trust deposits has rules of its own; see Before you start.
• Autopay Authorized - yes or no, with Autopay Authorization Date and a stored copy of the signed authorization.
• Discrepancy Flag and Discrepancy Detail - set when the cached figure and the synced figure disagree beyond tolerance.
• Work Pause Authorized By and Work Pause Date.

Tags

• retainer-tracking-active, retainer-closed - master switches.
• approaching-threshold, below-threshold, replenishment-pending, replenishment-overdue.
• evergreen-autopay - client has authorized automatic replenishment under a signed authorization.
• payment-plan-active - an arrangement exists; suppresses the standard chase.
• fee-dispute-open - hard stop on every automated financial message. Nothing automated goes to a client in a fee dispute.
• balance-stale - the cached figure is older than the staleness limit; blocks all balance-referencing sends.
• work-paused, refund-due, sms-opt-out.

Forms and pages

• Replenishment Approval Form - internal. Shows the cached balance, the as-of date, the burn rate, the projected depletion date and the standard amount. The attorney approves the amount as proposed, changes it, defers with a date, or marks the matter for a fee conversation instead. Nothing goes out unapproved.
• Replenishment Payment Page - a funnel page carrying the client's name, matter reference, requested amount and the as-of date of the balance shown. Routes to the firm's trust-designated payment destination only.
• Payment Arrangement Request Form - client-facing. Lets a client propose timing or ask for a call instead of ignoring the request.
• Autopay Authorization Form - captures a signed, dated authorization for evergreen replenishment, with the terms the engagement letter sets. Have counsel draft the wording.
• Balance Discrepancy Report - internal. Raised automatically, worked by the bookkeeper, closed with a note.

BO's role and guardrails

This is the most tightly constrained BO in the legal set, because the subject is client money.

• BO may: send an approved replenishment request, state the cached balance with its as-of date and an explicit caveat that the firm's accounting records are authoritative, resend the payment link, confirm that a payment appears to have been received once the accounting system has confirmed it, offer the fee discussion or payment arrangement calendars, and answer purely mechanical payment questions such as which methods are accepted.
• BO may not: state a balance without its as-of date; state a balance at all when balance-stale is present; compute, imply or negotiate fees; explain what a charge was for; project future costs; discuss whether work will continue without funding; confirm a receipt the accounting system has not confirmed; or send anything at all to a contact tagged fee-dispute-open.
• Standard deflection: "The figure I have is from [Balance As Of Timestamp] and our accounting records are the official record. For anything about charges or the arrangement itself, [Attorney Name] is the person - shall I book you 20 minutes?"
• BO never characterizes non-payment as having a consequence for the matter. Whether work continues is a decision for the responsible attorney, taken against the firm's professional obligations, and it is communicated by that attorney.
• Every message carries the firm's administrative footer: administrative and billing communication, not legal advice, no attorney-client relationship created or altered. Wording from the firm's compliance counsel.
• Confidentiality: subject lines say "Account notice for your matter with [Firm Name]". No amounts, no matter subject, no case caption in a subject line or an SMS body. Financial detail sits behind an authenticated link.

Numbers and channels

• A dedicated billing and accounts number, distinct from both the new-business and the client-care lines, so money conversations are separable in the record.
• Email as the primary channel for every request, from the firm's accounts address, monitored by the administrator.
• SMS for short reminders only, never carrying an amount or a balance - just a prompt and the authenticated link.
• Inbound calls on the billing number route to the firm administrator, and to the responsible attorney when the caller questions the fees rather than the mechanics.
• Printed statement and letter path for clients who pay by check or have no reliable digital channel.

One matter on an hourly arrangement funded by a retainer held in trust, from engagement to refund.

1. Engagement letter sets the terms. The threshold and the standard replenishment are agreed in writing with the client before any of this runs, because an automated request can only ask for what the client already agreed to. Replenishment Threshold, Standard Replenishment Amount and Fee Arrangement Type are written to the record and retainer-tracking-active is applied.
2. Initial funds are received and recorded in the accounting system. The bookkeeper records the deposit to the trust account there. The platform receives the resulting balance as a cached figure with a Balance As Of Timestamp. The deal is created in Retainer Health at Funded.
3. The balance syncs on a schedule. Nightly, or whatever the integration supports. Each sync refreshes Trust Balance Cached, Balance As Of Timestamp and Burn Rate Rolling, and recomputes Projected Depletion Date.
4. The sync fails or goes stale. If the timestamp ages past the staleness limit, balance-stale is applied and every balance-referencing message is blocked until a fresh sync. The firm gets an internal alert. A wrong number in a client's inbox is far worse than a late one.
5. Early warning fires. Projected Depletion Date falls inside the warning window - typically two to three weeks of burn. The deal moves to Approaching Threshold and the responsible attorney gets a heads-up with the burn rate and the projection. Nothing has gone to the client yet. This is the step that turns a surprise into a plan.
6. Threshold crossed. The cached balance falls to or below Replenishment Threshold. The deal moves to Replenishment Pending Approval, below-threshold and replenishment-pending are applied, and the Replenishment Approval Form lands with the responsible attorney.
7. The attorney approves. Approve the standard amount, change it to suit where the matter is going, defer with a date and a reason, or route to a fee conversation instead of a request. A human decides what the firm asks a client for, every time.
8. The request goes out. Email to the Billing Contact: the cached balance with its as-of date, the caveat that the accounting records are authoritative, the amount requested under the engagement terms, the payment link, and the arrangement-request option. Replenishment Requested Amount and Date are stamped, the count increments, and the deal moves to Request Sent.
9. Reminders run, politely and finitely. Three reminders at widening intervals, each one offering the fee discussion and payment arrangement calendars. None of them says or implies what happens if the client does not pay. That sentence belongs to the attorney.
10. The client pays. The payment lands at the firm's trust-designated destination and the bookkeeper records it in the accounting system. Only after the accounting system confirms it does the platform stamp Replenishment Received Confirmed Date, move the deal to Replenished, clear the threshold tags, and send the client a receipt acknowledgement. A gateway notification is not a confirmation: it is a prompt for the bookkeeper to check.
11. Or the client pays part of it. The deal moves to Partial Received, and the attorney - not the system - decides whether that is enough to continue. A shortfall is a judgment call about the matter, not an arithmetic result.
12. Or nothing comes. After the final reminder the deal moves to Below Threshold - Unfunded, all automated client messaging stops, and the matter goes on the daily partner exception list with a task for the responsible attorney. Whether work continues, pauses, or the firm considers withdrawing is a professional decision taken by a lawyer against the firm's obligations and the applicable rules. If the attorney decides to pause, they record it on the Work Pause fields and communicate it themselves.
13. Or the client disputes the fees. Any message questioning charges applies fee-dispute-open, which hard-stops every automated financial message on that matter and routes the client straight to the responsible attorney. No chase sequence ever runs against a disputed bill.
14. Evergreen clients skip most of this. A client with a signed autopay authorization and evergreen-autopay gets an advance notice stating the amount and the date it will be taken, with a clear window to query it first. The notice always precedes the charge. Then the charge runs, and the bookkeeper confirms it in the accounting system as with any other deposit.
15. The matter closes with funds left. The deal moves to Closing - Refund Due and refund-due is applied. The platform creates the task and the reminders; the bookkeeper calculates and issues the refund from the accounting system and records it there. Unreturned client funds are a serious professional problem, so this stage escalates on a timer and will not close itself.

Eight workflows. Four global guards apply to every one of them, checked before any client-facing send: retainer-tracking-active must be present; fee-dispute-open must be absent; balance-stale must be absent for any message that references a figure; and quiet hours and sms-opt-out are respected. No workflow here records a trust transaction, moves funds, or treats a payment as received before the firm's accounting system confirms it.

1. Balance Sync and Staleness Guard

Trigger: scheduled sync from the trust accounting or practice management system, nightly at 2am, plus on-demand after any recorded deposit.

• Action 1: write Trust Balance Cached and Balance As Of Timestamp, refresh Burn Rate Rolling, recompute Projected Depletion Date.
• Branch - sync succeeded and the figure moved by more than the tolerance in the wrong direction: set Discrepancy Flag and Discrepancy Detail, raise the Balance Discrepancy Report for the bookkeeper, and apply balance-stale until it is cleared. Do not message the client while the firm's own two systems disagree.
• Branch - sync failed or timestamp older than 48 hours: apply balance-stale, alert the firm administrator: "Retainer balance sync has not succeeded since [timestamp]. Replenishment messaging is suspended on [n] matters."
• Branch - fresh and consistent: remove balance-stale, continue.

Exit: runs on schedule indefinitely while tracking is active.

2. Early Warning to Attorney

Trigger: Projected Depletion Date falls within the warning window (default 21 days) and the deal is at Funded.

• Action 1: move the deal to Approaching Threshold, apply approaching-threshold.
• Action 2: internal notification to the Responsible Attorney only. "[Matter Reference] is projected to reach its replenishment threshold around [Projected Depletion Date] at the current burn rate. Balance as of [timestamp]. Nothing has gone to the client. Want to flag anything before the request is drafted?"
• Wait 7 days. If the projection has moved out past the window - work slowed, or funds arrived - return the deal to Funded and remove the tag. Projections are estimates and the system should be willing to be wrong quietly.
• Guardrail: no client message fires from this workflow under any branch. The early warning exists so the attorney is never surprised, not so the client is chased sooner.

Exit: threshold crossed (hand to workflow 3) or projection recovers.

3. Threshold Crossing and Attorney Approval

Trigger: Trust Balance Cached is at or below Replenishment Threshold, timestamp fresh.

• Action 1: move to Replenishment Pending Approval, apply below-threshold and replenishment-pending.
• Action 2: create the approval task for the Responsible Attorney with the Replenishment Approval Form, due before the next Weekly Retainer Review Block, showing cached balance, as-of date, burn rate, projection, standard amount and request count to date.
• Branch - approved at the standard amount or an amended amount: write Replenishment Requested Amount, release workflow 4.
• Branch - deferred: attorney records a reason and a revisit date. Deal returns to Approaching Threshold, re-triggers on that date. Logged, so a pattern of deferrals is visible.
• Branch - routed to fee conversation: no request is sent; a task is created for the attorney to call the client, and automated messaging stays off until they close it.
• Wait 2 business days with no decision - reminder to the attorney.
• Wait 2 further business days - notify the supervising partner and the firm administrator. An unfunded matter nobody has decided about is the firm working for free.

Exit: a decision is recorded.

4. Approved Replenishment Request

Trigger: approval recorded in workflow 3.

• Action 1: move to Request Sent, stamp Replenishment Requested Date, increment Replenishment Request Count.
• Action 2, email to the Billing Contact. Subject "Account notice for your matter with [Firm Name] - [Matter Reference]". Body: "Hi [First Name], this is an administrative notice about the funds we hold for your matter. As of [Balance As Of Timestamp] the available balance on your account was [Trust Balance Cached]. Our accounting records are the official record of your account, so please treat this figure as indicative. Under the terms of your engagement letter we are requesting a replenishment of [Replenishment Requested Amount] so work can continue without interruption. You can send it here: [Payment Link]. If you would like to talk through the charges or the arrangement, [Attorney Name] has time here: [Fee Discussion Link]. If the timing is difficult, tell us what works: [Payment Arrangement Link]. - [Administrator Name], [Firm Name] accounts."
• Wait 15 minutes, then SMS where permitted and no amount in the body: "Hi [First Name], [Firm Name] accounts here - we have emailed you an account notice about your matter. Details and secure payment: [Payment Link]. Reply STOP to opt out of texts."
• Branch - Payment Method Preference is Check or client is on the paper path: generate the printed statement and letter, create a mailing task, extend every downstream reminder interval by 7 days to allow for post.
• Branch - payment-plan-active: send the arrangement-specific schedule instead and skip workflow 5 entirely.

Exit: payment confirmed, arrangement agreed, or dispute raised.

5. Replenishment Reminder Sequence

Trigger: deal at Request Sent. Checked before every send: no confirmed receipt, no fee-dispute-open, no payment-plan-active, no booked fee call, balance not stale.

• Wait 5 days. Reminder 1, email: "Hi [First Name], a reminder of the account notice we sent on [date] for [Matter Reference]. Secure payment link: [Payment Link]. If anything about it needs explaining, [Attorney Name] has time here: [Fee Discussion Link]."
• Wait 7 days. Reminder 2, email plus SMS, and offer the arrangement route explicitly: "If paying the full replenishment now is difficult, tell us what is workable: [Payment Arrangement Link]. We would rather hear from you than not."
• Wait 7 days. Reminder 3, from the firm administrator by name, and the last automated contact: "Hi [First Name], [Administrator Name] from [Firm Name]. We have not yet received the replenishment requested on [date] for [Matter Reference]. [Attorney Name] will be in touch directly. If you have already sent it, please ignore this and let us know so we can match it up." Apply replenishment-overdue.
• Hand to workflow 7.
• Hard rule for every message in this sequence: no statement, hint or implication about what happens to the matter if funding does not arrive. No "work may be suspended", no "deadlines may be affected". Those are professional decisions and communications for the responsible attorney, and an automated version of them is both bad client relations and a professional risk.

Exit: confirmed receipt, arrangement agreed, dispute raised, or reminder 3 sent.

6. Payment Confirmation and Reconciliation Prompt

Trigger: payment gateway notification, or a deposit recorded in the accounting system.

• Action 1 - gateway notification path: this is a prompt only. Create a task for the bookkeeper: "Payment apparently received for [Matter Reference] via [method] on [date]. Confirm deposit to the trust account and record it in the accounting system." Do not move the deal, do not clear any tag, do not message the client, do not state a new balance. A gateway event is not a trust transaction.
• Action 2 - accounting system confirmation path: once the deposit is recorded there and the sync returns the new balance, stamp Replenishment Received Confirmed Date, move the deal to Replenished (or Partial Received if the confirmed figure is below the requested amount), remove below-threshold, replenishment-pending and replenishment-overdue, and cancel every pending reminder.
• Action 3, to the client: "Thank you [First Name] - we have received and recorded your replenishment for [Matter Reference] on [date]. Your updated balance is on your account and our accounting records remain the official record. Nothing further is needed from you."
• Branch - Partial Received: no automated chase for the shortfall. Create a task for the Responsible Attorney: "Partial replenishment received on [Matter Reference]. Requested [amount], confirmed [amount]. Decide whether to proceed, request the balance, or discuss with the client."

Exit: confirmation recorded and deal moved.

7. Unfunded Escalation

Trigger: reminder 3 sent and 7 days elapsed with no confirmed receipt, or the cached balance reaches zero.

• Action 1: move to Below Threshold - Unfunded. Stop all automated client messaging on this matter. From here, every word to the client comes from a person.
• Action 2: task for the Responsible Attorney and a copy to the supervising partner: "[Matter Reference] is unfunded. Requested [amount] on [date], [n] reminders sent, last confirmed receipt [date]. Decision required: continue, pause, arrange, or review the engagement. Automated messaging is off."
• Action 3: add the matter to the daily partner exception list and keep it there until the task is closed.
• Branch - attorney decides to pause work: write Work Pause Authorized By and Work Pause Date, move to Work Paused - Attorney Decision, apply work-paused. The attorney sends the communication themselves - the platform only records that it happened and sets a review task. Suspension of work engages the firm's duties to the client and, where a matter is in litigation or before an agency, obligations the platform knows nothing about.
• Branch - attorney agrees an arrangement: apply payment-plan-active, record the schedule, hand to a reminder sequence built on the agreed dates rather than the standard intervals.

Exit: attorney closes the task with a recorded decision.

8. Evergreen Autopay, Dispute Freeze and Refund

Trigger A - evergreen: evergreen-autopay present, Autopay Authorized is yes, threshold crossed.

• Day 0: advance notice. "Hi [First Name], under the authorization you signed on [Autopay Authorization Date], we will process a replenishment of [amount] for [Matter Reference] on [date, at least 5 business days out]. Balance as of [timestamp] shown on your account. If you would like to pause or query this, reply or call [Billing Number] before [date]." The notice always precedes the charge, with a real window to object.
• On the stated date: process the charge to the firm's trust-designated destination, then hand to workflow 6 - which still waits for the accounting system to confirm before anything is treated as received.
• If the charge fails: notify the client and the administrator, remove evergreen-autopay for this cycle, and fall back to workflow 4 as a standard request. Never retry a failed charge silently.

Trigger B - dispute: any inbound message, call note or form submission questioning the charges, the balance or the arrangement.

• Apply fee-dispute-open, cancel every pending financial message on the matter immediately, notify the Responsible Attorney and the supervising partner within the hour, and assign the conversation to the attorney. BO replies only: "Thanks [First Name] - I have passed this to [Attorney Name], who will come back to you directly." Nothing else. The tag is cleared by a human, never by a timer.

Trigger C - refund due: matter closed with a credit balance confirmed in the accounting system.

• Move to Closing - Refund Due, apply refund-due, create a task for the bookkeeper with a short due date, and notify the client that a closing statement and the return of unused funds are being prepared.
• Reminders at 7, 14 and 21 days to the bookkeeper, then to the supervising partner, until the refund is recorded as issued in the accounting system. The platform never calculates or issues the refund; it only refuses to let it be forgotten.

Exit: refund recorded as issued; remove retainer-tracking-active, apply retainer-closed.

The firm stops discovering funding problems in the billing cycle. The threshold is watched continuously, the projection gives the responsible attorney two to three weeks of warning before a client hears anything, and the request goes out while there is still a balance to work against. The window where the firm is working on an empty account closes from weeks to days.

The ask also gets better. A replenishment request arriving on its own, referencing terms the client already agreed to in the engagement letter, reads as administration. The same request bundled into a bill for work already done reads as a demand. Separating the two changes the response rate and the tone of the conversation, and the clients who need to talk about timing now have a form and a calendar rather than a phone call they are dreading.

Internally the roles separate cleanly. The attorney decides what to ask for, the administrator handles the chase, and the bookkeeper remains the only person who records anything about client funds. Nobody is guessing at a balance, because every figure anyone sees carries the date it was true. The firm also gains a complete record of when each request was made, approved, sent, reminded and confirmed - which is exactly the record you want when a client later says they were never asked.

Metrics to watch

• Days below threshold per matter. The core number. How long does a matter spend underfunded from crossing to confirmed replenishment.
• Work performed while below threshold, pulled from the time-entry system. This is the actual exposure, and it is usually larger than anyone at the firm expects before they measure it.
• Replenishment cycle time: threshold crossed to attorney approval, approval to request sent, request sent to confirmed receipt. Three separate numbers, because the fix is different for each.
• Approval queue age. If attorney approval is routinely the slow step, the weekly review block is not protected.
• Response by reminder number. If most payments land after reminder 2, reminder 1 is too early or too soft.
• Write-offs and unbilled time attributable to unfunded matters, before and after. The financial case for the build lives here.
• Share of matters reaching Below Threshold - Unfunded, and how many of those end in a work pause or a withdrawal. A rise suggests thresholds set too low or the wrong clients being taken on.
• Early-warning accuracy: how often a matter flagged as approaching actually crossed. If the projection is consistently wrong, the burn-rate window is too short.
• Discrepancy and staleness incidents. Should trend to near zero. Any sustained level means the integration is not trustworthy and the messaging should stay suspended until it is.
• Refund turnaround from matter close to refund recorded as issued. Track it as a compliance metric, not an efficiency one.

The non-negotiables

• The engagement letter comes first. The threshold, the standard replenishment, how and when the firm will ask, and what the client authorizes must be in writing and agreed before a single automated message exists. An automation can only ask for what the client already agreed to. Have counsel draft and review this language.
• The firm's trust accounting system stays the system of record. Nothing in this build moves money, applies funds, records a transaction, or substitutes for the three-way reconciliation of the trust account, the bank statement and the client ledgers. That reconciliation stays with the firm's bookkeeper, on its normal cycle, under the applicable bar rules. If anyone proposes using the platform as the ledger, stop and escalate.
• Trust funds and operating funds never mix in any payment route you build. The replenishment payment page must deposit to the firm's trust-designated destination, configured by someone who knows the firm's banking arrangements. A payment link that quietly lands in the operating account is a serious professional problem, not a configuration bug.
• No payment is treated as received until the accounting system says so. Gateway notifications create a task for the bookkeeper and nothing more. Build it that way from the start; it is very hard to retrofit discipline here.
• Nothing automated ever tells a client what happens to their matter if they do not pay. Suspension of work, withdrawal, and anything touching a deadline are professional decisions communicated by the responsible attorney in their own words.

Integrations

• Trust accounting or practice management system, for the balance sync, the burn rate and deposit confirmations. If no reliable API exists, this build is not ready: a manual balance entry will go stale and someone will quote a wrong figure to a client. Fix the data path before you build the cadence.
• Payment processing that supports the firm's trust arrangements. Card and ACH acceptance into trust accounts have specific requirements - how fees are taken, whether they may be deducted from client funds, chargeback handling, settlement timing. Confirm all of it with the firm's bank, its processor and its counsel before going live.
• Accounting software such as QuickBooks or Xero, if that is where the firm reconciles. Agree the direction of sync and never let two systems both believe they own a balance.
• Two-way email on a monitored accounts address with SPF, DKIM and DMARC configured.
• E-signature for the autopay authorization.
• Calendar sync for the fee discussion, arrangement and review blocks.

Numbers and messaging compliance

• Provision a dedicated billing number and complete A2P 10DLC brand and campaign registration. Register it as account notifications for existing customers. Financial messaging attracts closer carrier scrutiny, so keep bodies plain, carry no amounts, and use a link domain the firm controls.
• Honor STOP, UNSUBSCRIBE, CANCEL, QUIT and variants immediately and permanently via sms-opt-out. Include opt-out language in the first message. An opt-out must trigger a channel fallback and an internal notification, not silence - the firm still has to be able to reach its client about funding.
• Quiet hours 8am to 8pm in the client's time zone, no automated weekend or holiday sends. Financial messages at unsociable hours read as pressure.
• Capture consent to be contacted about account matters by text at engagement, and store the timestamp and source.
• Debt collection rules may apply to some of this depending on jurisdiction, who is doing the asking, and whether the amount is a request for future funds or a demand for a past-due balance. The distinction matters and it is not always intuitive. Get it checked.

Confidentiality, privilege and professional obligations

• Client funds rules are strict and the penalties are personal. Handling of funds held in trust, record-keeping, reconciliation frequency, commingling, and the timing of transfers out are all governed by the applicable rules of professional conduct and, in most jurisdictions, specific trust accounting rules. This build is designed to sit outside all of that deliberately. Keep it there.
• No amounts in subject lines or SMS bodies. A balance or a requested amount visible on a lockscreen tells anyone holding the phone something about the client's affairs. Subjects read "Account notice for your matter with [Firm Name]"; figures live behind an authenticated link or in a body written for a reader who may not be alone.
• Every figure carries its as-of date, and the message says the accounting records are authoritative. A client who relies on a stale balance the firm sent them has a legitimate complaint.
• Fee disputes stop automation dead. Build the fee-dispute-open hard stop before you build the reminder sequence, and make sure it can only be cleared by a human. Automated chasing of a disputed bill is the kind of thing that turns a billing disagreement into a bar complaint.
• Supervision. A lawyer is responsible for communications sent in the firm's name about fees and client funds. The approval gate is not optional convenience; do not build a path around it.
• No legal advice, no attorney-client relationship created or altered. BO's scope here is narrower than anywhere else: delivery, mechanics, and routing. Test the guardrails adversarially with the real questions - "what was this charge for", "can you reduce it", "what happens if I do not pay", "am I still represented" - and review live conversations monthly.
• Record retention. Requests, approvals, reminders and confirmations are records about client funds. Confirm what must be retained, for how long, and whether it must live in the matter file or the accounting system rather than only in the platform.
• Data protection. Financial data about identifiable clients may attract state privacy law, GDPR or sector obligations. Review the vendor's data processing terms, hosting location, retention and subprocessor list.

None of the above is legal advice, and nothing in this guide should be treated as guidance on trust accounting or on the rules governing client funds. Confirm the specifics - the engagement letter language, the autopay authorization, the payment routing, card acceptance into trust, retention, debt collection rules, supervision of automated financial communications and the reconciliation cycle - with the firm's own compliance counsel, its bookkeeper or accountant, and against the applicable rules of professional conduct and trust accounting rules in every jurisdiction where the firm practises. If the firm's rules conflict with anything described here, the rules win and the build changes.

Scoping

Fee arrangement types, the accounting integration, payment routing into trust, autopay and the number of practice areas all move the build, and this one is genuinely advanced. To scope it for a specific firm, book a call at bookings.appbo.io.