The per diem problem: why flat rates don't work anymore

Most companies set a per diem rate once, file it in the policy document, and forget about it. Typically there’s a fixed daily amount for meals and maybe a separate overnight rate - simple to administer, easy to communicate.

The problem is that flat rates are built on assumptions that are no longer true.

The flat rate assumption

Flat per diem rates assume that every destination costs the same, every trip type is equivalent, and every employee has the same needs on the road.

None of those things are true.

A flat £40 daily meal allowance works fine for a team visit to a mid-sized city. It creates problems on a trip to London, or navigating client dinners in Manhattan or Paris.

When the rate is set once for the whole company and never revisited, it gradually detaches from reality. And when employees notice the gap between what the policy says and what things actually cost, they find workarounds — or they quietly absorb the difference out of their own pocket.

Where flat rates break down

The most obvious failure is geography. Cost of living varies enormously across even a single country, let alone across markets. For example, a finance manager travelling between Frankfurt and a small-town German client visit will have a very different daily expense reality than someone attending a conference in Munich. A flat rate either over-compensates one or under-compensates the other.

Multi-city trips make the problem worse. An employee who spends Monday in Amsterdam, Tuesday in London, and Wednesday in Paris is operating in three different cost environments in the same week. A flat rate denominated in one currency, set for one cost level, doesn't reflect that reality at all.

International travel introduces a currency dimension on top of the cost-of-living one. A per diem set in GBP or EUR and applied to a trip to New York or Singapore may not translate meaningfully to what things actually cost — and it almost certainly won't align with the local government benchmark rates that affect tax treatment.

The employee experience problem

When per diem rates are too low, employees don't always push back. Many absorb the difference and say nothing. That might look like compliance, but it's a form of quiet resentment — and it shows up over time in how people feel about travel programmes.

Employees who regularly feel out of pocket on business trips become less willing to travel, less willing to attend events, and less likely to book the most efficient options. The impact is diffuse but real.

The opposite problem is also worth naming. When flat rates are set too high — often by accident, because they were calibrated for a high-cost scenario and applied everywhere — some employees naturally spend up to the limit regardless of what things actually cost. 

A flat daily meal rate becomes a daily meal budget that employees feel entitled to use in full, even on a day when lunch was a £10 sandwich at a train station.

Neither outcome is what finance teams want. Both are products of a rate that doesn't flex with context.

Outdated rates can be a tax compliance issue

Per diem rates aren't just a convenience mechanism — they're also a tax efficiency tool. In most European markets, per diem allowances paid at or below official government benchmark rates are treated as tax-free for employees. This is one of the main reasons companies use per diems rather than receipt-based reimbursement.

The compliance risk cuts both ways. If your per diem rate is set below the official benchmark, you're leaving a tax efficiency on the table. If it's set above without adequate documentation and justification, the excess over the benchmark can become a taxable benefit-in-kind for the employee.

A flat rate that was set years ago — or calibrated for one market and applied globally — is unlikely to sit in the right relationship with the benchmark rates that govern tax treatment in each market your employees operate in. 

A smarter approach to per diems

The alternative to a flat rate isn't complexity for its own sake. It's a structure that reflects how costs actually vary.

Destination-based rates are the most common upgrade. Instead of one number, you maintain a small table: domestic standard, domestic major cities, European travel, international travel. This covers the vast majority of use cases without requiring per-city lookup for every trip.

Trip duration tiering adds another dimension. Government benchmark rates in markets like Germany already distinguish between trips of different lengths — an 8-hour day trip, a full-day trip, and an overnight stay all have different applicable allowances. Aligning your internal rates with this logic both improves accuracy and simplifies tax treatment.

For multi-destination trips, defining a clear rule — for example use the rate for the city where the employee spends the majority of the day, or use the highest applicable rate for the full day — eliminates a common source of ambiguity.

These structures don't require a sophisticated system to design. But they do reward having one to administer, because manual calculation of variable per diems quickly becomes burdensome.

Automating per diems to reduce shadow work

Once you move beyond a single flat rate, someone has to look up the applicable rate for every trip, calculate partial days, handle multi-destination itineraries, and check that the resulting allowance is within the correct tax band for that market.

Done manually, that overhead is significant. Done automatically — with a system like Perk that reads the destination and trip details and applies the right rate without anyone needing to look anything up — it becomes invisible.

When per diem rates are calculated automatically based on where an employee is travelling and how long they'll be there, finance gets accurate allowance data without administrative overhead. Employees get a figure that reflects their actual situation, not a generic number that may or may not cover what things cost on a particular trip.

The flat rate was a reasonable shortcut when travel was simpler. It's become a source of friction, resentment, and quiet compliance risk as travel patterns have grown more complex.