Positive Pay Sounds Simple Until You Are the One Deciding What to Do With 15 Exceptions at 9 AM

Positive pay is one of the most effective bank fraud controls available to treasury teams. The concept is easy to explain: the company tells the bank what payments it expects, and the bank flags anything that does not match. In practice, the process is more demanding than that description suggests. How positive pay works depends on whether the organization is protecting checks, ACH transactions, or both. Each variant operates differently, generates different types of exceptions, and requires different decision workflows. For treasury analysts at large property managers handling hundreds of accounts across dozens of entities, positive pay is not a set it and forget it control. It is a daily operational commitment that requires attention, speed, and judgment.

Check Positive Pay: Matching What Was Issued Against What Was Presented

Check positive pay is the original form. The process starts when the company issues checks and transmits an issuance file to the bank containing the details: check number, dollar amount, date, and payee name. When a check is presented for payment at the bank, the bank compares it against the issuance file. If the details match, the check clears. If they do not match, the bank creates an exception.

Exceptions fall into predictable categories. A check presented with an amount that differs from the issued amount. A check number that does not appear on the issuance file at all. A payee name that does not match the issued record. A stale dated check that was issued months ago and never voided. Each exception requires the treasury analyst to review the item and make a pay or return decision, typically within a window of a few hours on the morning the exception is presented. We often see large property managers with active check programs generate 5 to 15 check exceptions per week across their account portfolio, each requiring manual review before the bank's decision deadline.

ACH Positive Pay: Filtering What Was Not Authorized

ACH positive pay operates on different mechanics. Unlike checks, where the company initiates the payment and tells the bank what to expect, ACH debits are initiated by external parties pulling funds from the company's account. ACH positive pay gives the company control over which originators are allowed to debit which accounts, for what amounts, and at what frequency. The company maintains an authorization filter, sometimes called an ACH debit block with exceptions, that tells the bank which incoming debits to allow and which to flag.

When an ACH debit arrives that does not match the filter, it becomes an exception. The treasury analyst must decide whether to authorize or return it, again within a tight window. ACH exceptions are often more ambiguous than check exceptions because the originator information may not clearly identify the source. A payroll tax debit from a state agency may arrive with a company ID the analyst does not immediately recognize. A utility payment may come through under a different originator name than expected. Bank fraud controls at the ACH level depend entirely on how well the authorization filter is maintained and how quickly the team can resolve ambiguous exceptions.

The Exception Decision Is Where the Process Gets Real

The issuance file and the authorization filter are the prevention layer. The exception decision is the judgment layer. Every exception is a question: is this legitimate or not. The answer is rarely obvious from the bank's exception report alone.

• A check exception shows a payee name mismatch, but the vendor recently changed its legal name and the issuance file was not updated

• An ACH exception flags a debit from an unrecognized originator, but it is a new insurance premium that AP set up last week without notifying treasury

• A check is presented for an amount that is one cent different from the issued amount due to a rounding difference in the AP system

• An ACH debit arrives from a utility company that services three properties, but the filter was only set up for two

Each requires the analyst to investigate, confirm, and decide within hours. Returning a legitimate item creates vendor disruption. Paying a fraudulent item creates financial loss. The pressure is asymmetric: the cost of a wrong pay decision is immediate and visible, while the cost of a wrong return decision surfaces days later as a vendor complaint or a service disruption at a property.

The Issuance File Is the Foundation. Most Problems Start There.

The effectiveness of check positive pay depends entirely on the quality and timeliness of the issuance file. A check issued on Monday but not transmitted to the bank until Wednesday leaves a two day window where that check could be presented without a matching record, generating a false exception. A voided check that was never removed from the file creates a phantom match that could authorize a fraudulent item. We often see 30% to 50% of check positive pay exceptions at large property managers trace back to issuance file timing or maintenance issues rather than actual fraud attempts. Treasury best practices require the issuance file to be transmitted on the same day checks are issued, and void records to be updated within 24 hours. The gap between that standard and actual practice is where most false exceptions originate.

What Arpari Provides for Positive Pay Operations

A company with five bank accounts and one check run per week can manage positive pay manually with minimal effort. A large property manager with 50 to 200 accounts across multiple banks, entities, and properties operates in a fundamentally different environment. Exception volumes scale with account count. Each bank may present exceptions through a different portal with a different deadline. The authorization filters for ACH must be maintained across every account, and property level changes like a new utility provider or a new tax jurisdiction require filter updates that are easy to miss. Bank fraud controls at this scale are only as strong as the operational process supporting them.

Arpari centralizes the bank data and treasury workflows that positive pay operations depend on. Issuance files can be managed through a single platform rather than transmitted bank by bank. Exception notifications are consolidated across institutions so the analyst reviews every item in one place rather than logging into multiple portals. ACH authorization filters are visible alongside account and entity structures, making it easier to maintain and update them as properties change. How positive pay works in practice becomes a governed, visible process rather than a daily scramble across disconnected bank channels. Treasury best practices are enforceable because the workflow is centralized rather than distributed across portals and spreadsheets.

Key Takeaways

How positive pay works in concept is simple: match what was expected against what was presented, and flag the rest. How it works in practice requires daily operational discipline, fast exception decisions under time pressure, and meticulous maintenance of issuance files and ACH authorization filters. Check positive pay catches mismatches against issued items. ACH positive pay filters unauthorized debits against maintained authorizations. Both generate exceptions that demand judgment, context, and speed. For large property managers operating at scale, the challenge is not understanding the control. It is maintaining the operational process that makes the control effective across dozens of banks and hundreds of accounts. The best positive pay program is not the one with the fewest exceptions. It is the one where every exception is reviewed, decided, and resolved before the deadline, every single day.

See it in action
Welcome to the next level of clarity from Arpari. Want to try it live? Book a 30-minute demo at www.arpari.com/demo to see how Arpari centralizes positive pay exceptions, issuance files, and ACH filters into one workflow across all your banks.

Arpari is the modern treasury platform for real estate owners, operators, and finance teams. We aggregate bank data, automate cash reporting, and now let you move money securely, across every bank, in one workspace.

‍