Try it now, capture a real invoice
Free plan · No credit card · Your data stays yours
A payment run is a scheduled batch process where accounts payable pays a group of approved invoices at once, rather than cutting each payment one at a time. Instead of an AP clerk sending money whenever an invoice clears, the team collects everything that is approved and due, reviews the batch, and releases all the payments together on a set day. Most businesses run one or two payment runs a week, which turns a constant trickle of individual payments into a controlled, predictable event.
The point of batching payments is control and efficiency. One review covers many invoices, cash outflow is planned rather than random, and there is a single approval gate before money leaves the company. This article walks through what happens in a payment run, the steps involved, how to decide the schedule, and the checks that keep a run safe.
What happens in a payment run
A payment run pulls together every invoice that has cleared approval and is due for payment, groups them by how they will be paid, and sends the money in one batch. The system generates the ACH file, prints or issues the checks, or queues the card payments, and produces remittance advice so each vendor knows what the payment covers. Because it is one batch, AP can see the total cash impact before releasing anything, which is the moment to catch a duplicate, a wrong amount, or a payment that should be held.
The steps in an AP payment run
The process is the same each cycle, which is what makes it reliable and auditable.
| Step | What happens |
|---|---|
| 1. Select invoices | Pull all approved invoices that are due, or due within the run window, filtered by date and status |
| 2. Review the batch | Check the proposed payments for duplicates, wrong amounts, or bills that should be held |
| 3. Apply discounts | Capture any early-payment discounts still available and confirm terms are met |
| 4. Approve the run | A designated approver signs off on the total batch before money moves |
| 5. Generate payments | Create the ACH file, checks, or card payments and send remittance advice to vendors |
| 6. Post and reconcile | Record the payments in the ledger and reconcile them against the bank |
The review and approval steps are where the safety lives. A payment run is the last checkpoint before cash leaves, so a second set of eyes on the batch total and the vendor list catches errors that slipped through invoice-level approval.
How often should you run a payment run?
Most companies settle on a weekly or twice-weekly schedule. A fixed cadence lets you time payments to capture early-payment discounts without paying everything the day it arrives, and it gives vendors a predictable answer when they ask when they will be paid. Running too often erases the efficiency of batching; running too rarely risks late payments and missed discounts. The right frequency depends on invoice volume and how tightly you manage cash, but a set day beats paying reactively.
Manual vs automated payment runs
Done manually, a payment run means exporting an approved-invoice list, keying payments into the bank, and reconciling by hand. That is slow and easy to get wrong, especially matching payments back to invoices afterward. Automated vendor payment software builds the batch from approved invoices, generates the ACH file or checks, sends remittance automatically, and posts the payments back to your ledger. AP reviews and approves rather than keying, and the reconciliation is already done.
The payment method matters too. Paying by ACH instead of paper checks makes runs faster, cheaper, and easier to reconcile, since the electronic record ties straight back to the invoice. Once payments post, bringing that activity into your accounting system keeps the books current; if you reconcile in QuickBooks, you can bring the bank and payment activity into QuickBooks without manual entry.
Frequently asked questions
What is a payment run?
A payment run is a scheduled batch process in accounts payable where a group of approved, due invoices is paid together rather than one at a time. AP collects everything ready to pay, reviews the batch, gets approval, and releases the payments as ACH, checks, or card in a single controlled event, usually once or twice a week.
What is the purpose of a payment run?
The purpose is control and efficiency. Batching approved invoices into one run lets AP review total cash outflow before releasing money, apply a single approval gate, capture early-payment discounts, and pay vendors on a predictable schedule. It replaces a constant stream of individual payments with a planned, auditable process.
How often should a business run payment runs?
Most businesses run payments weekly or twice a week. A fixed schedule balances paying on time and capturing discounts against the efficiency of batching. The exact frequency depends on invoice volume and cash management, but a set cadence is better than paying reactively as each invoice clears.
What is the difference between a payment run and a check run?
A check run is a payment run limited to paper checks. A payment run is the broader term and covers all methods, ACH, checks, and card, in the same batch. As businesses move away from paper, most payment runs are now mostly electronic, with checks as one option rather than the default.
Who approves a payment run?
A designated approver, often a controller or AP manager, signs off on the full batch before payments are released. This final approval reviews the total amount and the vendor list, acting as the last checkpoint to catch duplicates, errors, or payments that should be held before cash leaves the company.