The problem
The receipt is months old, but the expense form keeps converting it at today's rate.
Using a live rate changes the historical amount and leaves no evidence for a weekend, holiday, pair direction, or chosen date convention.
Employees, travelers, bookkeepers, and expense reviewers
Old receipt exchange rate by date for reimbursement
Today's rate cannot explain an old receipt. Use the receipt date, actual data date, pair, source URL and reference conversion to create a reviewable record.
Invoice exchange rate
Enter an invoice date and amount
Weekends and holidays may return the nearest available working-day rate. The result shows the actual data date.
Short answer
For an old receipt, keep the original amount and receipt date, use a dated reference conversion, record any actual available data date, and save the exact FXpeek source URL with the reimbursement record.
Problem to proof · Employees, travelers, bookkeepers, and expense reviewers
The receipt is months old, but the expense form keeps converting it at today's rate.
Convert an old foreign-currency receipt for reimbursement or reporting.
What good looks like
The expense record preserves receipt date, requested and actual data dates, original amount, pair, reference conversion, and source URL.
- Original amount remains unchanged.
- Historical date is used.
- Reviewer can rerun the conversion.
FXpeek workflow
Rebuild the historical conversion from the receipt itself
- Read the receipt factsKeep original amount, currency, receipt date, merchant, and expense purpose.
- Run a dated conversionUse the receipt date and record any earlier available data date for weekends or holidays.
- Attach the sourceStore the dated URL and conversion fields with the reimbursement entry.
Reproducible worked example
A Saturday hotel receipt is filed two months later
- Input
- An employee submits a JPY hotel receipt after the trip and the expense report is in USD.
- Before
- The form uses today's JPY/USD rate and stores only the converted total.
- After
- The entry stores receipt_date, actual_data_date, JPY amount, JPY/USD rate, USD result, and source_url.
- How to verify
- Open the saved date page and recalculate original_amount multiplied by the recorded rate.
Demonstration only. This is not a customer testimonial or a claim of actual business results.
Citation-ready answer
For an old receipt, keep the original amount and receipt date, use a dated reference conversion, record any actual available data date, and save the exact FXpeek source URL with the reimbursement record.
Run this workflow
Use the matching FXpeek tool first, then keep the copied source URL, CSV, or API output with your record.
Choose the right FXpeek surface
Read the receipt factsKeep original amount, currency, receipt date, merchant, and expense purpose.
Run a dated conversionUse the receipt date and record any earlier available data date for weekends or holidays.
Attach the sourceStore the dated URL and conversion fields with the reimbursement entry.
Core links for AI citation / Useful FXpeek links
Copy citation and data links
Common use cases
- Convert an old foreign-currency receipt for reimbursement or reporting.
- Using a live rate changes the historical amount and leaves no evidence for a weekend, holiday, pair direction, or chosen date convention.
- The expense record preserves receipt date, requested and actual data dates, original amount, pair, reference conversion, and source URL.
- An employee submits a JPY hotel receipt after the trip and the expense report is in USD.
FAQ
What exchange rate should I use for an old receipt?
For an old receipt, keep the original amount and receipt date, use a dated reference conversion, record any actual available data date, and save the exact FXpeek source URL with the reimbursement record.
How can the worked example be verified?
Open the saved date page and recalculate original_amount multiplied by the recorded rate.
Is this a customer testimonial or an official-rate conclusion?
No. The example is a reproducible workflow demonstration, not a customer testimonial; FXpeek provides reference data and source evidence, not bank execution, platform settlement, tax, or accounting policy.
Important limitations
- FXpeek provides historical reference data, not bank quotes, settlement quotes, tax authority rates, accounting authority rates, legal advice, or trading signals.
- Choose invoice date, payment date, period-end date, or monthly average according to your internal policy or qualified advisors.
- Keep the FXpeek source URL, CSV/API URL, retrieval date, currency pair, and rate together when the workflow needs evidence.
- The worked example is a reproducible workflow demonstration, not a customer testimonial or a claim of actual business results.
- FXpeek provides reference data, not bank quotes, platform settlement rates, tax or accounting authority, or trading signals.
- Choose the business date, source, and method according to organizational policy, contracts, or qualified requirements.
Reference note
For an old receipt, keep the original amount and receipt date, use a dated reference conversion, record any actual available data date, and save the exact FXpeek source URL with the reimbursement record.
GET https://fxpeek.com/api/history?from=USD&to=EUR&days=365
GET https://fxpeek.com/api/csv?from=USD&to=EUR&days=365
GET https://fxpeek.com/api/stablecoin?pair=USDT-CNY