Positive pay for builders is one of the simplest ways to stop a forged or altered check before it clears. The idea is straightforward: your bank compares every check presented for payment against the list of checks you actually issued, and anything that does not match is held for review. The hard part is the list. If your team runs Sage Intacct, that file usually depends on someone remembering to export it and upload it to the bank after every check run.
This guide explains how positive pay works, why builders carry more check fraud exposure than most businesses, where the manual process in Sage Intacct breaks down, and what it looks like when positive pay runs on its own.
Why Check Fraud Still Hits Builders Hard
Checks have not gone away in construction. Subcontractors, suppliers, and vendors are still routinely paid by check, and a busy builder can issue a high volume of them every month across several projects and entities. That volume is exactly what fraudsters look for.
According to the 2026 AFP Payments Fraud and Control Survey, 76% of U.S. organizations experienced attempted or actual payments fraud in 2025, and paper checks were the most targeted payment method, cited by 58% of respondents. Mail theft feeds the problem. FinCEN reported more than $688 million in suspicious activity tied to mail theft-related check fraud in a single six-month period in 2023. FinCEN Financial Trend Analysis on mail theft-related check fraud, September 2024
A stolen check can be washed, rewritten with a new payee or a higher amount, and deposited within days. Without positive pay for builders in place, the first sign of trouble is often a bank statement that arrives weeks later.
How Positive Pay Works
Positive pay is a fraud control offered by most commercial banks. It follows the same cycle every time:
- Issue. Your team prints or releases a batch of checks from the accounting system.
- Send the file. You send the bank a file listing each check: account number, check number, issue date, and amount. Many banks also accept the payee name, a stronger version often called payee positive pay.
- Match. When a check is presented for payment, the bank compares it against your file.
- Decide. Any check that does not match becomes an exception. Your team reviews it and tells the bank to pay or return it before the daily cutoff.
The protection is only as good as the file. A legitimate check that is missing from the file gets flagged as an exception, and a file that never reaches the bank leaves every check in that run unprotected.
Positive Pay for Builders: Why the Stakes Are Higher
Every business that writes checks benefits from positive pay. Builders face a few conditions that make it harder to run well and more costly to skip.
Multiple Entities and Multiple Banks
Many builders operate through several legal entities, such as a parent company plus separate entities for individual projects or developments. Each entity has its own operating accounts, and those accounts may sit at different banks. Every bank has its own file format and its own portal, which multiplies the work behind positive pay for builders.
Ad Hoc Checks
Not every payment goes out on the scheduled check run. A rush check to keep a subcontractor on site or a one-off payment to release materials is easy to issue and easy to leave out of the file. Those off-cycle checks are exactly the ones that end up unprotected or flagged by mistake.
Lenders and Auditors Are Watching
Draws depend on clean books. Lenders and auditors want proof that disbursements went where they were supposed to go, and a check-level record of what was sent to the bank, and when, makes that conversation much shorter.
Where Sage Intacct Positive Pay Breaks Down
Sage Intacct is built to handle multi-entity accounting, which is one reason it suits builders that operate through several entities. Positive pay is a different story. Sage Intacct can produce a positive pay file, but a common approach is a custom accounts payable report that pulls check number, date, and amount, which the team exports and uploads to each bank portal after every check run. Implementation partners note that this report cannot be uploaded to the bank automatically and may not meet every bank’s format requirements.
In practice, that leaves three gaps:
- Someone has to log in. If the person responsible is out, busy, or simply forgets, no file gets sent and every check in that run clears without a match.
- Ad hoc checks slip through. Off-cycle checks often never make it into a file at all.
- Every bank is different. More entities and more banks mean more formats, more portals, and more chances for an upload to fail without anyone noticing.
None of these are flaws in Sage Intacct itself. They are the cost of a manual step in a control that only works when it runs every single time.
What Automated Positive Pay for Builders Looks Like
Automation removes the manual step without changing how accounts payable works. A strong setup should:
- Read check data directly from Sage Intacct as payments are made, with no exports.
- Generate a file in each bank’s format, across every entity and account.
- Transmit on every check run, including ad hoc checks.
- Confirm each transmission and alert the team right away if one fails.
- Keep a check-level audit trail with the user and timestamp behind each action.
When those five things happen without anyone logging in, positive pay for builders stops being a task on someone’s list. It becomes a control that runs in the background and helps ensure only authorized disbursements clear your accounts.
How Rynoh Helps Builders on Sage Intacct
Rynoh gives builders on Sage Intacct two ways to close the gap between issuing a check and knowing it cleared the way it should.
- PosPay for Sage Intacct. Available on the Sage Intacct Marketplace, connects through Sage Intacct Web Services using your existing credentials. After a one-time setup, it generates bank-specific positive pay files and sends them for every scheduled and ad hoc check run, with no portal logins or manual uploads. It supports multiple banks and entities, works with more than 1,000 banks, and logs every transmission with a timestamp. “launched in August 2026”
- RynohBuild. For construction finance teams that want oversight beyond positive pay, adds daily reconciliation, verification of checks and payments against the ledger before funds leave the account, real-time alerts when an account is off balance, and a searchable, user-attributed audit trail.
PosPay closes the positive pay gap inside Sage Intacct. RynohBuild extends that same oversight to every account, every day.
Frequently Asked Questions
What is positive pay for builders?
Positive pay for builders is a bank fraud control in which a construction company sends its bank a file of every check it issues. The bank compares each check presented for payment against that file and holds any mismatch in check number, amount, date, or payee for review. It is especially valuable for builders that pay many subcontractors and suppliers by check across multiple entities.
Does Sage Intacct have positive pay?
Sage Intacct can produce a positive pay file, commonly through a custom accounts payable report. That file typically has to be exported and uploaded to each bank by hand after every check run, and it may not match every bank’s format. Tools such as Rynoh PosPay for Sage Intacct automate the file generation and transmission so no one has to log in.
Does positive pay cover ACH payments?
Check positive pay covers checks. Many banks offer a separate service, often called ACH positive pay or ACH debit block and filter, that screens electronic debits against rules you set. Builders should ask their bank which ACH controls it offers alongside check positive pay so both payment types are covered.
What happens if a check is missing from the positive pay file?
The bank treats it as an exception. Your team has to review it and approve payment before the bank’s cutoff, or the check may be returned depending on your default setting. For a builder, that can mean a delayed payment to a subcontractor or supplier, which is why covering ad hoc checks automatically matters.
How long does it take to automate Sage Intacct positive pay?
With Rynoh PosPay for Sage Intacct, setup is a one-time step that uses your existing Sage Intacct credentials and prebuilt bank configurations. Rynoh states that most teams are operational in hours, not weeks.
Positive pay for builders only protects you when the file reaches the bank on every check run, including the rush checks no one planned for. On Sage Intacct, that has traditionally meant a manual export and upload that depends on one person remembering. Automating it turns positive pay into what it was meant to be: a control that runs every time.
Want to see how it works with your banks and entities? Request more information about Rynoh PosPay for Sage Intacct
