Disputed invoices and why lenders exclude them

A disputed invoice is a receivable with an asterisk. The customer is not refusing to pay because they cannot; they are refusing because they claim they do not owe it, and buyers generally have the right to raise defenses about the underlying goods or services against whoever is collecting, including the lender. Collateral value that depends on winning an argument is not collateral a lender advances against.

Disputes are also a leading indicator. A rising dispute rate usually precedes rising dilution, since most disputes end in a credit memo, and it often signals the same operational problems: pricing errors, short shipments, quality escapes. Lenders track the dispute rate alongside dilution for exactly that reason.

Agreements split on scope. The more common construction excludes the disputed amount, leaving the undisputed remainder eligible. Stricter agreements exclude the entire invoice once any portion is disputed, and the strictest cross into the obligor's whole balance for material disputes. Here is one invoice under the two common treatments.

At an 85 percent advance rate, the two readings differ by $212,500 of availability on a single invoice. Multiply that across a normal dispute book and the scope question is worth real money, which is why it is worth knowing exactly which construction your agreement uses before you sign it.

The test needs a dispute flag, a disputed amount, and a dispute date on each affected invoice, alongside the usual obligor id and open amount. Almost no ERP is configured to hold all three. Disputes live in the collector's email, in a deductions workflow tool, or in a notes field that says per Karen at Kembrook, holding 150k. The invoice itself carries no flag, so the certificate reports it as clean while the collections team knows it is not.

That gap is dangerous, because most agreements require the borrower to report disputes they know about, not just disputes the system tracks. A field exam that finds disputed balances in collection notes but not on certificates reads it as misreporting, even when the omission was a data plumbing problem rather than an intent problem.

• Dispute flags and disputed amounts are first class fields on every invoice, so what collections knows and what the certificate reports are the same thing.
• Scope is configured per facility: disputed amount only, whole invoice, or obligor level escalation for material disputes, matching the agreement.
• The exclusion is deterministic: the same dispute data always produces the same ineligible figure, with no monthly judgment calls.
• Every excluded dollar traces to the invoice, the flagged amount, and the dispute date, so resolved disputes flow back into eligibility with a clean audit trail.