Managing Payment Holds for Disputed Invoices

1. Place the hold: prevent the payment from releasing while the dispute is open. 2. Document the reason: record what is disputed and the amount in question. 3. Identify the owner: determine who can resolve the dispute. 4. Route it: send the dispute to that owner with the context. 5. Communicate: keep the vendor informed of status and what is needed. 6. Resolve: settle the dispute, obtaining a credit or correction if warranted. 7. Release or reject: pay the agreed amount with re-approval if it changed, or reject.

The hold itself is the first action. Placing it so the payment cannot release ensures the business does not pay a contested amount while the question is open. A partial dispute may justify holding the disputed portion while the undisputed amount proceeds, depending on policy.

Documentation gives the hold a basis. Recording what is disputed, the amount in question, and who raised it turns the hold from an unexplained pause into an auditable control. Without that record, a held payment looks like a stalled one.

A dispute is usually resolved by someone other than the AP processor. A price or quantity dispute may involve procurement or the requester, a quality issue may involve the receiving department, and a credit question involves the vendor. Routing the dispute to the owner who can actually resolve it is what moves it forward.

AP coordinates but does not always decide. Sending the dispute to the right owner, with the invoice, the documentation, and the reason attached, keeps resolution from stalling in the AP queue.

Vendors escalate when they hear nothing. Keeping the vendor informed of the dispute status and what is needed to resolve it reduces the executive escalations that come from silence. A vendor who knows their invoice is under review and why is far less likely to escalate.

Resolution should produce a clean outcome. If the dispute results in a corrected amount or a credit, the invoice is updated and re-approved if the change is material, then the agreed amount is released. If the charge is not owed, the invoice is rejected with a documented reason. Either way, the hold ends with a recorded resolution.

Stampli supports holds through validation guardrails that can block a payment from releasing, so a disputed invoice does not move to payment while it is open. Segregation of duties between invoice and payment approval is enforced by design, which keeps the hold and release controlled.

Because the invoice is the workspace in Stampli, the dispute reason, documents, comments, and approval history stay attached to the invoice. The dispute can be routed and discussed in context rather than across separate email threads, and the vendor portal gives vendors a channel for related communication.

Every action is captured in an immutable audit trail with full context. The hold, the dispute discussion, any re-approval, and the release or rejection are all on the record, which supports both the payment decision and audit.