International Per Diem
An international per diem is the daily allowance for travel outside the company's home country, where currency, country cost differences and local tax rules all come into play. International travel is lower in volume than domestic but higher in cost and complexity per trip, so the international per diem needs more care even though it fires less often. This page covers how to source international rates, how to handle currency, and the compliance wrinkles that distinguish an international per diem from a domestic one.
People also ask
- 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.
- Daily rate for travel outside the home country
- Sourced from country/city cost references
- Requires a clear currency-conversion rule
- Higher cost and compliance load per trip than domestic
Sourcing international per-diem rates
An international per diem cannot be guessed; it has to be sourced per destination country and often per city. Anchor rates to a recognised international schedule — government foreign per-diem tables or a reputable cost-of-living dataset — so each country's figure is defensible. Because you cannot maintain a bespoke rate for every city on earth, group destinations into cost bands and assign the band rate, with a mechanism to override for genuinely exceptional cities. The discipline is the same as domestic, but the references are international and the spread between the cheapest and most expensive destination is far wider.
Handling currency in an international per diem
Currency is the feature that most distinguishes an international per diem from a domestic one. The policy must state which currency the per diem is denominated in, the exchange-rate source, and the date used for conversion — booking date, travel date, or reimbursement date — because the rate moves and ambiguity creates disputes. Many programs pay the international per diem in the employee's home currency at a published rate to remove FX risk from the traveller. Whatever the choice, writing the currency rule into the travel policy is what keeps an international per diem clean and reproducible at the close.
Compliance wrinkles unique to international travel
International travel layers on compliance that domestic does not. Some countries treat foreign per diems differently for tax, immigration paperwork can affect what counts as a business day, and recoverable foreign VAT depends on documentation that varies by jurisdiction. An international per diem that ignores these treats every country as if it were home, which is where exposure builds. The travel policy should flag the highest-traffic destinations with any special treatment and route genuinely unusual trips to a finance review, rather than assuming the standard international per diem covers every border.
Balancing fairness and simplicity internationally
The international per diem faces the same fairness-versus-simplicity tension as domestic, but stretched wider because destinations range from low-cost to extremely expensive cities. Too few bands and the rate is unfair at the extremes; too many and the table becomes unmaintainable. The pragmatic answer is a moderate set of cost bands plus an exception path for outliers, all encoded in the platform so the right international per diem applies automatically from the destination country. Reviewing the bands annually against fresh international cost data keeps the rates credible as exchange rates and local costs drift.
Handling currency, lodging, and tax on international trips
International per-diems add three variables a domestic schedule never has to face: currency, wildly different lodging markets, and cross-border tax treatment. Set each destination rate in a single reference currency and convert at a documented FX rate on the trip date, so an employee is never penalised by a swing in exchange rates between booking and reimbursement. Decide whether lodging sits inside the per-diem or is reimbursed on actuals — for international travel, actual lodging plus a fixed meals-and-incidentals per-diem is usually cleaner, because hotel prices vary far more than meal costs. Check the tax rules in both the home and host country, since some jurisdictions treat per-diems above a published ceiling as taxable income. Capture the destination, the dates, and the reference rate on every claim so the whole calculation can be reproduced by an auditor years later.
FAQ
- How is an international per diem different from a domestic one?
- It adds currency handling, country-by-country cost references, and jurisdiction-specific tax and VAT treatment. It is lower volume but higher cost and complexity per trip, so it needs careful sourcing even though it fires less often.
- Which exchange rate should an international per diem use?
- Pick one published source and one date rule — booking, travel, or reimbursement date — and state it in the policy. Many teams pay in the employee's home currency at a published rate to remove FX risk from the traveller.
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.