Commercial Card Management

Commercial Card Management and Virtual Card Solutions

This page explains how the commercial card management and virtual card capabilities inside Synovus Gateway let finance teams issue, control, and reconcile business card spending from a single online workspace. It covers what the tools do, how they behave day to day, and the practical decisions a controller or treasury lead needs to make when running a card program in Synovus Gateway.

How commercial card management works

A commercial card program in Synovus Gateway is organized as a hierarchy. At the top sits the company account, which defines the overall credit line and the master billing relationship. Beneath it, administrators create groups such as departments, cost centers, or locations, and beneath those sit the individual cardholders. This structure matters because most controls and reports in Synovus Gateway can be applied at any level, so a policy set once at the department level flows down to every card inside it.

When a new employee needs a card, an authorized administrator issues it directly in Synovus Gateway. The administrator sets a spending limit, assigns the card to a group, and applies any category restrictions before the card is ever activated. Because the request, approval, and issuance all happen in one place, there is a clear audit trail in Synovus Gateway from the moment a card is requested to the moment it makes its first purchase.

Day to day, cardholders use their cards the way they would any commercial card, while the program administrator watches the activity accumulate in Synovus Gateway. Transactions post to the portal, where they can be reviewed, coded to a general ledger account, flagged for a receipt, or disputed. The administrator does not need to wait for a paper statement at month end; the ledger in Synovus Gateway reflects activity as it clears.

Roles keep this manageable. Synovus Gateway separates the person who administers the program from the cardholders who spend and, often, from an approver who signs off on coded transactions or limit changes. A treasury lead can hold the top-level view, a department manager can approve within a cost center, and a cardholder can only see and act on their own activity. In Synovus Gateway this separation of duties is a control in its own right, and it is enforced by the permission model rather than by trust.

Virtual card solutions

A virtual card is a unique account number that exists only in software. It carries its own limit, expiration, and rules, but there is no physical card to lose, forget, or hand around an office. In Synovus Gateway, an administrator or an approved system generates a virtual card number for a specific purpose and delivers it to the person or process that needs to pay.

The most common pattern is the single-use card. Here Synovus Gateway issues a number tied to one expected charge, often matched to the amount of a purchase order or invoice. Once the supplier charges that amount, the card is effectively spent and will decline anything further. This makes single-use virtual cards in Synovus Gateway especially strong against duplicate billing and against a card number leaking after a transaction, because there is nothing left to steal.

A second pattern is the lodged or recurring virtual card, which stays open for a defined period and a defined supplier. A company might lodge a virtual card with a travel management partner or a recurring software vendor, letting Synovus Gateway route those charges through a controlled number while keeping the underlying account private. The supplier only ever sees the virtual number issued by Synovus Gateway, so the real account details never leave the building.

Virtual cards are also how many organizations pay accounts payable. Instead of cutting a check or sending an ACH, the payables team issues a virtual card through Synovus Gateway for each approved invoice. This can convert a slow, manual payment into a fast electronic one, and because commercial card spend frequently earns a rebate, it can turn a cost center into a modest source of return. The point is not the rebate alone, but that the same spend in Synovus Gateway becomes traceable, scoped, and reconciled automatically.

Because a virtual card can be born and retired in seconds, it fits workflows that a physical card cannot. A one-time vendor, a seasonal campaign, a contractor engaged for a single project, or an emergency purchase can each get its own number in Synovus Gateway, with a limit that exactly matches the need and an expiration that closes the door afterward. When the work is done, the card is deactivated in Synovus Gateway and the exposure disappears.

Spend controls and policy enforcement

Controls are where a card program earns its keep. Synovus Gateway lets an administrator shape what each card can and cannot do before any money moves, so policy is enforced at the point of purchase rather than caught weeks later in a review. The controls in Synovus Gateway stack on top of one another, and the tightest applicable rule always wins.

The most direct control is the credit limit. Every card in Synovus Gateway carries a spending ceiling, and virtual cards can carry one small enough to match a single invoice. Beyond a lifetime limit, an administrator can set velocity rules in Synovus Gateway that cap spending per day, per week, or per transaction, so a compromised card cannot drain a line before anyone notices.

Merchant category controls narrow where a card works. Using the standard merchant category codes that card networks assign, Synovus Gateway can allow a fleet card to buy fuel and repairs while blocking restaurants and retail, or permit a marketing card to spend at ad platforms and nowhere else. These category rules in Synovus Gateway travel with the card, so they apply everywhere the card is presented.

Temporary and conditional controls handle the exceptions that policy alone cannot anticipate. In Synovus Gateway an administrator can lift a limit for a single large purchase and let it snap back, freeze a card the instant an employee reports it missing, or open a category for one trip. Because these changes in Synovus Gateway take effect immediately, the control keeps pace with real business rather than the billing cycle.

For finance leaders, the value is that these controls are preventive. A well-configured program in Synovus Gateway declines out-of-policy spend at the register instead of generating a difficult conversation after the fact, which reduces both fraud loss and the softer cost of chasing employees for explanations.

Reconciliation, data, and reporting

A card program produces data whether or not anyone uses it, and the difference between a good program and a painful one is usually how that data flows into the accounting system. Synovus Gateway is built to turn raw card activity into coded, reconciled entries with as little manual keying as possible.

Every transaction that posts to Synovus Gateway arrives with rich detail: the merchant, the amount, the date, the card, and often line-level information from the supplier. Administrators and cardholders can attach a general ledger code, a project or cost-center tag, and a receipt image to each item. Rules in Synovus Gateway can pre-code recurring merchants automatically, so a monthly software charge lands in the right account without anyone touching it.

At period end, this coded data leaves Synovus Gateway as a structured export or a direct feed into an accounting or ERP system. Because the coding in Synovus Gateway happens continuously rather than in a single crunch, the month-end close becomes a review of exceptions instead of a marathon of data entry. The reconciliation is largely already done by the time the statement cycles.

Reporting in Synovus Gateway serves two audiences. Operationally, a program manager can watch spend by department, by merchant, by category, and by cardholder, spotting a maverick supplier or a drift toward an off-contract vendor. Strategically, the same data from Synovus Gateway feeds spend analysis that helps a company negotiate with its largest suppliers, because it can show exactly how much it buys and from whom.

The audit trail is a quiet but important product of all this. Since issuance, limit changes, transactions, coding, and approvals are all recorded in Synovus Gateway, an auditor or an internal reviewer can trace any dollar back to the decision that authorized it. That traceability is often what makes a card program run through Synovus Gateway acceptable to a company's controls framework in the first place.

Card program comparison

Most programs run a mix of card types. The table below outlines how the main options within Synovus Gateway typically differ, so a program owner can match the right instrument to each spending situation.

None of these is universally better. A field technician needs a physical card in a wallet, a payables clerk paying a one-off supplier is better served by a single-use number, and a travel desk booking dozens of trips wants a lodged card. Synovus Gateway supports all three from the same administration console, which is what lets a company right-size each payment instead of forcing everything through one card type. Because the choice sits in one place, a program owner can revisit it inside Synovus Gateway as spending patterns change.

Program metrics that matter

A card program is worth measuring, and a handful of indicators tell most of the story. The bars below illustrate the kinds of program health metrics a manager reviews inside Synovus Gateway; the figures are illustrative examples of a maturing program rather than a benchmark for any particular company.

Watching these numbers over time is how a program owner knows whether Synovus Gateway is doing its job. A rising share of coded-before-close transactions in Synovus Gateway means the reconciliation load is shrinking; a growing share of supplier payments moving to virtual cards means more spend is being captured cleanly; and a high percentage of cards inside policy means the controls in Synovus Gateway are set sensibly rather than being routinely overridden.

Commercial card and virtual card usage has grown across business banking as electronic payments displace checks; general industry reporting from outlets such as Forbes has tracked the broader shift toward digital B2B payments. The tools in Synovus Gateway are built to help a company participate in that shift on its own terms.

Common use cases

Accounts payable

A payables team replaces checks and slower transfers with virtual cards issued from Synovus Gateway, one per approved invoice. Payment speeds up, the vendor gets paid on a controlled number, and each payment reconciles to its invoice automatically inside Synovus Gateway.

Travel and expense

Employees carry physical cards with category controls that permit airlines, hotels, and ground transport while blocking unrelated spend. A travel desk can also lodge a virtual card with a booking partner, and every trip flows into Synovus Gateway already coded to the right cost center.

Subscriptions and software

Recurring vendors get lodged virtual cards, so a company can see exactly what it spends on software and switch off a number the moment a contract ends. This alone often surfaces forgotten subscriptions that Synovus Gateway makes visible in one report.

Project and contractor spend

A project lead requests a scoped card in Synovus Gateway with a limit and an end date that match the engagement. When the project closes, the card retires with it, and Synovus Gateway keeps the spend already tagged to the project for a clean cost report.

How to get started

Standing up a card program in Synovus Gateway follows a short, deliberate sequence. Working through it in order keeps the program in Synovus Gateway consistent from the first card forward.

1. 01

   Define the hierarchy. Map departments, cost centers, and approvers so that when cards are created in Synovus Gateway they fall into the right groups from day one.

2. 02

   Set the controls. Decide default limits, velocity caps, and merchant category rules at the group level in Synovus Gateway so every new card inherits sensible guardrails.

3. 03

   Issue the first cards. Create physical cards for ongoing spenders and configure virtual cards in Synovus Gateway for payables and recurring vendors.

4. 04

   Connect the coding. Set general ledger mappings and auto-coding rules, then confirm the export or feed into your accounting system so Synovus Gateway data lands correctly.

5. 05

   Review and refine. After the first cycle, use the reporting in Synovus Gateway to tune limits, tighten categories, and expand virtual card use where it saves the most effort.