CSA Codes on Settlement Statements (and Why Multi-Entity Statements Confuse Everyone)

Every FedEx Ground settlement statement carries a CSA code — the identifier for the Contracted Service Area the statement belongs to. For a contractor with one CSA it's easy to ignore. For anyone operating multiple entities, or comparing paperwork across an acquisition, it is the single most important field on the page — and misreading it is, in our experience, the most common reason a self-audit "finds" discrepancies that don't exist.

What it is

A CSA (Contracted Service Area) is the unit FedEx contracts at: a defined territory with its own agreement, its own Schedule A territory definition, and its own Schedule C rate card. The CSA code on a settlement tells you which of those contracts the statement is settling. One operating company can hold multiple CSAs; each settles separately, under its own rates, even if the same drivers and trucks serve both on the ground.

Why multi-entity statements confuse everyone

The confusion comes from a mismatch between how the business feels and how the paperwork works. Day to day, you run one operation: one terminal, one fleet, one team. But contractually you may be two or three CSAs, and the paperwork is strictly per-CSA. That produces predictable traps:

• Comparing a statement to the wrong rate card.Each CSA's rates are negotiated separately. Check CSA 309's statement against CSA 307's Schedule C and you'll manufacture a page of phantom rate discrepancies — every number is "wrong" because the reference is wrong.
• Aggregating across entities by accident. Add two CSAs' statements into one weekly total without labeling, and later comparisons — this week against a week where you only counted one entity — show swings that never happened.
• Assuming similar entities have similar rates.Two CSAs under the same roof can have meaningfully different per-stop and per-package rates, different contract dates, and different amendments. "They should match" is an assumption, not a fact about your contracts.
• Losing track during transitions. Buying, selling, or restructuring entities means statements can arrive under codes you don't recognize yet. Label first, analyze second.

What to check

• Read the CSA code before reading any number.Make it a reflex: identify which contract you're looking at, then evaluate the figures.
• File rate cards by CSA code. Keep each Schedule C labeled with its code and effective date, and only ever compare same-code to same-code.
• Track weekly figures per CSA, not just in total.A combined number is fine for the bank account; per-CSA series are what make trends and rate checks meaningful.
• When something looks off, check the join first.Before concluding a rate is wrong, confirm the statement and the reference rate card carry the same CSA code. Most "discrepancies" die right there.

The join rule, automated

We're opinionated about this because we validated it the hard way: naive settlement checking that ignores entity boundaries produces large, official-looking, and entirely fictional "variance" numbers. That's why Route Impact's weekly settlement checks join strictly on CSA code — each statement is compared only against the rate card on file for its own CSA, and if the codes can't be matched the platform says so and declines to make rate findings at all, rather than guessing. Anything that does get flagged is flagged for your review with the matching evidence shown. If you take one habit from this article, take that one: match the entity before you trust the comparison.