A company issues a cheque for S$2,500 to a supplier. A few days later, its bank receives a cheque showing the same serial number but a different amount. The bank must decide whether to pay it. The company needs a dependable opportunity to recognise the discrepancy before money leaves the account, without delaying legitimate suppliers or treating every mismatch as proven fraud.
Cheque Positive Pay services compare incoming cheque presentments with the issuing company’s authorised file of cheques it actually wrote. Differences become exceptions for defined review and a timely pay-or-return decision. The gold standard is an accurately maintained issue file, authenticated instructions, clear decision cutoffs, correct default treatment and reconciled bank statements—not a promise that every kind of payment fraud is impossible.
The Chase treasury services guide describes Positive Pay comparison and optional payee verification, while the U.S. Office of the Comptroller of the Currency explains cheque washing, forgeries and unauthorised transactions. This is a specialist bank control distinct from Bank Payment Investigation, Direct Debit Collection and the wider Gold Standard hub. The provider examples describe U.S. banking products; local availability and legal duties vary.
At a glance: a Positive Pay exception is not yet a bank loss
| Control stage | What it proves | Next decision |
|---|---|---|
| Issue register | Company recorded an authorised cheque | Confirm file acceptance by bank |
| Presentment match | Serial, amount and optional payee compared | Review unsupported or conflicting data |
| Exception notice | Potential mismatch is visible | Authorised pay-or-return decision before cutoff |
| Bank action | Bank pays or returns according to rules | Verify true account posting |
| Final reconciliation | Issued and settled cheques agree | Resolve unresolved or disputed debits |
Fictional issue file and incoming bank items
| Cheque | Recorded by company | Presented to bank | Exception |
|---|---|---|---|
| 1048 | S$2,500 | S$5,200 | S$2,700 amount difference |
| 1049 | S$1,800 | S$1,800 | No amount difference |
| 1050 | S$900 | Not presented | Open valid issued cheque |
| 1051 | No issue record | S$1,100 | Unknown item, investigate |
These are examples, not a list of fraudsters or universal bank decisions. A responsible business verifies each exception, issues authorised instructions in time and reconciles what the bank actually debited.
Eighteen practical Positive Pay operating chapters
1. A Positive Pay match is a preventative check, not a cleared payment
Start with the company’s authentic issued-cheque record
Positive Pay typically compares the bank’s presented cheque with information sent by the business about cheques actually issued. A match may allow normal processing, while a discrepancy or missing record can prompt exception review. But sending an issue file is not the same as the bank paying the cheque, and a match alone cannot prove the underlying purchase or supplier relationship was legitimate.
Keep the financial stages distinct
Record authorised issuance, file receipt, presentment, comparison, exception, final decision and bank posting separately. Chase describes these stages in its treasury management services. A customer needs to know when the bank has accepted the file and when the cheque has actually cleared. A successful file upload with no bank acknowledgement should not be presented as effective fraud protection.
2. Positive Pay differs from reverse Positive Pay
The party performing the comparison changes
Under conventional Positive Pay, the issuer supplies a cheque issue file and the bank compares incoming presentments against it. Under reverse Positive Pay or cheque monitoring, the bank supplies presentment information and the company reviews items against its own internal records, sometimes using a preset threshold. The choice can change staffing requirements and the risk of missing a review window.
Do not apply one bank’s default response universally
Chase’s public descriptions distinguish Check Protection from Check Monitoring, including potentially different actions if an exception is not reviewed. The actual contractual settings determine whether an unanswered item is paid or returned. Staff must know which product and accounts are enrolled, and the process should test what happens when a reviewer is absent. Both models require timely attention and sound company records.
3. Create an issue file before the cheque can be presented
A late upload weakens the comparison
A legitimate cheque may reach the bank before a business’s issue file is uploaded or accepted. The bank can flag the cheque as unknown despite its authenticity, creating unnecessary investigation or a return. Worse, a file sent to the wrong bank account can falsely match an unrelated record.
Assign file creation and acknowledgement ownership
Use the provider’s prescribed fields for company account, serial number, amount, date and payee when supported. Confirm successful bank acceptance and process rejects before the cheque becomes available to the recipient. Do not treat a scheduled nightly export as complete merely because the accounting system says sent. Keep evidence of which items were validly registered for that banking day.
4. Check number, amount and payee answer different questions
One field cannot detect every kind of alteration
The cheque number can identify the issued item; the amount can reveal an unauthorised change; and payee verification, when available, can flag altered destination details. A correct cheque number by itself does not mean the amount or intended recipient is correct. Scanning and payee recognition can also produce ambiguous results rather than irrefutable proof.
Use the bank’s supported comparison features
Chase Positive Pay with Payee Name Verification describes using images and issue-file data. Define when a payee mismatch requires manual review, how legitimate legal-name variations are assessed and which exceptions require dual approval. Do not claim every Positive Pay plan verifies the payee: product capabilities and actual enrolment differ across banks.
5. A worked discrepancy should expose the original item
An issued S$2,500 cheque may be presented at S$5,200
In a fictional example, the business records cheque 1048, payable to Supplier A, for S$2,500. The bank receives an item with number 1048 but S$5,200. The comparison correctly raises a S$2,700 difference. A reviewer should examine the record and presentment evidence rather than pay an altered amount because the cheque number matches.
Avoid assuming the discrepancy proves a particular person committed fraud
It could be an altered cheque, an issue-file mistake or another operational problem. The business verifies its authorised documentation, confirms any correction through trusted channels and gives a valid bank instruction before cutoff. The S$2,700 is an arithmetic discrepancy, not money that has necessarily been lost. The final bank posting determines whether funds moved.
6. Missing issue records need practical exception treatment
A real cheque can be absent from the file
Emergency cheque writing, manual cheque books or a delayed software synchronisation can leave an item unregistered. The bank may therefore flag a cheque that is economically legitimate. Automatically classifying an unmatched item as fraudulent can harm a supplier, while paying all unmatched items defeats a major control objective.
Separate unidentified from established unauthorised items
Investigate original authorised purchase approval, cheque register, signer authority and evidence from the bank. If the business genuinely issued the item, use the permitted positive decision or valid record correction. Maintain why the exception occurred and repair the issuance workflow. The business should never fabricate a historic issue entry merely to avoid review.
7. Voids and stop-payment requests require different controls
A cancelled cheque number is not a new payable item
A company may physically void a cheque or request the bank to stop payment after loss, error or commercial dispute. The accounting ledger needs a void state, while the bank can have separate legal and operational stop-payment requirements. Uploading a revised issue file does not necessarily create every bank instruction needed to stop an otherwise payable instrument.
Reconcile the stop or void with actual banking authority
Store the bank’s accepted stop instruction, effective period and terms alongside the original issued record. Reconcile voided serial numbers and payment reversals. A cheque marked void in accounting software may still be payable if the bank has not received a valid stop. Do not promise that the act of clicking cancel guarantees legal nonpayment.
8. Exception decisions must meet the actual cutoff
A missed deadline can determine whether funds move
Banks can present exceptions to authorised company users and require payment decisions by a defined local-business-day time. Provider products may differ in whether no response means pay or return. The exact time and default cannot be guessed from another account’s practice.
Design staffing and escalation for genuine timeliness
Chase’s product materials warn businesses to act before the relevant cutoff. Assign primary and backup reviewers, alerting, holidays and escalation to a bank contact when a system is unavailable. The company must understand that a bank action can occur even while a manager is considering the discrepancy. A post-cutoff email may not reverse a payment already processed.
9. Pay-or-return authority requires authenticated people
A fraudster can target the review portal itself
Positive Pay loses much of its value if anybody with an ordinary accounting password can override a high-value exception or upload a new issue file. Separation between cheque preparation, bank file administration and exception approval helps detect tampering and mistakes.
Use user roles, secure changes and suitable dual control
Approve high-risk actions through properly authorised personnel with recorded timestamps and rationale. Audit additions to bank beneficiaries, user entitlements and device changes. The bank portal’s confirmation should be independently retrievable. A shared inbox or casual group-chat instruction is not a safe substitute for an approved bank pay decision.
10. An exception should not be treated as a customer accusation
Anomaly and misconduct are different states
The comparison engine may detect missing payee characters, altered amounts or an unknown cheque number. That justifies investigation, but it does not show who changed a cheque or whether there was criminal intent. Poorly handled accusations can damage vendor relationships and cause unnecessary payment disruption.
Preserve evidence and use neutral language
Describe the record mismatch, actual bank posting and requested verification. If the case is suspected fraud, use the bank’s secure reporting route and applicable legal process. The OCC’s fraud guidance discusses reporting unauthorised transactions promptly. Customers should not be left with a generic “fraud” label when the bank never proved any loss.
11. The cheque image needs independent source integrity
A scanned image can support but not replace controls
Banks may offer presentment images to help review cheque amount, date, payee and other visible details. The image might be blurred or contain recognition errors, and a digital representation may not capture every physical security feature. A decision should be based on the actual evidence and bank process.
Keep secure image access and relevant retention
Authorised reviewers should compare source records and consult the bank where ambiguity is material. Do not forward sensitive cheque images through unsecured personal messaging or expose full account details to unrelated employees. An image viewed after the deadline may still be important for recovery or investigation but cannot be presumed to change an already final posting.
12. Duplicate cheque attempts need careful reconciliation
A similar item may appear more than once
A bank can encounter duplicate deposit attempts or presentment records, and a company can accidentally upload duplicate cheque entries. The business should avoid paying twice for one authorised expense while distinguishing a duplicate technical notice from a genuine second bank debit.
Compare durable references and actual account postings
The Chase check-fraud guidance discusses duplicate presentment risk. Match original serial, account, amount, bank posting and any returned or adjusted entries. Do not assume two alert emails equal two settled withdrawals. If an unauthorised duplicate debit occurred, open the proper bank dispute and track the correction through receipt.
13. Positive Pay should not be confused with ACH debit control
Different instruments have different protections
A cheque issued by a company, a card payment and an ACH debit do not share the same authorisation records. Some banks offer ACH Positive Pay or debit blocking in addition to cheque Positive Pay. The cheque issue file does not by itself allow a customer to approve every electronic debit.
Apply the right control to each payment rail
Identify the business’s actual ACH services, approved originators or debit filters where relevant. Chase treasury services lists cheque and ACH fraud-protection products as separate offerings. Do not assure a firm that bank accounts are protected from all external withdrawals because its paper cheques are enrolled.
14. The issued item must reconcile to the company payable ledger
Fraud prevention and financial reporting are connected
A genuine cheque can be matched perfectly by the bank while the company has posted it to the wrong supplier invoice or expense period. Conversely, a bank-approved correction may not have been recorded in the accounts payable system. Positive Pay controls cheque authenticity, not complete procurement or financial-statement accuracy.
Trace purchase approval through bank debit
Maintain approved supplier invoice, cheque creation, signatories, bank accepted file, presented cheque and posted debit. Assign unmatched accounts payable or bank differences to a reviewer. A clean bank Positive Pay report should not be interpreted as proof that every underlying purchase was properly authorised.
15. File formats and system changes create avoidable exceptions
Simple data errors can stop valid payments
An accounting upgrade may strip leading zeros from serial numbers, truncate payee names, change currency formatting or export an amount in cents rather than dollars. The resulting mismatch can cause dozens of legitimate cheque returns during one business day.
Rehearse integration and recovery before release
Test representative issued, voided, amended and high-value cheques against the provider’s actual format. Compare sent count with bank accepted count and rejected rows. Preserve a manual contingency route with approvals if the automatic file fails. After recovery, reconcile every affected presentment; restarting the connector does not automatically repair incorrect bank decisions.
16. A fictional supplier payment is saved by a timely review
Three issue records tell a simple story
The company issues cheques 1048 for S$2,500, 1049 for S$1,800 and 1050 for S$900. The bank sees 1048 presented for S$5,200, 1049 for S$1,800 and an unknown item 1051 for S$1,100. Two records require review; cheque 1049 matches its registered amount, subject to other supported checks.
Close the actual financial outcomes rather than the alert
The company investigates and instructs valid return of the altered item and the unknown item before the applicable deadline. It then confirms through the bank that those items were not debited while the proper cheque was processed. The illustration is fictional and does not specify a universal default bank decision or prove the identity of a fraudster.
17. Fraud-risk measures need denominators and genuine results
Counting exceptions alone is not evidence of protection
A spike in mismatches might reflect more forgery attempts, a broken issue-file process or a newly enabled payee comparison. A quiet dashboard could mean clean payments or missing company files. The institution needs measures that distinguish detection quality from technical availability.
Audit meaningful performance and customer consequences
Measure actual bank issue-file acceptance, time to decision, wrongful returns, unresolved discrepancies, confirmed unauthorised debits, file-format failures and vendor complaints. Review exception root causes and repair them. A service that prevents a genuine unauthorised payment and can prove its result is more valuable than one that merely generates many warning emails.
18. The gold standard is a bank decision backed by an authentic record
Prevention must work on the payment day
Cheque Positive Pay can help deter or detect altered and unissued cheques, but it does not remove all fraud, account compromise or legitimate banking disputes. It is one control among careful issuance, signer authority and bank reconciliation.
The measurable promise is a truthful check-by-check outcome
A gold-standard service can reconstruct what the company issued, what the bank received, how each exception was decided and what was actually paid or returned. It makes supplier payments dependable while giving businesses evidence to investigate mistakes and potential fraud without overstating what the technology guarantees.
Cheque Positive Pay FAQs
Does Positive Pay guarantee no cheque fraud?
No. It compares the presentment with supported issuance data and still depends on accurate files, timely review and the bank’s actual process.
Does payee verification come with every Positive Pay service?
Not necessarily. It may be an additional feature requiring the payee in the issue file and appropriate image processing.
Will the bank always return an exception if nobody responds?
No universal assumption is safe. Defaults differ by product and agreement.
Is reverse Positive Pay the same as conventional Positive Pay?
No. The company can receive the bank’s presented items to review against its own register rather than pre-send each item for bank comparison.
Is cheque Positive Pay also a control for ACH debits?
No. Electronic debit controls are separate products or rules.
Does a bank alert mean the cheque amount was actually debited?
Not necessarily. Check actual processing and bank posting before treating the item as paid.
The cheque protection audit
- Match cheque issue files to approved payment requests and valid bank accounts.
- Validate issued, void and stop-payment handling under the actual bank agreement.
- Compare serial, amount and payee only to the extent supported by the enrolled service.
- Authenticate banking decisions, reviewers, permissions and exception deadlines.
- Distinguish alert, pay instruction, bank posting and actual return status.
- Reconcile duplicate items, errors, proper supplier invoices and finance records.
- Test issue-file failures, cutoff coverage and fraud escalation with clear customer communication.
Bank and regulator references and related eduKate articles
- Chase Business Treasury: Positive Pay and Payee Name Verification.
- Chase Business: Check Fraud, Altered Amounts and Duplicate Presentments.
- Chase Business Security: Check Protection and Reverse Positive Pay.
- OCC: Common Cheque Fraud and Reporting Misuse.
- eduKate: Bank Payment Investigation and Trace.
- eduKate: Direct Debit Collection.
- eduKate: Merchant Acquiring.
Educational bank fraud-control operations only. The bank examples are U.S.-specific; available Positive Pay features, pay-or-return defaults, service deadlines and customer legal remedies vary by account, institution and jurisdiction.