
A carrier document can establish a published charge. It cannot, by itself, establish that the same amount belongs on your invoice. That second conclusion requires a chain of evidence about the shipment and your agreement.
Use the 2027 FedEx changes to request that chain before accepting a revised rate card. The aim is not to presume an error. It is to make the adjustment explainable and reviewable.
Start with the trigger
FedEx's 2027 delivery-area document identifies destination ZIP codes for surcharge assessment, effective January 4. It directs readers to the Service Guide for amounts. Official 2027 delivery-area ZIP lists.
A destination appearing in a surcharge list is a pricing fact. It is not proof that delivery is unavailable or that service has deteriorated. Keep coverage eligibility, delivery performance and surcharge treatment as separate questions.
Build a five-link evidence chain
Our proposed review tool uses five links:
| Link | Evidence to request | Question it answers |
|---|---|---|
| Carrier rule | Dated official notice or table | What published rule applies? |
| Shipment facts | Service, date, destination and package record | Does this shipment meet the trigger? |
| Account terms | Applicable agreement or documented rate treatment | What net treatment applies to the account? |
| Provider billing rule | Your agreed pass-through, bundle or markup method | How does carrier cost become your charge? |
| Invoice result | Charge detail and any adjustment record | Was the rule implemented consistently? |
This is an editorial checklist, not an audit certification. We have not reviewed any provider's contracts or billing system.
A missing document is not a zero charge
Consider three fictional evidence packets. Packet A contains only a carrier notice. Packet B adds a shipment and carrier charge but omits the brand's billing agreement. Packet C includes all five links and a reproducible calculation.
Packet A supports investigation, not a conclusion about what the brand owes. Packet B helps establish a carrier event but leaves the provider-to-brand treatment unresolved. Packet C makes review possible, although the calculation still needs to be checked.
The distinction matters when an invoice looks plausible. A matching number is not enough if the wrong date, service or agreement was used.
Test boundaries as well as ordinary orders
Ask for a small review covering a normal shipment, an affected surcharge destination, an adjustment to an earlier shipment and a credit. Agree on the relevant date rule rather than assuming invoice date determines the tariff.
Record each result as supported, inconsistent or unresolved. Do not count unresolved rows as confirmed savings or confirmed overcharges. Keep the evidence request specific: identify the missing agreement provision, shipment attribute or carrier reference.
If the provider cannot share a confidential carrier contract, ask what alternative evidence it can provide to substantiate your agreed billing treatment. The purpose is verification of your bill, not unrestricted access to someone else's commercial terms.
Decide what closes the review
Set an owner and deadline for each unresolved item. A revised explanation, corrected invoice or documented commercial agreement may resolve different cases.
A strong provider response makes the chain easier to follow. Your decision should rest on that evidence and its consistency across shipments, rather than the confidence of the explanation alone.
Verify the tariff version as well as the destination
The annual package changes begin January 4, while selected domestic ZIP-pair zone changes are announced for February 1. FedEx announcement. Retain the origin, destination and relevant date with the evidence packet.
Ask the reviewer to identify the exact version used, rather than attaching a screenshot labeled “current rates.” A geographic surcharge list and an origin-to-destination zone table answer different questions. Neither proves a named alternative carrier's coverage, pickup capacity or delivery performance.
Related reading
Sources
Checked September 29, 2026. Future changes are announced, not yet effective. Recheck before publication.