Billing discrepancies in construction are not edge cases. They are a regular feature of every project that involves material deliveries, subcontractor work, or unit-price contracts. The difference between well-managed and poorly-managed projects is not whether discrepancies exist — it's how quickly they're caught.

Types of Billing Discrepancies

Quantity Discrepancies

The invoiced quantity doesn't match the delivered quantity. This is especially common with bulk materials measured by weight, where scale accuracy, moisture content, and tare weight adjustments create legitimate variances — but also create cover for overbilling.

Price Discrepancies

The unit price on the invoice doesn't match the contract rate. Suppliers may have escalation clauses, zone-based pricing, or time-of-day rates. Without systematic comparison to contract terms, overcharges go unnoticed.

Duplicate Charges

The same work or delivery appears on multiple invoices. This can happen when invoice periods overlap, when tickets are carried forward, or when both a progress invoice and a final invoice capture the same line items.

Scope Discrepancies

Work or materials that were not authorized are included on the invoice. This requires comparison against the contract scope and approved change orders — a process that is often skipped when teams are under time pressure.

Why Manual Catching Fails

Manual discrepancy detection fails at scale because:

1. **Volume**: A single project may have thousands of invoice line items per month 2. **Format inconsistency**: Tickets and invoices come in different formats from different suppliers 3. **Time pressure**: Billing deadlines mean invoices get approved without thorough review 4. **Memory dependence**: Catching duplicates requires remembering (or searching) all previous tickets

A Systematic Approach with Commodity Manager

Import Everything

Import all delivery tickets, invoices, and contracts into Commodity Manager. The system accepts Excel, PDF, and CSV formats and tracks import history with audit logs.

Let Validation Rules Work

Configure validation rules once at the org level. Every imported line is automatically checked against:

Quantity range thresholds for each material type

UOM consistency between tickets and invoices

Date validity (is the ticket date within the invoice period?)

Ticket number format standards

Lines that fail validation are flagged for review. Legitimate exceptions get overrides.

Review Automated Matches

When invoices are imported, Commodity Manager finds potential ticket matches for each invoice line. The matching algorithm uses date proximity, quantity tolerance, and ticket number normalization. Unmatched lines are highlighted as "Missing Tickets."

Compare Against Contract Rates

Contracts and POs establish the benchmark. Every invoice price is compared against the agreed rate for that material, vendor, and UOM. Deviations are flagged immediately.

Monitor the Dashboard

The Overview dashboard shows cumulative curves comparing JTD received vs. JTD invoiced. When the invoiced curve diverges from the received curve, you know there's a systemic discrepancy worth investigating.

The Bottom Line

Catching billing discrepancies is not about being adversarial with suppliers. It's about verifying accuracy before payment — the same due diligence you'd apply to any business transaction. The difference is doing it systematically instead of sporadically.

Learn more about Commodity Manager or contact us to discuss your reconciliation needs.

How to Catch Billing Discrepancies Before They Cost You Thousands