FXpeek
EN

Finance analysts, researchers, and reporting teams

Monthly average exchange rate with a defined date

Short answer

A monthly average exchange rate should identify the period, pair direction, included daily observations, missing-date treatment, averaging method, and source URL so the result can be recalculated from the underlying rows.

A monthly average is not one convenient daily rate. Define the period, included observations, missing-date treatment and source before using it in a report.

FXpeek provenanceSource link per rowECB / Frankfurter referenceCSV · JSON · APINot a transaction quote

Many invoices? Get every rate in one CSV

Paste one invoice per line (date, currencies, amount) and preview the first 3 rows free; the full CSV (up to 200 rows, with the dated reference rate and converted amount) is $9. Reference data only, not a bank or tax settlement rate.

Open the batch invoice rate tool

Problem to proof · Finance analysts, researchers, and reporting teams

The report says “monthly average,” but the spreadsheet actually uses the last rate somebody pasted.

Use a documented monthly average instead of an arbitrary single-day rate.

The problem

The report says “monthly average,” but the spreadsheet actually uses the last rate somebody pasted.

Without a defined date range, included observations, missing-date rule, and pair direction, two people can calculate different averages and both call them correct.

What good looks like

The report states the month, pair, observation set, averaging method, source URL, and link to daily rows behind the result.

  • The period is explicit.
  • Daily observations can be inspected.
  • The method is not confused with month-end.

FXpeek workflow

Make the monthly average reproducible from daily rows

  1. Define the periodState the calendar month or approved reporting range and pair direction.
  2. Inspect included rowsUse available daily observations and document how non-publishing days are treated.
  3. Keep method and sourceSave the monthly page, daily CSV or API URL, row count, and averaging note.

Reproducible worked example

A monthly revenue report needs USD/EUR average

Input
An analyst must translate a month of USD revenue into an EUR management report.
Before
The workbook uses the final visible daily rate and labels it “average.”
After
It stores period_start, period_end, observation_count, method, average_rate, and source_url.
How to verify
Download the daily rows, apply the documented method, and compare the recalculated average.

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

Citation-ready answer

A monthly average exchange rate should identify the period, pair direction, included daily observations, missing-date treatment, averaging method, and source URL so the result can be recalculated from the underlying rows.

Run this workflow

Dated reference rates for this workflow

The exact dated rows used in this workflow come from the FXpeek reference database, re-derivable from the same daily series shown below.

Latest reference rate
0.8789
Data date: 2026-09-28
12-month high
0.8797
USD to EUR
12-month low
0.8548
USD to EUR
Source
ECB daily reference rate
US Dollar / Euro
ECB source

Reference data only. Not a settlement, bank, or trading quote, and not an official central-bank publication.

Full historyDownload CSVDownload JSONConvert an amount

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

Define the periodState the calendar month or approved reporting range and pair direction.
Inspect included rowsUse available daily observations and document how non-publishing days are treated.
Keep method and sourceSave the monthly page, daily CSV or API URL, row count, and averaging note.

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

When should I use a monthly-average exchange rate?

Use it only when the workflow or policy accepts period-average rates instead of a specific date.

Can FXpeek show daily rows behind the monthly average?

FXpeek links monthly pages to daily history and CSV/API endpoints for supported currency pairs.

Can I import monthly-average data into spreadsheets?

Use the CSV endpoint for spreadsheet-ready rows and keep the monthly-average source URL for context.

Is monthly average a settlement rate?

No, FXpeek monthly averages are reference data, not settlement, bank, or trading quotes.

How do I calculate a monthly average exchange rate?

A monthly average exchange rate should identify the period, pair direction, included daily observations, missing-date treatment, averaging method, and source URL so the result can be recalculated from the underlying rows.

How can the worked example be verified?

Download the daily rows, apply the documented method, and compare the recalculated average.

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

A monthly average exchange rate should identify the period, pair direction, included daily observations, missing-date treatment, averaging method, and source URL so the result can be recalculated from the underlying rows.

GET https://fxpeek.com/api/history?from=CNY&to=TRY&days=365
GET https://fxpeek.com/api/csv?from=CNY&to=TRY&days=365
GET https://fxpeek.com/api/stablecoin?pair=USDT-CNY
Monthly average exchange rate with a defined date