What Is Positive Pay: Check, ACH, and UCC Liability

Positive Pay is a bank fraud-prevention service that compares every check and ACH debit presented against your account to a list of payments you’ve already authorized, and blocks anything that doesn’t match before the money leaves. Instead of catching fraud weeks later during reconciliation, the bank stops the suspicious item at the moment it’s presented and asks you what to do with it. The service comes in several forms covering paper checks, payee names, and electronic debits, and for a business account it’s often the difference between recovering a loss and absorbing it.

How Check Positive Pay Works

Check Positive Pay runs on a simple comparison. Every check presented against your account has to match a check you actually wrote, or the bank won’t pay it.

The workflow starts on your side. When your business prints checks, you transmit an “issue file” to your bank, ideally the same day. The file lists each check’s number, dollar amount, issue date, and account number. It has to reach the bank before those checks are presented for payment, because without it there’s nothing to compare against.

When someone deposits or cashes one of your checks, the bank’s equipment reads the MICR line along the bottom edge, which encodes the routing number, account number, and check number. The system cross-references the check number and amount against your issue file. Match, and it clears. Altered amount, unfamiliar check number, or a counterfeit drawn on stolen blank stock, and the system flags it as an exception and holds payment.

That covers the most common check fraud patterns. It doesn’t cover payee manipulation, which is where the next layer comes in.

Payee Positive Pay

Standard Check Positive Pay doesn’t verify who the check is made out to. If a thief intercepts a check and chemically washes off the payee name while leaving the amount and check number intact, basic matching won’t catch it. Payee Positive Pay closes that gap by adding the payee name to the issue file. When the check clears, the bank uses optical character recognition to read the payee line on the check image and compare it to what you authorized. A mismatch triggers the same exception process.

OCR isn’t flawless. Handwritten or smudged text can produce false positives. But for businesses issuing printed checks with machine-readable payee lines, it adds real protection against check washing.

How ACH Positive Pay Works

ACH Positive Pay works differently because there’s no physical item to read. Instead of uploading a file of items you’ve issued, you set standing rules that tell the bank which companies may pull money from your account and under what conditions.

The core mechanism is a whitelist of approved Originator IDs. Every company that initiates ACH debits has an Originator ID that identifies it in the ACH network. You give your bank the IDs you trust, and any incoming debit from an ID that isn’t on the list is blocked automatically. You can layer additional controls: a dollar cap per originator, a frequency limit, or a rule that blocks all incoming debits and forces you to approve them one by one.

Once set, the rules run on their own. You update them when your vendor relationships change.

Why a Business Account Needs This

Consumer accounts have federal protection under Regulation E, which caps liability for unauthorized electronic transfers and gives the customer 60 days to report problems. Business accounts get none of that. Regulation E defines a protected “account” as one established primarily for personal, family, or household purposes and limits “consumer” to a natural person.1Consumer Financial Protection Bureau. Electronic Fund Transfers Regulation E 1005.2 Definitions A commercial operating account sits outside the safety net.

The practical consequence is short. Under NACHA rules, a business has roughly two business days from settlement to return an unauthorized corporate ACH debit. Miss that window and the money is gone, with no regulatory mechanism to claw it back, compared to the 60-day window consumers enjoy.2Nacha. Differentiating Unauthorized Return Reasons ACH Positive Pay blocks the debit before it settles, so you’re not racing a clock you may not know is running.

Reverse Positive Pay

Not every business can maintain the daily discipline of uploading issue files. Reverse Positive Pay inverts the workflow. The bank sends you a daily list of checks presented against your account, and you flag anything you didn’t authorize. Items you approve clear; items you reject are returned unpaid.

The upside is simplicity. No issue files to generate or transmit. The downside is that you’re reviewing every presented check yourself instead of only exceptions. For low check volumes, that’s fine. For a company writing hundreds of checks a week, it becomes impractical fast. Reverse Positive Pay sits between no protection and full Positive Pay, and it depends entirely on your ability to review and respond before the bank’s daily cutoff.

What Happens When Something Is Flagged

When the system flags an item, clearing stops and you’re notified, usually through the bank’s online portal. The notice shows the item’s amount, check number, date, and often an image of the check.

Your decision is binary: pay or return. “Pay” fits when the item is legitimate but your issue file had a typo or wasn’t uploaded. “Return” confirms the item is unauthorized and directs the bank to reject it.

The window is tight, generally one to two business days depending on the bank’s cutoff. If you don’t respond, the bank applies its default disposition. Many banks default to returning unreviewed items, which is safer against fraud but can bounce legitimate payments to vendors when nobody reviewed them in time. Some banks let you set the default at the account level, so raise it during setup.

Positive Pay doesn’t just run in the background. Someone has to log in daily, review exceptions, and decide before cutoff. Businesses that treat exception review as optional tend to find out the hard way that their default either passed a fraudulent check or bounced a real one.

What Positive Pay Does Not Catch

Positive Pay is effective against a specific set of threats. Knowing its blind spots matters.

  • Internal fraud. If an employee with check-writing authority issues an unauthorized check and includes it in the issue file, the system approves it. As far as matching logic is concerned, it’s authorized.
  • Payee fraud without the payee module. Standard Check Positive Pay validates check numbers and amounts, not payee names. A washed check with the original amount and check number will pass. You need Payee Positive Pay to catch it.
  • Authorized push payment scams. If a fraudster impersonates a vendor and tricks you into issuing a real payment to a fake account, you’ll upload that check to the issue file yourself. Positive Pay catches unauthorized items, not payments you were deceived into authorizing.
  • Timing gaps. If the issue file isn’t uploaded before a check is presented, the bank has nothing to compare against. Depending on configuration, the check gets flagged as unmatched or processed under a default rule. Same-day uploads matter.

Treat Positive Pay as one layer in a broader fraud strategy, alongside internal controls, dual authorization on payments, and vendor verification.

Liability Under the UCC and Why Declining Matters

The legal framework for check fraud liability comes from the Uniform Commercial Code, adopted in some form by every state. Positive Pay doesn’t just prevent fraud; it can also shift who bears the loss when fraud happens.

The Baseline

Under UCC Article 4, a bank may only charge your account for items that are “properly payable,” meaning items you actually authorized.3Legal Information Institute. UCC 4-401 When Bank May Charge Customer Account An altered or forged check isn’t properly payable, and the default rule puts the loss on the bank. Two provisions erode that protection.

Your Duty to Review Statements

UCC Section 4-406 requires you to examine your bank statements with “reasonable promptness” and report unauthorized signatures or alterations. If the same fraudster hits your account repeatedly and you miss the first instance, you can lose the right to recover on later checks from the same source.4Legal Information Institute. UCC 4-406 Customer Duty to Discover and Report Unauthorized Signature or Alteration

Negligence That Contributes to Fraud

UCC Section 3-406 goes further. If your failure to exercise ordinary care substantially contributed to the forgery or alteration, you’re precluded from asserting the fraud against a bank that paid in good faith.5Legal Information Institute. UCC 3-406 Negligence Contributing to Forged Signature or Alteration of Instrument Unsecured blank check stock, mailing checks without safeguards, or declining fraud tools your bank offered can all be characterized as failures of ordinary care.

Declining Positive Pay Can Shift the Loss to You

Many banks now include Positive Pay clauses in their commercial deposit agreements. A typical provision says that if the bank offers Positive Pay and you decline it, you accept responsibility for fraud losses the service was designed to prevent. Courts have enforced these provisions. In one federal case, a commercial customer that repeatedly declined to implement Positive Pay was barred from recovering losses on altered checks; the court held the deposit agreement permissibly allocated the risk to the customer and validly varied the default UCC “properly payable” rule.

Even without an explicit clause, declining an available fraud tool gives the bank a strong argument under Section 3-406 that your negligence contributed to the loss. Positive Pay has become widespread enough that courts and regulators increasingly treat it as a commercially reasonable security measure. Turning it down when your bank offers it is a decision with legal consequences, not just an operational preference.

What It Costs and How Setup Works

Pricing varies by bank and usually sits inside a treasury management fee schedule rather than as a standalone product. Expect a monthly service fee for the module, a per-account fee, and per-item charges. Per-item fees typically apply both to items in your issue file and, at a higher rate, to flagged exceptions. Check Positive Pay and ACH Positive Pay carry separate monthly fees. Payee Positive Pay is usually an add-on with its own charge. Reverse Positive Pay carries a lower monthly fee but still charges per exception. Ask for the full fee schedule rather than a summary, because ancillary charges add up.

Setup involves your accounting team and the bank’s treasury management group. A service agreement defines the technical parameters, your file transmission responsibilities, the exception review process, and the default disposition for unreviewed items.

For Check Positive Pay, the main technical requirement is a reliable method for transmitting the issue file. Most banks support manual upload through the portal, automated transmission via Secure File Transfer Protocol, or direct integration between your accounting software and the bank through an API. A company writing a dozen checks a month can upload manually. A company processing thousands needs automation. Your accounting software likely has a Positive Pay export function, but it will need to map to your bank’s specific format during setup.

For ACH Positive Pay, setup is less technical but requires more planning. Build your initial whitelist by gathering ACH Originator IDs from every vendor, payroll processor, tax authority, and insurance company authorized to debit your account. Miss a legitimate originator during setup and its next debit gets blocked, so build a complete list before going live.

The maintenance obligation is straightforward and unforgiving. Upload issue files every day you write checks, before the cutoff. Review and decision exceptions daily. Update ACH rules whenever vendor relationships change. The service works only as well as the internal process behind it.