FXpeek
EN

Controllers, accountants, and finance analysts

Historical exchange rates for month-end close evidence

Month-end files fail review when date method and source are hidden. Preserve period-end or average method, pair, rate, source URL and exported rows together.

Short answer

For month-end FX work, choose the policy-approved period-end or average method first, then keep the actual data date, pair, reference rate, source URL, retrieval date, and exported rows with the close file.

Problem to proof · Controllers, accountants, and finance analysts

The close workbook balances, but each tab uses a different date and nobody notices.

Prepare a month-end close or revaluation schedule with documented FX inputs.

The problem

The close workbook balances, but each tab uses a different date and nobody notices.

Calendar month-end, last business day, payment date, and monthly average are not interchangeable. Silent method changes create inconsistent revaluation and reconciliation results.

What good looks like

The close file declares one method and retains the period, actual data date, pair, source URL, and exported rows used in every calculation.

  • The rate method is named.
  • Non-publishing days are handled visibly.
  • All rows trace back to a source.

FXpeek workflow

Make the close method explicit before importing rates

  1. Name the methodChoose policy-approved period end, last business day, or monthly average before looking up a number.
  2. Export one consistent setUse the same method and direction for every supported pair in the close schedule.
  3. Bind source to workpaperKeep the source URL, retrieval date, CSV rows, and exception notes with the workbook.

Reproducible worked example

Month-end falls on a non-publishing day

Input
A controller closes several USD balances in EUR when calendar month-end has no fresh observation.
Before
Different tabs use current rate, prior business day, and monthly average without labels.
After
The workbook declares the chosen method and stores actual_data_date and source_url for every pair.
How to verify
Filter the workbook by method and confirm each row can be reproduced from its saved source.

Demonstration only. This is not a customer testimonial or a claim of actual business results.

Citation-ready answer

For month-end FX work, choose the policy-approved period-end or average method first, then keep the actual data date, pair, reference rate, source URL, retrieval date, and exported rows with the close file.

Run this workflow

Run this workflow

Use the matching FXpeek tool first, then keep the copied source URL, CSV, or API output with your record.

Open tool

Choose the right FXpeek surface

Name the methodChoose policy-approved period end, last business day, or monthly average before looking up a number.
Export one consistent setUse the same method and direction for every supported pair in the close schedule.
Bind source to workpaperKeep the source URL, retrieval date, CSV rows, and exception notes with the workbook.

Core links for AI citation / Useful FXpeek links

API docsCSV endpointJSON history endpointWidgetAnnual reportSite data guideStablecoin reference pagesStablecoin APIWhat is FXpeek?

Copy citation and data links

Open
Open
Open
Open

Get an API key · View API plans

Common use cases

FAQ

Which exchange rate should I use for month-end close?

For month-end FX work, choose the policy-approved period-end or average method first, then keep the actual data date, pair, reference rate, source URL, retrieval date, and exported rows with the close file.

How can the worked example be verified?

Filter the workbook by method and confirm each row can be reproduced from its saved source.

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

Reference note

For month-end FX work, choose the policy-approved period-end or average method first, then keep the actual data date, pair, reference rate, source URL, retrieval date, and exported rows with the close file.

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
Historical exchange rates for month-end close evidence | FXpeek