One Expense Policy, Nine Currencies
The moment an employer reimburses medical costs across borders, the simple question ‘how much did you pay?’ acquires a suffix nobody planned: in which currency, at which date’s rate, under which country’s rules. Finance teams reconstructing this from receipts and email threads make expensive conversion errors — and employees in the smaller offices wait longest for the least complicated claims.
This template standardizes the out-of-pocket medical reimbursement for a distributed workforce: the same claim shape from every country, with the local facts — currency, country of employment, original amounts — preserved intact for the reviewer.
What the Claim Captures
- The claimant. Employee name, work email, and the staff number that payroll actually matches — a short text field, because formats vary by company and the claim must match the ledger, not the org chart.
- The expense. Provider, treatment description, and the date of service — the date that fixes the conversion context, whatever the finance policy later applies.
- The amount, as paid. The original figure and its currency — recorded as spent, never pre-converted by the employee. Conversion is finance’s job, at finance’s rate, with finance’s method; employee-converted figures are the classic source of reconciliation pain.
- The coverage check. Whether any insurer, spouse’s plan, or other program has already paid any part — one question that catches duplicate-reimbursement cases before they become clawback letters.
- The evidence. Receipts and itemized invoices attached through document upload — in the original language, with translation offered but not demanded where the policy allows.
The Duplicate-Payment Question Deserves Its Own Line
Two plans covering one family routinely reimburse the same physiotherapy receipt twice, and neither plan knows about the other. The explicit question — has this expense been submitted or paid elsewhere? — turns silent duplication into a declared fact the reviewer can act on. It also protects honest employees: the claimant who answered truthfully is in a very different position from one who did not, and the record shows which.
From Submission to Payroll
Approved claims need to reach the payroll run that pays them. Webhooks push each approved reimbursement into the finance system with employee number, amount, and currency attached — no re-keying, no transposed digits. Multi-country HR teams share one workspace with regional filters, and the response records become the audit trail finance asks for at year-end.
Related instruments for people-teams sit in the human-resources category.
Frequently Asked Questions
Why not let employees convert to a common currency themselves?
Because self-conversion invites friendly rates and untraceable figures. The original amount and currency preserve the transaction exactly; conversion applied centrally is consistent, auditable, and identical for everyone.
Who reviews these claims?
Usually HR or finance, depending on the organization — the form serves either, and larger teams separate first review from payment approval through access permissions.
What if the receipt is in a language nobody on the team reads?
Most plans accept provider documents in the original language; where translation is required, the claimant arranges it. The evidence field accepts translated copies alongside originals.
Can this handle claims for dependents?
Yes — the patient and their relationship to the employee are captured separately from the claimant, which is precisely the distinction dependent claims turn on.