Automated exchange rate feeds over REST API for SAP, NetSuite and Oracle general ledgers. A daily 22:00 UTC close, hourly and minute rates for teams that revalue during the day, or your own cut-off such as 4pm London. 150+ currencies and 50+ cryptocurrencies, with audit-grade history back to 1990.
| Pair | Low – High | Close |
|---|---|---|
| EUR / USDEuro to US dollar | 1.1113 – 1.1169 | 1.1154 |
| GBP / USDPound to US dollar | 1.3273 – 1.3339 | 1.3327 |
| USD / JPYUS dollar to yen | 157.656 – 158.347 | 157.836 |
| USD / CHFUS dollar to Swiss franc | -- | -- |
| USD / CNYUS dollar to yuan | -- | -- |
| USD / INRUS dollar to rupee | -- | -- |
What a nightly revaluation job fetches. Same values on any later date.
Trusted by top companies & institutions. Read our customer stories
Built for groups that still copy rates between systems at period end, or pay a data vendor by the tier for a close they could have in every system by morning.
A single 22:00 UTC closing rate across 150+ currencies, so subsidiaries, the ledger and the consolidation all revalue on the same number. Teams that mark positions during the day take the hourly or minute bar from the same key instead.
Load the day's close into S/4HANA Cloud through Market Rates Management with one short script we publish. No middleware subscription in between.
Closing rates arrive in your Snowflake account by data share, ready to join against the ledger. Nothing to schedule, nothing to load. Daily rates are being added to the share shortly; ask us and we will tell you when it is live.
Add-ins put live and historical rates into the exposure and hedging models treasury already runs, without an engineering ticket.
Daily history back to 1990 and tick data since 2016. Any date returns the same close whenever you ask, so a restatement reproduces the original number.
You keep your ERP, your rate types and your close process. We supply the number.
/historical for the date, an intraday run asks /hour_historical or /minute_historical for the bar it needs, or the Snowflake share refreshes on its own.
Each team takes the close in the tool it already uses. The number is the same in all three.
A nightly script fetches the close over REST and uploads it to SAP Market Rates Management, where S/4HANA's own import job collects it. Other ERPs take the same /historical JSON or a CSV through their standard rate upload.
Closing rates shared straight into your Snowflake account. No pipeline to build, nothing to load, ready to join against the ledger and the hedge book. Daily rates are being added to the share shortly.
Live and historical functions inside the workbook, so exposure, hedging and cash forecasting models refresh themselves instead of waiting for a paste.
We checked the publicly listed plans of a widely used FX data provider for treasury and accounting teams in October 2026. Where we don't do something, the table says so.
| A widely used FX data provider* | TraderMade | |
|---|---|---|
| Open and close rates | From the second tier, $9,000 a year | Open, high, low and close in every daily record |
| Quotes per month | 100,000 on the entry plan, unlimited above | Sized to your close run. A nightly load of 150 currencies is a handful of calls |
| Into the ERP | Marketplace connector or an integration-platform subscription | Published SAP S/4HANA script; REST or CSV into any ERP that imports rates |
| Into the warehouse | Pull it yourself over the API | Snowflake data share, no pipeline |
| Into spreadsheets | Download and paste, or a converter tool with 2 seats on the second tier | Excel and Google Sheets add-ins with live and historical functions; no per-user fees |
| Intraday rates | "3-5 second spot" from the third tier, $13,500 a year | WebSocket ticks and REST live rates, on the same key |
| Your own cut-off | Not listed on the public plan pages | Any minute of any day from minute history: 4pm London, 5pm New York or your month-end time |
| History | Back to 1990 | Daily, hourly and minute since 1990; tick since 2016 |
Send us your currency list, the systems that need the close and your renewal date. We'll map your plan line by line and come back with a like-for-like quote, SAP and Snowflake included.
Everything a nightly revaluation, an hourly mark, a restatement or a live exposure view needs, with the same field names throughout.
One date, every pair you list, with open, high, low and close. The call a nightly ERP job makes, and the one an auditor's query makes a year later.
Historical docshour_historical and minute_historical return the open, high, low and close for one hour or one minute of any day; timeseries returns a run of daily, hourly or minute bars for a date range. For intraday revaluation, hedge checks, period averages and backfilling a new entity's history.
Bid, ask and mid right now, polled over REST or streamed tick by tick, for intraday exposure monitoring and dealing desks that cannot wait for the close.
WebSocket docsThe record a revaluation job receives for month end, 30 September 2026.
# after 22:00 UTC: the day that has just closed, for the whole list curl "https://marketdata.tradermade.com/api/v1/historical\ ?currency=EURUSD,USDJPY,USDCHF,USDCNY,USDINR\ &date=2026-09-30&api_key=YOUR_KEY" # or your own cut-off: the minute bar at 16:00 London (15:00 UTC in summer time) curl "https://marketdata.tradermade.com/api/v1/minute_historical\ ?currency=EURUSD&date_time=2026-09-30-15:00\ &api_key=YOUR_KEY"
Banks, audit practices and payment companies run on the same feed. Here is what makes the number stand up.
Aggregated from Tier-1 liquidity, filtered for outliers before it is stored, captured into the daily bar at 22:00 UTC. The stored value never changes: the close you booked is the close you retrieve at the audit.
Legally backed on enterprise agreements, measured by an independent third party and published on our status page. The nightly job runs.
3S Money prices cross-border business payments on it; BITA calculates systematic indices on it; Chainlink publishes FX feeds on-chain from it.
The close, revaluation, SAP, Snowflake, history, cut-off times and group licensing.
22:00 UTC. The close is the mid price at that moment, and each daily record also carries the open, high and low. Before 22:00 UTC the day's bar is still forming, so overnight jobs load the day that has just closed. If group policy sets a different time, such as 4pm London, take the minute bar at that time instead (next question).
Yes. Live and historical endpoints return bid, ask and mid with the same timestamp, so a group can revalue on the mid and price intercompany transfers on the side it deals on, from one source.
On S/4HANA Cloud, a short Python script we publish fetches the close and uploads it to Market Rates Management (Bring Your Own Rates); SAP's import job then collects it on a schedule. On-premise and other ERPs import the same JSON or CSV through their standard rate upload. The tutorial walks through the SAP setup, the script and the schedule.
Daily, hourly and minute history back to 1990 and tick data since 2016. Any date returns the same close whenever you ask, so restatements and audit queries reproduce the original number. See historical data.
Rates are shared into your Snowflake account as a data share, so there is no pipeline to build and nothing to load. Join them against the ledger directly. Daily closing rates are being added to the share shortly; request information below and we will let you know when it is live and set you up.
Yes. Group internal use across subsidiaries, shared service centres and the data warehouse is covered under one agreement, with no per-user fees. Showing rates to customers or the public needs display terms, which we add on request.
Yes. Minute history covers every pair, so a job can take the mid at 16:00 London, 17:00 New York or whatever time group policy names, every business day, and store it as the day's rate. It is our aggregated market mid at that minute, and that is how to describe it in your policy. Intraday, the same key returns a live rate on every REST request and streams ticks over WebSocket for exposure monitoring.
Yes. hour_historical and minute_historical return the open, high, low and close for any hour or minute since 1990, and timeseries returns a run of hourly or minute bars for a range. Treasury teams use them for intraday revaluation, hedge effectiveness checks and a group cut-off that is not the close. Same key, same field names as the daily close, so the parser that loads the close loads the hourly bar too.
Tell us your currency list, the systems that need the close and the time your books close. A market data engineer will come back with terms, evaluation access and the right endpoint for each system.
Talk to an engineerPlease fill the form with your details and requirements and someone from our data team will contact you shortly.