How to Handle Positive Pay Exceptions
Positive pay catches fraud by comparing every check that hits your account against a list of checks you actually wrote. When a presented check does not match that list, the bank flags it as an exception and waits for you to decide what to do. That decision has a deadline, and missing it has consequences. This page explains what exceptions are, how the daily review window works, and how to work through flagged items without guessing.
What a positive pay exception is
An exception is any check that clears your account but does not match the check issue file you sent the bank. Most banks compare a few fields on each cleared item against your issued list: the check (serial) number, the dollar amount, and often the payee name. If any of those does not line up, the item drops into an exception queue for your review instead of paying automatically.
Common exception reasons you will see, using the labels most bank portals use:
- Paid not issued or issue not on file: a check cleared that the bank has no record of you issuing. This is the classic counterfeit signal, and it also happens when you simply forgot to include the check in your upload.
- Amount mismatch: the cleared amount differs from the amount on your issued check. An altered check shows up here, and so does a typo in your register.
- Invalid or duplicate serial number: the check number does not match issue information, or the same check number cleared twice.
- Stale dated: the check is older than your stale-date threshold. Banks often default to 180 days unless you set your own limit.
- Payee mismatch (payee positive pay only): the payee name on the cleared check does not match the name you issued it to.
An exception is not a verdict. It is a question. The bank is asking whether this specific item is a real check you authorized or something you want to send back.
The daily decision window
Exceptions are reviewed on a fixed daily schedule. Each business day the bank posts the items that did not match and gives you a cutoff time to mark each one pay or return. Across the banks we reviewed, cutoffs commonly fall between noon and 2:00 p.m. local time. Citizens Business Bank and First Multifamily Federal Credit Union both use a 12:00 p.m. cutoff for check exceptions, Prosperity Bank uses noon Central, and First Horizon uses 2:00 p.m. Central. ACH positive pay windows differ again; Choice Bank runs an ACH decision window from 8:00 a.m. to 3:00 p.m. Eastern. Your bank publishes its own time, so confirm it before you build a daily routine around it.
The deadline exists because the bank itself is on a clock. Under the Uniform Commercial Code, a paying bank generally has to decide whether to pay or return an item by midnight of the next banking day after it is presented. Your decision has to land early enough for the bank to act inside that legal window, which is why the customer cutoff sits in the early afternoon rather than end of day.
What happens if you miss the cutoff
If you do not decision an item by the deadline, the bank applies its default decision and makes the call for you. The default is set in your service agreement and is not the same at every bank. Citizens Business Bank states plainly that an item left undecided by the cutoff will be returned. Other institutions default to pay. Neither default is automatically the safe one:
- A default to return protects you from fraud you never looked at, but it will bounce legitimate checks if you are out of the office, which annoys real vendors and can trigger fees.
- A default to pay keeps good checks moving, but it lets a fraudulent item through on any day you forget to log in.
Find out which default your account uses and write it down. It tells you exactly how much risk a missed day carries.
Deciding pay or return
For each flagged item, the goal is to confirm whether the check is one you actually authorized. A workable order of operations:
- Read the exception reason first. A stale-date flag and a paid-not-issued flag call for completely different checks. The reason tells you where to look.
- Open the check image. Almost every positive pay portal shows the front (and often the back) of the cleared item. Compare the payee, amount, and signature against your records.
- Match it to your register. Pull the check number in your accounting file. If the amount and payee match what you recorded, the exception is usually a data problem, not fraud. The most common cause of a false exception is a check you issued but never uploaded, or one you uploaded with a different amount.
- Decide. If everything reconciles, mark it pay. If the payee looks wrong, the amount was altered, the check number is unfamiliar, or you cannot tie it to anything you wrote, mark it return and contact the bank's fraud or treasury desk. A returned item you suspect is fraud should be reported, not just bounced.
When you are unsure, returning is the more conservative choice. A legitimate vendor whose check is returned will call you, and you can reissue. A fraudulent check you paid is money gone.
Best practices that cut down on exceptions
Most exceptions are avoidable, and the ones that remain are easier to clear when your process is tight.
- Upload your check issue file the same day you print checks. A check that clears before its issue record reaches the bank becomes a paid-not-issued exception. Same-day submission is the single biggest reducer of false flags.
- Record voids and reissues. Include voided and stopped checks in your file so a reused or stale number does not surprise you later.
- Check the queue every business day, even on light days. Build it into a fixed time before the cutoff. Decisions you skip get made for you.
- Name a backup decisioner. Vacations and sick days are when fraud slips through a default-to-pay account. Give a second person access.
- Match your file format to the bank exactly. Many false exceptions trace back to a sloppy issue file: a wrong column, a stray comma in an amount, a check number with the wrong padding. Clean data going in means fewer mismatches coming out.
Getting the issue file right in the first place
Exceptions start with the file you send the bank. QuickBooks and most accounting software cannot export a positive pay file natively, so the issue list often gets hand-built in a spreadsheet, which is where formatting errors creep in. PositivePayMaker is a free, browser-based tool that converts your check register (CSV or Excel) into your bank's positive pay format. It runs entirely in your browser, so your check data never leaves your computer. It includes layouts built from published specs for banks like Chase and Huntington, a custom format builder for matching any layout your bank documents, and a file validator to catch problems before you upload. Higher-volume shops that want installed, multi-format desktop software may prefer paid tools such as Treasury Software or Big Red Consulting; for most small businesses, a clean free converter does the job.
Whichever tool you use, verify your first generated file with your bank before relying on it. Send a small batch, confirm it loads without errors on the bank side, and check that the resulting exception count looks right. A file the bank silently rejects produces a queue full of paid-not-issued exceptions, which is exactly what you are trying to avoid. For more on getting the upload right, see our QuickBooks positive pay guide.