Data Panda brings the euro reference rates together with the data from the rest of your business. From one place, we turn them into dashboards, automations, AI workflows and custom apps your team uses every day.
The European Central Bank publishes euro foreign exchange reference rates for around thirty currencies. They come out of a daily concertation procedure between European central banks that normally takes place around 14:10 CET, and they land on the ECB site around 16:00 CET on every working day that is not a TARGET closing day. The rates are free, need no API key, and are served both as a daily XML feed and through the ECB Data Portal web service, where a key like D.USD.EUR.SP00.A returns the daily dollar rate against the euro.
EU VAT rules let you convert a foreign-currency invoice at the ECB rate of the date the tax became chargeable, provided you apply that choice consistently. Consistency is exactly what breaks when your invoicing tool, your accounting package and your consolidation each fetch their own rate. One stored table per day and per pair gives all three the same number, with the publication date on the row, so the answer to which rate applied on which date comes from your own data instead of a screenshot of a website.
One ECB rate per pair per day, joined to the invoice, payment or declaration it converted.
Invoicing, payouts and alerts all read the same stored rate for that date.
Use the published history to model exposure and test price scenarios.
Internal tools that read one rate table instead of scraping the ECB site.
A list of concrete reports, automations and AI features we have built on ECB Exchange Rates data. Pick the one that matches your situation.
Which rate did we use to convert this export invoice, and can we defend it?
The ECB rate for that pair and that date sits in the warehouse with its publication date, and the invoice carries the same number. EU VAT rules let you convert at the ECB rate of the day the tax became chargeable as long as you apply that choice consistently, and consistency is easy to show when invoicing, accounting and consolidation all read one table.
What did our bank's conversion spread cost us last quarter?
Every foreign-currency payment lands next to the ECB reference rate of the same date, so the gap between the rate your bank applied and the published one shows up per transaction. Totalled per quarter and per currency, that gap becomes a number you can take into a bank conversation instead of a suspicion you cannot size.
How exposed are we per currency on everything still open?
Net position per pair from open receivables, payables and cash, measured against the range the ECB published over the last twelve months. The CFO sees which pair drives the exposure, and which single customer or supplier sits behind most of it.
One rate table that invoicing, the VAT return and the consolidation all read from. Month-end revaluation runs on rates that carry their publication date, so an auditor asking which rate applied on 14 March gets the answer from the row itself. Realised and unrealised FX results split per customer, supplier and period out of the same source.
Multi-currency quotes apply the rate of the day the proposal went out, so the price the customer sees matches what the books expect later. Account owners see where FX ate the margin between quote and invoice, per deal, instead of hearing about it in a variance review weeks afterwards.
Supplier payouts convert on the rate of the day the order was confirmed, so reconciliation lands on the amount that was agreed. Alerts on tracked pairs fire when a daily move crosses a set band, which gives purchasing time to adjust before the next batch of orders goes out.
Every Exact Online invoice in a foreign currency picks up the ECB rate of the date the tax became chargeable, and that rate is written onto the invoice line. Month-end revaluation runs against the closing rate from the same table, so the realised and unrealised results in Exact trace back to one published number per date.
The daily rate per currency pair posts into Business Central as the exchange rate of the day, so AR and AP entries in foreign currency revalue against the published reference. At consolidation the closing rate matches what the warehouse stored, instead of a sheet somebody loaded by hand at the end of the quarter.
A Billit invoice in a foreign currency carries the ECB rate of the invoice date and the publication timestamp behind it. When a customer or an inspector questions the converted VAT amount, one lookup in your own data settles it.
Each Stripe charge in a foreign currency lands next to the ECB rate of the same date, with the presentment and settlement amounts kept on the row. The spread Stripe took on conversion becomes visible per payout and per currency, which turns the cost of card-network FX into a line you can total at year end.
Every Shopify order in a foreign currency is matched to the ECB rate of the order date, alongside the rate Shopify applied at checkout. The difference lands per order, so you see per store and per currency where the checkout rate quietly moved the margin, and whether a markup setting needs changing.
When a pair you follow moves beyond a set percentage on a single publication day, a finance channel gets the move with the open exposure and the deals priced on the previous rate attached. Somebody adjusts a quote or brings a payout forward the same afternoon, rather than at the next FX review.
These are the 2 tables we currently pull from ECB Exchange Rates into your warehouse. Query them directly in SQL, join them to the rest of your stack, or build reports on top.
Missing a table you need? We can extend the sync. Tell us what is missing and we will build it for you.
You keep the reporting tool you already have. We connect it to the warehouse where your ECB Exchange Rates data lives.
OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.
Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.
We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.
We set up the foundation. Your team builds on top.
Best fit Teams that already have a BI analyst or data engineer and want to own the build.
We build the whole thing, end to end.
Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.
You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.
Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.
No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.
For reporting and for VAT conversion, yes. EU VAT rules explicitly allow converting at the ECB rate of the date the tax became chargeable, provided you apply that choice consistently. What the ECB discourages is treating a reference rate as the rate you actually trade at. Your bank's dealing rate will differ, and holding both next to each other is precisely what makes that difference measurable.
No rate is published, so the table has gaps by design. We fill them with a rule you choose, usually carrying the last published rate forward, and the row records that the rate was carried rather than published. A Sunday order then cannot quietly pick up Friday's rate without anyone being able to see that it did.
The reference list covers around thirty currencies, and EUR/RUB has been suspended since 1 March 2022. For anything outside the list you convert through the euro in two steps, or we pull a second source alongside the ECB feed and keep both on the row, so it stays clear which number came from where.
We review your ECB Exchange Rates setup and the systems around it. Together we pick the first thing worth building.