Do employees need receipts under a per diem?

For the items the per diem covers, no — that is the point. The employee usually only needs proof that the travel happened. Lodging handled as actual cost still needs a receipt, but meals and incidentals on a per diem do not.

Is a per diem taxable?

A per diem at or below a recognised reference rate, paid for genuine business travel, is generally not taxable. Amounts above the reference rate can be treated as taxable income, so calibrate to a credible schedule and check your country's rules.

What is an expense policy?

An expense policy is a written set of rules defining which work-related expenses a company will reimburse, the limits per category, the receipt and approval requirements, and the country-specific compliance addenda. It is the contract between the employee and finance.

Who owns the expense policy?

The CFO owns the document, with sign-off from the General Counsel for legal language and the People / HR lead for the employee-facing clauses. Local controllers own the country addenda. Sales-ops, IT and Travel are consulted but do not approve.

How long should an expense policy be?

Eight to twelve pages for the master policy, plus a one-page addendum per country. Anything longer goes unread; anything shorter cannot cover client meals, travel, cards, exceptions and country compliance with the required specificity.

How is an expense policy enforced?

Encode the rules in your expense platform (policy-as-code), surface the relevant clause inline at submission, audit 100% of items above $1,000 and statistically below, and publish a monthly violation-rate dashboard. Enforcement that lives only on PDF is not enforced.

How often should an expense policy be reviewed?

Once a year as a hard minimum, plus an out-of-cycle update whenever the IRS, HMRC, SAT, DIAN or Receita Federal changes a relevant deduction rule, mileage rate or per-diem table.

Per Diem

A per diem is a fixed daily allowance a company pays an employee to cover travel costs — typically meals and incidentals, sometimes lodging — without itemising receipts for each item. The per diem trades a little precision for a lot of simplicity: the employee knows their daily budget before they leave, and finance processes a flat, predictable number. This pillar explains what a per diem covers, how to set the rate so it is fair and defensible, and where the per-diem model fits in a travel policy.

What a per diem covers

A per diem most commonly covers meals and incidental expenses — tips, local transport, small sundries — at a single daily figure the employee can spend without collecting receipts for each item. Some programs extend the per diem to lodging, but because hotel prices vary so much, lodging is more often handled as a capped actual cost while meals and incidentals run on the per diem. The defining feature is that the per diem is paid as a flat allowance: the employee is not reimbursed for what they spent, they are given an amount for the day and keep the difference if they spend less.

Setting a fair per-diem rate

A per-diem rate has to be calibrated to the destination, because a daily figure that is generous in one city is inadequate in another. Anchor your rates to a recognised reference — government schedules like GSA or the equivalent, or surveyed local costs — and band them by city cost tier rather than setting one global number. A rate set too low quietly pushes employees to spend their own money or pad other categories; set too high it becomes disguised compensation. The test is whether an auditor can reproduce your per-diem rate from a credible cost source.

When the per-diem model is the right choice

The per-diem model shines when travel is frequent, costs are predictable, and the company values speed and a small audit surface over granular spend data. It removes the single most tedious part of travel expense — collecting and reviewing meal receipts — and gives employees clarity that improves the travel experience. It fits less well where finance needs precise per-city cost analytics, or where travel is rare enough that the effort of maintaining rate tables outweighs the saved receipt-handling. For most teams, a per diem on meals and incidentals is the low-friction default.

Per diem in the wider travel policy

A per diem is one clause inside the travel section of the expense policy, and it has to agree with the others. The policy should state the per-diem rates by destination tier, whether the per diem covers travel days at a partial rate, how it interacts with company-provided meals (a conference lunch should reduce that day's per diem), and the documentation — usually just proof of travel, since the whole point is no item-level receipts. Keeping the per-diem clause explicit and consistent is what prevents disputes over what a given day's allowance was supposed to include.

Choosing a per-diem rate that is fair and audit-proof

A per-diem rate works when it is generous enough that employees do not lose money on the road and disciplined enough that finance is not overpaying. Anchor each rate to a published reference — a government schedule or a recognised cost-of-living index for the destination — so the number has a defensible source rather than a round figure someone guessed. Split the allowance into meals and incidentals so partial travel days prorate cleanly, and state explicitly whether lodging is inside the per-diem or reimbursed on actuals. Decide upfront how the first and last days of a trip are handled, since that single rule causes most per-diem disputes. Revisit the rates at least once a year against inflation and FX moves. A per-diem that is documented, sourced, and reviewed removes receipts from the equation without inviting an auditor's frown.

FAQ

Do employees need receipts under a per diem?: For the items the per diem covers, no — that is the point. The employee usually only needs proof that the travel happened. Lodging handled as actual cost still needs a receipt, but meals and incidentals on a per diem do not.
Is a per diem taxable?: A per diem at or below a recognised reference rate, paid for genuine business travel, is generally not taxable. Amounts above the reference rate can be treated as taxable income, so calibrate to a credible schedule and check your country's rules.

Why this expense-policy library exists

Every page on this site is built from the same opinionated framework: an explicit per-category cap, a named approver chain, a documented exception path, and a review cadence anchored to the controller's close calendar. We publish the framework openly so finance leaders, controllers, and operations teams can adopt it without a vendor lock-in or a six-figure consulting engagement. The expense-policy generator turns the framework into a finished document in three languages, with country-specific tax compliance baked in from the first draft.

Behind every URL is a typed registry — landing pages, glossary entries, calculators, country pillars, and learning hubs are all generated from the same data layer that powers the policy generator itself. That means the per-diem rate you see in the calculator, the GSA-aligned mileage benchmark in the rates table, and the threshold language in the generated PDF are all sourced from one canonical place and refreshed on the same cadence. There is no drift between what we write here and what the generator produces.

Trust signals are non-negotiable: every editorial page lists the reviewer, the review date, and the underlying source — IRS publication, HMRC manual, SAT criterio, Receita Federal IN, or peer-reviewed research. When a regulator updates a per-diem schedule, the change propagates to the calculator, the country pillar, the glossary entry, and the policy template in the same release. That is the bar we hold ourselves to, and the reason controllers across the US, UK, Mexico, Brazil, and the broader LATAM region rely on this library when they re-issue their expense policy each fiscal year.

The editorial program is organized into four parallel surfaces. The industry vertical (SaaS, FinTech, Manufacturing, Retail, Hospitality, Agency, Healthcare, Nonprofit) gives every reader a starting template tuned to the cost categories, regulators, and audit findings that dominate their sector. The country pillar (United States, United Kingdom, Mexico, Brazil, Colombia, Argentina, Chile, Peru, Spain, and Portugal) layers on the local tax-compliance overlay — CFDI, NF-e, DIAN, AFIP, SII, IRS Form 8027, HMRC P11D — so the generated policy is enforceable in every jurisdiction where you operate. The persona track (CFO, controller, finance manager, head of operations, founder) reframes the same building blocks around the buyer's specific quarterly priorities. Finally, the calculator suite (per-diem, mileage, VAT-recovery, T&E benchmark, carbon, tax-id validator) gives finance teams the specific numerical inputs they need to set thresholds, justify caps, and back-test the policy against actual spend before it ships.

Cross-linking between these surfaces is deliberate, not accidental. A SaaS reader landing on the industry page is one click from the country overlay that matches their primary entity, the calculator that backs the per-diem cap they are about to commit to in writing, and the glossary entry that defines whatever IRS or SAT term they have not seen before. We measure the ratio of internal links per page weekly and refuse to publish a new landing without at least four anchors into the topical hubs. That single discipline is why a CFO can land on any page in this library and reach the policy generator in under three clicks — no matter which surface their search engine routed them through.