How to Audit Your Own FedEx Settlement Against Your Rate Card

Every week, FedEx sends you a settlement statement that is, in effect, an invoice you didn't write for work you already did. Most contractors read the total and move on. Auditing it — actually checking the statement against the rates in your contract — is not hard, but it is exacting: the handful of rules below separate a useful audit from one that manufactures phantom problems. This is the complete method, learned partly by doing it wrong first. You can run it in a spreadsheet in well under an hour a week once set up.

Before you start: three rules that prevent false alarms

We validated this process against real statements, and the failure modes are consistent enough to state as rules:

• Rule 1 — match the entity. Every statement carries a CSA code, and every Schedule C belongs to a specific CSA. Only ever compare same-code to same-code. Cross-entity comparison is the single biggest source of fictional "discrepancies" — official-looking variance numbers that describe nothing real. If you can't match the codes, stop; don't audit against a guess.
• Rule 2 — skip floating lines. The fuel surcharge moves weekly by design. It has no fixed rate-card reference, so a fuel-rate change is never a finding. Audit fuel only structurally: is the line present at all?
• Rule 3 — findings are questions, not accusations.A mismatch means "flag for review," not "FedEx shorted me." Amendments, reclassifications, and timing can all explain a difference. The audit's job is to surface the lines worth asking about while the week is fresh.

Step 1 — Assemble the documents

• The week's settlement statement, downloaded from the portal (CSV or Excel keeps the numbers workable; PDF works but means retyping).
• Your current Schedule C rate card for the same CSA — current meaning as-amended, not the version from onboarding. If you've accepted a MESO or any amendment since, the old card will fail you.
• Your prior 4–8 statements for the same CSA, for the history-based checks in Step 4.

Note the statement's service week — FedEx weeks run Saturday through Friday — and label everything by the week-ending Friday. Consistent week keying is what makes next month's comparisons possible.

Step 2 — Verify the join

Read the CSA code off the statement and confirm it matches the Schedule C you're about to use. If you run multiple entities, do this per section: multi-entity statements interleave, and a statement page can switch entities on you. This step takes ten seconds and protects everything downstream.

Step 3 — Compute effective rates on the fixed lines

For each revenue line that has both a unit count and a dollar amount — stop charges, per-package and activity-based charges, e-commerce lines:

• Effective rate = dollars paid ÷ units performed.
• Compare it to the Schedule C rate for that exact charge type. Match charge names carefully; similarly named lines with different frequencies are different charges.
• Expect exact or near-exact agreement. A statement that matches its rate card matches to the penny — we've verified this on real data. Small persistent gaps are therefore meaningful, not rounding noise, and one-week gaps deserve a second week of observation before you spend energy on them.

A clean pass here is a real result, not a wasted week: it's the evidence that your revenue engine is working as contracted, and it's what makes any future mismatch stand out immediately.

Step 4 — Run the structural checks

Rate math catches wrong numbers; structural checks catch missing and unexpected ones. Against your recent statements, ask:

• Is every recurring line present? A fuel surcharge or standing program charge that vanishes is more significant than one that moves.
• Any new deduction labels? Identify what contract term or event each new line traces to — before it becomes furniture.
• Any recurring deduction that changed without a reason? Fleet changes and amendments explain most moves; the unexplained remainder is your review list.
• Any duplicates? Same label, same amount, twice in one statement — rare, quick to scan for.
• Do the sections reconcile? Gross revenue minus deductions should tie to the settlement total. A statement that doesn't internally reconcile is worth a support inquiry on its own. One caution from real statements: settlement breakdowns can nest — a total line alongside its own break-out components. Sum categories without subtracting the break-outs and you'll double-count.

Step 5 — Record, then decide

Log each flagged line with: the statement week, the line, expected vs. observed, and the signed dollar difference. Then triage — small one-week oddities get watched; persistent or growing gaps get a polite, specific inquiry to your Business Support Manager with the evidence attached ("week ending X, charge Y settled at effective rate Z against a rate card value of W — can you help me understand the difference?"). Specific questions with evidence get better answers than vague complaints.

Step 6 — Make it survivable

The audit only has value as a habit. The realistic failure mode isn't doing it wrong — it's stopping. Template the spreadsheet, do it the same morning each week, and when your contract changes, update the rate-card tab the same day. If a week genuinely can't be checked (no time, missing document), leave it visibly unchecked rather than half-checked — a gap you can see beats a false green.

Or let the machine hold the discipline

Everything above is exactly what Route Impact automates: upload a settlement and it joins by CSA code, computes effective rates against the Schedule C on file, runs the structural checks, skips the floating lines, and flags anything unusual for your review with the line-level evidence and signed dollar delta attached — never asserting an error, because Rule 3 is built in. Clean passes are recorded too, so your history accumulates either way. The spreadsheet version genuinely works; the difference is which one still happens in December.