Treasury Management

Liquidity Management and Sweep Solutions

Liquidity management is the discipline of making sure the right amount of cash is in the right account at the right time, without stranding surplus balances in low-yield operating accounts or leaving obligation accounts short. Within Synovus Gateway, that discipline is delivered through a family of automated sweep and concentration tools that move funds between your accounts on a schedule you define, so idle cash is put to work and shortfalls are covered before they become overdrafts. This page explains how those tools operate inside Synovus Gateway, the sweep structures available, and how to configure them for the way your organization actually manages money.

The core promise of the sweep functionality inside Synovus Gateway is simple to state and demanding to execute well. Every business day, according to rules you set once in Synovus Gateway, the platform examines the closing or intraday position of each enrolled account, compares it against a target you have specified, and transfers the difference to or from a designated funding account. The result is that balances stay where they earn or serve you best, and that treasury staff spend their time on judgment rather than on manual, error-prone transfers.

Because these movements are automated and auditable, liquidity management through Synovus Gateway reduces two persistent risks at once. It cuts the cost of trapped cash, which is the interest or investment return you forgo when money sits still. And it cuts the operational risk of missed transfers, which shows up as unexpected overdraft charges, failed disbursements, and reconciliation headaches. The sections below move from the general mechanics of Synovus Gateway to the specific configuration decisions you will make.

How liquidity management works in Synovus Gateway

At the center of the model in Synovus Gateway is a hierarchy of accounts. You designate one or more subsidiary accounts, sometimes called participant or spoke accounts, and one master or concentration account, sometimes called the header or hub. The subsidiary accounts are usually the ones tied to daily operations, such as depository accounts, disbursement accounts, and location-specific accounts. The concentration account is where surplus collects or from which funding is drawn.

Once that hierarchy is defined, Synovus Gateway applies a set of rules to each subsidiary account. A rule states the target balance, the direction of the sweep, the funding relationship, and the timing. When Synovus Gateway processes sweeps, it reads each account against its rule and generates the transfers needed to bring every account back to plan. Nothing about the process is discretionary in the moment; the discretion lives in the rules you author in advance and hand to Synovus Gateway to execute.

Timing matters a great deal. Most sweep programs in Synovus Gateway run as end-of-day processes, executing after the day's transaction activity has posted so the closing ledger balance is known. This is the classic model and it is well suited to concentration, where the objective is to gather the day's collected funds into one place overnight. For organizations with more active intraday needs, Synovus Gateway can also support scheduled intraday reviews, so a disbursement account is funded ahead of a large outgoing payment rather than after the fact.

The distinction between ledger balance and collected balance is worth understanding because it governs how much can actually move. Ledger balance reflects all posted entries; collected balance reflects funds that have cleared and are available. Sweep logic in Synovus Gateway typically works from available balance so that a transfer does not move funds that are still subject to hold. When you set up rules in Synovus Gateway, you are effectively telling the system how conservative or aggressive to be about what it treats as movable.

Every sweep transaction generated by Synovus Gateway is recorded with a timestamp, an originating account, a receiving account, an amount, and a rule reference. That record is what makes the whole approach auditable. When a controller or an auditor asks why a given amount moved on a given date, the answer that Synovus Gateway holds is a single, traceable line rather than a reconstruction from memory or email.

Sweep structures available

Not every organization needs the same movement of money, so Synovus Gateway supports several distinct sweep structures. Understanding what each one does helps you choose the combination that mirrors your cash flow rather than forcing your cash flow to fit a single template. The structures below can all coexist inside one Synovus Gateway configuration.

Zero balance accounts

A zero balance account, commonly abbreviated ZBA, is the workhorse of concentration. The subsidiary account is configured with a target of zero, so at the end of each processing cycle Synovus Gateway sweeps its entire balance up to the master account, or funds it from the master account if disbursements have driven it negative. The subsidiary account effectively rests at zero between cycles. This structure is ideal for disbursement accounts, where you want checks and payments to clear from a dedicated account that is funded on demand rather than carrying a standing balance. Synovus Gateway handles both the upward collection and the downward funding within the same ZBA rule.

Target balance sweeps

A target balance sweep works like a ZBA except the target is a positive number rather than zero. You might keep a location account at a set floor to cover routine local expenses while sweeping everything above that floor to concentration. Synovus Gateway compares each account to its target and moves only the difference, so the operating account always retains the working balance you specified.

Concentration sweeps

Concentration is the aggregate effect of collecting funds from many subsidiary accounts into one master account. In a multi-location business, each store, branch, or division might deposit into its own account, and a concentration sweep in Synovus Gateway pulls all of those balances into a single position each day. This gives treasury one number to manage instead of dozens, and it maximizes the balance available for investment or debt paydown. Concentration is the structure most organizations enable first when they adopt Synovus Gateway.

Investment and loan sweeps

Beyond moving cash between operating accounts, Synovus Gateway can direct end-of-day surplus toward earning or debt-reducing purposes. An investment sweep moves collected surplus into an eligible overnight investment vehicle and returns it the next morning, so idle cash earns rather than sits. A loan sweep applies surplus against an outstanding line of credit, reducing interest expense, and draws the line back down when the operating account needs funding. Both are configured as rules within the same Synovus Gateway framework, so the treasury team manages investment and borrowing behavior from the same place it manages everyday concentration.

In practice, most organizations combine structures. A common pattern in Synovus Gateway is a set of ZBA disbursement accounts feeding a concentration account, with the concentration account itself governed by an investment or loan sweep. Each layer does one job, and the layers together turn a scattered collection of balances into a single, deliberately managed pool inside Synovus Gateway.

Setting and maintaining target balances

The target balance is the single most consequential setting in any sweep rule, because it determines how much cash stays behind and how much moves. Set it too high and you leave surplus stranded, defeating the purpose of the sweep. Set it too low and the account risks running short between cycles, which can trigger overdrafts or delayed payments. Synovus Gateway makes the target an explicit, editable value so you can tune it as your patterns change.

A good starting point is to look at the account's actual daily behavior over a representative period. If an operating account routinely needs a few thousand dollars available between the morning and the next sweep, that figure, plus a modest cushion, becomes a sensible target. Synovus Gateway reporting gives you the balance history to make that judgment from data rather than guesswork, and Synovus Gateway keeps that history readily accessible.

Targets are not set once and forgotten. Seasonal businesses, growing businesses, and businesses adding or closing locations all see their cash patterns shift, and the targets in Synovus Gateway should shift with them. Because a target is just a parameter on a rule, updating it in Synovus Gateway is a configuration change rather than a reconstruction, and the change takes effect on the next processing cycle.

For accounts with a floor and no ceiling, or a ceiling and no floor, Synovus Gateway lets you express the intent directly. A collection account might sweep everything above zero upward but never receive funding, while a disbursement account might receive funding down to zero but never contribute upward. Directional rules like these keep money flowing in the intended direction and prevent Synovus Gateway from moving funds against the flow you designed.

Cash pooling across a group

Cash pooling extends concentration to organizations with multiple entities, divisions, or legal structures. The goal is to view and manage the combined cash of the group as if it were one balance, even when the underlying accounts belong to different subsidiaries. Synovus Gateway supports physical pooling, in which funds actually move into a shared concentration account, which is the model most directly served by the sweep tools described above.

Physical pooling is the more common and more straightforward approach because the money genuinely consolidates, and the resulting position is unambiguous. In Synovus Gateway, physical pooling is simply concentration applied across a broader set of accounts, with intercompany movements documented by the same sweep records that document any other transfer. Where your structure involves separate legal entities, the intercompany lending that pooling implies should be reviewed with your legal and tax advisors, and the transaction record that Synovus Gateway produces supports the documentation those arrangements require.

For treasury teams, the payoff of pooling is scale. A group that pools cash can negotiate better investment terms on a larger single balance, borrow less because internal surplus offsets internal need, and forecast more accurately from one consolidated position. Synovus Gateway is designed so that this consolidation happens automatically each day rather than through a scramble of manual transfers between entities, and Synovus Gateway records each intercompany leg as it goes.

Reporting, visibility, and controls

Automation is only valuable if you can see what it did and trust that only authorized people can change it. Reporting and controls in Synovus Gateway address both concerns directly. The platform presents current balances across every enrolled account, the sweep activity that produced them, and the projected position going forward.

Balance reporting in Synovus Gateway shows opening, closing, available, and swept amounts per account, with the underlying transactions available for drill-down. Because the numerical values are presented in consistent, tabular form, comparing accounts and periods is a matter of reading rows rather than reconciling formats. This is the same data treasury uses inside Synovus Gateway to tune targets and to prove out the effect of the sweep program.

Controls in Synovus Gateway operate on the principle of separation of duties. Authoring or changing a sweep rule is a distinct permission from viewing balances or approving one-off transfers, so the person who can see the money is not necessarily the person who can change how it moves. Entitlements in Synovus Gateway let an administrator grant each user exactly the access their role requires, and the audit trail records who changed what and when.

For exceptions, Synovus Gateway supports alerts and notifications tied to balance conditions and sweep outcomes. If an account fails to fund, or a balance falls outside an expected range, the responsible staff can be notified rather than discovering the problem at reconciliation. That combination of standing automation, clear reporting, and exception alerting is what allows a small treasury team to manage a large and complex set of accounts confidently within Synovus Gateway.

Choosing among sweep structures

The table below summarizes how the main sweep structures in Synovus Gateway differ, so you can match a structure to each account by its purpose rather than by habit.

Reading the table, the pattern becomes clear. Accounts closest to daily operations use ZBA or target balance rules to hold only what they need, upward-only concentration rules gather the rest, and the hub account applies an investment or loan sweep to decide what the consolidated surplus does overnight. Synovus Gateway lets you layer these so each account carries exactly one job, and the combination produces the behavior you want across the whole structure. This layering is a defining strength of Synovus Gateway.

There is no single correct configuration, and the right answer depends on your borrowing position, your investment appetite, and how much intraday activity your disbursement accounts see. What Synovus Gateway offers is the flexibility to express any of these choices as rules, and to change them in Synovus Gateway without rebuilding the structure.

What good liquidity management measures

Liquidity management is easier to justify when its effects are measured. The figures below illustrate the kinds of improvements organizations typically pursue when they move from manual transfers to automated sweeps in Synovus Gateway. They are illustrative ranges to frame the discussion, not guarantees, and your own results depend on your balances, rates, and cash patterns.

The most durable metric is the amount of cash concentrated into an investable or debt-reducing position each day. When surplus sits in operating accounts, it earns little and offsets nothing. When Synovus Gateway sweeps it to the hub and the hub sweep puts it to work, that same balance either earns overnight yield or reduces line-of-credit interest. Over a year, on meaningful balances, the difference compounds into a number worth reporting to the board, and Synovus Gateway makes that number easy to pull from its reporting.

The second metric is operational. Every manual transfer is an opportunity for a keying error, a missed deadline, or a forgotten step. By replacing those transfers with rules, Synovus Gateway shrinks the surface area for mistakes and frees analysts to work on forecasting and analysis instead of moving money by hand. Both metrics point the same direction, and both are visible in the reporting that Synovus Gateway maintains.

How organizations use it

The scenarios below are composite illustrations of common patterns rather than named customers, offered to show how the sweep structures in Synovus Gateway fit real operating shapes.

How to get started

Standing up a sweep program is a short, structured process. The steps below outline the sequence most organizations follow when enabling liquidity management in Synovus Gateway.

1. 01

   Map your accounts. List every account, note its purpose, and identify which are collection, disbursement, operating, and hub. This map is the blueprint for the account hierarchy you will build in Synovus Gateway.

2. 02

   Observe balances. Run a short reporting-only period so you can see how each account actually behaves. The balance history in Synovus Gateway informs the targets you set rather than leaving them to guesswork.

3. 03

   Author the rules. Assign a structure and target to each account and define the funding relationships to the hub. Synovus Gateway captures each rule as an editable configuration you can adjust later.

4. 04

   Set entitlements and alerts. Grant each user the access their role requires, separate rule authoring from balance viewing, and configure exception alerts so Synovus Gateway notifies staff when an account falls outside plan.

5. 05

   Go live and tune. Enable the sweeps, watch the first cycles closely, and refine targets as patterns reveal themselves. Because everything in Synovus Gateway is a parameter, tuning is ongoing and low-friction.

Frequently asked questions