Disputed Invoices: The Tracking System That Keeps Disagreements From Becoming Payment Defaults

Disputed invoices are unavoidable on construction projects. A sub bills for work the GC believes wasn't part of their scope. The GC applies a back charge the sub contests. Quantities don't match what the field staff remember. Quality issues trigger withholding. Whatever the specifics, every active project has some volume of invoices in disputed status — and how those disputes are handled affects vendor relationships, cash flow, and operational efficiency.

Without systematic tracking, disputed invoices become a source of drift. They sit in someone's inbox waiting for resolution; they age past the point where anyone remembers the details; they generate follow-up calls from vendors asking about status; they turn into collection letters when vendors lose patience. With systematic tracking, they move through a defined resolution process with clear status, appropriate communication, and timely escalation.

Common Dispute Categories

Disputes fall into recognizable categories:

Each category has its own typical resolution pattern. Categorization helps route disputes to appropriate resolvers and track patterns by category over time.

Capturing Disputes Early

Disputes should be captured when identified, not at crisis point:

Disputes left as unresolved items without explicit dispute status get forgotten. Flagging them explicitly creates tracking and visibility. A monthly review of all disputed items surfaces anything stuck.

Partial Payment Strategy

Most disputes don't affect the whole invoice:

Partial payment maintains sub cash flow on undisputed work while giving time to resolve the disputed portion. Holding the entire invoice over a disputed 10% harms the relationship and rarely produces faster resolution. Partial payment with clear communication is almost always better.

Resolution Workflow

Disputes work through a resolution sequence:

Each step has owners and timelines. Disputes stuck at "waiting for documentation" for weeks need escalation. The workflow ensures movement rather than items drifting indefinitely.

Communication with Vendors

How disputes are communicated affects outcomes:

Vendors respond better to professional, specific communication than to generic hold notices. "Your invoice is under review" is frustrating; "We're questioning line 5, which appears to double-bill the February placement already billed on invoice 4532" is specific and actionable.

Back Charge Documentation

Back charges need specific documentation:

Back charges without documentation often don't survive challenge. A back charge for damage to adjacent work should include photos showing the damage, documentation that the sub caused it, and the cost to repair. Without this, the sub can legitimately dispute and the back charge may not hold.

Aging Management

Disputed items age:

Aged disputes indicate process breakdown. A 90-day-old dispute is usually stuck — someone isn't responding, documentation never materialized, or the resolution decision was deferred indefinitely. Systematic aging review surfaces these for escalation.

Escalation Procedures

Some disputes need escalation:

Escalation path clarity prevents disputes sitting with AP when they actually need higher-level attention. A $250K back charge dispute isn't an AP issue; it's a project and commercial issue.

Settlement Documentation

Resolved disputes should be documented:

Undocumented settlements can reopen. A sub who accepts partial payment verbally but never signs release may later claim the full amount. Written settlement documents prevent reopening.

Pattern Analysis

Dispute patterns reveal systemic issues:

Patterns inform upstream changes. A vendor generating constant disputes may need relationship review. A PM generating many disputes may need coaching. Systemic issue categories (like chronic back charge disputes) may need process improvements.

Bottom Line

Disputed invoice tracking systematizes what's otherwise ad hoc handling of payment disagreements. Clear categorization, early flagging, partial payment strategy for undisputed portions, structured resolution workflow, specific communication with vendors, back charge documentation, aging management, escalation procedures, settlement documentation, and pattern analysis together convert disputes from a source of ongoing friction into a managed operational process. Vendors appreciate clarity and promptness even when the news isn't what they wanted. GCs preserve cash on legitimate disputes while maintaining sub relationships. The discipline is modest; the benefit to vendor relationships, cash management, and operational efficiency is meaningful over a project's life.