Ask ten AP managers how often they run payments and you'll get three answers: weekly, bi-weekly, daily. Each defends their cadence with the same reasons — cash flow visibility, processing efficiency, vendor satisfaction. Most are picking the wrong tradeoff, but not in the way they think. Their cadence isn't broken; they picked a cadence before answering two more important questions.

Payment run scheduling looks simple and hides a lot of consequence. Pick the wrong cadence and you miss discount windows, push half your vendors into late territory, and burn through the AP team's week chasing exceptions. Pick the right cadence on top of two broken upstream decisions, and the same things happen anyway. The schedule is downstream. This piece walks the full sequence: the two upstream decisions that determine what your cadence should be, the cutoff design that makes any cadence work, the batching tactics that prevent Friday scrambles, and the 90-day implementation path.

The Cadence Trap: Why "How Often" Is the Wrong Starting Question

Three patterns show up over and over in AP teams that think they have a scheduling problem:

"Vendors are complaining we pay late, so we need to run payments more often." Usually false. The invoices triggering complaints almost always cleared the AP queue 5-10 days before their due date but got paid 3-7 days after. That's an approval queue collapse, not a cadence problem. Running payments daily won't help if approvers respond in 4 days; you'll produce more partial batches and the same late tail.

"We're running daily because too many vendors need fast payment." Usually a segmentation gap. When every vendor is in the same lane, the urgent ones force the cadence for everyone — controllers approve the same volume spread across five small batches instead of one organized batch. Same-day payment rails (wires, instant ACH) also carry per-transaction fees 2-10x higher than standard ACH.

"Bi-weekly saves us time." Usually pushes you past every cutoff. A bi-weekly Wednesday cadence puts approval cutoff Tuesday afternoon. A controller out sick, traveling, or hitting a multi-step approval blows through the cutoff and the invoice slides 14 days, not 2. Bi-weekly works if your approval queue is robust. It's a trap if it isn't.

Cadence sits on top of two earlier decisions: how you segment vendors, and how you design cutoffs. Skip them and you tune the wrong knob.

Decision 1: Vendor Segmentation — Three Tiers, Not One Cadence

The first decision is segmentation. Most AP teams run a single cadence across all vendors. The fix is to split your vendor base into three tiers and assign a cadence to each — not because three is magic, but because vendor payment behavior actually clusters into three patterns that need different treatment.

Tier A — Standard vendors. Long-tail recurring spend, on Net 30 or Net 45 terms, with no time-sensitive obligations. SaaS subscriptions, professional services with standard contracts, recurring supplies. Pay weekly in a single batch. Use standard ACH. These are roughly 80% of vendor count at most mid-market companies and about 45% of payment value — high volume, lower stakes per invoice.

Tier B — Time-sensitive vendors. Utilities and telecoms with short windows before service interruption. Contractors and freelancers with tight cash flow on Net 7 or Net 15 terms. Regulated payments (tax authorities, insurance, payroll-adjacent). Strategic suppliers with early payment discounts on the table. Run twice-weekly batches or scheduled exact-due-date payments. About 15% of vendor count, 45% of payment value — fewer vendors but the bigger checks and tighter timing live here.

Tier C — Exceptions. Broken supply requiring expedited reissue. COD or pre-pay arrangements. One-off urgent vendors. Customer-impacting payments (refunds processed through AP). Use a same-day rail — wire, instant ACH, or virtual card — with a hard volume cap. These should be 5% of vendor count and 10% of payment value. If your Tier C is bigger, you have a queue problem dressed up as an exception problem.

Three Vendor Tiers, Three Cadences

Typical mid-market split. Tier A vendors dominate vendor count but only carry about half the payment value. Tier B is the hidden risk band — fewer vendors, equal value share, tight payment timing. Tier C is the same-day exception lane with a hard volume cap.

The tier determines the rail (standard ACH for Tier A, same-day ACH or wire for B and C), the frequency, the approval path, and how exceptions get handled. The 80/15/5 split is empirical — it's what most mid-market AP teams settle into once they actually segment. The companies running daily payments for everyone are usually misclassifying Tier A as Tier B because nobody drew the lines.

Decision 2: Cutoff Design — The 24-Hour Rule

The second decision is cutoffs. Cutoffs are where most payment run schedules break, and they break invisibly — the schedule technically runs on time, but the work inside it doesn't.

A payment run has two cutoffs that matter. The bank cutoff is set by your bank: ACH typically closes around 5pm ET, same-day ACH around 2:45pm ET, domestic wires around 5-6pm ET. Miss it and your batch settles the next business day. The internal approval cutoff is the time you stop accepting newly-approved invoices into the current run. Most AP teams set the approval cutoff at or just before the bank cutoff. That's the mistake.

The 24-hour rule: your approval cutoff should sit at least 24 hours before your bank cutoff. The reason is exception handling. When an approver rejects an invoice, requests more documentation, or kicks it to a different cost center, the AP team needs time to handle that exception inside the same run — not push it to the next one. With a 1-hour gap, every late rejection slides invoices 7-14 days. With a 24-hour gap, they slide one day, often into the same week's batch on a different cycle.

Walk it backwards from the bank cutoff. If you settle ACH at 5pm Wednesday:

Approval cutoff: 5pm Tuesday (24 hours earlier)
Pre-stage and review: Tuesday afternoon
Last call to approvers: Tuesday morning, with an automated nudge
Invoice intake for this run: closes Monday EOD

That's a five-day intake window for a Wednesday run. Compare it to the typical setup — intake all the way through Wednesday morning, approvals due by 4pm Wednesday, batch submitted at 4:55pm — and the difference shows up immediately in your on-time-payment rate.

The same math works for daily, weekly, or bi-weekly cadences. Daily runs need a daily 24-hour-ahead cutoff (yesterday's approvals settle today). Weekly runs need a fixed weekly approval cutoff one full business day before the bank cutoff. Bi-weekly runs are the hardest to get right — the long gap between cutoffs means a missed approval slides a full two weeks, which is why bi-weekly is structurally more fragile than weekly for the same approval discipline.

Batching Tactics That Actually Work

Once segmentation and cutoffs are set, the batching itself becomes mechanical. Four rules carry most of the weight:

Batch by payment method, not by vendor. Group all ACH payments into one batch, all wires into another, all virtual card payments into a third. Banks process one batch per method anyway, and grouping by vendor splits the work across more batches than you need. Most modern AP platforms do this automatically.

Pre-stage at T-24h, not at cutoff. The batch should exist 24 hours before submission, with all line items already approved and coded. The hour before bank cutoff is for review, not assembly. Teams that build batches at submission time discover errors at the worst possible moment — the moment they have no time to fix them.

Don't let one stuck invoice block 200 others. Configure your AP system so a flagged or held invoice gets pulled from the batch, not blocking the batch. The held invoice goes into the next run automatically once cleared. This sounds obvious; about a third of AP teams still have batch-blocking workflows that hold every payment until every invoice is reconciled.

Don't intermix runs across legal entities. If you operate multiple entities, run separate batches per entity even if they share a bank. Mixing entities creates reconciliation pain, audit ambiguity, and intercompany cleanup at month-end close. The 5 minutes you save submitting one combined batch costs you hours during month-end close.

Exception Handling Without Breaking the Schedule

Tier C exists to absorb urgency. The trap is letting Tier C grow until it's eating Tier A. Three guardrails keep that from happening:

Volume cap. Tier C should be 5-7% of weekly payment volume by count. If you're consistently above 10%, you don't have an exception lane — you have a parallel daily payment process, and it's costing you in fees and reconciliation overhead. The fix is upstream: shorten the standard approval queue so urgent invoices don't need to escape it.

Audit trail per exception. Every Tier C payment should record why it bypassed the standard run — vendor request, broken supply, customer refund, regulatory deadline. Three months of this data tells you what's actually generating exceptions, and almost every team finds 60-80% of exceptions trace to two or three preventable upstream patterns (duplicate payments reissued, vendor onboarding lag, missing PO).

Reconcile in a separate GL bucket. Same-day exception payments should land in a dedicated subaccount so they don't muddy your standard AP reconciliation. Month-end close gets faster, the exception cost stays visible, and you can measure the exception rate as its own KPI.

What Automation Changes (and What It Doesn't)

Modern AP automation reshapes payment run scheduling in three specific ways. It enforces the segmentation automatically — vendor tier flows from contract terms and payment history rather than manual classification. It enforces the 24-hour cutoff rule — approvers get nudged ahead of cutoff, and late approvals route to the next available run rather than blowing through the bank cutoff. It triages exceptions in real time — Slack notifications surface stuck invoices to the approver who can unstick them, not the AP clerk who can only chase.

What automation doesn't change: the underlying vendor terms, the bank rails and their cutoffs, fraud controls and dual-approval requirements above policy thresholds. Those are decisions you still own. Ken handles the segmentation, the cutoff orchestration, and the exception triage; you handle the policy.

The cleanest version of this in 2026 looks like a three-lane payment process where the AP team's day-to-day work is reviewing exceptions, not assembling batches. The batches assemble themselves on schedule. The team's attention goes to the 5-7% of payments that actually need human judgment.

Stop Optimizing DPO

One last reframe. AP teams under cash flow pressure often try to optimize payment scheduling by stretching DPO (days payable outstanding) — extending payment dates to hold cash longer. The instinct is reasonable but the metric is misleading.

DPO measures what you paid, when. It does not measure what suppliers did in response: pricing creep at the next contract renewal, deprioritized allocation when supply is tight, slower problem-solving when issues come up, reduced willingness to extend credit on large orders. Suppliers absorb late payments invisibly — and the cost shows up 6-18 months later, off the AP scorecard, in places no AP director gets credit or blame for. C2FO's 2026 supply chain analysis found 28% of suppliers are actively seeking financing despite high rates, which means your slow payments are pushing them onto credit lines they're already maxing out.

A better target: on-time payment rate (target 95%+), discount capture rate on discount-eligible invoices (target 80%+), and exception rate (target under 7%). Those numbers tell you whether your schedule is actually working. DPO tells you the story your CFO wants to hear, which is not always the same thing.

Implementation Sequence (90 Days)

If you're rebuilding payment run scheduling from a single-cadence setup, work in this order:

Week 1-2: Pull six months of payment data. Tag every vendor by current Tier (A, B, C) using payment terms, on-time-rate, and historical urgency requests. Most teams find their existing "everyone is Tier B" approach is wrong on 70% of vendors.
Week 3-4: Set new cutoff times using the 24-hour rule. Document an exception policy with named approval thresholds (e.g., "exceptions over $25K require controller sign-off").
Week 5-8: Run the new schedule in parallel with the old one for one full cycle. Measure on-time rate, discount capture, and exception count. Adjust tier assignments based on actual data.
Week 9-12: Cut over fully. Decommission the old cadence. Track the same KPIs monthly and revisit tier assignments quarterly.

By the end of week 12, most teams see on-time rate climb from 70-80% to 92-96%, exception count drop by 40-60%, and AP team time spent on payment runs drop by half. The discount capture rate is the slowest to move — that one tracks discount-eligible invoice volume, which depends on contract negotiation, not just scheduling.

FAQ

How often should we run payments?

For most mid-market companies, the answer is weekly for Tier A vendors plus a same-day rail for exceptions. Weekly gives predictable cash flow visibility, allows a single weekly approval cutoff, and matches how most discount windows are structured — Net 10, Net 15, and Net 30 all align cleanly with weekly batches. Daily payments add reconciliation cost and per-transaction fees without solving the underlying issues that drive urgency. Bi-weekly is structurally more fragile because a missed approval slides 14 days instead of 7. The exception is high-volume operations processing 1,000+ invoices per week, where daily batches reduce per-batch size to something humans can review.

What's the right cutoff time for payment runs?

Set your internal approval cutoff at least 24 hours before your bank's submission cutoff. For a 5pm ET ACH submission on Wednesday, approvals close 5pm Tuesday. The 24-hour gap absorbs late-stage exceptions — rejected invoices, missing documentation, escalations — without sliding payments to the next cycle. Same-day ACH cutoffs are around 2:45pm ET; wire cutoffs vary by bank but are typically 5-6pm ET. Check your specific bank and build a buffer for federal holidays.

Should we run payments daily?

Only if your invoice volume justifies it (1,000+ per week) or you've chosen daily as a service offering for vendors. Daily payments multiply your batch count fivefold and push approval discipline harder. Most teams asking this question are solving an approval queue problem that daily payments will not fix. Weekly for Tier A, twice-weekly for Tier B, same-day for Tier C exceptions — that combination delivers same-day responsiveness for the urgent 5% without the cost of running daily for the other 95%.

Does AP automation eliminate the need for batched payment runs?

No, it makes batched runs work better. Banks charge per-batch fees that scale better than per-transaction, reconciliation is cleaner with fewer batches per period, and approval discipline is easier to enforce on a schedule than continuously. What automation changes is the work inside the batch: vendor segmentation runs automatically, the 24-hour cutoff gets enforced by the system, and exceptions surface to approvers in Slack rather than waiting for the AP clerk to find them. The batched cadence stays; the manual labor disappears.

Make Ken Schedule and Run Your Payments

Ken segments your vendors into the right tiers based on payment terms and history, enforces 24-hour cutoffs automatically, and routes exceptions to the right approver in Slack — so payment runs assemble themselves on schedule instead of consuming your AP team's Friday afternoon. Start a free trial and ship a cleaner payment run schedule in 30 days.

Payment Run Scheduling Without Burning Vendor Trust