Payment Runs Done Right: Batching, Approvals, and Controls
Everything else in accounts payable — receiving the invoice, coding it, matching it, routing it for approval — is preparation. The payment run is the event. It is the moment money actually leaves the company's bank account, and it is the single point in the AP process where a mistake is the hardest to reverse. A bad invoice that gets caught at matching is a non-event. The same bad invoice that gets paid in a run is a recovery problem, a vendor conversation, and sometimes a loss.
Because the payment run is where money moves, it is also where fraud is aimed. The schemes that matter — a redirected vendor payment, a duplicate slipped into the batch, a payee that does not match an approved invoice — all have to survive the run to succeed. A disciplined payment run is therefore not bureaucratic overhead. It is the last and most important checkpoint, and a contractor that runs it loosely has left the cash door unlocked no matter how good the controls upstream were.
This article covers what a payment run is, how to choose a cadence, how to batch and prioritize, the controls that make the run safe, the construction-specific sequencing every contractor needs, the right payment-method mix, and how automation makes the run both faster and harder to attack.
$0M
Median annual fraud loss in organizations whose schemes involved billing or check-and-payment tampering — categories that succeed or fail at the payment run (ACFE Report to the Nations)
A payment run is the controlled, scheduled process of paying a batch of approved invoices together. Rather than cutting checks and sending ACH payments one at a time as invoices come due, the AP team collects all the invoices that are approved and due, assembles them into a single batch, runs that batch through a defined approval and review process, and releases the payments together.
Batching is not just an efficiency choice. It is what makes control possible. A run is a discrete, reviewable event with a defined list, a total, and a release step — which means a second person can review the whole thing before it goes out. Paying invoices individually and continuously gives no such moment. There is no batch to review, no total to sanity-check, no single release to require dual approval on. The payment run exists so that money leaves the company on a schedule, in a controlled way, with a checkpoint, rather than in a continuous trickle no one is watching as a whole.
The cadence is how often the run happens. A weekly payment run is the common standard for construction contractors, and it is a sensible default. Weekly is frequent enough that invoices do not age toward their due dates or past discount windows while waiting, and infrequent enough that each run is a substantial, deliberate event worth a reviewer's full attention.
Running too often — daily, or on demand whenever someone asks — defeats the purpose. It fragments payments into many small batches that no one reviews as a whole, and it creates constant pressure to add 'just one more' payment outside any controlled cycle. Running too rarely — monthly — causes the opposite problem: invoices sit unpaid long enough to age past early-payment discount windows and to strain vendor relationships, and the single monthly run becomes so large it is hard to review carefully. Weekly is the balance. Some contractors run a primary weekly cycle plus a tightly controlled exception process for the genuine emergency that cannot wait — but the exception process should be rare, documented, and held to the same dual-approval standard as the regular run.
Not every approved invoice should be paid in every run. When available cash is less than the total of everything approved and due, the run has to be prioritized — and prioritization should follow a written policy, not the squeakiest wheel.
A sensible priority order for a payment run
- Invoices with early-payment discounts inside their discount window — paying these first captures a return that usually beats the cost of the cash
- Payments tied to lien rights and statutory deadlines — subcontractor and supplier payments where late payment creates lien exposure or triggers prompt-payment penalties
- Invoices approaching their due date — pay before they go past terms
- Critical-vendor payments — suppliers and subs whose continued performance the active jobs depend on
- Routine invoices still within terms — these can wait for a later run without cost or risk
The discipline is to make this a policy applied consistently, not a negotiation. When prioritization is ad hoc, the vendors who call the most get paid first, regardless of whether that is the right use of the cash — and discounts get missed while non-urgent invoices jump the line.
A payment run without controls is just a faster way to lose money. Four controls do the real work.
The person who enters and vouchers an invoice must not be the person who releases the payment run. This is the foundational control. When one person can both create a payable and pay it, that person can pay a fictitious vendor with no second set of eyes. Splitting voucher from pay means a fraudulent payable created by one person has to survive review by another before any money moves.
The assembled batch — the full list of payees, amounts, and the total — should require review and sign-off by a second authorized person before release. The reviewer is not re-approving each invoice; they are sanity-checking the batch as a whole: a total that fits expectations, no unfamiliar payees, no obvious duplicate, no amount that looks wrong for that vendor. It takes minutes and it is the last human checkpoint before the cash is gone.
Positive pay is a bank service: the company sends the bank a file of the checks it issued — check number, payee, amount — and the bank pays only checks that match the file, rejecting anything that does not. ACH positive pay (also called ACH debit filtering) does the analogous job for electronic debits, allowing only ACH transactions from approved originators. Together they are the backstop that catches an altered or counterfeit check and an unauthorized ACH pull even if something slipped past the internal review.
Get AP insights in your inbox
A short monthly roundup of construction AP + accounting posts. No spam, ever.
No spam. Unsubscribe anytime.
Bank-detail change verification
The most effective payment fraud today is not a forged check — it is a request to change a legitimate vendor's bank account or remittance address, so a real, approved invoice pays into the fraudster's account. Every change to vendor banking details must be verified through an independent channel: a callback to a known phone number on file, never a number or email from the change request itself. This control sits just before the run, because it is the run that turns a redirected detail into a lost payment.
Treat any vendor bank-detail change as a fraud event until proven otherwise. Verify it by calling a number you already had on file — not one supplied in the change request — and record who verified it and when. Business email compromise overwhelmingly targets exactly this step, because a redirected payment is indistinguishable from a normal one once the run releases.
A construction payment run has rules a generic AP run does not, because construction payments are entangled with funding, lien rights, and contract terms.
First, release subcontractor payments against funding and the lien-waiver exchange. A contractor should generally pay a subcontractor for a given period only when it has been funded for that work by the owner — and the payment should be exchanged for the appropriate lien waiver. The standard pattern is conditional waiver against the progress payment and unconditional waiver confirming the prior payment cleared. A run that releases sub payments without collecting waivers leaves the contractor exposed to liens on work it has already paid for.
Second, honor pay-when-paid and pay-if-paid terms where they are contractually in force. If a subcontract conditions the contractor's obligation to pay on receipt of payment from the owner, the run should reflect that timing rather than advancing the contractor's own cash ahead of the owner's. This is a contract-management point as much as an AP point — the run is where the contract term becomes a cash decision.
Third, sequence the run so that owner collections and sub payments stay aligned. The healthiest construction cash position pays subs out of the cash the owner has already funded for that work, rather than fronting it. Tying the run's timing to collections, where the contract allows, keeps the cash cycle from running negative.
A modern payment run is a mix of methods, chosen per vendor. ACH should be the default — it is cheaper than a check, faster to settle, and leaves a clean electronic trail, and it is protected by ACH positive pay. Checks still have a place for vendors not set up for electronic payment, but checks are also the most fraud-prone instrument, which is why check-paying contractors should run positive pay without exception. Virtual cards — single-use card numbers issued per payment — suit certain vendor categories, can earn rebate revenue, and carry strong built-in controls because each number is locked to one payment and amount.
Shifting the payment mix toward ACH and virtual card and away from paper checks reduces both cost and fraud exposure at the same time. Checks are the most expensive instrument to process and the easiest to alter or counterfeit; every vendor moved off checks improves the run on both fronts.
Automation improves the payment run on both dimensions at once. On speed, it assembles the batch automatically from approved, due invoices, applies the prioritization rules, and generates the ACH file, the check file, and the positive pay file without manual re-keying — turning a run that took most of a day into one that takes an hour. On safety, it enforces the controls rather than relying on people to remember them: segregation of duties is built into roles so a voucher-er cannot release a run, dual approval on the batch is required by the workflow, the positive pay file is generated as a matter of course, and a flag on a vendor whose bank details recently changed can hold that payment out of the run until the change is verified.
Crucially, automation keeps the audit trail. Every run has a record of who assembled it, who approved it, what was in it, what was held and why, and when it released. Manual runs degrade under pressure — controls get skipped during a busy week. An automated run applies the same checks every time, which is exactly what a control is supposed to do.
The payment run is where AP either holds or fails, because it is where money actually moves. Batch invoices into a regular cycle — weekly is the sensible default — so the run is a discrete, reviewable event. Prioritize by a written policy, not by who calls. Enforce the four controls: segregation of duties, dual approval on the batch, positive pay on both checks and ACH, and verified bank-detail changes. Layer in construction's own rules — fund before you pay subs, exchange lien waivers, honor pay-when-paid. Then let automation make the whole run faster while making the controls unskippable. The run is the last checkpoint before the cash is gone; treat it that way.
Written by
Sarah Blake
Head of Product
Former AP Manager at a $200M construction firm, now leads product at Covinly. Writes about what AP teams actually need from automation — beyond the marketing promises.
View all posts