Handling Vendor Disputes and Short Pays
A short pay is when you pay a vendor less than their invoice asks for. In some industries that signals a problem. In construction it is routine and often correct — the invoice billed for more than was delivered, included disputed extra work, applied retainage incorrectly, or double-billed a line already paid. Short-paying is frequently the accurate thing to do.
The problem is never the short pay itself. It is how it is handled. Done badly, a short pay becomes an angry phone call, a vendor relationship strained over a misunderstanding, and a reconciliation tangle that takes months to clear. Done well, it is simply a documented decision and clean data. This article is about the difference.
A short pay is a deliberate, partial payment against an invoice, with the unpaid portion either disputed or deferred. It is not the same as paying late, and it is not the same as refusing to pay. It is a statement: 'we agree we owe this much, we do not yet agree on the rest, and here is why.' Treating it as a clear, reasoned position rather than a vague underpayment is the whole game.
Disputes and short pays in construction AP cluster around a predictable set of causes. Knowing them helps you spot a dispute early instead of after the payment goes out.
Common short-pay and dispute triggers
- Quantity mismatch — the invoice bills more units or hours than were delivered or approved
- Pricing variance — the rate billed does not match the PO, subcontract, or quoted price
- Unapproved change orders — work billed that was never authorized in writing
- Retainage errors — retainage not withheld, or withheld at the wrong percentage
- Duplicate billing — a line item already invoiced and paid on an earlier invoice
- Incomplete or defective work — billing for scope that is not finished or did not pass inspection
- Missing compliance documents — a required lien waiver or COI not yet provided
The single most important habit in handling short pays is to record the reason at the moment you make the decision — not later, when memory has faded. Which line items, what amount, why, and who decided. A short pay without a documented reason is a future argument waiting to happen: in three weeks no one will remember whether $4,200 was withheld for retainage or for a quantity dispute, and the vendor certainly will not agree.
Attach the dispute reason to the specific invoice and line, not to a separate spreadsheet or someone's email. When the vendor calls, the answer should be one click from the payment — not a search through three systems and two memories.
Get AP insights in your inbox
A short monthly roundup of construction AP + accounting posts. No spam, ever.
No spam. Unsubscribe anytime.
A vendor who discovers a short pay by reconciling their own bank deposit is already annoyed before the conversation starts. A vendor who receives a clear note — 'we paid $46,800 of the $51,000; the $4,200 difference is the disputed change-order line, here is why' — at the time of payment is dealing with a transparent partner. Same money, completely different relationship. Proactive communication turns a confrontation into a routine clarification.
A short pay opens a small open item: the disputed amount that is still unresolved. Those items have to be tracked to closure, or they rot. An untracked dispute becomes an aged balance no one can explain, a vendor who quietly stops prioritizing your jobs, and a year-end reconciliation problem. Every disputed amount needs an owner and a status until it is either paid or formally written off.
“We used to short-pay and say nothing, figuring the vendor would call if they cared. They cared. Now we send the reason with every short pay. The disputes did not go away — but the angry calls did, because nobody is surprised anymore.”
— AP Manager, general contractor
0
The discipline that prevents most dispute escalation — every short pay tied to the specific line item and a recorded reason
Covinly handles short pays as structured data rather than informal exceptions: a disputed amount is recorded against the specific invoice line with a reason and an owner, the open item is tracked until it resolves, and the full history stays attached to the invoice and the vendor. When a vendor calls, the reason is right there — and disputed balances never quietly age into a mystery.
Short-paying an invoice is often the correct decision — the skill is in the handling, not the avoiding. Document the reason as you decide it, tell the vendor before they find out themselves, and track every disputed amount to a real resolution. Do that and a short pay stops being a relationship risk and becomes what it should be: a clear, well-recorded business decision.
Written by
Sarah Blake
Head of Product
Former AP Manager at a $200M construction firm, now leads product at Covinly. Writes about what AP teams actually need from automation — beyond the marketing promises.
View all posts