I’ve lost count of how many times I’ve watched a so‑called “global” per diem policy fall apart the moment someone books a trip to New York, London, or Zurich. On paper, the numbers look tidy. In real life, travelers are paying out of pocket, managers are approving one‑off exceptions by email, and finance is quietly reclassifying half the reimbursements as taxable income.

If that sounds familiar, this guide is for you. We’ll walk through the decisions that actually matter when you’re designing a global per diem policy that holds up in high‑cost cities, not just in spreadsheets.

1. Decide: Benchmark or Build Your Own Rates?

The first big decision is philosophical: do you want to be a rate designer or a rate selector?

Most companies don’t need to invent per diem rates from scratch. There are already solid benchmarks you can lean on when you’re building a multinational per diem strategy:

  • GSA CONUS rates for U.S. domestic travel (continental U.S.). For FY2026, the standard rate is around $107 for lodging and $59 for M&IE in many areas, with higher rates for high‑cost cities like New York or San Francisco (source).
  • IRS high–low method for U.S. tax purposes, with fixed daily rates for high‑cost vs low‑cost locations (e.g., $319 vs $225 per day for 2025–2026, split between lodging and M&IE).
  • U.S. State Department foreign per diem for international travel, updated monthly and highly granular by city and even season (source).

Here’s where many “global” policies go wrong: they pick one benchmark and apply it everywhere. That’s how you end up with a high cost city per diem rate that works in Kansas City but collapses in Tokyo.

Instead, use a simple structure when you’re designing a corporate per diem system:

  • U.S. domestic (CONUS): anchor to GSA or IRS high–low. Decide which is your primary reference and document it clearly.
  • Non‑U.S. travel: anchor to State Department foreign per diem. Treat it as a ceiling, not automatically as your default payout.
  • Company overlay: apply a consistent policy factor (for example, 90% of benchmark for standard cities, 100–110% for strategic high‑cost hubs).

The key idea: one flat rate is never “fair” globally. It’s tempting, but it doesn’t reflect reality. Use public benchmarks, then decide where you want to be more generous and where you’re comfortable being conservative.

2. Decide: Per Diem vs Actuals (and Where to Mix Them)

Next question: do you pay per diem, actual expenses, or a hybrid? Most companies end up with a hybrid model anyway, they just don’t write it down. That’s where confusion starts.

Per diem has clear advantages when you’re shaping a travel reimbursement policy design:

  • Predictable costs and easier budgeting.
  • Less receipt chasing and fewer arguments over what’s “reasonable.”
  • Potentially non‑taxable reimbursements when aligned with IRS/GSA rules.

But per diem has limits, especially in high‑cost locations. A flat daily allowance that works in Dallas may be laughable in Geneva during a major conference. That’s where many per diem mistakes in expensive cities show up.

Here’s a practical model that balances per diem vs actual expenses:

  • Lodging: reimburse actuals up to a cap (often tied to GSA/State/IRS lodging rates). This is where high‑cost cities hurt the most, so give yourself room to move.
  • Meals & Incidentals (M&IE): pay per diem, aligned with GSA/IRS/State benchmarks. This keeps admin light and expectations clear.
  • Incidentals‑only days: use a small fixed rate (e.g., the IRS $5 incidental‑only rate) when meals are fully provided.

Notice what this does: travelers don’t have to “game” the system in high‑cost cities. If the hotel market spikes, you can approve higher lodging within a documented cap (some federal rules even allow up to 300% of standard lodging in exceptional cases with approval). Meanwhile, meals stay predictable and easier to manage across your international per diem reimbursement rules.

Decision checkpoint: write down, in one sentence, when you use per diem and when you use actuals. If you can’t do that, your travelers definitely can’t either.

3. Decide: How Will You Handle Truly High‑Cost Cities?

This is where most policies quietly fail. High‑cost cities are no longer edge cases. They’re where your executives, sales teams, and project leads often go, and where your per diem policy for financial hubs gets stress‑tested.

Think about cities like:

  • New York, San Francisco, Washington, DC
  • London, Paris, Zurich
  • Tokyo, Singapore, Hong Kong

Benchmarks already recognize these as expensive. For example, IRS high‑low per diem designates specific high‑cost locations with higher daily rates, and the State Department sets significantly higher foreign per diem for hubs like London or Zurich.

You still have to decide how your global per diem policy responds:

  • Do you pay full benchmark in these cities? Or a percentage of it?
  • Do you allow exceptions above benchmark? If yes, who approves and how is it documented?
  • Do you differentiate by traveler type? For example, senior executives vs junior staff, or long‑term assignments vs short trips.

Here’s a pattern that works well in a multinational per diem strategy:

  1. Define a list of “Tier 1” high‑cost cities (e.g., NYC, London, Tokyo, Zurich). Use IRS/State lists as a starting point and refine based on your own travel data.
  2. Set a clear rule: “In Tier 1 cities, we reimburse lodging up to 120–150% of the benchmark rate with manager approval; meals per diem is 100% of benchmark.”
  3. Document seasonal spikes: some cities are high‑cost only during certain months. IRS and State Department tables already reflect this; don’t ignore it when you’re benchmarking per diem by city.

If you skip this, one of two things usually happens: travelers quietly subsidize the company (and resent it), or managers approve ad‑hoc exceptions that blow up your budget and your tax compliance.

4. Decide: How Strictly Will You Align with Tax Rules?

Per diem isn’t just a budgeting tool; it’s a tax tool. Ignore that, and your clean‑looking corporate travel cost reimbursement policy can turn into a payroll headache.

In the U.S., the basic pattern is:

  • At or below federal rates (GSA/IRS/State) under an accountable plan, per diem is generally non‑taxable.
  • Above federal rates, the excess is taxable income.
  • Documentation (time, place, business purpose) is mandatory to keep reimbursements non‑taxable.
  • Owners with 10%+ interest often cannot use per diem methods and must use actual expenses instead.

So you have a choice when you’re thinking about per diem compliance for global companies:

  • Compliance‑first: cap per diem at federal benchmarks and treat any extra as taxable. This keeps payroll clean but may feel tight in high‑cost cities.
  • Flexibility‑first: allow higher per diem in specific cases, but explicitly treat the excess as taxable and automate that through payroll.

Neither approach is wrong. What causes trouble is pretending you’re doing one while actually doing the other.

Practical approach: pick a default (for example, “We align with GSA/IRS/State rates; any higher amounts are taxable”) and build your tools and training around that. Make sure finance and payroll are in the room when you decide. They’re the ones who live with the consequences.

5. Decide: How Will You Handle Travel Days, Partial Meals, and Incidentals?

This is where the small rules either save you or sink you. Travelers remember the little frictions: Why did they cut my per diem on the first day? Why did they dock me for the conference lunch?

Most public benchmarks already have answers, and they’re useful when you’re building a consistent cost guide for global per diem:

  • First and last day of travel: U.S. federal rules typically pay 75% of the M&IE rate on those days, regardless of departure/arrival time.
  • Provided meals: M&IE is broken down by meal (breakfast, lunch, dinner, incidentals). If a meal is provided, you reduce the per diem by that portion.
  • Incidentals: small items like tips and service charges are included in M&IE; there’s also a $5 incidental‑only rate when no meals are reimbursed.

Here’s what you should decide and document:

  1. Will you adopt the 75% rule for travel days? If yes, say so explicitly. If no, explain your alternative and keep it simple.
  2. How will you reduce per diem for provided meals? For example: “If breakfast is provided, we reduce M&IE by 20%; lunch 25%; dinner 55%.”
  3. What counts as an incidental? Spell out examples: tips, baggage fees, small service charges.

These details matter more in high‑cost cities, where travelers are already stretching their per diem. A clear rule about provided meals can prevent both overpayment and resentment.

6. Decide: How Much Flexibility Will You Give Managers?

No matter how well you design your travel reimbursement policy, reality will throw you curveballs: sold‑out hotels, last‑minute trips, major events that triple prices overnight. The question isn’t Will we make exceptions? It’s How controlled will those exceptions be?

Here’s a structure that keeps you sane and keeps your international per diem reimbursement auditable:

  • Standard band: up to 100% of benchmark per diem and lodging caps. No special approval needed.
  • Flex band: 101–150% of benchmark in defined high‑cost cities, with manager approval and a short justification.
  • Exception band: above 150% (or up to 300% of lodging in extreme cases), requiring higher‑level approval and documentation.

Then decide:

  • Who can approve each band? Line manager? Director? Finance?
  • How is it recorded? In your expense tool? In a travel request system?
  • How often will you review exceptions? Quarterly reviews can reveal patterns that justify permanent policy changes or updating international per diem rates.

The goal isn’t to eliminate exceptions. It’s to make sure they’re visible, intentional, and auditable.

7. Decide: How Will You Communicate and Enforce the Policy?

A beautifully designed per diem policy that lives in a forgotten PDF is useless. Travelers will default to whatever their manager tells them, and managers will default to whatever they did at their last company.

So you need a communication and enforcement plan that supports your global per diem policy in day‑to‑day use:

  • One-page summary: create a simple, non‑legalistic overview: what per diem is, how rates are set, what’s different in high‑cost cities.
  • Role‑based training: short guides for travelers, managers, and finance. Each group needs different details.
  • Embedded rules: configure your expense or travel tool to enforce caps, apply travel‑day percentages, and flag exceptions automatically.
  • Feedback loop: invite travelers to report when per diem feels unrealistic in specific cities. Use that data to adjust your tiers and refine your per diem caps in high cost locations.

Be honest in your messaging. If your policy is intentionally conservative, say so. If you’re aiming to be market‑competitive in high‑cost cities, say that too. People can handle trade‑offs; they hate surprises.

8. Pulling It Together: A Policy That Doesn’t Backfire

Designing a global per diem and reimbursement system that doesn’t fail in high‑cost cities isn’t about finding the perfect number. It’s about making explicit decisions on the structure of your corporate travel cost reimbursement approach:

  • Which benchmarks you use and how you adjust them.
  • Where you use per diem vs actuals.
  • How you treat truly high‑cost cities and seasonal spikes.
  • How tightly you align with tax rules.
  • How you handle travel days, provided meals, and incidentals.
  • How much flexibility you give managers and how you track it.
  • How you communicate and embed the policy in your tools.

If you walk through those decisions deliberately, you’ll end up with a global per diem policy that’s not just compliant on paper, but actually livable for travelers on the ground in New York, London, or Singapore.

And that’s the real test: would you personally be willing to travel under your own policy? If the answer is no, you already know where to start revising.

Chart or graphic illustrating international per diem concepts