It's a Tuesday in February. Your 2027 freight budget locked in the final weeks of last year, after three or four iterations, and you have settled into execution mode, probably by finalizing the tender you will launch very soon.
Then a forwarded news headline lands in your inbox: ocean rates on the major trades are down 30%. Above it, one line from finance. "Why isn't our number down?"
If you manage freight spend, some version of this scene is way too familiar. The budget you built in August (and the three updated ones you were asked for in October, November, and December) does not get filed away when it locks. It follows you through every monthly review, every quarterly close, and every market headline your CEO or CFO happens to read. The real work of budget season is not producing the number. It is being able to defend it for the twelve months that follow, and explain why it didn't pan out, which it never does.
The question is rarely "how was this built?"
Procurement teams often prepare for finance to challenge their methodology. In practice, across hundreds of conversations with shippers, we see a different pattern. Once your budget makes it past your assigned Controller, finance rarely asks how the budget was built, and certainly not while things are on track. The interrogation is continuous and it is about variance: how are we performing against the number you gave us, and why does this month not match (again).
The sharper version of the question arrives armed with a headline or a (more or less relevant) public index. Finance teams read the same market coverage everyone else does, and the trigger does not have to be a rate index: reporting that capacity is up, or simply that rates on the major trades are falling, works just as well. When a widely reported index says rates have fallen 30% while your forecast line has not moved, the gap becomes yours to explain and own. Here is the uncomfortable part: both numbers can be correct. Public indices typically track spot rates on headline lanes. Your spend sits in long-term contracts, across your specific corridors (your trade lanes), with your own surcharge structure, volume commitments, payment terms, free-time agreements, fuel adjustment mechanisms, and other commercial terms not reflected in the index. A spot index falling 30% tells you very little about what a contracted shipper in your particular reality should expect to pay. And notice what each side is holding. Finance has a story: a headline, a line of market commentary, a figure picked up from the trade press. Procurement is the side that should be holding the actual market data for its own corridors. When it is, that conversation is short. When it isn't, a headline becomes hard to argue with, no matter how little it says about the rates you actually pay.
The "how was this built" question gets asked twice, in two different tones. It comes up during the build itself, from the CPO and the Controller as the budget iterates, and reasonably so: a number heading for the annual plan should be able to show its work. Then it comes back after a miss, in the post-mortem, where it is no longer a process question but an accountability one. Either way, the answer needs to be better than a spreadsheet of last year's rates with a growth factor applied.
The CFO and the Controller want different things
Part of what makes explaining freight costs difficult is that "finance" is not one audience. The CFO cares about a single number: was freight a saving or an on-cost against plan, and why, ideally in no more than three bullet points. Rare is the CFO who asks in detail how a freight budget was constructed. What rolls up to them is an outcome and a short narrative they can carry into board meetings and analyst calls.
The person who does care about the detail is the Controller, specifically the Controller closest to the activity, be it a back-office function, a product line, a division, or a region. They prepare the monthly and quarterly reviews that become the CFO's number, and they want every deviation explained in a consistent order: volume against budget, changes in mix, currency movement, commercial conditions in the shipping market, and finally extraordinary circumstances, the disruptions and one-off events that get pulled out for a deeper look. Controllers call these buckets, and the word is worth borrowing.
That breakdown matters enormously for procurement, because it is the difference between a fair review and an unfair one. If the market bucket cannot be separated from the rest with credible data, every dollar of variance lands in the same place: on the team that bought the freight. Independent benchmarks are what allow a Controller to write "actual costs on our corridors rose 4% above budget. Approximately 50% of the increase was caused by spot market movement, 25% by mix, 20% by exchange rate fluctuations, and 5% by extraordinary circumstances."
The burden of proof falls on procurement
The annual budget is a fixed baseline once it locks. Anything that follows is a forecast. This is when functions re-state their expectations versus the budget, accompanied by evidence that must clear a high bar, and the burden of producing that evidence falls entirely on procurement.
The bar is high for a reason. A carrier or forwarder forecast, however well intentioned, comes from a party with a commercial interest in the outcome. Your own analysis, however careful, is an assertion from the team asking for the bigger number (or occasionally, committing to a lower one). A neutral third party demonstrating that the market itself has shifted is an invaluable help when lifting that burden: rates on your corridors, benchmarked against what thousands of other shippers are actually paying, moving in a direction and magnitude that no procurement decision could have offset.
This is also why the annual exercise and the monthly defense are essentially the same problem. The data that lets you build a credible number in August (where the market sits today on your corridors, where contracted rates are heading, what best and worst case look like) is the same data that lets you explain February's variance without the meeting running long.
What a defensible number looks like
A freight budget that survives twelve months of scrutiny tends to share four characteristics.
It is built on contracted rates rather than headline spot indices, because that is what most BCO spend actually is, and because it removes the "rates are falling, why aren't yours" ambush before it happens. When your budget and your benchmark are both built on contracted rates, the comparison finance makes is finally the right one.
It is a range rather than a point estimate. Finance teams increasingly ask for scenarios directly: a best case, a "most likely" case, and a worst case, and the variance between them. A single number is a guess that will be wrong in one direction or the other. Three scenarios built from your own volumes at current market levels give finance something they can actually plan against, and give you a corridor of outcomes you can defend rather than a line you will inevitably miss.
It is corridor-level and current. Freight markets do not move uniformly, and a budget that averages across trades hides exactly the detail the Controller will later ask about. This is not extra work invented by data vendors: the budget was built trade lane by trade lane in the first place, so the review should follow the same lines. Monthly refreshes matter for the same reason: the budget vs. actual vs. forecast conversation is continuous, so the evidence needs to be, too.
And it looks forward. A budget built in the autumn for contracts that renew in the spring is pricing rates that do not exist yet. Today's market is the starting point, and a forward outlook on where contracted rates are heading over the next three to six months is what turns that starting point into an assumption you can put your name to.
Defending it all year
The best teams build the defense in from the start. They set the number with scenarios and independent benchmarks, then carry the same structure into every monthly review: a variance breakdown where the market bucket arrives with evidence attached, and where the extraordinary events bucket is reserved for events that were genuinely unforeseeable rather than used as a place to hide everything uncomfortable.
That discipline changes the conversation with finance from defensive to routine. The question stops being "why is your number wrong" and becomes "what did the market do this month," which is a question procurement can answer in minutes with the right data behind it.
The market will move against your number at some point next year. That part is certain. Whether you spend next February explaining or defending is the part you decide now.
Decide now whether you'll explain or defend
Xeneta's freight forecasting and budget planning tools handle both halves of the job: Budget Outlook prices your own volumes at today's market in best, conservative, and worst case scenarios, and Market Rate Outlook shows where contracted rates on your corridors head over the next 3 to 6 months.
.jpg?width=387&name=black-swan%20(1).jpg)