Skip to main content
Product WalkthroughsGuideIntermediate

Setting Up Positive Pay to Catch Check Fraud

Every check you issue, checked against what your bank reports as cleared - amount mismatches, wrong-account clears, and a voided check that clears anyway all surface on their own.

Vijay PatelHead of Product, Accountdesq Updated 8 min readIndia, United Kingdom, United States +1

30-second summary

  • Positive Pay is a comparison register, not a live bank feed - it reads Vendor Payments recorded with a cheque source and checks them against Bank Transactions your statement import already matched.
  • A check is "issued" the moment you record that Vendor Payment - there is no separate check-writing step.
  • "Cleared" is not a separate action inside Positive Pay - it happens automatically once the ordinary Bank Transactions Match step links a statement line to that vendor payment.
  • Every check lands in one of six states: outstanding, cleared, voided, amount_mismatch, wrong_account, or voided_but_cleared.
  • voided_but_cleared is the one that should never happen - a check you voided in your own books still cleared through the bank, which is exactly the fraud/error pattern this control exists to catch.

What Positive Pay actually compares

Positive Pay is a fraud-control register, not a live connection to your bank. It takes every check you have recorded as issued and checks it against what your imported bank statement has already matched inside Bank Transactions - catching a check that cleared for the wrong amount, or through a different bank account entirely, on top of the more obvious "did this clear yet" question. There is no file sent to the bank and nothing pulled from it automatically; it works entirely from records already inside AccountDesq.

Recording an issued check

There is no separate "write a check" step. Issuing a check just means recording an ordinary Vendor Payment with its source set to Cheque, a cheque/reference number, and the specific bank account it is drawn on. That one record is both the payment itself and its Positive Pay register entry - nothing else to fill in, and nothing to remember to do afterward.

How cleared-check matching works

Matching is not a separate action inside Positive Pay either - it reuses the ordinary Bank Transactions Match step. When you import a bank statement and match a line to that vendor payment, Positive Pay picks that up automatically and shows the real cleared amount, date, and account. One detail matters here: matching is checked against a transaction on ANY of your bank accounts, not only the one the check was issued from - which is exactly what makes it possible to catch a check that cleared through the wrong account.

What each status means

Every issued check lands in exactly one of these
StatusWhat it meansWhat to do
outstandingIssued, and nothing has cleared against it yetNothing - this is the normal state until the bank processes it
clearedMatched to a bank transaction on the same account, for the same amountNothing - a clean match
voidedYou voided the check in AccountDesq, and nothing has cleared against itNothing - the safe, expected result of a void
amount_mismatchMatched, but the bank transaction amount does not equal the amount you issued forInvestigate today - could be an altered check or a data-entry error on either side
wrong_accountMatched, but the bank transaction posted to a different bank account than the one the check was drawn onInvestigate today - a check should never clear through an account it was not issued from
voided_but_clearedYou voided the check, but it still cleared through the bankTreat as a live incident - contact your bank immediately

Every issued check lands in exactly one of these

voided_but_cleared is the status that should never appear

A void means you have told AccountDesq this check will never be paid. If a bank transaction matches it anyway, someone (or something) cashed a check you already cancelled - the exact fraud/error pattern Positive Pay exists to catch. Positive Pay groups amount_mismatch, wrong_account, and voided_but_cleared together into one exception count on the register so none of the three can quietly sit unreviewed among a long list of clean, outstanding checks.

Worked example: an amount mismatch

You issue a ₹25,000 check to a vendor. The imported bank statement shows a transaction for ₹25,200 that matches to it. Positive Pay reports this row as amount_mismatch, not cleared, and rolls it into the register’s exception count. Before assuming it is a small bank fee, confirm with the vendor and the bank what the extra ₹200 actually was - a real check-fraud attempt often starts with a small, easy-to-miss amount change.

Does Positive Pay stop a fraudulent check from clearing?

No - it is advisory only, the same as Watchlist Screening. AccountDesq does not connect live to your bank, so nothing here can block a check from clearing; it can only flag the mismatch once your next statement import brings the transaction in.

Do ACH payments or wire transfers show up in Positive Pay?

No - only Vendor Payments recorded with a Cheque source appear in the register. Positive Pay is specifically a check-fraud control; other payment methods are covered by ordinary Bank Transactions matching instead.

I found a wrong_account result but I am sure I issued it from the right account - now what?

Open the matched bank transaction and confirm which account it actually posted to. If your records and the bank genuinely disagree about which account a check cleared through, treat it the same as an amount_mismatch - contact the bank rather than editing the vendor payment to make the flag disappear.

Resources

Was this guide helpful?

Continue learning

Product Walkthroughs·Guide

Banking & Cash Operations in AccountDesq

What Categorize, Match, and Ignore actually do to a bank line - and which Banking screens genuinely post to your ledger versus which ones only help you decide.

13 min readUpdated Intermediate

Vijay Patel · Head of Product, Accountdesq

Product Walkthroughs·Guide

The Purchasing Workflow in AccountDesq

A Purchase Order never touches your ledger. A Goods Receipt does. A Bill does. Here’s the real accounting behind every purchasing screen in AccountDesq.

11 min readUpdated Intermediate

Vijay Patel · Head of Product, Accountdesq

One useful email a week

New guides, templates and tax deadlines that matter - no fluff, unsubscribe anytime.