A G.B. Industry companyHow to reconcile a freight invoice, BOL, and POD without inventing the join
A convincing freight match needs a document-level key, traceable values, and an explicit exception path. Similar dates or amounts are useful clues, but they are not shipment identity.
Effective October 27, 2026
1. Freeze one bounded document packet
Start with one freight invoice, one bill of lading or rate confirmation, and one proof of delivery when available. Keep the originals unchanged and record which file supplied each observation.
2. Build an identifier matrix before comparing charges
| Document | Candidate identifiers | Safe rule |
|---|---|---|
| Invoice | Invoice, load, shipment, BOL, or PRO reference | Use only printed values; do not derive a missing load ID. |
| BOL or rate confirmation | BOL, load, carrier, equipment, origin, destination | Record the document source and preserve leading zeros. |
| POD | BOL, PRO, delivery reference, delivered date | A date or location alone is not a shipment join. |
3. Normalize format, not meaning
Trimming whitespace or comparing a documented identifier with and without separators can be a controlled normalization. Fuzzy matching, guessed prefixes, location similarity, and amount proximity should not silently convert an exception into a match.
4. Reconcile evidence in a fixed order
- Confirm one shared shipment identifier.
- Compare carrier, origin, destination, and service details.
- Compare agreed, invoiced, and supported accessorial charges.
- Confirm delivery evidence and dates.
- Record every missing, conflicting, or unreadable value as an exception.
5. Stop safely when the join is uncertain
When no reliable shared key exists, route the packet to buyer review. Do not manufacture a match from timing, geography, or price. The exception record should state what is present, what conflicts, what is missing, and which buyer-owned evidence could resolve it.
Choose the right fixed scope
Use the $199 Freight Workflow Evidence Check for one bounded workflow and up to three text-readable PDFs when the immediate question is whether the supplied packet supports safe extraction, joining, and exception handling.
Use the $499 Full Freight Workflow Audit when the buyer needs one end-to-end workflow mapped across up to ten PDFs with a control register and implementation-ready remediation plan.
What the $199 evidence check does not claim
It does not guarantee OCR accuracy, validate an unseen buyer population, access production systems, implement automation, approve charges, or prove ROI. Work begins only after verified funding and complete authorized text-readable inputs.
Inspect the public freight evidence sample · Review the fixed $199 evidence-check scope