Invoice Dispute

An invoice dispute arises when a customer refuses to pay an invoice, in whole or part, because they contest something about it: pricing that does not match the quote or contract, quantities that do not match receipts, damaged or non-conforming goods, missing purchase order references, tax errors, or billing to the wrong entity. While disputed, the invoice sits in AR aging as past due, but it is not a collection problem in the ordinary sense; no amount of dunning collects an invoice the customer believes is wrong.

Disputes deserve their own workflow, separate from collections, with structured capture (reason code, disputed amount versus undisputed remainder, owner, promised resolution date) and routing to whoever can actually resolve the issue, which is usually sales, pricing, or the warehouse rather than the AR team. Two disciplines pay for themselves immediately: split the invoice so the undisputed portion is paid on normal terms rather than the entire invoice hostage to a $200 discrepancy, and timestamp everything, because dispute cycle time is a manageable metric and an unmanaged one quietly adds days to DSO.

Dispute reason codes, analyzed quarterly, are a diagnostic instrument for the whole order-to-cash process. A cluster of pricing disputes points at contract-to-billing sync failures; recurring quantity disputes point at warehouse or carrier processes; wrong-entity disputes point at customer master data. Preventing the top two or three root causes typically removes more aging than any collections initiative, because disputed receivables are the stickiest part of the ledger.