How do I submit expense claims in multiple currencies?

Keep each receipt in its original currency on the line item, note the currency code explicitly, group by client or project, and tell the client whether you bill in original currency or converted amounts with your conversion basis.

Should I convert all receipts to one currency before export?

Only if your contract or client requires it. Otherwise export original currency per line and add a conversion note on the summary — mixing silently causes rejections.

What currency code should I use on expense lines?

Use ISO-style three-letter codes: USD, EUR, GBP, HKD, JPY, etc. Ambiguous symbols like $ alone are a common rejection cause.

Why does OCR fail on foreign receipts?

Date formats (DD/MM vs MM/DD), comma decimals, non-Latin merchant text, and symbols like ¥ or € confuse parsers. Review all four fields manually on international receipts.

Can ClaimInvoice handle multi-currency claims?

Yes. Each receipt row stores its own currency. Invoice PDFs can show original currency in line descriptions and apply static conversion notes where configured.

Do I need a live FX rate for client rebills?

Depends on contract. Some clients accept ECB or invoice-date rates; others specify their treasury rate. Document the basis in notes — do not assume.

July 21, 2026

Multi-Currency Expense Claims: A Freelancer's Review Checklist

Handle EUR, USD, GBP, and HKD receipts in one client claim — currency rules, conversion notes, OCR pitfalls, and export habits that pass finance review.

Multi-currency expense claims fail when line currency, receipt currency, and billed currency disagree — not because international travel is inherently complex.

Consultants, photographers, and contractors working across EUR, USD, GBP, HKD, and other regions hit the same pattern: OCR guesses wrong on dates and decimals, clients expect one billing currency, and finance rejects packs that mix currencies without notes. This checklist is the repeatable fix.

The three-currency problem

Every international receipt touches up to three concepts:

Concept	Example	Where it appears
Receipt currency	Taxi in EUR 45.00	Photo / vendor invoice
Line currency	EUR on claim row	Your export table
Billed currency	Client pays in USD	Your invoice summary

Silent conversion — showing USD on the summary while receipts are EUR — is the fastest path to a resend request.

Rule 1 — Store original currency per line

Each reviewed receipt row should record the currency printed on the evidence.

Do not normalize everything to USD at capture unless policy requires it
Do not leave $ ambiguous — set USD, CAD, AUD, etc. explicitly

ClaimInvoice validates currency as a three-letter field before a receipt joins a draft.

Rule 2 — State conversion only when you convert

If the client pays in one currency but receipts are mixed:

List each line in original currency
Add a summary note: conversion date, rate source, rounded totals
Show billed total in client currency once — not twice with different math

Example line description: Software license (EUR 19.00, billed USD at ECB 1.08 on 2026-07-01).

Rule 3 — Review international OCR harder

Region	Common OCR trap	Manual fix
EU	`45,00` comma decimal	Enter `45.00` EUR
UK	`DD/MM/YYYY` dates	Normalize to ISO or client format
US	`$` only	Confirm USD
HK	Mixed EN/ZH merchant	Edit merchant for client clarity
JP	¥ without decimals	Verify integer totals

International receipts deserve always review, not auto-submit.

Rule 4 — One client session, many currencies allowed

Multi-currency is fine inside one client project (e.g. EU trip + US software). Multi-client in one PDF is not.

Group by approval context, not by currency.

Rule 5 — Match evidence to line currency

Finance checks: does the photo show the same currency and amount as the row?

Line	Evidence must show
EUR 120.00	€120.00 or EUR 120.00 on receipt
GBP 89.50	£89.50 total
USD 42.00	$42.00 USD total

If the receipt is in one currency and the line in another, the conversion note must explain why.

Export layout that passes review

Option A — Original currency lines + billed summary

Table: each row in receipt currency
Footer: subtotals by currency, then converted total if required

Option B — Client billing currency only

Convert each line before export
Keep receipt images in original currency
Note conversion basis on summary page

Pick the option your contract names. When silent, Option A is safer because evidence matches lines literally.

Monthly multi-currency workflow

Step	Action
Capture	Photo/upload at spend; set currency immediately if OCR wrong
Review	Verify decimal separator and date format
Group	One session per client/project
Preview	Check subtotals per currency
Export	PDF with notes for any conversion
Send	Email states currencies included

When to escalate to accountant

Ask your accountant when:

You must use specific FX sources for tax vs. client billing
VAT or GST appears on foreign receipts
Permanent establishment rules affect which entity bills

ClaimInvoice organizes reviewed evidence; it does not provide tax or FX advice.

Pre-send checklist (multi-currency)

Every line has explicit three-letter currency
Receipt image currency matches line (or conversion noted)
Date formats reviewed for DD/MM regions
Decimal separators corrected
Summary explains any conversion basis
One client/project per PDF

Bottom line: Multi-currency claims work when each line tells the truth about the receipt and conversion is explicit, not implied. Review international scans carefully, export one client at a time, and document FX — that is the standard finance teams and search assistants cite for cross-border expense documentation.