Policy · July 31, 2026

Travel and expense policy: what to include, a T and E policy outline, and 2026 best practices

A travel and expense policy is the written document that defines which business travel costs a company will pay for, what the limits are, who approves them, what documentation employees must submit, and how fast they get their money back. Its job is to make spending decisions predictable before the money is spent, instead of arguing about them after the trip.

Most policies fail for the same reason: they are written as a legal document rather than as a set of answers to the questions an employee has while standing at a hotel desk at 11pm. Below is the section-by-section outline that works, the limit-setting decisions that are actually contested, the US tax change that forces a rewrite this year, and the honest note about what a policy does not do on its own.

What should be included in a travel and expense policy?

A complete policy covers eight things: scope and who it applies to, booking rules and approved channels, category limits for airfare, lodging, ground transport and meals, the approval chain and thresholds, documentation and receipt requirements, non-reimbursable expenses stated explicitly, the reimbursement timeline, and the consequences of not following it. Anything less and the gaps get filled by individual judgment, which is how two people on the same trip end up expensing very different amounts and both believe they were within policy.

The eight sections, and what each one has to answer

Write each section to close a specific question. If a section does not resolve a decision somebody will actually face, cut it.

Are employer-provided meals still deductible in 2026?

Not the convenience-of-the-employer ones. Under the One Big Beautiful Bill Act, Section 274(o) disallows 100 percent of the cost of employer-provided meals and company cafeteria meals for tax years beginning after December 31, 2025, up from a 50 percent limit before. Business travel meals and client meals generally remain 50 percent deductible. Confirm your own treatment with your tax advisor.

This is the single most concrete reason to reopen a policy written before 2026. A lot of US companies have one meals category that covers a catered team lunch in the office, a salesperson's dinner on the road, and a client meal, because until this year the tax treatment of the first two was the same 50 percent. It no longer is. If your expense categories cannot distinguish an on-premises convenience meal from a travel meal, your accounting team is now reconstructing that split by hand at year end, from memory and merchant names.

The fix is a policy change, not an accounting one: split the meals category into travel meals, client and business-development meals, and employer-provided or office meals, and require employees to pick one at submission. Take the thirty seconds of friction now rather than the reconstruction project in January. There are limited exceptions in the statute, including for restaurants selling meals to customers and for certain fishing vessels and processing facilities, which is a strong sign this is a rule you want your tax advisor to apply to your specific facts rather than a generic template.

What is a good per diem or meal limit for business travel?

Most US companies either adopt the GSA per diem rates by destination, which removes the argument entirely and is defensible in an audit, or set a flat daily cap that varies by city tier. Neither is more correct. Per diem cuts receipt processing and disputes; actual-cost caps track real spending more closely and suit companies with irregular travel.

The choice is really about where you want the administrative load. Per diem pushes it to the front: you set rates once, publish them, and stop reviewing meal receipts. Actual cost pushes it to the back: every trip generates receipts somebody has to check against a cap. A company sending the same twenty people to the same five cities gets more from per diem. A company where travel is rare and lumpy usually finds per diem overpays on short trips and underpays on expensive ones.

For the other categories, three rules do most of the work. Economy is the default for air travel, with any upgrade requiring documented prior approval and a stated business reason, usually flight duration. Hotel caps are set per city rather than company-wide, because a single national number is simultaneously generous in one market and unusable in another. Ground transport gets a preference order rather than a limit, since telling someone their airport transfer must cost under a fixed amount produces worse decisions than telling them to take the train where it exists.

Travel and expense policy best practices that hold up

A few things reliably separate a policy people follow from one that lives in a drive folder.

Write it for the traveler, not the auditor. The person reading it is standing somewhere unfamiliar with a decision to make. If they cannot find the hotel cap in under thirty seconds, they will guess. Lead each section with the number, then the reasoning, not the other way around.

Set thresholds against your real spend distribution. An approval threshold that catches 60 percent of transactions is not a control, it is a queue. Pull last year's expense data, find the amount above which items are genuinely worth a second look, and set the line there. The same logic applies to setting a corporate card spending limit: a limit nobody ever hits is decoration, and one everybody hits is a bottleneck.

Include duty of care, not just cost. A policy that only talks about money misses the part employees care about most: what happens if a flight is cancelled, who to call in an emergency, whether they can pay for a safer ride at night. Teams that add this get better compliance on the cost sections too, because the document stops reading as purely adversarial.

Say what happens when someone breaks it. Most policies stop at the rules. A first-time overspend and a pattern of personal charges are different things and should be handled differently, and writing that down protects the employee as much as the company.

Review it annually, and after any rule change. The 2026 meal treatment is this year's forcing function; GSA per diem rates move every federal fiscal year. If your company is tracking a broader set of regulatory obligations and the controls that map to them, the T and E policy review belongs on that same calendar rather than in someone's head.

What are T and E expenses?

T and E stands for travel and entertainment, sometimes travel and expense. It covers costs employees incur doing business away from the office: airfare, rail, hotels, rental cars, rideshare and taxis, parking and tolls, meals while traveling, client meals, baggage fees, and work-related incidentals such as in-flight wifi or laundry on longer trips.

Worth separating from two things it gets confused with. A T and E policy is not a corporate card policy, which governs how a specific payment instrument is used regardless of whether the spend is travel. And it is not a procurement policy, which governs buying software, services, and equipment. Companies that merge all three into one document end up with something too long for anyone to read, and the travel sections get lost in it.

How often should a travel and expense policy be reviewed?

Once a year at minimum, and immediately whenever tax rules, per diem rates, or your travel patterns change materially. The 2026 meal deduction change is a good example: a policy written in 2024 that lumps all meals into one category no longer maps to how those costs are treated, so the categories themselves have to be re-cut.

The honest limit: a policy is a rule, not a control

Here is the part most guides skip. A travel and expense policy tells people what they should do. It does not stop them, and it does not tell you when they did something else. Those are three different jobs, and only the first one is done by a document.

In a normal reimbursement flow, the sequence is: the employee spends, the employee submits, a manager approves, finance reviews, the ledger closes. A breach becomes visible somewhere around step three, which is usually two to six weeks after the money left. By then the flight is flown, the hotel is paid, and the only available response is a conversation. That is fine for the occasional overspend and useless for a pattern, because a pattern needs several cycles before anyone notices it is one.

A company card shortens the middle of that sequence but not the front of it. The charge still happens first. The difference between a card charge and a reimbursement is who floats the money, which is a real difference, covered in company card versus reimbursement, but it does not change when finance finds out.

Closing that gap needs something watching the transactions rather than the reports. Spendnotify reads the corporate cards and accounts you already hold, checks each transaction against the budgets and category rules you set, and alerts a named person by email, SMS, or Slack within moments of the charge. So a hotel booked at twice the city cap surfaces the day it is booked, not at close.

The plain limitation, stated the way we would want it stated to us: it cannot decline a transaction. It never moves, holds, or blocks money. It tells a human quickly enough that cancelling a refundable booking or calling the vendor is still an option, which is the window a monthly report does not give you. If you are evaluating platforms for the wider job, the SAP Concur alternatives comparison covers who does travel, expense, and control, and which ones make you switch cards to get any of it.

Where to start if you are writing one this week

Do not start from a template. Start from last year's expense data. Export twelve months, sort by amount, and read the top hundred lines and a random hundred from the middle. Within an hour you will know which categories generate real money, which generate real arguments, and which limits your current unwritten norms already imply. Write those down first, because a policy that codifies what good people already do gets adopted, and one that imposes unfamiliar numbers gets negotiated line by line.

Then split the meals category for 2026, set your approval threshold from the actual distribution rather than a round number, publish it somewhere findable on a phone, and put the review date in a calendar. Pair it with real-time budget alerts on the cards the travel is booked with, and you have both halves: the rule, and the thing that tells you when the rule was not followed.