Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
DictionaryDDated Exchange Rates
AdministrationAdvanced

Dated Exchange Rates

Dated Exchange Rates in Salesforce are time-specific currency conversion rates that apply for a defined date range, layered on top of the org's default ConversionRate (which is the always-current static rate).

§ 01

Definition

Dated Exchange Rates in Salesforce are time-specific currency conversion rates that apply for a defined date range, layered on top of the org's default ConversionRate (which is the always-current static rate). With Dated Exchange Rates enabled, the org maintains a history of rates per currency per date range; financial calculations (Opportunity Amount, Quote pricing, roll-up summaries) use the rate that was in effect on the relevant transaction date rather than the always-current rate. The feature is essential for finance teams that need historically-accurate conversion for reporting and audit purposes.

Dated Exchange Rates exist because static ConversionRate produces misleading historical reports. An Opportunity worth 100,000 EUR closed in Q1 2024 when EUR/USD was 1.10 produced 110,000 USD in revenue; an always-current rate of 1.05 in 2026 would re-report the same opportunity as 105,000 USD. Finance teams need the historical rate to match what actually happened. Dated Exchange Rates produce the right answer for historical reporting at the cost of maintenance overhead (admins or scheduled jobs must enter new rate rows as periods elapse).

§ 02

Why Dated Exchange Rates matter for historically-accurate financial reporting

Where Dated Exchange Rates live in setup

Setup, Company Settings, Manage Currencies, Dated Exchange Rates. The page lists every currency with its rate history (start date, end date, conversion rate). New Dated Exchange Rates open a row to add. The feature requires multi-currency enabled on the org and the Manage Currencies permission. Admins maintain the rate history per currency per period; entering a new rate automatically closes the previous period's end date to the day before.

Static ConversionRate vs Dated Exchange Rate

The CurrencyType object has two related concepts. ConversionRate is the single current rate that always applies (when Dated rates are not configured for the relevant date). DatedConversionRate is the time-specific rate. Salesforce uses the Dated rate first if one exists for the transaction date; falls back to ConversionRate if no Dated rate covers the date. The fallback matters; orgs that enable Dated Exchange Rates but forget to enter rates for new periods get the static rate by accident, producing inconsistent historical numbers.

Which fields use Dated Exchange Rates

Currency conversion applies anywhere Salesforce converts between currencies. Opportunity Amount conversion to corporate currency uses Dated rates if configured. Quote Line Item totals, Order Line Item totals, Forecasting roll-ups all use Dated rates. Reports that show converted amounts respect Dated rates. Formula fields that reference converted amounts respect Dated rates. The pattern is consistent; once enabled, Dated rates apply throughout the platform without per-feature configuration.

Effective date and the conversion timing

Each record involved in conversion has an effective date that drives which Dated rate applies. Opportunity uses Close Date. Order uses Activation Date. Quote uses Created Date. Custom objects can use any date field configurable on the conversion settings. The effective date is what links the transaction to the historically-accurate rate. Misconfiguration of the effective date (using Created Date when Close Date was the correct choice) produces wrong conversions even when Dated rates are otherwise correct.

Rate sourcing and the operational discipline

Rates do not appear automatically. Finance teams typically subscribe to a rate provider (Bloomberg, Reuters, central bank feeds) and ingest the rates monthly or quarterly. The ingestion is custom: a scheduled Apex job or Flow that reads from the provider and inserts DatedConversionRate rows for the new period. Without automation, admins enter rates manually; with manual entry, periods get missed and the historical record becomes incomplete. Most finance-driven orgs build automation; admin-only orgs run manual entry per month.

Audit, restatement, and the historical accuracy question

Once a Dated rate is set for a period, changing it restates every historical conversion that used that period. Changing the EUR rate for Q1 2024 from 1.10 to 1.12 changes every Q1 2024 opportunity's reported USD value. Restatement is sometimes required (rate correction, late provider update); sometimes prohibited (closed financial period, audited numbers). Document the rate-change policy explicitly; restatement without communication produces confusion downstream and audit findings.

Performance and the historical-data implications

Conversion with Dated rates is more computationally expensive than static; the platform must look up the right rate per transaction date. For most orgs the overhead is negligible. For very large orgs with millions of historical opportunities, report performance can slow when Dated rates apply across deep historical data. The optimization: limit the Dated rate history to the periods actively reported on, archive or summarize older periods, accept that very old data uses approximate rates.

§ 03

How to enable and operate Dated Exchange Rates

The pattern: confirm multi-currency is enabled, enable Dated Exchange Rates, ingest historical rates, automate ongoing rate updates, document the restatement policy. The feature is one-way (cannot be cleanly disabled) and operationally demanding; plan deliberately with finance before enabling.

  1. Confirm multi-currency is enabled on the org

    Setup, Company Information. Multi-currency is a prerequisite for Dated Exchange Rates and is itself one-way; ensure both are intentional.

  2. Enable Dated Exchange Rates

    Setup, Manage Currencies, Activate Advanced Currency Management. The feature is one-way; cannot be cleanly disabled. Coordinate with finance.

  3. Ingest historical rates for the period in scope

    Pull rates from the provider for the relevant historical period (typically the last 3 to 5 years). Insert as DatedConversionRate rows.

  4. Build automation for ongoing rate updates

    Scheduled Apex or Flow that pulls from the provider weekly or monthly and inserts new period rows. Manual entry does not scale.

  5. Configure the effective date per relevant object

    Opportunity uses Close Date by default; verify. Custom objects need explicit effective date configuration.

  6. Document the rate-change policy with finance

    When are rate restatements allowed, who authorizes, how is the change communicated. The policy prevents accidental restatement of closed periods.

  7. Audit conversion accuracy quarterly

    Sample historical opportunities, verify converted amounts match the period's actual rate. The audit catches missed periods and rate misconfigurations.

Key options
Multi-currency prerequisiteremember

Required; cannot enable Dated rates without multi-currency.

Rate history depthremember

How many historical periods to maintain. Balance accuracy against performance.

Provider integrationremember

Bloomberg, Reuters, central bank, or other. The source of truth for rates.

Effective date per objectremember

Opportunity Close Date, Order Activation Date, custom field per custom object.

Restatement policyremember

When and how to change rates for closed periods. Document with finance.

Gotchas
  • Dated Exchange Rates is one-way; once enabled, cannot be cleanly disabled. Coordinate with finance before flipping.
  • Missing rates for a period fall back to the static ConversionRate. The fallback produces inconsistent historical numbers; missed periods need to be caught explicitly.
  • Changing a rate for a closed period restates historical conversions. Document the restatement policy explicitly to prevent accidents.
  • Effective date misconfiguration produces wrong conversions even with correct rates. Verify each object's effective date matches finance expectations.
  • Very deep historical rate data can slow large reports. Optimize by archiving very old periods or accepting approximate rates for ancient data.
§

Trust & references

Sources

Cross-checked against the following references.

Official documentation

Straight from the source - Salesforce's reference material on Dated Exchange Rates.

Was this entry helpful?
Help us write better definitions. Quick reactions or detailed edit suggestions.

About the Author

Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.

§

Test your knowledge

Q1. What do Dated Exchange Rates enable?

Q2. What happens without Dated Exchange Rates?

Q3. Who needs Dated Exchange Rates?

§

Discussion

Loading…

Loading discussion…