How to Handle Disputed Supplier Invoices Without Losing Cost Control

A supplier invoice can be valid in principle and still be wrong in detail.

The materials may have arrived, but the quantity is disputed. The subcontract work may be complete, but the invoice includes an unapproved variation. A plant hire charge may continue beyond the off-hire date. The invoice may use the correct purchase order while charging the wrong project.

In each case, accounts needs an answer from the operational team before payment. The problem is what happens while that answer is being found.

If the invoice simply sits in someone's inbox, the job cost may be understated and the supplier receives no useful update. If it remains approved at full value, the business risks paying a charge that has not been accepted. A controlled query process keeps the cost visible, records the exact disagreement and gives one person responsibility for resolving it.

What makes an invoice disputed?

An invoice is disputed when the business does not accept that the full amount is currently due.

That is different from an invoice that is merely waiting for routine approval. An approver may not have reviewed a correct invoice yet. A disputed invoice has been reviewed far enough to identify a specific problem that must be resolved with the supplier, site team or commercial team.

Common construction invoice disputes include:

• The quantity invoiced does not match the delivery note.
• Materials were damaged, returned or delivered to the wrong site.
• The rate differs from the purchase order or subcontract.
• A variation was completed without an agreed instruction or price.
• Plant or equipment is charged beyond the recorded off-hire date.
• The invoice includes work that is incomplete or defective.
• Labour hours do not agree with signed timesheets.
• Retention, discount or contra charges have been treated incorrectly.
• The invoice is allocated to the wrong job, phase or cost code.
• A previous payment, credit note or deposit has not been deducted.

The query needs to state which of these applies. "Invoice wrong" is not enough information for accounts, the supplier or the person expected to resolve it.

Record the exact point of disagreement

The first step is to turn a vague objection into a recorded exception.

For each queried invoice, capture:

• Supplier name and invoice number.
• Purchase order, subcontract or agreed instruction.
• Project and site reference.
• Total invoice value.
• Amount accepted, if any.
• Amount disputed.
• Reason for the dispute.
• Supporting evidence required.
• Person responsible for the next action.
• Date the query was raised.
• Target review or response date.

For example, the useful note is not "check with site". It is: "Invoice includes 14 doors; signed delivery note records 12. Site manager to confirm whether two were delivered separately by 16 June."

That note tells everyone what is being checked, who owns it and what evidence will close the query.

Keep the invoice visible in job costing

Putting a disputed invoice on hold should not make the potential cost disappear.

The business may still owe some or all of the amount. If the entire invoice is excluded from project reporting until the dispute is resolved, the job can appear more profitable than it really is. This is particularly risky near month end or when directors are reviewing forecast margin.

A practical approach is to show the invoice with a clear queried status and separate:

• The amount accepted.
• The amount disputed.
• The amount currently approved for payment.
• The remaining commitment against the purchase order.

Suppose a supplier invoices £9,600, but £1,200 relates to an unapproved extra. The £8,400 accepted cost should remain visible. The £1,200 should also remain visible as a disputed exposure until it is rejected, credited or approved.

This gives management a more honest view than either approving £9,600 or pretending the invoice does not exist.

Do not use rejection as a filing system

Some teams reject an invoice simply to remove it from the approval queue.

That can be appropriate when the document is definitely invalid, addressed to the wrong legal entity or requires a formal replacement. It is less useful when the business is still checking a quantity, rate or delivery.

A rejected invoice may vanish from the approver's normal view even though the commercial issue remains open. The supplier may resend the same document, creating a duplicate invoice risk. Accounts may then have two records and no clear link between them.

Use distinct statuses where possible:

• Awaiting approval.
• Query raised.
• Awaiting site evidence.
• Awaiting supplier response.
• Part approved.
• Credit note required.
• Replacement invoice required.
• Resolved and approved.
• Rejected or cancelled.

The status should describe the real position rather than merely clearing someone's task list.

Decide whether part payment is appropriate

Not every dispute needs to hold the full invoice.

Where the accepted and disputed amounts are clear, the business may be able to approve the undisputed portion and hold the balance. This can protect supplier relationships and cash flow through the supply chain while preserving the right to challenge the questionable charge.

Before part payment, confirm:

1. The invoice can be processed correctly in the accounting system.
2. The supplier understands which amount is being paid and why.
3. The disputed balance remains visible and is not treated as a forgotten short payment.
4. Any VAT treatment is handled correctly by accounts.
5. The purchase order and job-cost record show the part payment.
6. The final resolution will be supported by a credit note, revised invoice or documented agreement.

Part payment is not always suitable. If the supplier needs to cancel and reissue the document, or if the whole charge depends on disputed completion, holding the full invoice may be cleaner. Accounts should agree the treatment rather than improvising it during the payment run.

Keep evidence with the invoice

Construction invoice disputes are usually resolved by operational evidence.

Useful documents might include:

• The approved purchase order.
• Delivery notes and goods-received records.
• Photographs of damaged or missing materials.
• Signed timesheets.
• Plant on-hire and off-hire confirmations.
• Variation instructions and agreed quotations.
• Valuation or completion records.
• Emails confirming rates, scope or returns.
• Previous invoices, payments and credit notes.

Keep that evidence linked to the invoice query. If the explanation sits only in a private email or WhatsApp thread, accounts cannot see why the amount changed and another person cannot pick up the issue when someone is away.

This is also why clear project codes and site references matter. The correct reference helps the query reach the person who actually knows what happened on site.

Give every query an owner and a deadline

"Waiting for site" is not ownership.

The query should name the person responsible for the next action. That may be the project manager checking quantities, the buyer requesting a credit note, the quantity surveyor reviewing a variation or accounts asking the supplier for a revised document.

Set a realistic follow-up date. The aim is not to manufacture urgency for every small query. It is to stop unresolved invoices ageing unnoticed until the supplier puts the account on hold or month-end reporting is already being prepared.

A short weekly review can focus on:

• New invoice queries.
• Queries with no named owner.
• Supplier responses that need a decision.
• Promised credit notes not yet received.
• Disputes older than the agreed review period.
• High-value queried amounts affecting job forecasts.
• Invoices due for payment before the next review.

Escalation should follow value, age and operational effect. A small pricing discrepancy may not need a director. A large disputed application that could stop a key subcontractor returning to site may need prompt commercial attention.

Close the query with a documented outcome

A query is not closed because the supplier stops chasing.

The final record should show one of four broad outcomes:

• The invoice was correct and approved.
• Part of the invoice was accepted and the remainder credited.
• The original invoice was cancelled and replaced.
• The charge was rejected with the reason recorded.

Where a credit note is due, keep the query open until the credit arrives and is matched to the original invoice. A verbal promise does not correct the supplier ledger or the project cost.

Where the business accepts an initially disputed amount, record who approved it and what evidence changed the decision. This protects the audit trail and helps the team distinguish a genuine resolution from an invoice that was released simply because it became old.

How BuilderDash supports a controlled query workflow

BuilderDash helps connect supplier invoices with purchase orders, project references, approvals and supporting documents.

Instead of sending a questionable invoice around separate inboxes, the team can keep the document and its status in one operational workflow. Accounts can see that a query has been raised, the project team can see what evidence is needed, and the cost remains connected to the correct job while the issue is resolved.

The useful outcome is not more administration. It is a shared answer to four questions:

• What exactly is disputed?
• How much is currently accepted?
• Who has the next action?
• What must happen before payment?

That visibility also supports a cleaner purchase order variation process because unapproved extras can be identified before they become unexplained invoice balances.

A practical disputed-invoice checklist

Review the invoices currently on hold and ask:

• Does each invoice have a specific query reason?
• Is the accepted and disputed value recorded separately?
• Is the possible cost still visible against the correct job?
• Is supporting evidence linked to the invoice?
• Does one named person own the next action?
• Has the supplier received a clear explanation?
• Is there a follow-up date?
• Are promised credit notes or replacement invoices tracked?
• Will the final decision update the PO, invoice record and job cost?

If any answer is no, the invoice is not being controlled; it is simply waiting.

Resolve the issue without losing sight of the cost

Disputed supplier invoices are a normal part of construction operations. Deliveries, variations, hire periods and measured work do not always line up neatly with the first invoice received.

The control failure is not the existence of a query. It is allowing the query to become an unowned email chain, an invisible job cost or a last-minute payment-run decision.

Record the exact issue, separate accepted and disputed values, keep the exposure visible, assign the next action and close the record with proper evidence. That gives accounts, project teams and suppliers a clearer route to resolution.

Suggested internal links: Prevent duplicate supplier invoices, control purchase order overspend and variations, and why project codes and site references matter.

Call to action: Use BuilderDash to connect supplier invoices, purchase orders, project references, approvals and query evidence, so disputed costs stay visible and payment decisions keep moving.