Reverse Positive Pay, Explained: How Reviewing Presented Checks Yourself Catches Fraud Without an Issued-Check File

You write maybe a dozen checks a month — rent, a contractor, the quarterly insurance premium. One Tuesday morning you open your bank's business portal and there is a short list waiting for you: every check presented against your account yesterday. Three of them are yours. The fourth is a check you never wrote, drawn on your account number, made out to a name you have never paid. You click "return," the bank bounces it, and the fraud dies right there for the price of two minutes of your morning. That daily list — and your daily decision — is reverse positive pay.

What reverse positive pay actually is​

Reverse positive pay is a check-fraud control your bank offers that flips the standard positive pay workflow around. To see the difference, start with the standard version: every time you issue checks, you send the bank an issue file — check numbers, dates, amounts, sometimes payee names. When a check is presented for payment, the bank compares it against your file automatically. Matches clear; mismatches get flagged as exceptions for you to approve or reject.

Reverse positive pay removes the issue file entirely. Instead, the bank sends you a report of everything presented against your account, usually the business day after presentment, and you decide what is legitimate. Nothing is matched automatically. Your eyes are the matching engine.

That sounds like a weaker version of the same thing, and in one sense it is. But it exists for a practical reason: plenty of small businesses cannot produce an issue file at all. If you write checks by hand, or your accounting setup has no export your bank accepts, standard positive pay is protection you can never switch on. Reverse positive pay asks nothing of your systems — only a few minutes of a human's morning. That is why banks pitch it specifically at low-volume check writers: businesses that write ten checks a month get real protection from it, while businesses writing a hundred a month would drown in the daily review.

How the daily workflow works​

The cycle runs every business day, and once you see it you will understand both the service's power and its one big demand on you.

Day one: checks are presented. Someone deposits or cashes checks drawn on your account — your real payees, and possibly someone else's forgery. The bank pays these items in the normal course of business. Nothing is held for verification the way standard positive pay holds exceptions.

Day two: the bank posts your report. The morning after presentment, the bank publishes a list of every check presented the prior business day in your online banking portal. Each item typically shows the check number, amount, and often an image of the physical check. Some banks also make the report available through a mobile app so the review does not depend on anyone being at a desk.

You review and decision each item. You — or whoever owns this job — compare every item on the report against your own check register: your books, your accounting software, your carbon copies. Legitimate items you mark "pay." Anything you do not recognize, or whose amount or payee looks wrong, you mark "return." The bank then returns the rejected items unpaid.

The deadline decides everything you skipped. Every bank sets a daily cutoff for your decisions, and the cutoff is early in the day — commonly late morning to mid-afternoon depending on the bank. Items you have not decisioned by the cutoff are paid by default. There is no second chance queue: a fraudulent check you never got around to reviewing clears exactly like a legitimate one.

One structural gap to know about: teller-cashed items are typically excluded from the report. A check cashed over the counter at a branch often never appears on your review list, because the bank already parted with the cash. Ask your bank explicitly how it treats teller-cashed items before you enroll — this is the most common "but I thought I was covered" surprise.

The deadline is the whole game​

With standard positive pay, only exceptions need your attention — most days there are none, and silence is safe. Reverse positive pay inverts that: every presented check needs your attention, and silence means "pay everything." That makes the daily deadline the load-bearing wall of the entire control.

Cutoff times vary by bank. Some set the decision deadline around midday, others mid-afternoon; a few give you until roughly 10 AM the next business day after the report posts. What matters more than the specific hour is the failure mode: miss the window — a sick day, a vacation, a busy Monday when nobody opened the portal — and every fraudulent item in that day's batch clears automatically. There is no partial credit for reviewing four out of five days a week. A forger only needs one unreviewed day.

This has three practical consequences worth planning for before you enroll:

1. Name a backup reviewer. The review cannot belong to one person with no coverage. Whoever can approve or reject items needs a trained second who actually watches the inbox when the first is out. Banks generally let you enroll multiple users with decision authority.
2. Turn on every alert the bank offers. Text and email notifications when the daily report posts, and especially when the cutoff is approaching with undecided items, are the difference between a control and a hope.
3. Treat review volume as a tripwire. If your check volume grows past the point where a human carefully reviews every item every day — many bankers put the comfort zone at a few dozen checks a month — that is your signal to graduate to standard positive pay, where the bank's automated matching does the bulk work and you only see exceptions.

What it catches — and what it misses​

Reverse positive pay earns its keep against the most common check-fraud shapes, because all of them produce an item on your report that does not match your register:

• Counterfeit checks. Forgeries printed with your account number show up as check numbers you never issued. Against your register, they stick out immediately.
• Altered checks. A legitimate check whose amount or payee was changed after it left your hands — the classic "washed check" — appears with details that do not match what you recorded. Check images in the report make this comparison concrete.
• Duplicate presentment. The same check deposited twice, or deposited after you already paid it, appears as a second presentment your register says should not exist.
• Stale, voided, or stop-payment checks. A check you voided months ago that someone tries to cash anyway is instantly recognizable as yours-but-dead.

What it misses — or catches only if your review is genuinely careful — is the other half of the honest picture:

• Payee-name alterations without close image review. Standard positive pay with payee matching compares the payee name automatically. Under reverse, the altered payee is visible only if the reviewer opens the image and reads it, not just the number and amount. A reviewer who skims amounts will clear these.
• Anything you rubber-stamp. The control is exactly as good as the review. A daily list approved on autopilot, without comparing to the register, is security theater with a monthly fee.
• Electronic fraud. Reverse positive pay covers paper checks only. Fraudulent ACH debits pulling straight from your account need a separate control — ACH positive pay or ACH debit filters, which work on authorization rules rather than daily review.
• Teller-cashed items, as noted above, which typically bypass the report entirely.

None of this is an argument against the service. It is an argument for knowing which fraud shapes each control covers, so the gaps get covered by something else instead of by nobody.

Reverse vs. standard positive pay: which fits your business​

The choice comes down to volume, systems, and who you want doing the matching.

A freelancer writing eight checks a month should take reverse positive pay and never look back: the review takes minutes, there is no file to generate, and the fee is small. A business writing a hundred checks a month, or one whose accounting software can already produce an issue file, should take standard positive pay: at that volume the daily review becomes a part-time job, and automated matching plus payee verification is strictly stronger protection.

There is also a middle path many banks support: start on reverse, and migrate to standard when volume or staffing makes the daily review unreliable. The fraud landscape does not care which control you use — checks remain the most fraud-hit payment method in the country, with well over half of organizations reporting attempted or actual check fraud in recent AFP surveys — so the right answer is the control you will actually operate every day, not the stronger one you will let lapse.

Booking it in your ledger​

Reverse positive pay touches your books in two small ways, and both are easy to get right if you handle them deliberately.

First, the monthly service fee is an ordinary bank charge. Book it when it hits the statement, the same as any account fee.

Second, decide in advance how voided and reissued checks are recorded, because the review process surfaces them. When the report shows an altered check and you return it, nothing cleared your account — but your books still show the original payment to the real payee as outstanding. You need to void the original check entry and record its replacement, so the reissued check does not look like a duplicate payment at month-end. Here is the shape of that in a plain-text ledger:

2026-10-01 open Assets:Checking:Operating
2026-10-01 open Expenses:Office:Supplies
2026-10-01 open Expenses:Bank:Service-Charges
 
2026-10-14 * "Staples" "Check 1042 - office supplies"
  Assets:Checking:Operating  -245.18 USD
  Expenses:Office:Supplies
 
2026-10-16 * "First Bank" "Reverse positive pay monthly fee"
  Assets:Checking:Operating  -15.00 USD
  Expenses:Bank:Service-Charges
 
2026-10-17 * "Staples" "Check 1042 voided - altered in transit, returned unpaid"
  Assets:Checking:Operating   245.18 USD
  Expenses:Office:Supplies   -245.18 USD
 
2026-10-17 * "Staples" "Check 1043 - reissue of voided check 1042"
  Assets:Checking:Operating  -245.18 USD
  Expenses:Office:Supplies

The void-and-reissue pair keeps the expense recorded exactly once while tying the paper trail together: check 1042 went out, came back fraudulent, was voided, and check 1043 replaced it. Anyone reconciling the account — including you during tomorrow's review — can see the full story. For the mechanics of querying outstanding checks from a ledger like this, the Beancount documentation covers balance and clearing workflows in detail.

Your next three steps​

If you write checks and have no positive pay of either flavor today, you are exactly who this service is for. Call your bank's treasury or business banking line this week and ask four questions: what is the daily decision cutoff, are undecided items paid by default, are teller-cashed items included in the report, and what is the monthly fee. Then name two reviewers — yourself and one backup — and put a recurring morning block on both calendars for the review. The control costs minutes a day and stops the fraud shape that hits small businesses most often. The only way it fails is the day nobody looks.