Shipping Audit Checklist

Please remove this form template insights section before publishing.

Overall Form Strengths

Here are detailed insights into the logic behind the Shipping Audit Checklist. These points explain why each section exists, helping your users understand the value of the data they are inputting.

1. The Anchor: Data Matching Logic

The core of any audit is the "Three-Way Match." Your form should prompt the user to compare the Carrier Invoice, the Original Bill of Lading (BOL), and the Contracted Rate Sheet. If these three do not align, the payment should be flagged.

• Insight: Inconsistencies often stem from manual entry errors at the shipping dock. By capturing the BOL number early in your form, you create a digital paper trail that simplifies future searches.

2. The Weight & Density Factor

Carrier pricing is often determined by the space a package occupies, not just its actual weight.

• Insight: Your form should include a field for Dimensional Weight. If the carrier’s "billed weight" is higher than the "actual weight," the form helps the user identify if the carrier applied a "Dim Factor" correctly.
• Formula for the form:
  Volume = Length * Width * Height
  Checking this prevents paying for "air" in a half-empty trailer.

3. Accessorial "Scope Creep"

Accessorials are the "hidden" fees (like residential delivery or fuel surcharges) that can inflate a bill by 20% to 40%.

• Insight: Use your form to categorize these fees. This allows the user to see patterns. For example, if one carrier consistently charges for a "Liftgate" that was never requested, the user can identify a systematic billing error rather than a one-time mistake.

4. Fuel Surcharge Sensitivity

Fuel is a volatile cost that changes weekly. Most agreements tie this to a specific national or regional index.

• Insight: A good audit form asks for the Shipment Date. This is crucial because the fuel percentage must match the index price on that specific day, not the day the invoice was printed. This prevents carriers from overcharging during weeks when fuel prices drop.

5. Service Level Verification (SLV)

This is about performance versus cost. If a user pays for "Next Day Air" and the package arrives in three days, the contract has not been fulfilled.

• Insight: Including a "Actual Delivery Date" field next to the "Service Level Selected" field empowers the user to request credits. Many shippers ignore these small "late" fees, but they represent a significant portion of wasted spend over a fiscal year.

6. Route Compliance Tracking

Sometimes the error isn't the carrier's; it's the shipper's.

• Insight: This section of the form identifies "Out of Network" spend. If the form shows that a premium carrier was used when a contracted, lower-cost carrier was available, it highlights a training opportunity for the warehouse team.

Please remove this mandatory questions recommendation section before publishing.

Mandatory Field Rationale

To build an effective form template, you need to distinguish between "nice-to-have" data and the Mandatory Fields that drive the actual audit logic. Without these specific data points, the audit cannot cross-reference the carrier's claims against your internal records.

Here are the mandatory questions for your digital form and the reasoning behind each.

1. Unique Identifier: Pro Number or Invoice Number

• The Question: "What is the Progressive (Pro) Number or Carrier Invoice Number?"
• The "Why": This is the primary key for your entire database. It prevents double-billing and ensures that you aren't paying for the same movement twice. In a digital form, this field should ideally have a "unique constraint" to alert the user if that number has already been entered in the system.

2. Shipping Date (Pickup Date)

• The Question: "What was the actual date the freight was picked up?"
• The "Why": Freight rates, especially Fuel Surcharges (FSC), are pegged to specific weekly indices. If the date is off by even a few days, the fuel calculation might be based on a different week's rate, leading to overpayment. It also establishes the timeline for "on-time" delivery performance.

3. Origin and Destination Zip/Postal Codes

• The Question: "What are the starting and ending Zip/Postal Codes?"
• The "Why": Most freight contracts are "zone-based" or "lane-based." A single digit error in a zip code can shift a shipment into a higher pricing tier. This data is required to verify that the carrier applied the correct "Base Rate" from your negotiated rate table.

4. Billed Weight vs. Actual Weight

• The Question: "Enter the Actual Weight (from BOL) and the Billed Weight (from Invoice)."
• The "Why": This is the most frequent source of "hidden" costs. Carriers often "re-weigh" freight and increase the bill. By making both fields mandatory, the form can automatically calculate the variance. If the billed weight is significantly higher without a re-weigh certificate, it triggers a dispute.

5. NMFC Class or Freight Category

• The Question: "What is the NMFC (National Motor Freight Classification) code or Freight Class?"
• The "Why": Density and stowability determine the "Class" (ranging from 50 to 500). Lower classes are cheaper to ship. Carriers often "re-classify" items to a higher, more expensive class. Mandatory input here allows the system to check if the carrier changed the classification mid-transit.

6. Accessorial Itemization

• The Question: "Select any additional services performed (Liftgate, Residential, Inside Delivery, etc.)."
• The "Why": You cannot audit what you don't categorize. By forcing a selection (even if it is "None"), the form ensures the user has looked at the "extra charges" section of the invoice. This prevents "blind approval" of miscellaneous fees that weren't actually authorized or performed.

7. Service Level Agreement (SLA) Type

• The Question: "Was this shipped via Standard, Ground, Expedited, or Next-Day?"
• The "Why": This is essential for cost-recovery. If "Expedited" is selected but the delivery date shows it arrived via a "Standard" timeline, the user is entitled to a service failure credit. Without this field, you are essentially paying for a premium service that wasn't provided.