JPY to EUR

Reference notes for JPY/EUR

When you typically see JPY/EUR

This direction shows up for Japanese travelers to the Schengen area, for Japanese subscribers to EU-billed services (Hetzner, OVH, Mailgun's EU region), and for Japanese SMEs importing finished goods or components from Germany, France, or Italy. The Italian-leather, German-Mittelstand-machinery, and French-luxury supply chains all bill in EUR and settle in EUR; the JPY translation is recorded for the Japanese buyer's books only. Personal subscription accounts are the highest-frequency case: a Japan resident paying an Italian or French subscription monthly produces 12 jpy-to-eur lookups per year per service. With the spread of EU-region cloud hosting for GDPR reasons, this volume keeps growing.

How JPY/EUR behaves in accounting

Mizuho publishes EUR/JPY TTM, TTS, and TTB directly. No cross-rate needed. The pair is the second-most-watched in Japan after USD/JPY, so coverage is dense and reliable. EUR/JPY is sensitive to ECB policy meetings (typically Thursdays at 14:15 CET) and to BOJ statements. The combined sensitivity creates wider daily ranges around those event days than USD/JPY usually shows. For monthly subscription accounting this rarely matters; for end-of-quarter revaluation of EUR-denominated payables it can. Some Japanese accounting teams prefer prior-month-end EUR/JPY for translation of recurring vendor payments — one rate per month is easier to defend in audit than 12 rates per year. Zenrate's prior-month-end policy reads Mizuho's last-business-day TTM of the previous month for this purpose.

Common conversion mistakes for JPY/EUR

Using the ECB reference rate (published 14:15 CET) when the company's policy specifies the Mizuho TTM (published earlier in the Tokyo day). Both are real, both are reference rates; they will not match. For a Japanese-domiciled company, Mizuho is the conventional answer; for an EU-domiciled subsidiary, ECB is. Mixing them in the same set of books produces small but persistent reconciliation gaps. Forgetting that Italy, France, and Germany all observe EU national holidays that do NOT line up with Japanese ones. A purchase on August 15 (Ferragosto) will not match a same-day reference rate, because EU markets are thin and Mizuho's TTM still publishes. Use the published TTM regardless; it represents what a Tokyo bank would have transacted at if asked. Treating a EUR-denominated invoice paid by SEPA from a Wise multi-currency JPY balance as a JPY-to-EUR conversion at the moment of payment. Wise holds the balance in JPY but converts only at the moment SEPA executes — the rate to record is Wise's executed rate on that timestamp, not Mizuho TTM.

What Zenrate stores for JPY/EUR

Live conversion uses exchangerate-api.com (USD-base, cross-rated for JPY/EUR). Cached twelve hours. Historical rates: Mizuho JPY/EUR via the same dbFetcher/edgeFunction pattern used for USD; ECB EUR/JPY directly via Frankfurter (note the direction — ECB always publishes from EUR). All six rate policies apply. The prior-month-average policy is the heaviest fetcher load for this pair, since it iterates roughly 20 business days; the dbFetcher absorbs this if the month is already ingested, otherwise each lookup falls through to the edge function.

These notes describe the rate sources actually implemented in @zenrate/core/rate-sources at the time of publication. Behavior may evolve; the source code is the ground truth.