I’ve lost count of how many times I’ve heard this on a trip: The per diem doesn’t even cover dinner here. And then, a week later in another city: I can eat like a king on this allowance. Same policy, totally different experience. That’s what happens when corporate per diem rates aren’t grounded in what things actually cost in each city.

In this guide, I’ll walk through how to think about per diem vs actual expenses and how to set fair, city‑specific daily rates without drowning in admin or tripping over tax rules.

1. Start with the real question: what problem is your per diem solving?

Before you touch a spreadsheet, ask one blunt question: Is your corporate travel per diem policy about simplicity, control, or fairness? You can’t fully optimize all three at once.

  • Simplicity: Fast approvals, minimal receipts, easy payroll and expense runs.
  • Control: Tight budgets, detailed data, and the ability to challenge outliers.
  • Fairness: Employees in New York and Omaha feel equally treated, even though their costs are nowhere near the same.

Per diem looks like it can do everything. In reality, it’s a trade‑off. As many per diem vs actual expenses comparisons show, a flat daily allowance gives predictable costs but drifts away from real prices in very cheap or very expensive cities.

So be explicit about your priority:

  • If you care most about speed and simplicity, you’ll lean toward flat or high–low per diem models.
  • If you care most about precision and control, you’ll lean toward actual expenses or hybrid models.
  • If you care most about fairness by city, you’ll lean toward city‑specific per diem guidelines tied to government tables.

Once you’re honest about what you’re solving for, the rest of your corporate per diem policy gets much easier to design.

2. Use GSA/IRS rates as your baseline, not your ceiling

In the U.S., you don’t have to invent per diem rates from scratch. The federal government already did the heavy lifting.

IRS Per Diem Rates for 2025: What Changed

The GSA CONUS rates (for the continental U.S.) and IRS guidance give you a city‑by‑city starting point for setting fair per diem by city:

  • For FY 2025, the standard CONUS rate is $178/day: $110 lodging + $68 M&IE (meals & incidental expenses).
  • There are hundreds of non‑standard areas (NSAs) with higher rates — think Arlington, Alexandria, New York, San Francisco.
  • Outside CONUS (Alaska, Hawaii, territories) has separate, usually higher rates.

These numbers aren’t random. Lodging per diem is based on average daily rate (ADR) data — real hotel prices and demand patterns. M&IE is tiered and broken down by meal so you can reduce the allowance when meals are provided.

Here’s how to use these tables in a practical, low‑drama way:

  1. Adopt GSA M&IE as‑is. It’s usually fair enough and keeps you aligned with non‑taxable limits.
  2. Decide what to do with lodging:
    • Use GSA lodging per diem as your cap, and reimburse actuals up to that amount (a hybrid model).
    • Or pay full per diem for lodging if you want maximum simplicity and predictability.
  3. Document the link to GSA/IRS in your policy so HR, finance, and employees know where the numbers come from.

Thinking of paying more than GSA because you want to be generous? You can. But once you exceed federal limits, you’re likely creating taxable income for employees and extra complexity for payroll. That’s rarely worth it unless you’re intentionally using per diem as a compensation tool.

3. Choose your model: flat, high–low, or fully city-based?

Once you accept that location matters, you still have to decide how much detail you’re willing to manage. Most companies end up with one of three models for their per diem cost comparison by city.

Professionally dressed people collaborating in a modern office setting with laptops and documents.

Model A: Flat rate everywhere

What it is: One per diem for all U.S. trips (or maybe one domestic, one international).

  • Pros: Simple, easy to explain, fast to administer.
  • Cons: Almost guaranteed to be unfair in either New York (too low) or small cities (too high).
  • Best for: Very small travel programs, low travel volume, or early‑stage startups that just need something workable.

If you go this route, still anchor it to something rational — for example, the standard CONUS rate or the IRS low‑cost high–low rate — and accept that it’s a blunt instrument, not a finely tuned travel cost guide for corporate per diems.

Model B: IRS high–low method

What it is: Two rates: one for high‑cost localities, one for everywhere else. For example, IRS guidance uses figures like $319/day for high‑cost areas and $225/day for others (check the current year’s notice for exact numbers).

  • Pros: Much simpler than full city‑by‑city, but more realistic than a single flat rate.
  • Cons: Still rough; some cities will be over‑ or under‑funded. You must track which locations are on the IRS high‑cost list.
  • Best for: Companies with recurring travel to a mix of big and mid‑size cities, but limited admin capacity.

This is a solid compromise if you want to stay within IRS safe harbors without doing a GSA lookup for every single trip.

Model C: Full GSA city-based rates

What it is: You use the GSA per diem lookup for each city and date, and pay those rates (or use them as caps).

  • Pros: Most accurate, most fair by city, and the cleanest alignment with federal rules.
  • Cons: More admin unless you automate; rates change annually and sometimes seasonally.
  • Best for: Construction, consulting, field services, or any business with varied destinations and meaningful travel spend.

My rule of thumb: if your travelers regularly say, This per diem makes no sense here, you’re probably ready to move from flat or high–low to full city‑based rates and more deliberate per diem benchmarking against GSA rates.

4. Reality check: does your per diem match actual prices in key cities?

Many companies say, We follow GSA rates, but when you look at real bookings, the numbers don’t match what hotels and restaurants actually charge. That’s where a quick reality check helps.

Pick a few representative cities for a per diem vs real hotel and meal prices comparison:

  • High-cost: New York, San Francisco, Washington DC, Honolulu.
  • Mid-cost: Denver, Austin, Charlotte.
  • Lower-cost: Omaha, Tulsa, smaller Virginia cities outside NSAs.

For each city, run a simple test:

  1. Look up the GSA lodging and M&IE for the travel dates.
  2. Check a few mid‑range hotels near likely work sites (not the airport, not the priciest downtown property).
  3. Estimate realistic meals: breakfast, a modest lunch, a normal dinner, plus tips.

Then ask yourself:

  • Can a traveler book a safe, reasonable hotel within the lodging per diem most of the time?
  • Can they eat three normal meals without gaming the system or skipping food?
  • Are we consistently under or over in certain cities or seasons?

If the answer is no for a key city, don’t immediately throw money at the problem. First, look at the context:

  • Are you forcing travelers into peak seasons or premium neighborhoods?
  • Could you steer them to corporate rates or preferred hotels that fit the per diem?
  • Is this a rare exception where you should allow actual expense reimbursement instead of per diem?

Even the Federal Travel Regulation allows actual expense reimbursement when per diem is insufficient under specific conditions. Your policy can mirror that logic: per diem is the default, but there’s a clear path for exceptions when the numbers just don’t work.

5. Design the rules that make or break fairness (not just the dollar amount)

Two companies can use the same GSA rates and still create totally different employee experiences. The difference is in the rules around the rates, not just the dollar figure.

Woman counting cash with a calculator at a desk, managing finances.

First and last day: the 75% rule

Federal rules typically pay 75% of M&IE on the first and last travel days. It makes sense — you’re not eating three full meals on a half‑day travel schedule.

You can copy this rule or tweak it, but keep it clear and consistent. A simple approach:

  • Pay 75% of M&IE on departure and return days.
  • Pay full M&IE on full work days at the destination.

Provided meals: what actually reduces per diem?

This is where confusion (and resentment) often starts. Federal guidance is surprisingly specific, and it’s worth echoing in your corporate travel per diem policy:

  • Reduce M&IE when meals are provided by the employer or included in a registration fee.
  • Do not reduce for meals from common carriers (e.g., airline meals) or complimentary hotel breakfasts.

Because M&IE is broken down by meal, you can deduct the appropriate portion when a meal is provided. For example, if dinner is provided, you remove the dinner component from that day’s per diem. Spell this out so no one is guessing.

Incidentals: keep the definition tight

Incidentals are not a catch‑all for every small purchase. They’re usually limited to things like:

  • Tips to hotel staff and porters.
  • Small service fees related to lodging.

Restaurant tips are part of the meal cost, not incidentals. Make that explicit in your policy so you’re not debating $5 tips on expense reports.

Hybrid models: per diem for meals, actuals for lodging

Many companies quietly adopt a hybrid approach because it balances fairness, control, and admin effort:

  • Meals & incidentals: Per diem based on GSA M&IE, with the 75% rule and meal deductions.
  • Lodging: Actual expenses reimbursed up to the GSA lodging cap (or a company cap), with receipts.

This way, you avoid overpaying for hotels in cheap markets and underfunding in expensive ones, while still giving employees flexibility on meals. It’s a practical middle ground when you’re refining per diem allowance fairness.

6. Keep it compliant: tax rules, one-year limits, and documentation

Even the fairest per diem can backfire if it’s not compliant. The IRS doesn’t care how elegant your policy looks; it cares whether you followed the rules.

Key points to keep in mind when you’re figuring out how to calculate corporate per diem and keep it non‑taxable:

  • Per diem is non-taxable only if:
    • The per diem does not exceed federal rates (GSA/IRS tables or high–low limits).
    • The employee provides a timely expense report (often within 60 days) with dates, locations, and business purpose.
    • The trip is temporary — generally under one year at a single location.
  • Excess per diem above federal limits is usually taxable wages.
  • Trips of a year or more at one location can turn the site into a tax home, making per diem taxable.

On top of that, the FLSA doesn’t explicitly require travel reimbursement, but if you don’t cover reasonable travel costs and an employee’s effective pay drops below minimum wage or affects overtime, you may have a problem.

To stay on the safe side:

  • Align rates with GSA/IRS tables or clearly documented high–low limits.
  • Require simple but consistent trip logs (time, place, business purpose).
  • Keep digital records for 3–7 years, depending on your risk tolerance and industry.

When you’re updating corporate per diem rates, treat compliance as a design constraint, not an afterthought.

7. Automate the boring parts so you can focus on fairness

All of this is painful if you’re doing it in spreadsheets and email. That’s usually when companies either oversimplify (one flat rate) or overcomplicate (manual GSA lookups for every trip).

Business Travel at its smartest

Modern travel and expense tools can handle the repetitive work for you:

  • Pull current per diem rates by city and date automatically.
  • Apply your 75% rules and meal deductions without manual math.
  • Handle multi‑city trips, currency conversion, and company caps.
  • Generate clean reports for finance, HR, and audits.

If you’re big enough that manual per diem tracking feels painful, you’re big enough that bad per diem design is expensive. Automation frees you up to focus on the strategic questions: Are our rates fair? Are we competitive? Are we sending the right signals about how we treat travelers?

8. A practical blueprint you can implement this quarter

If you needed to roll out a more fair, city‑sensitive per diem policy this quarter, here’s a straightforward blueprint you could follow.

  1. Pick your model:
    • Low travel volume → flat or high–low model.
    • High travel volume, many cities → full GSA city‑based model.
  2. Anchor to GSA/IRS: Use GSA M&IE as your default; use GSA lodging as a cap or as a lodging per diem.
  3. Define rules clearly:
    • 75% M&IE on first and last day.
    • Meal deduction logic when meals are provided.
    • What counts as incidentals (and what doesn’t).
  4. Run a reality check on 5–10 key cities to be sure travelers can actually live with the numbers.
  5. Document compliance: Tie your policy to IRS/GSA guidance, set expense report deadlines, and note the one‑year rule.
  6. Automate where possible so city lookups, proration, and adjusting per diem for high cost cities don’t become a daily headache.

In the end, a good per diem policy doesn’t try to be perfect. It aims to be predictable, explainable, and fair enough that employees trust it and finance can budget around it. When your travelers stop saying, This per diem makes no sense in this city, you’ll know you’re close.