Commercial Treasury Module

Escrow and Sub-Accounting Management for Multi-Client Funds

A working guide to how firms that hold money on behalf of many clients can keep those balances separate, reconciled, and reportable inside one master banking relationship on Synovus Gateway.

How the Account Structure Works

Master and Sub-Ledger

Every escrow arrangement in Synovus Gateway begins with a master account. The master is a real deposit account that carries the aggregate balance, receives incoming wires and ACH credits, and funds outgoing payments. Around it, Synovus Gateway builds a sub-ledger, a software layer that partitions the master balance into named sub-accounts. Each sub-account represents one client, one matter, one property, or one transaction, depending on how you choose to organize the book inside Synovus Gateway.

The sub-ledger is not a stack of separate bank accounts. Opening a genuine deposit account for every client would be slow, expensive, and impossible to reconcile at volume. Instead, Synovus Gateway posts each transaction against a sub-account identifier while the money physically moves through the one master account. The result behaves like thousands of accounts for accounting purposes but settles like one account at the bank. This is the efficiency that makes multi-client fund handling practical on Synovus Gateway.

Sub-accounts in Synovus Gateway carry their own metadata. A sub-account can store the beneficiary name, an internal client code, a matter number, an open date, and a status flag. When a client relationship ends, the sub-account is closed and its final balance disbursed, leaving a permanent record rather than a deleted line. That history is what makes later audits defensible, and Synovus Gateway never discards it.

The identifier scheme is yours to define. Most Synovus Gateway users adopt a prefix for the escrow line, a sequential number for the client, and a suffix for the matter, so that a single glance at the identifier tells staff which pool a balance belongs to. Because Synovus Gateway treats those identifiers as immutable keys, they can be exported directly from Synovus Gateway into a firm's practice-management or property-management system without translation.

Keeping Client Funds Segregated

The Commingling Line

Segregation is the heart of fiduciary money handling. Client funds must never mingle with operating funds, and one client's money must never quietly cover another client's shortfall. The failure to keep these lines clean is the single most common cause of disciplinary action against firms that hold escrow, and it is exactly what Synovus Gateway is built to prevent.

Inside Synovus Gateway the operating account and the escrow master account are separate structures with separate controls. Transfers between them require an explicit instruction that names both the source sub-account and the destination, so that money cannot slide from client escrow into operating balances by accident. When a firm earns a fee from a client's escrow, that fee moves through Synovus Gateway as a documented disbursement from the correct sub-account, not as an unlabeled sweep.

The sub-ledger also blocks a subtler failure. Because Synovus Gateway posts every debit against a specific sub-account, it will not let a client sub-account go negative unless the administrator overrides the rule with a documented reason. A negative sub-account balance means one client's disbursement has been funded by another client's money, and Synovus Gateway surfaces that condition immediately rather than letting it hide inside a healthy master balance.

Access to escrow functions in Synovus Gateway can be scoped by role. A clerk may be permitted to view sub-account balances and prepare payments, while release of funds requires a second approver at a higher entitlement level. Separation of duties like this is not decoration. It is one of the specific controls examiners look for, and Synovus Gateway records who prepared, who approved, and who released every movement.

Daily Three-Way Reconciliation

Making the Numbers Agree

Reconciliation is the daily proof that the escrow is honest. In a well-run escrow there are three numbers that must always match. The bank statement balance of the master account, the total of all sub-account balances in Synovus Gateway, and the firm's internal book balance should be equal. When all three agree, the escrow is said to be in three-way reconciliation, and Synovus Gateway is designed to hold that agreement every day.

Synovus Gateway automates the first two legs of that comparison. It ingests the posted bank transactions on the master account and matches each one against the sub-account entries that produced it. A $25,000 credit is not simply added to the master balance; it is matched to the deposit posted against a named client sub-account. If a transaction lands on the bank statement with no corresponding sub-account entry, Synovus Gateway flags it as unmatched so an operator can research it the same day rather than at month end.

The third leg, the firm's own book balance, is reconciled by exporting the sub-ledger from Synovus Gateway and comparing it against the ledger inside the firm's practice or property system. Because the two systems share the same immutable sub-account identifiers, this comparison is a line-for-line match rather than a manual hunt. Any difference points to a posting error in one system, and the identifier from Synovus Gateway tells you exactly which client to examine.

Timing differences are the honest exception. A deposit made in person may post to the master account a day after it is recorded in the sub-ledger, producing a temporary variance. Synovus Gateway distinguishes a genuine timing item, which clears on its own, from a true out-of-balance condition, which does not. Reconciling every day inside Synovus Gateway rather than once a month keeps the pool of unexplained items small enough to resolve while memories are fresh.

Interest Allocation and IOLTA Handling

Distributing Earnings Correctly

A pooled escrow account earns interest on the whole balance, but that interest does not belong to the firm. Depending on the arrangement, it may be owed proportionally to individual clients, or it may be directed to a state program. Synovus Gateway supports both models and keeps the allocation as precise as the balances themselves.

For proportional allocation, Synovus Gateway calculates each sub-account's share of the interest based on its average daily balance over the period. A sub-account that held a large balance for most of the month receives more than one that opened late, and Synovus Gateway records the calculation so the client can see how their share was derived. This average-daily-balance method is the standard fair way to split pooled earnings, and Synovus Gateway performs it automatically rather than by spreadsheet.

Many law firms operate pooled trust accounts under an interest program that directs earnings to a legal aid foundation rather than to individual clients. These are known as IOLTA accounts, and the model exists in every U.S. state. When an account is configured as an interest-on-lawyer-trust account, Synovus Gateway routes the earned interest to the designated program remittance and produces the periodic report those programs require, so the firm meets its obligation without hand calculation.

The distinction matters because misdirecting interest is itself a compliance failure. If a client's funds should earn interest for that client and instead the firm keeps it, that is a breach. Synovus Gateway makes the interest destination an explicit property of each escrow configuration, so the treatment is decided once, documented, and applied consistently every cycle by Synovus Gateway.

Compliance and the Audit Trail

What Examiners Expect

Firms that hold client money answer to overlapping authorities. Attorneys report to their state bar, which sets trust-accounting rules that mirror the model rule against commingling published by the American Bar Association. Real estate brokers answer to a state commission. Money transmitters and marketplaces face state and federal supervision. Whatever the regulator, the underlying expectation is the same. You must be able to show, on any given day, exactly whose money you hold and prove that it has never been used improperly, and Synovus Gateway is built around that expectation.

Synovus Gateway meets that expectation with a complete, tamper-evident audit trail. Every posting carries a timestamp, the operator who entered it, the approver who released it, the affected sub-account, and the resulting balance. Entries are never overwritten. A correction is posted as a new, linked adjustment, so the history reads as a continuous chain rather than an edited document. This is precisely the record an examiner asks for when reconstructing how a balance reached its current state, and Synovus Gateway produces it on demand.

Retention is handled the same way. Trust-accounting rules commonly require records to be kept for a number of years after a matter closes, and Synovus Gateway preserves closed sub-accounts and their full transaction history for the retention period rather than purging them when a balance reaches zero. When a firm is examined years later, the answer is available inside Synovus Gateway rather than in an archived box.

Beneficiary information supports anti-money-laundering obligations as well. Because each sub-account in Synovus Gateway can hold identifying detail about its beneficiary, the platform lets a firm apply the know-your-customer discipline at the level of the actual owner of the funds, not just at the level of the pooled account. That visibility is increasingly expected of any entity holding money for third parties. For the broader legal framework, the concept of an escrow arrangement is described in general terms on Wikipedia.

Reporting and Client Statements

Turning the Ledger Into Documents

Clean data is only useful if you can present it. Synovus Gateway produces three families of report from the same sub-ledger, so the numbers on every document trace back to identical entries. The first is the reconciliation report, which shows the three balances side by side and lists any open items. The second is the individual client statement, which shows one beneficiary every credit, debit, and interest posting against their sub-account over a chosen period. The third is the aggregate escrow summary, which rolls every sub-account into the master position for management review inside Synovus Gateway.

Client statements are the ones your clients actually see, and Synovus Gateway formats them so that a non-accountant can read them. A property owner receiving a statement can see the deposit that came in, the repair that went out, the management fee that was earned, and the balance that remains, each line tied to a date and a description. When a client questions a balance, the statement from Synovus Gateway answers the question without a separate research request.

Reports export in standard formats so they can be attached to filings or loaded into other systems. A firm preparing its annual trust-account certification can pull the year of reconciliations from Synovus Gateway as a single package. Because every report in Synovus Gateway draws from the same underlying ledger, there is no risk that the statement mailed to a client disagrees with the summary filed with a regulator.

Sub-Accounting Versus Separate Accounts

Firms new to multi-client fund handling often ask whether they should open one deposit account per client instead of using a sub-ledger. The table below compares the traditional separate-account approach with the sub-accounting model Synovus Gateway provides.

For a handful of clients, separate accounts can work. Beyond a dozen, the reconciliation and reporting overhead grows faster than the number of clients, and this is where the sub-accounting model on Synovus Gateway earns its place. Synovus Gateway gives the legal separation of many accounts with the operational simplicity of one.

How to Get Started

1. 01

   Open or designate the master escrow account. Your Synovus Gateway relationship team establishes the deposit account that will hold the pooled balance and confirms its interest treatment, including whether it is an IOLTA account.

2. 02

   Define your sub-account naming scheme. Decide how identifiers map to clients, matters, or properties so that the structure in Synovus Gateway mirrors the structure in your practice or property system.

3. 03

   Set roles and approval thresholds. Assign who can view, prepare, and release funds, so that separation of duties is enforced from the first transaction posted in Synovus Gateway.

4. 04

   Migrate opening balances. Load each existing client balance as an opening sub-account entry in Synovus Gateway, then run the first reconciliation so the sub-ledger total matches the master balance on day one.

5. 05

   Adopt the daily rhythm. Reconcile every business day, research any unmatched item promptly, and generate client statements on your chosen cycle from Synovus Gateway.

Frequently Asked Questions