3PL invoice audit checklist

1. Define the review

• Record provider, contracting entity, facility, invoice number, billing period, service period, and currency.
• Choose the newest invoice whose contractual dispute window may still be open.
• State which charge families and operational events are in scope.
• Record total billed spend, but leave evaluated spend blank until each line has a supported check.
• Assign one person to preserve source files and one review version of the worksheet.

2. Collect governing documents and evidence

• Complete invoice PDF and itemized CSV or XLSX export, if available.
• Signed MSA, SOW, pricing exhibits, rate cards, amendments, and concessions.
• Dispute-window, notice, currency, tax, and document-precedence clauses.
• Relevant sibling invoices, credit memos, inventory statements, and carrier adjustments.
• Orders, shipments, receipts, returns, weights, zones, or other event records required by the selected checks.
• Credit promises and correspondence with an exact date, amount, reference, and source citation.

Confirm versions and dates

• Give every document a stable source ID and record its effective date range.
• Resolve amendments using the agreement’s precedence language.
• Preserve page, row, or cell coordinates for every extracted term.
• Mark redactions, missing pages, unreadable scans, and conflicts as evidence gaps.

3. Preserve and reconcile the invoice

• Keep raw line IDs and descriptions unchanged beside normalized fields.
• Reconcile line amounts, credits, taxes, and other sections to the displayed invoice total.
• Record unsupported sections rather than dropping them from the denominator.
• Check whether displayed quantity × displayed rate ties to displayed amount where the units make that formula plausible.
• Record order, shipment, tracking, receipt, SKU, case, and credit references without treating them as interchangeable.

4. Normalize the rate card and map invoice lines

• Capture source description, provider charge code, normalized category, unit, recurrence, and quantity basis.
• Capture exact rate, currency, rounding, scope, conditions, and effective dates.
• Represent flat, unit, first/additional, matrix, tier, minimum, storage-age, percentage, and cost-plus mechanics distinctly.
• Map a line only when its code or description, date, unit, scope, and condition are compatible.
• Keep ambiguous category-only matches in review; do not infer a favorable rate.

Use the 3PL rate-card guide for examples of each mechanic.

5. Run billing checks

• Rate mismatch: compare the billed rate with a source-backed active rule using the same unit and scope.
• Duplicate charge: establish one unique economic event and exclude legitimate repetition.
• Storage: verify unit, quantity source, receipt lot, age, period, and seasonal band.
• Volume tier: confirm the metric, scope, full measurement period, and bracket semantics.
• Missing credit: reconcile a documented promise against later invoices and credit memos after the expected lag.
• Other review questions: keep minimums, undefined charges, rate drift, tax, mapping, and document integrity in their correct evidence state.

Open the common 3PL billing errors guide for required evidence and false-positive guards.

Rule out innocent explanations

• Later amendment or written concession.
• Different unit, facility, channel, service level, currency, or effective date.
• Split shipment, reshipment, recurring fee, or per-container composition.
• Credit-and-rebill, reversal, lagged adjustment, or overlapping export period.
• Complete-period tier, minimum, storage age, new receipts, or seasonal rate.
• Netted or differently referenced credit.

6. Assess dispute readiness and track the outcome

• Calculate the dispute deadline from the cited governing clause and supported anchor date.
• State whether the window is open, expired, or unknown.
• Attach the billed line, expected rule, exact arithmetic, source citations, blockers, and assumptions to every candidate.
• Keep review candidates, verification items, observations, underbilling, and optimization separate.
• Require merchant approval before any future dispatch.
• Track submitted, provider-acknowledged, credited, and recovered states separately; never backfill them from a flag.

Downloadable workbook and field schema

Download workbook v1.0 (.xlsx)

Use one row per invoice line or one row per defined candidate, but never mix grains without an explicit record type. The expected-amount and candidate-variance columns are starting formulas for simple unit rates; tiers, matrices, minimums, percentage charges, and other mechanics need their own source-backed formulas.

How to interpret completion

Ready to calculate

The governing rule and required inputs are source-backed, compatible, and complete enough for deterministic arithmetic.

Missing evidence

A required source or operational fact is absent. State the gap and keep the affected spend outside evaluated coverage.

Review required

The arithmetic or pattern is useful, but an explanation, contract interpretation, publication cell, or other proof remains unresolved.

No supported conclusion

The available sources cannot establish either an error or clean billing. The honest output is a specific question or silence.

Read the full step-by-step audit guide, inspect the synthetic sample, or review the decision rules in the methodology.