ECB vs Fed vs Bank of England Exchange Rates: Which Official Rate Should You Use?

Ask three central banks what EUR/USD was on the same day and you will get three different numbers. That is not an error — each bank photographs a moving market at a different hour, by a different method, for a different audience. The practical question for anyone building invoicing, accounting, or reporting systems is not "which rate is correct?" (all of them) but "which rate is correct for my document?"

The three, side by side

The differences are structural, worth restating: the ECB quotes units of currency per euro; the Fed mixes conventions by pair; the BoE quotes against sterling. The Fed's H.10 is also a weekly release of daily figures — on Wednesday, this week's rates do not exist publicly yet, which surprises every first-time integrator. Details per bank: ECB, Fed, Bank of England.

How to decide, in order

1. Something already names a rate — use that

EU legal instruments and much euro-area accounting name the ECB reference rate. UK customs and VAT name HMRC's monthly rates — a tax authority's list, not the BoE's. US federal reporting names Treasury Reporting Rates, quarterly. Contracts often name a specific fixing outright. When a rate is named, the decision is made; your only job is to fetch the right number for the right date, with the source attached.

2. Nothing names a rate — match jurisdiction to publisher

Reporting to a euro-area parent: ECB. UK entity, sterling books: BoE. US entity: Fed H.10, or Treasury for federal filings. The principle is that an auditor should recognise the source without a footnote war.

3. Whatever you pick — write it down and stay consistent

The expensive failure is not choosing the "wrong" official rate; all are defensible. It is mixing them — ECB in Q1, a market feed in Q2, BoE in the subsidiary — so that eliminations stop netting to zero and no one can say why. A one-line policy ("group FX: ECB reference rate, transaction date, previous published day for non-publication dates") ends the ambiguity permanently.

The same-day spread is real money at scale

On a calm day, the ECB 16:00 CET number and the Fed's noon-New-York number differ by a handful of basis points; on a volatile day, meaningfully more. On a €10M intercompany position, 10 basis points is €10,000 of pure methodology. That is not a rounding argument for choosing carefully — it is the audit answer for why the two subsidiaries' numbers differ when each correctly used its own local official rate.

Fetching all three without three integrations

The three banks deliver via XML (ECB), a weekly statistical release (Fed), and a legacy query interface (BoE). Through a unified API they are one request shape:

# Same pair, three official views
curl "https://allratestoday.com/api/v1/central-bank/ecb/latest?source=EUR&target=USD" -H "Authorization: Bearer KEY"
curl "https://allratestoday.com/api/v1/central-bank/fed/latest?source=EUR&target=USD" -H "Authorization: Bearer KEY"
curl "https://allratestoday.com/api/v1/central-bank/boe/latest?source=EUR&target=USD" -H "Authorization: Bearer KEY"

Each response carries the bank's own publication date; pairs a bank never printed are computed from its published table and flagged derived: true — so "BoE view of EUR/USD" is honest about being a cross via GBP. The latest tables are free (300 requests/month); history is on paid plans.

FAQ

Which is more accurate — ECB, Fed, or BoE?

None. "Accurate" implies a single true rate, and there isn't one for a decentralised 24-hour market. Each is a well-defined official snapshot. Pick by applicability, not accuracy.

Why is the Fed rate missing for this week?

H.10 is released weekly, each Monday, covering the prior week's business days. For a same-day official dollar view, use another bank's daily publication or wait for the release.

What about the 32 other central banks?

The same logic extends everywhere: Mexican law names the Banxico FIX, Indian trade uses RBI/FBIL rates, Switzerland publishes monthly SNB averages. The full catalogue covers 35 banks under one key.