Thorough preparation prevents costly oversights. Use this section to collect baseline data, define audit scope, and secure stakeholder alignment before touching a single invoice.
Unique audit identifier or reference code
Name of the entity commissioning this audit
Audit start date
Audit end date (target completion)
Primary audit lead (full name)
Backup auditor (full name)
Audit scope
Domestic only
International only
Both domestic & international
Transport modes included
Road
Rail
Ocean
Air
Intermodal
All modes
Earliest invoice date to be audited
Latest invoice date to be audited
Estimated total spend under review
Number of carriers included
Have you compiled a master carrier list with contact details?
Are original service contracts & rate cards accessible?
Are SLAs & KPI definitions documented?
Is access to TMS/ERP data granted to auditors?
Have you created a secure file repository for evidence?
Which documents have been pre-collected?
Rate cards
Fuel surcharge tables
Accessorial charges matrix
Transit-time schedules
Proof-of-delivery samples
Claim history
None of the above
Known disputes or exceptions to flag during audit
Even minor rounding errors multiply across thousands of shipments. Validate every numeric field, tax logic, and currency conversion.
Is the invoice currency consistent with the contract currency?
Are exchange rates (if applied) sourced from the agreed reference?
Are base freight charges calculated using the correct rate card version?
Is the fuel surcharge percentage applied as per the agreed index & date?
Are dimensional weight calculations verified against actual measurements?
Are accessorial charges (e.g., lift-gate, inside delivery) pre-approved or within SLA tolerances?
Are taxes computed using the correct jurisdiction and tax class?
Is the total amount the arithmetic sum of line items?
Are duplicate invoice numbers present?
Are credit notes correctly offset against original invoices?
Are rounding differences within the tolerance defined in the contract?
Is the invoice format readable by automated extraction tools?
Count of invoices with mathematical discrepancies found so far
Total overcharge detected in this audit batch
Total undercharge detected in this audit batch
Describe the three largest invoice errors discovered
Beyond math, verify that services, rates, and penalties comply with the negotiated contract clauses and SLA thresholds.
Are rates applied from the correct rate card effective on the shipment date?
Are minimum charges respected (no billing below the stated minimum)?
Are maximum caps (e.g., fuel surcharge ceiling) enforced?
Are declared value charges aligned with the cargo insurance terms?
Are transit-time commitments met as per the agreed service level?
Are penalties for service failure automatically credited?
Are packaging requirements (e.g., pallet type) billed only when deviated?
Are detention & demurrage charges within free-time allowances?
Are peak-season surcharges applied only within the defined window?
Are currency adjustment factors (CAF) computed per the contract formula?
Are CO2 surcharge fees aligned with the agreed index?
Are terminal handling charges (THC) per the agreed tariff?
Are documentation fees within the stipulated limit?
Are customs clearance fees only billed when the carrier performs the service?
Are re-weigh or re-measure charges justified with evidence?
Number of SLA breaches detected
Total service credits owed but not yet received
Describe any pattern of repeated non-compliance observed
Quantify impact, assign corrective actions, and feed insights into procurement and operations for continuous improvement.
Total invoices audited
Total invoices with exceptions
Total potential cost recovery identified
Total process efficiencies identified (soft savings)
Primary root-cause category for overcharges
Rate card misapplication
Fuel surcharge error
Accessorial billing
Currency/tax
Service failure not credited
Other
Have disputed amounts been formally logged with carriers?
Has a recovery timeline been agreed with carriers?
Has the audit report been reviewed by procurement?
Have corrective actions been assigned to owners with due dates?
Have findings been shared with finance for accrual adjustments?
Have KPIs been updated to prevent recurrence?
Target date for full recovery of overcharges
Next audit cycle scheduled date
Overall confidence in carrier compliance (1 = very low, 5 = very high)
Recommendations for contract renegotiation based on audit insights
Attach supporting documents and obtain formal sign-off to close the audit loop and maintain an audit trail.
Upload the master audit report (PDF preferred)
Upload carrier response file (if available)
Upload a screenshot of the disputed invoice summary (mask sensitive data if required)
Is all evidence stored in the designated secure repository?
Repository path or link where evidence is stored
I confirm that this audit was conducted per the approved audit protocol
I confirm that all numerical findings have been double-checked
Lead auditor signature
Sign-off timestamp
Analysis for Freight Audit Checklist
Important Note: This analysis provides strategic insights to help you get the most from your form's submission data for powerful follow-up actions and better outcomes. Please remove this content before publishing the form to the public.
This Freight Audit Checklist is a best-practice blueprint for supply-chain finance teams. It systematically forces auditors to prove—question by question—that every cent billed has a matching contract clause, rate card, or SLA. The four-section structure (Pre-Audit, Invoice Accuracy, Contract Compliance, Post-Audit) mirrors the life-cycle of an audit engagement, eliminating the risk that critical checks are forgotten. Mandatory yes/no gates act as hard stops: if the user cannot confirm that fuel surcharges follow the agreed index or that dimensional-weight logic was verified, the audit cannot progress, guaranteeing data integrity. Rich optional fields (currency amounts, narrative descriptions, file uploads) collect the evidence trail needed for carrier disputes or finance accruals without creating completion fatigue. Finally, the form embeds continuous-improvement loops—root-cause categories, KPI updates, and renegotiation recommendations—so findings translate into future savings rather than dusty PDFs.
From a usability standpoint, the mix of single-choice, yes/no, and numeric fields keeps cognitive load low; auditors can rapid-fire through line-item checks while still capturing quantitative impact (overcharge totals, SLA breach counts). Placeholder text and explicit field formats (date, currency, percentage) reduce input ambiguity. The closing Evidence & Documentation section with digital signatures creates an immutable audit trail that will satisfy both internal controls and external auditors. In short, the form elegantly balances comprehensiveness with speed, ensuring that even a junior analyst can execute a defensible, CFO-ready freight audit.
Purpose: Every audit engagement must be traceable for finance, legal, and carrier dispute purposes. A unique identifier becomes the primary key that links this checklist to TMS extracts, carrier responses, and eventual journal entries.
Effective Design: Making this field mandatory and placing it at the very start of the form guarantees that all downstream files, emails, and reports can be tagged with a consistent reference. The single-line open text gives teams flexibility to use internal naming conventions (e.g., "FA-2024-Q3-EMEA") without forcing a rigid format that might not fit every ERP.
Data Quality & Privacy: Because the identifier is user-generated, no sensitive data is exposed at this stage, reducing GDPR/CCPA risk. The field length is implicitly capped by the single-line control, preventing database overflow or XSS injection.
User Experience: Auditors immediately understand that this is the "file name" for the entire project, establishing mental context for every subsequent question. Auto-suggest or auto-generation could be a future enhancement, but the current free-text approach keeps implementation friction near zero.
Purpose: The start date drives SLA clocks, carrier claim windows, and finance cut-off periods. Without it, the audit scope is ambiguous and may miss invoices that aged out of recourse.
Effective Design: Using a native HTML5 date picker enforces ISO formatting, eliminating locale confusion (MM/DD vs. DD/MM). Mandatory status ensures that no checklist can be submitted with an open-ended timeline, protecting the company’s recovery rights.
Data Collection Implications: A valid date field enables time-series analytics—teams can trend how long audits take or how quickly carriers repay overcharges. The date is PII-free, so it can be shared with external consultants without redaction.
Usability Considerations: The picker is faster than typing and prevents impossible dates (Feb 30). Optional end-date and invoice-date fields later in the form create a coherent timeline narrative, reducing cognitive load for the auditor.
Purpose: Domestic, international, or both? The answer determines which rate cards, customs rules, and currency conversions must be validated. A mis-aligned scope can invalidate the entire audit.
Strengths: Single-choice radio buttons eliminate multi-select ambiguity; the auditor must consciously choose, preventing the "I forgot to check a box" problem. The mandatory flag ensures finance teams cannot accidentally scope an audit too narrowly and miss high-value international lanes.
Data & Reporting: Because the value is constrained to three options, BI dashboards can aggregate recovery rates by scope, revealing whether international invoices are more error-prone than domestic ones.
User Friction: Zero friction—three clearly labeled options, no scrolling required on mobile. The horizontal layout typical for radio groups scales well on small screens.
Purpose: Each mode (Road, Rail, Ocean, Air, Intermodal) has unique surcharge rules and billing events. Identifying modes up-front prevents auditors from applying road-fuel logic to jet-fuel indexes.
Design Excellence: Multiple-choice checkboxes allow combinatorial selection while keeping the question concise. Mandatory status guarantees that at least one mode is chosen, avoiding null-scope audits.
Quality & Risk: Constraining the answer to predefined options eliminates typos ("Ocen" vs. "Ocean") and ensures downstream automation rules can fire correctly. The field also flags high-risk modes—ocean audits often recover the largest dollar amounts due to demurruree complexity.
UX Note: The inclusion of an "All modes" option acts as a select-all shortcut, reducing click fatigue for full-network audits yet preserving granularity when only parcel air is in scope.
Purpose: Disputes move at the speed of communication. Without a verified carrier roster, overcharge emails bounce and recovery timelines slip.
Mandatory Justification: A missing contact list is a project-blocking defect; hence the form enforces a yes/no gate. This prevents teams from discovering missing data mid-audit when carrier response SLAs are already ticking.
Data Integrity: The yes/no format is binary—no partial credit—so management can confidently report readiness metrics ("100% of audits have carrier lists").
User Consideration: The question acts as a forcing function; if the user answers "No," they must exit the checklist and prepare the list, ensuring downstream steps aren’t wasted on unreachable carriers.
Purpose: Contracts are the legal basis for every dollar recovered. If the auditor cannot cite the exact clause, the carrier will reject the claim.
Design Strength: Mandatory yes/no creates a non-negotiable checkpoint. The form will not proceed unless the auditor has the contracts in hand, eliminating the all-too-common scenario of discovering missing addenda after discrepancies are found.
Privacy & Security: The checklist does not ask for the contracts themselves—only confirmation of access—reducing the risk of uploading confidential commercial terms to an insecure location.
Efficiency: By front-loading this confirmation, the form prevents wasted hours reviewing invoices against stale rate cards, a major source of false positives in freight audits.
Purpose: Late deliveries or service failures trigger credits. Without documented SLA thresholds, carriers can argue that transit-time penalties are "not applicable."
Effective Design: The mandatory flag compels audit teams to locate the exact SLA document (often an appendix to the master service agreement) before ticking "Yes," ensuring every on-time delivery claim is enforceable.
Data Implications: Documented SLAs can be coded into audit software, enabling automated breach detection against actual transit data. The yes/no answer acts as a green-light for automation.
User Friction: Minimal—most TMS implementations store SLAs as PDFs; the auditor simply confirms existence rather than re-typing clauses.
Purpose: Without raw shipment, charge, and payment data, auditors must rely on carrier-supplied summaries—an inherent conflict of interest.
Strength: The mandatory yes/no gate prevents the checklist from becoming a paper exercise. If access is denied, the audit is paused until IT provisions read-only roles, ensuring data authenticity.
Security & Compliance: The question reminds stakeholders to apply least-privilege access (read-only, anonymized if needed) rather than blanket exports, aligning with SOX and ISO-27001 controls.
UX: Auditors immediately know whether they can automate sampling or must resort to manual PDF reviews, setting correct expectations for timeline and effort.
Purpose: Audit evidence (invoices, photos, emails) must be tamper-evident for legal discovery and carrier negotiations.
Design Merit: Mandatory yes/no ensures compliance with internal audit standards and external regulations such as CBP’s record-keeping rules for international shipments.
Data Governance: The affirmative answer triggers downstream workflows: automatic encryption, retention tagging, and access logging. Missing this step would invalidate the entire audit trail.
User Guidance: The question implicitly reminds auditors to use company-sanctioned tools (SharePoint, Box, S3) rather than personal drives, reducing data-leak risk.
Every yes/no question in this section (currency consistency, exchange-rate source, rate card version, fuel index, dimensional weight, accessorial approval, tax jurisdiction, arithmetic sum, duplicate detection, credit-note offset, rounding tolerance, invoice format) is mandatory. Collectively they create a bullet-proof line-item validation protocol. The binary nature removes subjectivity—either the carrier followed the rule or they did not—yielding clean, dispute-ready evidence. By forcing the auditor to consciously answer each checkpoint, the form guarantees that no low-hanging fruit (duplicate invoices, arithmetic errors) is overlooked, which historically represent 30-40% of overcharges. The design also supports automation: because answers are constrained, rules engines can pre-score invoices before human review, slashing audit cycle time.
Similarly, every yes/no here (rate card date, minimum charges, maximum caps, declared value, transit-time, penalties, packaging, detention, peak season, CAF, CO2 surcharge, THC, documentation fees, customs clearance, re-weigh evidence) is mandatory. These questions operationalize the contract clauses most frequently disputed by carriers. The checklist approach ensures parity: if a carrier imposes a peak-season surcharge, the auditor must verify it falls inside the contractual window. The cumulative effect is a quantified compliance score that finance can use to withhold payment or demand credits. The mandatory structure prevents selective auditing, a common pitfall where auditors check only the largest invoices and ignore systemic leakage across mid-tier spend.
The questions "Have disputed amounts been formally logged with carriers?" and "Has a recovery timeline been agreed?" are mandatory to ensure the audit exits the spreadsheet and enters the cash-collection phase. Without formal logging, carriers can claim they never received notice, resetting the dispute window. The remaining mandatory questions (report reviewed by procurement, corrective actions assigned, findings shared with finance, KPIs updated) enforce closed-loop governance, turning findings into process improvements rather than one-off recoveries.
Final mandatory yes/no and checkbox questions (evidence in secure repository, audit protocol confirmation, numerical findings double-checked) create a defensible sign-off page. Combined with signature and time-stamp fields, they produce an audit trail that satisfies both internal audit and external regulators such as DCAA or SOX auditors.
Mandatory Question Analysis for Freight Audit Checklist
Important Note: This analysis provides strategic insights to help you get the most from your form's submission data for powerful follow-up actions and better outcomes. Please remove this content before publishing the form to the public.
Unique audit identifier or reference code
Justification: This single string is the primary key that stitches together TMS extracts, carrier emails, dispute logs, and finance journal entries. Without a mandatory, consistent identifier, files get mis-filed, duplicate audits arise, and recovery cash cannot be traced back to the original claim, undermining CFO confidence.
Audit start date
Justification: Carrier dispute windows and statute-of-limitations clocks begin on the audit start date. Leaving this optional would risk missing legal deadlines, potentially forfeiting six-figure recoveries. The mandatory date field guarantees timeline accountability.
Audit scope
Justification: Domestic and international invoices operate under entirely different rate structures, tax regimes, and SLA definitions. A missing scope allows auditors to apply the wrong benchmarks, invalidating results and exposing the company to carrier pushback. Mandatory selection enforces unambiguous boundaries.
Transport modes included
Justification: Ocean demurrage rules do not apply to parcel air shipments. By forcing at least one mode to be selected, the form prevents null-scope audits and ensures the correct surcharge logic is invoked downstream.
Have you compiled a master carrier list with contact details?
Justification: Recovery emails sent to obsolete addresses are the #1 reason carriers ignore claims. Making this mandatory ensures the audit cannot proceed until a verified contact matrix exists, slashing response times and increasing recovery hit rates.
Are original service contracts & rate cards accessible?
Justification: Contracts are the legal bedrock of every dispute. Without mandatory confirmation, auditors may rely on outdated tariffs, producing unenforceable claims and damaging carrier relationships.
Are SLAs & KPI definitions documented?
Justification: Transit-time credits cannot be claimed if SLA thresholds are undocumented. This mandatory gate guarantees that service-failure penalties are quantifiable and defensible.
Is access to TMS/ERP data granted to auditors?
Justification: Self-reported carrier data is inherently biased. Mandatory access confirmation ensures auditors can independently verify shipment details, eliminating the risk of garbage-in-garbage-out audits.
Have you created a secure file repository for evidence?
Justification: Regulatory bodies such as CBP require record retention for up to five years. A mandatory yes/no forces compliance with retention policies and protects against data loss or tampering.
Invoice Accuracy – all yes/no questions
Justification: Each question targets a high-frequency error source (currency mismatch, duplicate invoices, rounding errors). Mandatory status ensures zero tolerance for arithmetic leakage, historically the largest bucket of overcharges.
Contract Compliance – all yes/no questions
Justification: These questions operationalize complex tariff clauses. By forcing auditors to answer each one, the form prevents selective auditing and guarantees systemic compliance verification.
Post-Audit – disputed amounts logged, recovery timeline agreed, report reviewed, corrective actions assigned, findings shared with finance, KPIs updated
Justification: Each mandatory checkpoint represents a critical hand-off: from auditor to carrier (dispute logged), carrier to treasury (timeline agreed), and audit to operations (KPI update). Skipping any step breaks the closed-loop process and turns recoveries into one-off events rather than continuous savings.
Evidence & Documentation – secure repository confirmed, protocol compliance checkbox, numerical findings double-checked checkbox
Justification: These final mandatory attestations create a legally defensible sign-off page that satisfies both internal audit standards and external regulator requirements (SOX, DCAA, ISO-27001).
The form strikes an optimal balance: only 31 of 79 questions are mandatory, focusing on pass/fail gates that protect legal rights, enforce data integrity, or unlock downstream automation. This ratio keeps completion friction low while safeguarding the highest-value audit controls. To further boost submission rates, consider making numeric impact fields (total overcharge, SLA breach count) conditionally mandatory when the corresponding yes/no answer is "Yes," ensuring quantified evidence without upfront burden. Additionally, provide inline help links (e.g., "What counts as a secure repository?") so junior auditors understand the minimum standard before ticking "Yes." Finally, batch mandatory questions into collapsible sections with progress bars; psychologically, users tolerate required fields when they can see they are 90% complete, reducing abandonment at the final sign-off page.