Positive pay: the fraud control that fails on the exception deadline

Positive pay is a bank service in which a business sends its bank a file of the cheques it has issued — number, amount, date, and usually payee — and the bank compares every item presented against that list. Items that do not match are held as exceptions for the business to review and either pay or return. It is the standard defence against cheque fraud and altered items, and most banks offer it as a paid service.

What determines whether it actually works is not the matching. It is the exception review. Exceptions appear on a short window, typically the same business day with a cut-off in the morning or early afternoon, and every service agreement specifies what happens if nobody responds — pay by default or return by default. A business that has enrolled and never assigned the review has automated the detection and left the decision to a default it may not have read.

The positive pay variants worth knowing

• Standard positive pay — matches cheque number, amount and issue date against the file.
• Payee positive pay — adds verification of the payee name, which is what catches an altered payee on an otherwise valid cheque. It is usually an extra charge and it is the version worth having.
• Reverse positive pay — the bank sends you the items presented and you decide, without an issue file. Cheaper, weaker, and dependent entirely on your review discipline.
• ACH positive pay, or debit filters and blocks — the electronic equivalent, allowing debits only from authorised originators, within limits you set.
• Teller positive pay — extends the check to items presented in branch, which is a common gap in otherwise complete coverage.

The issue file is the whole mechanism

• It has to be transmitted before the cheques can be presented — same day as issue, not weekly.
• It has to include voided and reissued cheques, or they become exceptions.
• Manual cheques written outside the accounting system are the classic failure: they never reach the file, they present, they are flagged, and somebody approves them out of exception because they recognise the payee — which trains the reviewer to approve exceptions.
• Formats are bank-specific and unforgiving; a changed column order silently breaks the upload.

Name a reviewer and a backup, and check the default in the service agreement. Exception windows do not pause for holidays or annual leave, and the cost of an unreviewed window is the fraud the service was bought to prevent.

It changes who bears the loss

Beyond the operational benefit, enrolment matters legally. Banking agreements commonly shift responsibility for fraudulent items to a customer who was offered positive pay and declined it, or who enrolled and failed to review exceptions. That is worth reading before treating the monthly fee as optional: the question is not only whether the service catches fraud but who pays when it is not used.

Running it alongside the ledger

The file comes from the cheque register, so the control is only as good as the register. Ettex Books holds the payments ledger the issue file is generated from, Ettex Sheets tracks exceptions with the decision and who made it, and the electronic side of the same problem is covered in ach authorization form.

Being direct: this is bookkeeping and records, not a banking service. Positive pay is bought from your bank; what this covers is the discipline around it, which is where it usually fails.