Finance Index
What is a payment run in accounts payable?
Reference guide to AP payment runs, including payment timing, method choices, control points, reconciliation, and vendor communication.
A payment run (also called a pay run or check run) is the scheduled batch process where AP selects approved invoices that are due, groups them into payments by vendor and method, routes the proposed batch for review and approval, and releases the payments. Most companies run payments weekly or twice weekly on a fixed cycle.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| A payment run in accounts | A payment run (also called a pay run or check run) is the scheduled batch process where AP selects approved invoices that are due, groups them into payments by vendor and method, routes the proposed batch for review and approval, and releases. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Workflow | Define the cycle: an approval cutoff (invoices must be fully approved by, say, Tuesday EOD), a selection step (pull approved invoices due before the next run, plus any discount-deadline invoices), a payment proposal for controller review, an approval step separate from invoice. | Keeps evidence clear and reduces control risk. |
| Control point | Exceptions, not every line: new vendors and first payments, changed bank details since last run, payments above a threshold, duplicates flagged by amount/vendor/date, off-cycle items, and the run's totals by bank account against available cash. | Keeps evidence clear and reduces control risk. |
| How do credit memos | Credit memos should be applied against the vendor's open invoices within the run so the net payment is correct - an unapplied credit alongside a full payment is an overpayment. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Payment impact | Weekly is the most common baseline; high-volume or discount-driven shops add a second weekly run. | Reduces payment errors, timing issues, and reconciliation cleanup. |
How do I set up a weekly payment run process from selection to release?
Define the cycle: an approval cutoff (invoices must be fully approved by, say, Tuesday EOD), a selection step (pull approved invoices due before the next run, plus any discount-deadline invoices), a payment proposal for controller review, an approval step separate from invoice approval, and a release step. Publish the calendar internally and to vendors so "urgent" requests have a known next window, and handle true exceptions through a documented off-cycle process rather than by breaking the run.
What should a controller actually review before approving a payment run?
Exceptions, not every line: new vendors and first payments, changed bank details since last run, payments above a threshold, duplicates flagged by amount/vendor/date, off-cycle items, and the run's totals by bank account against available cash. Line-by-line review of hundreds of payments produces rubber-stamping; structured exception review produces control.
How do credit memos and disputed invoices interact with a run?
Credit memos should be applied against the vendor's open invoices within the run so the net payment is correct - an unapplied credit alongside a full payment is an overpayment. Disputed invoices should be flagged and excluded at selection; pulling a single payment from an already-built batch should be possible without rebuilding the entire run.
How often should we run payments - weekly, twice weekly, or daily?
Weekly is the most common baseline; high-volume or discount-driven shops add a second weekly run. Daily runs usually signal poor scheduling discipline rather than service excellence.
How do I select which invoices go into a run?
All approved invoices due before the next run date, plus invoices whose discount window closes before the next run, plus approved priority exceptions - selection by due date and discount date, not by who emailed loudest.
What is payment batching and why are payments grouped?
Batching groups payments for efficient processing, approval, and bank transmission; it reduces per-payment overhead and gives reviewers a coherent unit to approve.
Should each run be one batch per bank account, entity, method, or currency?
Batch by funding bank account at minimum (each batch debits one account), and most teams also split by method and currency because timing and processing differ.
One vendor with multiple open invoices - one payment or several?
One payment covering all due invoices, with invoice-level remittance, unless the vendor requires per-invoice payments; fewer payments means fewer fees and easier reconciliation.
An invoice was approved after the cutoff and the vendor is angry - how do we handle stragglers?
Hold the line: stragglers wait for the next run unless they meet documented off-cycle criteria. If stragglers are frequent, fix approval cycle time - don't normalize run exceptions.
What's the right cutoff schedule for a weekly cycle?
Approval cutoff 1 - 2 days before the run, run/selection on a fixed day, review same day, release the following morning - giving reviewers real time without aging payments.
How do I build a payment proposal for controller review?
Generate a report from the selection showing vendor, invoice references, amounts, method, bank account, due/discount dates, and exception flags (new vendor, changed details, over threshold), with batch totals by account.
Our run included a disputed invoice - how do I pull one payment from a built batch?
Your system should allow removing a single payment before release, automatically rebalancing batch totals; if it doesn't, that's a tooling gap - manually voiding mid-release is where errors happen.
How do I run a payment proposal and batch in our ERP?
Every major ERP has a payment proposal/selection function (names differ - payment proposal, payment journal, pay bills) following the same select-review-approve-release pattern; the gaps are usually in approval workflow and bank execution, which is where AP platforms layer on.
Month-end and the payment run collide - should we freeze payments during close?
A short release freeze during the final close days simplifies cash cutoff, but don't freeze approvals or selection; just schedule runs around the close calendar so vendors aren't silently paid late.
What is a zero-dollar payment and why would a run generate one?
A payment where credits fully offset invoices, generated to clear both off the vendor ledger; it's bookkeeping hygiene, not an error.
How many payment runs and payments per run is typical at 5,000 invoices a month?
Typically one or two runs weekly, several hundred payments per run after invoice-to-payment consolidation - the better benchmark is the share of payments that bypass the run, which should stay in low single digits.
Stampli perspective
Stampli supports batch payment creation from approved invoices with invoice grouping and optimization, application of vendor credits and early-payment discounts at payment creation, and a payment approval workflow that is separate from invoice approval - so the run is reviewed by exception with full context, and each released payment reconciles 1-to-1 against the bank and ERP.