Quick answer
Finance doesn't lose trust in a mobility program because costs vary from the original estimate. Variance is normal. Finance loses trust when nobody can explain the variance quickly, because the assumptions behind the original number were never written down. The fix isn't a more precise estimate. It's a traceable one.
There's a quiet disagreement running through most global mobility programs, and it rarely gets named out loud. Mobility teams treat a cost estimate as a planning input, a reasonable projection to guide a decision. Finance treats it as a commitment, a number they'll be measured against at year end. Both sides are right about what they think an estimate is. That's the whole problem.
This gap doesn't usually show up as an argument. It shows up as a pattern. A mobility program comes in "close enough" on any single move, quarter after quarter, and finance still stops trusting the numbers by the third or fourth review cycle. The mobility team isn't failing by their own standard. They're being held to a standard nobody actually agreed on.
The cost of an assignment is really three numbers
Part of the confusion is that "the cost" isn't one figure. It's at least three, and programs that don't separate them are the ones that end up in the most disputes.
The estimate
What a move is projected to cost at the moment a decision gets made, based on the tax rules, exchange rates, and allowance structure in effect that day.
The commitment
What actually gets written into the letter of assignment and the compensation balance sheet, which can differ from the estimate if anything was negotiated before signing.
The actual
What the assignment truly costs once payroll, tax filings, currency movement, and any mid-assignment changes are all accounted for.
A healthy program can explain the gap between all three at any point. A struggling one can't even tell you which of the three someone means when they ask, "did we go over budget?"
Why chasing a more precise estimate is the wrong fix
It's tempting to treat the gap between estimate and actual as the core problem, and to respond by trying to make the up-front number more precise. That's usually the wrong move.
Currency movement, tax law changes, and cost-of-living shifts over an 18-month assignment aren't fully predictable, no matter how good the initial model is. Chasing perfect precision on the front end is a game you can't win, and trying to win it anyway just burns time that could go somewhere more useful.
Margin note
"We assumed a EUR exchange rate of X on this date, and it moved by Y" is a five minute conversation. "We're not totally sure why this cost more than planned" is the conversation that ends with finance pulling back approval authority.
That reframes the actual goal. A rigorous estimate doesn't need to be exactly right. It needs to be traceable: built on assumptions specific enough that when reality diverges from the plan, someone can point to exactly where and why, without launching a forensic reconstruction project three months later.
Where mobility programs actually lose finance's trust
A handful of patterns show up again and again in programs that struggle with finance credibility, regardless of company size or industry.
- There's no fixed point of comparison. If "the budget" is whichever version of the estimate happened to be saved last, rather than the version that was formally approved, every variance conversation starts with an argument about which number is even real.
- Assumptions live in someone's memory instead of a system. When the tax methodology, exchange rate, or cost of living index used in an estimate isn't recorded anywhere, explaining a variance six months later means tracking down whoever built the original estimate and hoping they remember.
- Estimates don't survive negotiation. A number gets revised during offer discussions, maybe an allowance gets added or the tax approach changes, and that update never makes it back into the system of record. Finance ends up measuring actuals against a plan that was already out of date.
- There's no program-level view. Individual estimates might each be reasonable on their own, but without a rolled-up view, nobody can answer "what's our total mobility exposure this year" until all the numbers are in, and by then it's too late to course correct.
- Comparison happens after the decision, not before. A cheaper structural alternative, a different policy tier or a different assignment type, often existed and was never modeled, simply because building a second estimate from scratch felt like too much work.
What actually closes the gap
None of this gets fixed by asking analysts to be more careful. It gets fixed by treating cost governance as infrastructure, not diligence.
- One number gets designated as "the plan." Not the last spreadsheet someone happened to save, not whichever attachment is newest in an inbox. One number, timestamped, that everyone agrees is what the program is actually measuring against.
- Assumptions get recorded as data, not memory. The exchange rate, tax methodology, and cost of living vintage behind every estimate should be retrievable months later without asking a person to recall it from a meeting.
- The record updates instead of forking. When negotiation changes a number, that change flows into the same record the estimate came from. It doesn't spin off a second, disconnected version of the truth.
- Finance sees the program, not just the assignment. Rolled-up exposure across the whole mobility program should be visible on demand, not reconstructed by hand once a year when someone finally asks for it.
- Scenario comparison happens before signing. The moment to model a cheaper alternative is before the offer goes out, when it can still change the decision, not in a retrospective about why the program overspent.
The underlying shift
Global mobility programs are increasingly being evaluated the way any other major line of spend gets evaluated, with an expectation of real governance, not just good intentions. The programs that hold up under that kind of scrutiny are the ones where the estimate, the commitment, and the actual are connected records, and where every number finance sees comes with its assumptions attached instead of buried where no one can find them.
Ready to give finance a mobility estimate they can actually trace? See how Topia Horizon connects estimates, commitments, and actuals with every assumption attached.
Frequently Asked Questions
- Why does finance stop trusting mobility budgets even when individual assignments are close to their estimates?
- Trust isn't built on accuracy alone. It's built on the program's ability to explain variance quickly and consistently. If assumptions were never documented, even small, reasonable variances start to look unexplainable, and unexplainable is what erodes trust over time.
- What's the difference between a cost estimate, a commitment, and an actual cost in global mobility?
- The estimate is the projected cost at the time a decision is made. The commitment is what's formally written into the assignment letter and compensation documents, which can shift during negotiation. The actual is the true cost once payroll, tax, and currency effects are all realized. Programs that don't distinguish between these three numbers tend to argue about which one they're even discussing.
- Does a more accurate cost estimate solve the trust problem with finance?
- Not on its own. Currency and tax conditions change over the life of an assignment in ways no estimate can fully predict. What matters more is whether the estimate's assumptions were recorded clearly enough to explain variance after the fact.
- What should a mobility program track to improve cost governance?
- At minimum: a single approved version of each estimate, the specific assumptions behind it (tax methodology, exchange rate, cost of living index and date), a rolled-up view of total program exposure, and a documented comparison of at least one alternative scenario before a decision is finalized.
