Wholesale and Retail Lockbox Services

A receivables module within Synovus Gateway that converts inbound paper payments into deposited funds and structured data, so your accounts receivable team can post faster and reconcile with less manual handling.

Lockbox services solve an old and stubborn problem. Businesses that receive payment by paper check still have to open envelopes, match checks to invoices, deposit the funds, and record every transaction against the right customer account. Done in-house, that work ties up staff, delays deposits, and introduces keying errors. Synovus Gateway lockbox services move the entire intake step to a controlled processing environment, where mail is collected, checks are captured, deposits are made, and payment detail is delivered to you as clean electronic data. Synovus Gateway treats the intake step as the front door of your receivables, not an afterthought.

The service on this page covers both major lockbox models. Wholesale lockbox is built for business-to-business receivables, where invoice volumes are lower but each payment carries rich remittance detail. Retail lockbox is built for high-volume consumer payments, where a scannable coupon accompanies the check and speed of processing matters most. Synovus Gateway supports both, and many organizations run both at once within Synovus Gateway because their payment mix spans corporate customers and consumer accounts.

Everything a lockbox produces flows back into the same portal you use for the rest of your treasury operations. Deposit reporting, remittance images, and reconciliation files all appear within Synovus Gateway, which means the funds side and the data side of a payment stay connected instead of arriving through separate channels. This page explains what the lockbox in Synovus Gateway does, how the wholesale and retail models differ, what data you receive, and how to get an account configured through Synovus Gateway.

How lockbox processing works

The collection and capture path

A lockbox begins with a dedicated post office box that receives your customers' payments in place of your own mailing address. Instead of directing remitters to your office, you print the lockbox address on invoices and statements. Payments arrive at that box, are collected on a defined schedule, and are transported to the processing site. Because pickups happen multiple times per business day, funds move toward deposit faster than they would if mail sat in an in-house mailroom overnight. Synovus Gateway coordinates that collection schedule so nothing lingers between the box and the deposit.

At the processing site, envelopes are opened, and each item is separated into the check and any accompanying documents. Checks are scanned to capture the payer, amount, and routing and account information. Accompanying documents such as invoices, statements, or coupons are also imaged. Synovus Gateway then applies the capture and data rules configured for your account, whether that means reading a scanline on a retail coupon or keying invoice numbers from a wholesale remittance. Every rule Synovus Gateway applies traces back to the configuration your team approved during setup.

Deposit and data delivery

Once items are captured, the checks are deposited to your account and the associated data is compiled into reporting and reconciliation output. This is the point where the two halves of a payment reconnect. You receive a credit to your deposit account, and you receive a file or an on-screen record that describes exactly which customers paid, how much, and against which invoices. Synovus Gateway makes both available so your accounts receivable team can post cash without re-handling paper, and Synovus Gateway keeps the credit and the detail in step.

Exception handling is a defined step rather than an afterthought. Payments arrive incomplete, illegible, unsigned, or without matching remittance detail more often than teams expect. A lockbox operation routes those items into a review queue where operators apply your rules, and Synovus Gateway surfaces exceptions with their images so you can make a decision quickly instead of chasing a physical document. Clear exception handling is what keeps a high-volume operation from stalling on the small share of items that do not process cleanly, and Synovus Gateway builds that queue into the standard workflow.

The whole path is designed around control. Dual custody of mail, image audit trails, and reconciliation between what was received and what was deposited all reduce the risk that a payment goes missing or is applied to the wrong account. When you evaluate a lockbox, the controls matter as much as the throughput, and Synovus Gateway treats both as part of the service rather than an add-on. That is the discipline Synovus Gateway carries into every processing site it runs.

Wholesale lockbox

Wholesale lockbox is designed for business-to-business receivables. In this model, payments tend to be larger in dollar value and lower in count, and they arrive with substantial remittance detail. A corporate customer paying an invoice will often enclose a check stub, a printed remittance statement, or a list of invoice numbers being paid, sometimes settling several invoices with a single check. The processing challenge is not raw speed but accurate association of one payment to one or many open items, and Synovus Gateway is configured for exactly that kind of matching.

Because each wholesale payment carries context, operators may key invoice numbers, purchase order references, or short-payment reasons directly from the remittance documents. Synovus Gateway captures these fields so they travel with the deposit into your reconciliation file. That detail is what lets your team apply cash at the invoice level rather than posting a lump credit and untangling it later, and Synovus Gateway keeps that detail attached to the item end to end.

Wholesale lockbox also handles the messier realities of commercial payments. A remitter may pay less than the invoiced amount and note a dispute, pay multiple invoices with rounding differences, or send a check with no remittance stub at all. Synovus Gateway supports capture rules and exception routing tuned for these situations, so your team sees the payment, the image of any enclosed documents, and the operator notes together. That combination shortens the research cycle that otherwise consumes analyst time at month end, and it is one of the reasons finance teams choose Synovus Gateway for commercial receivables.

A well-configured wholesale lockbox in Synovus Gateway reduces the days between receiving a payment and closing the corresponding receivable. It also improves the accuracy of your open-item aging, because payments are matched precisely instead of applied on account. For finance teams measured on days sales outstanding, that precision has a direct effect on reported working capital, and Synovus Gateway is designed to protect it.

Retail lockbox

Retail lockbox is designed for high-volume consumer payments where every payment follows a predictable format. Think of a utility bill, a loan payment, an insurance premium, or a subscription statement. Each is sent with a return coupon, and each coupon carries a machine-readable scanline that encodes the account number and often the amount due. That standardization is what makes retail lockbox fast and automatable, and Synovus Gateway is tuned to take advantage of it.

Because the coupon is standardized, retail processing leans heavily on automation. The scanline is read by machine, the payment is matched to the account, and the item advances without an operator keying data by hand. Synovus Gateway is built to move these payments through at scale, holding cost per item low while keeping the deposit timely. Where a wholesale item might justify manual keying, a retail item is expected to process automatically through Synovus Gateway, and only the exceptions draw human attention.

Exceptions still occur. A remitter may pay a different amount than the coupon states, send a check without the coupon, staple the check to the wrong stub, or write in a change of address. Retail processing rules define how each of these is handled, and Synovus Gateway routes the odd items to review while the clean majority flow through untouched. The efficiency of a retail lockbox in Synovus Gateway comes from keeping that manual share small.

The output of a retail lockbox is typically a single consolidated posting file. Rather than reconciling thousands of individual items, your systems ingest one file that credits each account. Synovus Gateway formats that file to match how your billing or receivables platform expects to receive it, so posting is a load step rather than a data-entry project. Synovus Gateway carries the same consolidated output pattern across each billing cycle you run.

Wholesale vs. retail at a glance

The two models are not interchangeable, and choosing correctly is the single biggest driver of value. The table below sets the defining traits of each side by side. Most organizations that carry both consumer and business receivables run both configurations under one Synovus Gateway relationship, and Synovus Gateway keeps them on a single set of credentials.

If you are unsure which model fits a given receivables stream, the practical test is the payment format. A payment that comes with a coupon and encodes its own account number belongs in retail. A payment that arrives with a remittance statement listing invoices belongs in wholesale. Synovus Gateway can route different payment types to the correct workflow, and the Synovus Gateway treasury team can help you map your streams during setup.

Data, images, and reporting

The reporting layer is where a lockbox earns its keep. Every payment that clears the operation produces a record, and Synovus Gateway packages those records so they are useful to both an operator reviewing a single item and a system ingesting an overnight batch. Inside Synovus Gateway you work with three kinds of output.

Deposit reporting

Deposit reporting tells you what was credited and when. It ties the total deposit back to the individual items that make it up, so the funds figure on your statement always reconciles to a detailed list. Within Synovus Gateway, deposit reporting is available the same day items are processed, which lets your team confirm cash position without waiting for a paper advice. Synovus Gateway keeps that report tied to the exact items behind it.

Remittance and image data

Images of checks and documents are retained and searchable, so an item in question can be pulled up by amount, date, or account without requesting a physical copy. For wholesale items, the keyed remittance fields travel with the image. For retail items, the scanline data does. In both cases, Synovus Gateway keeps the payment and its evidence together, which is what makes a later research request quick to resolve within Synovus Gateway.

Reconciliation and posting files

Reconciliation files are the machine-readable output your receivables or billing platform consumes. Synovus Gateway supports structured file formats that carry the account or invoice references, amounts, and item detail your system needs to auto-apply cash. The goal is straight-through posting, where a file loads and cash applies without an analyst rekeying anything. Where automatic application is not possible, the Synovus Gateway file still isolates the exceptions so staff work only the items that need judgment.

Access to all of this lives inside the portal you already sign into for the rest of your treasury activity. Because deposit reporting, images, and reconciliation output share one environment, Synovus Gateway keeps your lockbox from becoming a separate silo. Entitlements let you decide which users can view images, download files, or approve exception decisions, so the data is available to the right people and controlled from the same place. That single-environment design is a core reason organizations standardize on Synovus Gateway, and Synovus Gateway carries the same governance across every service in it.

How to read your processing metrics

Once a lockbox is running, a small set of numbers tells you whether it is doing its job. The illustrative meters below show the kind of figures a receivables manager watches inside Synovus Gateway. They are examples of the metric types, not a promise of specific results, since actual figures depend on your payment mix and how Synovus Gateway is configured for your account.

Watch these three together. A high posting rate with a low exception rate means your automation is well tuned; a strong same-day completion figure means your funds are moving as fast as the mail allows. When any of them drifts, Synovus Gateway reporting lets you drill into the underlying items to find the cause before it becomes a month-end problem. Synovus Gateway keeps every metric linked to the items that produced it, so no figure inside Synovus Gateway stands on its own.

How to get started

Setting up a lockbox is a configuration project, not a signup form, because the value comes from matching the workflow to your payment streams. The sequence below is how an implementation typically proceeds with Synovus Gateway.

1. Step 01

   Review your receivables. Identify which streams are consumer coupon payments and which are business remittances, and estimate item volumes for each. This mapping decides whether you configure wholesale, retail, or both within Synovus Gateway.

2. Step 02

   Define capture and exception rules. Decide which fields must be captured, how short payments are handled, and what happens to items missing remittance. These rules are the heart of the setup, and Synovus Gateway supports them for both models.

3. Step 03

   Design your output file. Match the reconciliation file format to what your receivables or billing system expects so cash applies automatically. Synovus Gateway formats output to your specification during this stage.

4. Step 04

   Update remit-to addresses. Print the new lockbox address on invoices, statements, and coupons so payments route to the box. Synovus Gateway usually stages this migration so both addresses work during the transition.

5. Step 05

   Test, then go live. Run sample items, confirm files post correctly, and set user entitlements. Once posting reconciles cleanly, the lockbox goes into production and reporting appears in Synovus Gateway.

Frequently asked questions