Which Exchange Rate Should Be Used for Cross-Border Reimbursements: Transaction Date, Statement Date, Payroll Rate, or Month-End Rate?

Cross-border reimbursements create a deceptively simple finance question: an employee spends in one currency, but the company reimburses and accounts in another. The exchange-rate policy determines whether the employee is made whole, whether finance can reproduce the calculation, and whether the accounting treatment stays consistent across countries and reporting periods.

For most actual-expense programs, the strongest policy is to separate three concepts that are often mixed together: the rate used to reimburse the employee, the rate used to recognize the expense in the entity's functional currency, and any later rate used to remeasure an outstanding payable. The same rate does not have to serve all three purposes.

Which Exchange Rate Should a Company Use?

A practical hierarchy is: use the employee's actual converted card or bank cost when reliable evidence exists and the policy is designed to make the employee whole; otherwise use an approved transaction-date rate for the original expense. Treat statement date as an evidence or fallback rule, not an automatic replacement for the transaction date. Use payroll rates only when they are a deliberate, documented approximation that local rules permit. Reserve month-end rates primarily for accounting remeasurement and reporting.

That hierarchy is also consistent with the accounting logic in IAS 21, which requires foreign-currency transactions to be initially recognized using the spot exchange rate at the transaction date and foreign-currency monetary items to be translated at the closing rate at period end.

Exchange Rate Options at a Glance

1. Transaction-Date Rate: The Best General Default

The transaction-date method ties the reimbursement calculation to the date on which the employee incurred the business cost. It is conceptually clean because the economic event and the FX conversion use the same date. It also gives finance a consistent rule across cash, bank transfer, mobile wallet, or card purchases when the employee does not provide a reliable home-currency settlement amount.

• Use a defined source. Choose a reputable bank, central bank, treasury feed, ERP rate table, or other approved provider and document the rate type and time zone.
• Preserve the original currency. Keep merchant currency, original amount, transaction date, applied rate, reimbursement currency, and converted amount together.
• Control weekend and holiday logic. Define whether the system uses the most recent available business-day rate or another approved convention.

For U.S. tax purposes, the IRS states that foreign-currency items affecting income tax should be translated using the exchange rate prevailing when the item is received, paid, or accrued, with a rate that properly reflects the income. See the IRS guidance on foreign currency and exchange rates for the current wording.

2. Actual Card or Bank Settlement: Best When Employee Fairness Is the Priority

If an employee used a personal card and the issuer has already converted the purchase into the employee's home currency, the strongest evidence of what the employee actually paid may be the settled transaction amount rather than a public market rate. This can be especially fair when the card network applied its own rate or the issuer charged an FX fee.

The policy should specify which evidence is acceptable: a settled card transaction, bank record, digital-wallet record, or statement line that clearly links to the receipt. It should also state whether foreign transaction fees are reimbursable and how refunds, reversals, tips, hotel deposits, or later adjustments are handled. A statement date itself is less important than the evidence of the actual converted charge.

3. Statement-Date Rate: Useful as Evidence, Weak as a Universal Rule

The statement is useful when it proves the final amount charged to the employee. However, using the statement date as the FX date for every expense can distort reimbursement because the statement may be issued days or weeks after the purchase. The company should distinguish between "use the statement to prove the settled amount" and "use a market rate from the statement date." Those are not the same policy.

A reasonable fallback is to use the statement or settled card amount when the transaction-specific conversion is visible, but revert to the transaction-date rate when the statement does not identify a reliable converted amount. This keeps the rule evidence-based rather than dependent on billing-cycle timing.

4. Payroll Rate: An Operational Simplification, Not a Default Accounting Answer

Some companies reimburse expenses through payroll or maintain a standard payroll FX table. That can be operationally efficient for large populations, but the payroll rate may have been designed for salary conversion, not employee-paid business expenses. A monthly payroll rate can therefore move away from the market rate that applied when the employee spent the money.

Use a payroll rate only when the organization has deliberately approved it for expenses, the method is permitted by local tax and employment rules, the source and effective dates are documented, and finance monitors whether the approximation produces material employee gains or losses. If the rate becomes stale or volatile currencies move sharply, the policy needs an exception or true-up mechanism.

5. Month-End Rate: Mainly for Accounting Close and Remeasurement

Month-end or closing rates solve a different problem. Under IAS 21, foreign-currency monetary items are translated using the closing rate at the end of the reporting period. That makes the month-end rate relevant when an employee payable or another monetary balance remains outstanding at close. It does not mean the employee's original expense should be recalculated using the month-end rate.

This distinction matters because finance may legitimately have two FX effects: the original expense recognized using the transaction-date methodology, and a later exchange difference on an outstanding payable or settlement. A reimbursement system should preserve enough detail to reconcile both instead of overwriting the original rate.

Separate the Reimbursement Rate from the Accounting Rate

A strong global design explicitly separates employee fairness from ledger mechanics. For example, an employee may submit a JPY 30,000 hotel receipt and show that the personal card settled at SGD 271.40. The company can reimburse SGD 271.40 because that is the actual employee cost, while the local entity books the expense using its approved accounting method and records any resulting FX difference according to its ERP and accounting policy.

HMRC likewise notes that business accounts may use exchange rates consistent with generally accepted accounting practice and, depending on the context, may use bank rates or other reputable published rates. See HMRC BIM39515 for the current guidance. The broader lesson for global teams is to document the purpose of each rate rather than forcing one operational rate into every finance use case.

How to Design a Global Exchange-Rate Policy

1. Define the reimbursement objective. Decide whether the policy is primarily designed to make employees whole for their actual converted cost or to apply one standardized corporate rate. State the priority clearly.
2. Choose the rate hierarchy and source. Define the primary method, acceptable evidence, approved FX source, weekend/holiday rule, rounding, time zone, and fallback when a rate is missing.
3. Separate payment and accounting treatment. Document how reimbursement currency, functional currency, ERP posting, employee payable, settlement, and FX differences are handled. Do not let reimbursement logic silently become the accounting policy.
4. Add local exceptions only where necessary. Tax, payroll, labor, exchange-control, and documentation rules can vary by country. Give local finance authority to maintain governed overrides rather than separate undocumented practices.
5. Test and monitor the policy. Pilot common currencies, volatile currencies, weekends, refunds, personal-card FX fees, late submissions, payroll reimbursement, and month-end open payables. Track employee disputes, manual adjustments, FX variance, and review time.

This approach aligns with the same global-governance principle: one documented baseline with controlled local overlays.

How Helios Supports Cross-Border Reimbursement Controls

Helios's public product page does not specify a particular FX-rate hierarchy for cross-border reimbursement, so companies should validate rate-source configuration, transaction-date logic, settlement evidence, multi-currency reimbursement, and ERP FX treatment during a tailored demonstration or pilot. Two capabilities are what actually let a company enforce the rate hierarchy above once it's decided:

1. Configure the policy layer. Automated policy control can enforce company spending rules, which during implementation means configuring which rate method applies to each employee population, expense type, entity, or country, and how exceptions escalate — turning the rate hierarchy from a policy document into something the system actually checks. For example, a claim submitted with a personal-card receipt showing a settled amount could apply the actual-settlement rate, while the same expense category submitted without that evidence would need to fall back to the transaction-date rate instead — the evidence attached, not just the category, is what should decide which rate applies.
2. Preserve the accounting handoff. Helios states that its accounting engine automatically generates journal entries from expense reports. This is the piece worth validating closely for cross-border claims specifically: confirm how original currency, reimbursement currency, applied rate, functional-currency value, and any later FX difference all map into the ERP, since collapsing them into one field would undo the separation this article argues for.

Finance should also fold rate variance and employee-adjustment data into the same governance review used for policy exceptions generally, rather than treating FX monitoring as a separate exercise.

FAQs About Exchange Rates for Cross-Border Reimbursements

Is the transaction-date rate always the right reimbursement rate?

No. It is a strong default, but an employee's documented card or bank settlement may better reflect the actual amount paid.

Should the statement date be used because the card statement is auditable?

Use the statement as evidence of the settled amount, not automatically as the market-rate date for every purchase — those are two different policies that get conflated often.

Can a company use one monthly payroll rate for all expenses?

It can be an operational simplification where local rules permit, but the company should monitor fairness and material FX differences rather than treat it as a permanent default.

A strong cross-border reimbursement policy is reproducible: the employee can see why they received the amount paid, finance can trace the rate source and date, and accounting can reconcile the expense and any later FX movement. Organizations evaluating an enterprise expense platform can explore Helios expense management and test their own currencies, settlement records, policies, approvals, and ERP posting scenarios in a controlled pilot.