Payment Run: Definition and AP Meaning | Glossary

Glossary definition of payment run, the batch process where AP releases approved invoices for payment, and why it is the last checkpoint before margin drift.

Twitter LinkedIn WhatsApp
Ask AI: ChatGPT Claude Gemini Grok
Payment Run: Definition and AP Meaning | Glossary

Margin drift is the gap between what a vendor contract says and what the invoice actually charges. A payment run is the batch process an accounts payable team runs to release approved invoices for payment on a set schedule, converting matched liabilities into ACH transfers, checks, or wires. It sits at the end of the AP cycle, after approval and matching, and before the money is actually gone.

A payment run is often mistaken for a control because it is the last step before cash leaves the company. It is not one. It executes decisions made earlier in the process rather than testing them again.

1. What exactly happens during a payment run?

A payment run pulls every invoice marked approved and payable, groups them by payment method and due date, and releases them as a batch of ACH transfers, checks, or wires. AP software or the ERP module generates the batch, a controller or AP lead reviews the total, and the bank or check printer executes disbursement. Nothing in that sequence re-examines whether the invoice was priced correctly.

The run is mechanical by design. It exists to move approved liabilities to cash on a predictable cadence, not to second-guess them.

Each invoice entering the run has already passed through approval and matching. The run treats that prior work as settled and focuses only on grouping, sequencing, and executing disbursement.

2. What decides which invoices are included?

An invoice enters a payment run once it has cleared approval workflow and matching against a purchase order and receipt, and once its due date or discount window falls inside the run's cutoff. Vendor terms, hold flags, and available cash set the timing. None of those gates test the invoice against the vendor contract's rate card, volume tier, or surcharge schedule.

Inclusion is a status check, not a pricing check. An invoice can be fully eligible for a run and still be wrong.

A hold flag stops payment for reasons like a missing approval or a vendor dispute. It does not exist to catch a rate that no longer matches the contract.

3. Where does a payment run sit relative to contract compliance?

A payment run happens after whatever contract compliance checking a company does, if it does any at all. Three-way matching confirms quantity and PO reference. A separate, often manual, comparison against the signed contract is what would catch a rate schedule violation or an expired discount, and that comparison sits outside the payment run entirely.

By the time an invoice reaches the run, the pricing question has already been answered, correctly or not.

Three-way matching checks the invoice against the purchase order and the receipt. It does not test whether the unit price on the invoice matches the rate card in the contract, or whether a surcharge that should have expired is still being applied.

4. Why does this matter once an invoice has been paid?

Once a payment run disburses funds, correcting an error changes from an internal fix to an external ask. The AP team can no longer simply adjust a line item; it has to request a credit memo, a refund, or a deduction on a future invoice, and the vendor controls whether that happens. The payment run is the point where a pricing error stops being cheap to fix.

This is why the controls that matter most sit before the run, not inside it.

A pricing error caught during matching is a line-item correction. The same error caught after disbursement becomes a negotiation, dependent on the vendor's own process and willingness to issue a credit.

For the wider pattern this sits inside, start with the margin drift guide. See also margin drift vs. legitimate price increases: how to tell them apart and off-contract resources: people billed outside the agreement.

5. Frequently Asked Questions (People Also Ask)

What is a payment run in accounts payable?

A payment run is the batch process AP uses to release approved, matched invoices for payment on a set schedule. It groups invoices by payment method and due date, then generates ACH transfers, checks, or wires. It executes payment decisions already made earlier in the AP cycle rather than testing them.

Does a payment run check pricing accuracy?

No. A payment run checks status: whether an invoice is approved, matched to a purchase order and receipt, and inside its due date window. It does not compare the invoice against the vendor contract's rate card, volume tier, or surcharge schedule.

How often do companies run a payment run?

Cadence is set by the company, commonly weekly or biweekly, tied to vendor terms and cash flow. The schedule is a company-specific policy choice rather than a fixed rule, and it does not change what the run itself checks.

What is the difference between three-way matching and a payment run?

Three-way matching compares the invoice, purchase order, and receipt for quantity and reference accuracy before approval. The payment run happens after that, converting already-approved liabilities into disbursed cash. Neither step tests the invoice against the contract's pricing terms.

Can an error be fixed after a payment run executes?

Yes, but the fix changes character. Before the run, AP can adjust a line item internally. After disbursement, AP has to request a credit memo, a refund, or a deduction on a future invoice, and the vendor controls whether and when that happens.

Who is responsible for reviewing a payment run before it executes?

A controller or AP lead typically reviews the batch total and disbursement list before release. That review confirms the run matches expected volume and vendor list; it is not designed to catch a mispriced line item.

Where should contract compliance checking happen if not in the payment run?

It has to happen earlier, ideally at invoice receipt or during matching, before the invoice reaches the payment run queue. Checking the invoice against the signed contract's rate card and surcharge terms at that stage keeps a pricing error correctable internally.

Why is a payment run sometimes mistaken for a control?

Because it is the final, visible step before money leaves the company, it can look like a checkpoint. It is procedural: it moves approved liabilities to cash on schedule without re-examining whether the underlying price was correct.

1. What exactly happens during a payment run?

A payment run pulls every invoice marked approved and payable, groups them by payment method and due date, and releases them as a batch of ACH transfers, checks, or wires. AP software or the ERP module generates the batch, a controller or AP lead reviews the total, and the bank or check printer executes disbursement. Nothing in that sequence re-examines whether the invoice was priced correctly. The run is mechanical by design. It exists to move approved liabilities to cash on a predictable cadence, not to second-guess them. Each invoice entering the run has already passed through approval and matching. The run treats that prior work as settled and focuses only on grouping, sequencing, and executing disbursement.

2. What decides which invoices are included?

An invoice enters a payment run once it has cleared approval workflow and matching against a purchase order and receipt, and once its due date or discount window falls inside the run's cutoff. Vendor terms, hold flags, and available cash set the timing. None of those gates test the invoice against the vendor contract's rate card, volume tier, or surcharge schedule. Inclusion is a status check, not a pricing check. An invoice can be fully eligible for a run and still be wrong. A hold flag stops payment for reasons like a missing approval or a vendor dispute. It does not exist to catch a rate that no longer matches the contract.

3. Where does a payment run sit relative to contract compliance?

A payment run happens after whatever contract compliance checking a company does, if it does any at all. Three-way matching confirms quantity and PO reference. A separate, often manual, comparison against the signed contract is what would catch a rate schedule violation or an expired discount, and that comparison sits outside the payment run entirely. By the time an invoice reaches the run, the pricing question has already been answered, correctly or not. Three-way matching checks the invoice against the purchase order and the receipt. It does not test whether the unit price on the invoice matches the rate card in the contract, or whether a surcharge that should have expired is still being applied.

4. Why does this matter once an invoice has been paid?

Once a payment run disburses funds, correcting an error changes from an internal fix to an external ask. The AP team can no longer simply adjust a line item; it has to request a credit memo, a refund, or a deduction on a future invoice, and the vendor controls whether that happens. The payment run is the point where a pricing error stops being cheap to fix. This is why the controls that matter most sit before the run, not inside it. A pricing error caught during matching is a line-item correction. The same error caught after disbursement becomes a negotiation, dependent on the vendor's own process and willingness to issue a credit. For the wider pattern this sits inside, start with the [margin drift](/insights/margin-drift-spend-leakage-guide) guide. See also [margin drift vs. legitimate price increases: how to tell them apart](/guides/margin-drift-vs-legitimate-price-increases-how-to-tell-them) and [off-contract resources: people billed outside the agreement](/guides/off-contract-resources-people-billed-outside-the-agreement).

Questions & Answers

What is a payment run in accounts payable?

A payment run is the batch process AP uses to release approved, matched invoices for payment on a set schedule. It groups invoices by payment method and due date, then generates ACH transfers, checks, or wires. It executes payment decisions already made earlier in the AP cycle rather than testing them.

Does a payment run check pricing accuracy?

No. A payment run checks status: whether an invoice is approved, matched to a purchase order and receipt, and inside its due date window. It does not compare the invoice against the vendor contract's rate card, volume tier, or surcharge schedule.

How often do companies run a payment run?

Cadence is set by the company, commonly weekly or biweekly, tied to vendor terms and cash flow. The schedule is a company-specific policy choice rather than a fixed rule, and it does not change what the run itself checks.

What is the difference between three-way matching and a payment run?

Three-way matching compares the invoice, purchase order, and receipt for quantity and reference accuracy before approval. The payment run happens after that, converting already-approved liabilities into disbursed cash. Neither step tests the invoice against the contract's pricing terms.

Can an error be fixed after a payment run executes?

Yes, but the fix changes character. Before the run, AP can adjust a line item internally. After disbursement, AP has to request a credit memo, a refund, or a deduction on a future invoice, and the vendor controls whether and when that happens.

Margin Drift Resources