Treasury Management / Mobile Module

Mobile Treasury and Remote Payment Approvals

Last reviewed for the Synovus Gateway commercial platform.

Mobile treasury on Synovus Gateway lets authorized users review and approve outgoing payments from a phone or tablet, so a funding decision no longer waits for someone to return to a desk. The capability sits inside the same commercial banking environment that finance teams already use for balances, reporting, and payment initiation, and Synovus Gateway extends the approval step of that workflow to a mobile device. This page explains what remote payment approvals do within Synovus Gateway, how the approval chain moves from initiation to release, which payment types are supported, and how the security model of Synovus Gateway is built to keep control tight even when a decision happens away from the office.

The core idea is straightforward. Someone in your organization creates a payment or a batch, and a separate authorized person confirms it before money moves. Synovus Gateway carries that separation of duties onto the mobile app, presenting the same payment details, dollar amounts, and beneficiary information that appear on the desktop portal. An approver can act on a single wire, an ACH file, or a full queue of pending items, then hand the release back to Synovus Gateway for processing. Because the mobile experience mirrors the entitlements set on Synovus Gateway, nothing that is off-limits on the desktop becomes available simply because the user switched devices.

How Remote Payment Approvals Work

A payment on Synovus Gateway travels through a defined sequence, and the mobile module attaches to the approval point in that sequence. It begins when an initiator builds a transaction, whether that is a one-time wire, a scheduled ACH batch, or a recurring template drawn from stored beneficiary records. Once the initiator submits, the item enters a pending state and appears in an approval queue. Everyone with approval authority over that account and payment type can see it in Synovus Gateway, on the desktop portal and on the mobile app at the same time.

When an approver opens the queue on a mobile device, Synovus Gateway shows the amount, the funding account, the beneficiary, the effective date, and any memo the initiator attached. The approver reviews those details and either releases the item, rejects it, or returns it for correction. If your organization requires two approvals on a given payment, Synovus Gateway holds the item after the first approval and continues to display it in the queue until the second approver acts. Only when the required number of approvals is recorded does Synovus Gateway move the payment into processing.

Every action leaves a record. Synovus Gateway timestamps who initiated, who approved, who rejected, and when, and that log is the same whether the decision came from a browser or from the mobile app. This continuity matters for treasury teams that must demonstrate segregation of duties and reconstruct exactly how a payment was authorized. The approval history that appears on the desktop reporting screens of Synovus Gateway already includes any actions taken on mobile, so there is no separate ledger to consolidate.

Payment Types You Can Approve on Mobile

The value of mobile approvals depends on covering the payments that actually create timing pressure, and those are usually wires and ACH files. In Synovus Gateway, an approver can release domestic wire transfers, which are time-sensitive because same-day settlement depends on hitting the cutoff. Being able to approve a wire from a phone means a large vendor payment or a real estate closing does not stall because the authorizing officer is in a meeting or traveling. Synovus Gateway keeps that release button close at hand for exactly those moments.

ACH batches are the other common case. Payroll files, supplier disbursements, and collection files often carry a fixed effective date, and Synovus Gateway lets an approver confirm the batch total and effective date on mobile before the file transmits. Because the mobile view in Synovus Gateway shows the same batch header the initiator created, the approver is confirming the same aggregate amount and count that will actually process, not a summary that hides detail.

Approvals also apply to internal transfers between company accounts and to any templated payments your treasury team has set up in Synovus Gateway. The exact set of payment types available to a given user is governed by that user's entitlements. If an organization does not enable wires for a particular approver, the Synovus Gateway mobile app will not present wires to that person, and the same holds for ACH, transfers, and other services. Synovus Gateway keeps the mobile capability strictly inside the boundaries already defined on the account.

Security Controls Behind Mobile Approvals

Moving approvals to a phone raises an obvious question, which is whether convenience weakens the controls that protect the money. Synovus Gateway answers that with the same layered security it applies to the desktop portal, plus device-level protections that the mobile environment adds. Access to the app requires the user's credentials, and Synovus Gateway supports multi-factor authentication so that a stolen password alone cannot reach the approval queue.

Dual authorization is the structural control that matters most for payments. When your treasury policy requires two approvers, Synovus Gateway enforces it on mobile exactly as it does on the desktop, and one person cannot both initiate and single-handedly release a payment that requires a second set of eyes. This separation of duties is a widely recommended safeguard against payment fraud and internal error, and keeping it intact on mobile is central to the design of Synovus Gateway. For background on why organizations separate these responsibilities, the general principle is documented in public references on separation of duties.

The Synovus Gateway mobile app also relies on modern device security. Where a phone supports biometric unlock, users can gate the Synovus Gateway session behind a fingerprint or face check, and inactivity timeouts close a session that is left open. Because approvers see genuine payment detail before acting, they act as a human control against fraudulent instructions, which matters given that business email compromise and payment redirection remain among the costliest schemes reported to the public, as ongoing coverage from outlets such as Reuters continues to note. Synovus Gateway supports that human review by surfacing the beneficiary and amount clearly on the approval screen.

Roles, Entitlements, and Limits

Mobile approvals are only as safe as the entitlement structure behind them, and Synovus Gateway lets an administrator define who can do what at a granular level. Roles typically split into initiators, who build payments, and approvers, who authorize them, though a single person can hold both rights on payment types where policy allows it. Your company administrator assigns these rights inside Synovus Gateway, and the mobile app inherits them without any separate setup.

Dollar limits reinforce the role structure. Synovus Gateway can cap the amount a given approver may release, per transaction or over a period, so a junior officer approving on mobile cannot exceed the authority the organization intends. Combined with dual-approval thresholds, this lets a treasury team route small routine payments through a single approver while forcing larger payments to gather two approvals before Synovus Gateway will release them.

Administrator functions such as adding users or changing entitlements generally remain a desktop task inside Synovus Gateway, which keeps the highest-privilege changes in a controlled environment while leaving the day-to-day approval work available on mobile. This division means Synovus Gateway can grant broad mobile access to approvers without exposing the sensitive administration screens to a handheld device.

Desktop Portal vs. Mobile Approvals

Mobile is not a replacement for the desktop portal in Synovus Gateway. It is a focused tool for the approval step, where speed matters and full data entry does not. The table below summarizes where each is the better fit, so treasury teams can decide which work belongs on which surface within Synovus Gateway.

In practice, teams build and stage payments on the desktop portal during business hours and reserve the Synovus Gateway mobile app for the moments when an approval cannot wait. Synovus Gateway keeps both surfaces in sync, so an item staged in the morning can be released from mobile in the afternoon without re-entering anything. This is the practical payoff of keeping a single record inside Synovus Gateway rather than splitting the workflow across disconnected tools.

How to Get Started with Mobile Approvals

1. 1

   Confirm your entitlements with your company administrator. Only users who already hold approval rights in Synovus Gateway can approve payments on mobile.

2. 2

   Install the mobile app associated with the Synovus Gateway commercial service and sign in with your existing Synovus Gateway credentials.

3. 3

   Complete multi-factor authentication and enable biometric unlock on your device so each Synovus Gateway session is protected before it reaches the queue.

4. 4

   Open the pending approval queue, review a test or low-value item end to end, and confirm the detail matches what appears on the Synovus Gateway desktop portal.

5. 5

   Set your internal policy for when mobile approval is appropriate, then begin releasing time-sensitive payments through Synovus Gateway on mobile.

Best Practices for Remote Approvals

Getting the most from mobile approvals is partly a matter of policy. The strongest treasury teams keep dual authorization on high-value payments regardless of channel, so the convenience of mobile never becomes a way to bypass a second approver in Synovus Gateway. Setting sensible per-transaction limits on individual approvers is the companion habit, since limits mean a lost or compromised device still cannot release more than the assigned authority allows within Synovus Gateway.

Approvers should also treat every mobile approval as a verification step, not a rubber stamp. Because Synovus Gateway shows the actual beneficiary and amount, an approver who receives an unexpected or oddly worded payment request has the information needed to pause, confirm the instruction through a known channel, and reject anything that does not reconcile. This human check is the last line before funds leave, and it is where mobile approvals in Synovus Gateway earn their keep when a suspicious wire lands in the queue.

Finally, keep the audit trail useful. Synovus Gateway records who approved each payment and when, so reviewing that history periodically confirms that approvals are coming from the expected people at reasonable times. If your organization notices approvals in Synovus Gateway happening at unusual hours or from unexpected users, that is a prompt to review entitlements and device security rather than a routine event to ignore.