Reducing Goods Billed Not Shipped Incidents: Procedures, Root Causes, And KPIs

Goods Billed Not Shipped A claim that merchandise appeared on an invoice but was not included in the shipment. Reducing incident frequency requires targeted process controls, technology, and supplier governance that span receiving, procurement, and accounts payable.

Retailers and their 3PL partners can substantially lower these claims by eliminating the root causes: timing gaps between invoicing and shipment, inaccurate packing lists or ASNs, manual data entry errors, and insufficient proof at the dock. The remedies are operational, contractual, and technological.

Process Controls That Cut Incidents

• Mandate ASNs Before Invoicing: Require suppliers to transmit ASNs or packing lists and receive acknowledgment before invoice issuance; this prevents premature billing.
• Three‑Way Match Automation: Configure ERP to block payment for invoice lines that fail PO-to-receipt matches and route them to exception queues for investigation.
• Standardized Receiving Procedures: Use SKU-level scanning, pallet license plates, and verified counts at the dock; require photographic evidence for unusual variances.

Technology And Integration Opportunities

EDI, supplier portals, and WMS integrations reduce manual errors. Implementing EDI 856 (ASN) and EDI 810 (Invoice) with validation rules prevents mismatches. When full EDI is not feasible, require structured supplier portals where packing lists and invoices are uploaded and validated against POs before AP accepts invoices.

Supplier Management And Contract Clauses

Include invoice accuracy SLAs, dispute response times, and recourse clauses in master agreements. Use supplier scorecards that track invoice accuracy (% invoices with discrepancies), short-shipment frequency, and average days to resolve claims. Tie corrective action plans to scorecard thresholds and consider financial penalties for repeated failures where appropriate.

KPIs To Monitor

• Bill/Ship Variance Rate: Percentage of invoice lines where invoiced quantity != received quantity.
• Claims Resolution Time: Average business days from claim open to closure (credit memo issued or replacement shipped).
• Cost Of Discrepancy: Direct cost including administrative handling plus any expedited replacement shipping.
• Supplier Accuracy Score: Percent of shipments per supplier with zero invoice or packing-list variances.

Root‑Cause Analysis Example

A national retailer observed a spike in goods billed not shipped incidents for one supplier. RCA found the supplier’s ERP auto-generated invoices at end-of-day based on orders rather than confirmed picks; whenever picks were delayed, invoices still reflected full order quantities. The retailer updated the contract to require ASN generation at pick completion and altered the supplier onboarding checklist to include ASN timing commitments. Within three months the variance rate dropped 78% for that supplier.

Operational Checklist For Implementation

• Define Clear SLAs: Put ASN, invoicing, and dispute response SLAs in writing and enforce through scorecards.
• Train Receiving: Ensure receiving teams know how to document, photograph, and escalate discrepancies fast.
• Automate Where Practical: Use WMS/ERP rules to prevent payment without verified receipts and route exceptions to a defined owner.
• Audit Regularly: Run periodic audits of matched vs unmatched invoices and perform supplier root-cause reviews when trends appear.

In short, the Goods Billed Not Shipped metric is both a symptom and an opportunity: treating it as a cross‑functional indicator — operations, procurement, and finance — lets retailers reduce payment risk, improve inventory accuracy, and preserve supplier relationships through a mix of controls, standards, and technology.