Definition
A flag on an invoice or vendor that keeps it out of payment runs until the reason is cleared, such as a dispute, a missing document or a suspected duplicate.
Also called: invoice hold, vendor hold, payment block
What it means
A payment hold is a stop signal. Someone has decided this invoice, or this vendor, should not be paid yet, and the flag keeps it out of the next payment run. The reason is usually one of three things: a dispute over the amount or the goods, a missing document such as a receipt or a signed contract, or a suspicion that the invoice is a duplicate. Until that reason is cleared, the money stays in the bank.
People also call it an invoice hold, a vendor hold or a payment block. The names overlap but they sit in different places. An invoice hold sits on one document. A vendor hold sits on the supplier record and stops every invoice from that supplier, which is what you want while bank details are being confirmed or while you check whether two vendor records are actually the same company.
A hold is not the same as a scheduled payment date. A payment date says when money should go out. A hold says it must not go out, whatever the date says. If you treat a hold as a note to yourself rather than a hard stop, the payment run will pick the invoice up and pay it.
Every hold needs a reason, an owner and a date to review it. A hold without an owner is just a late payment waiting to happen.
How it works in practice
In most setups the hold is a flag on the invoice or the vendor record in your ERP. The payment run skips flagged items. The AP clerk who sets the hold writes the reason in the notes, names the person who can release it, and puts a review date on it. That review date matters more than the flag itself, because holds that nobody revisits turn into late payments and late fees.
Take an invoice for $4,200 from a supplier who disputes a short delivery. The clerk sets a hold on Tuesday, Jan 13, 2026, notes the dispute, and names the purchasing manager as the person who can clear it. The invoice was due Thursday, Jan 15, 2026. If the purchasing manager confirms the dispute on Wednesday, Jan 14, the hold comes off and the invoice pays on time. If nobody checks, the due date passes and the supplier starts chasing.
Vendor-level holds work the same way but cover more ground. If a supplier emails new bank details and the request looks odd, put a hold on the vendor record while you confirm the change by calling a number you already had. That stops every open invoice from that supplier, not just the one in the email. The same applies while you check whether a second vendor record is a duplicate of an existing one.
A suspected duplicate is the clearest case. Suppose invoice 8841 for $4,200 arrives and invoice 8837 for $4,200 from the same supplier is already paid. Put a hold on 8841 and check the vendor record before anyone releases it. Releasing a hold on a suspected duplicate without checking it defeats the reason it was set.
Where it goes wrong
The most common failure is the hold nobody owns. A clerk sets it, goes on leave, and the invoice sits past its due date. The supplier charges a late fee, or the team pays it twice out of panic. The fix is simple: no hold without a named owner and a review date in the notes.
The second failure is releasing a hold to clear a queue. Someone sees a stack of held invoices before a payment run and lifts the flags to get the run through. That is how duplicate payments happen. If a hold was set because an invoice looked like a duplicate, the release has to come after a check, not before.
The third failure is the vendor hold that never gets lifted. Bank details get confirmed, the duplicate vendor question gets settled, and the hold stays on for months. The supplier's invoices pile up unpaid and the relationship suffers. Vendor holds need the same review date as invoice holds.
The fourth is a hold set in the wrong place. A clerk puts a note on the invoice but the payment run reads the vendor record, or the other way round. The invoice pays anyway. Check where your ERP actually looks before you trust a hold to stop a payment. Rules on holds differ by company and by contract, so follow your own policy on who can set and release them.
What to check
Before you set a hold, write the reason in plain words: dispute, missing document or suspected duplicate. Name the person who can release it. Put a review date on it, and make that date earlier than the invoice due date so there is room to act.
Before you release a hold, read the reason first. If it was a suspected duplicate, confirm the original invoice number and amount before you clear it. If it was a missing document, confirm the document is now on file. If it was a bank detail change, confirm the new details through a channel you already trusted, not through the email that asked for the change.
On a regular schedule, pull every open hold and check the owner and the review date. Anything past its review date gets chased that week. Anything older than a month gets escalated to the AP manager. A short list reviewed every week beats a long list nobody reads.
When a hold comes off, note who released it and why. That record is what lets you answer a controller's question six months later about why an invoice paid late or why a duplicate was caught. Holds are a control, and controls only work when someone can see what happened.
Questions
What is a payment hold on an invoice?
It is a flag that keeps the invoice out of payment runs until the reason for the hold is cleared. The reason is usually a dispute, a missing document or a suspected duplicate. The invoice stays unpaid even if its due date passes.
Who can release a payment hold?
That depends on your company policy. The safe rule is that the person who set the hold names the person who can release it, and that person checks the reason before clearing it. A suspected duplicate should only be released after the original invoice is confirmed.
What is the difference between an invoice hold and a vendor hold?
An invoice hold stops one document. A vendor hold sits on the supplier record and stops every invoice from that supplier, which is useful while bank details are being confirmed or a possible duplicate vendor is being checked. Both need an owner and a review date.
Updated Nov 22, 2026. Figures on this page are calculated by ERPSav from the definitions shown. The explanatory text is drafted with AI from those figures and checked automatically before it is published. General information only, not legal, tax or financial advice.