Multi-currency CRM setups are tricky because the system has to stay accurate for both sales and finance. The workflow only works when the currency used on the deal is stable, the exchange-rate logic is clear, and reports can still be read in a single financial view.
Selling across multiple countries creates a CRM configuration headache that domestic-only businesses never have to think about. The same deal can look completely different depending on whether you’re the rep, the customer, or the finance team — each working in a different currency. A deal closed with a German customer in EUR lands differently on the UK finance team’s GBP reports than it does in the rep’s EUR view. Add in exchange rate fluctuations, and you get a gap between what a deal was worth when it was created and what the CRM says it’s worth today. This guide covers how major CRM platforms handle multi-currency, what the reporting implications are, and the most common problems that come up in global sales organisations.
That means currency handling is not just a formatting issue. It affects forecasting, handoff, and the trust the business places in the numbers.
How Multi-Currency Works in CRM
| Component | Description |
|---|---|
| Corporate (default) currency | The base currency for the organisation — typically the currency of the headquartered entity or the primary finance reporting currency (e.g., USD for a US-headquartered company) |
| Supported currencies | The list of currencies that users can select when creating deals — each enabled with its exchange rate against the corporate currency |
| Static exchange rates | Administrator-set exchange rates that apply to all deals in that currency — if EUR/USD is set to 1.08, all EUR deals convert at 1.08 regardless of the actual rate at time of close |
| Dated exchange rates (Salesforce Advanced Currency Management) | Exchange rates that apply based on the date of the deal — a deal closed in Q1 uses the Q1 rate; a deal closed in Q3 uses the Q3 rate. More accurate for historical reporting. |
| Deal currency | The currency the deal is recorded in — typically the currency of the customer’s country or the contract currency |
| Reporting currency | The currency reports are displayed in — corporate currency for global rollup reports; local currency for territory-specific views |
Multi-Currency Configuration by CRM Platform
Salesforce: Salesforce has the most comprehensive multi-currency support of any enterprise CRM. Standard multi-currency lets administrators add supported currencies and set static exchange rates. Advanced Currency Management (ACM) goes further, applying dated exchange rates — different rates based on the opportunity’s close date — which matters a lot when exchange rates swing significantly over time. Salesforce also distinguishes between a “deal currency” (the currency the deal is recorded in) and a “user currency” (the currency a rep sees in their personal views). Available on Enterprise and above.
HubSpot: Multi-currency is available on Professional and Enterprise plans. Admins enable currencies and set exchange rates manually. Deal values display in the deal’s currency; reports can show any enabled currency. One important limitation: HubSpot exchange rates are static and manually updated. HubSpot doesn’t pull live rates automatically, so someone has to keep those rates current.
Zoho CRM: Multi-currency is available on Professional, Enterprise, and Ultimate editions. Zoho has an edge over HubSpot here — it supports automatic exchange rate updates from currency providers rather than requiring manual updates. Deals can be recorded in any enabled currency and reports convert to the base currency using the configured rate.
Pipedrive: Multi-currency is supported across all paid plans. Deals can be created in any enabled currency. The catch: Pipedrive shows deal values in the deal currency, so if you want aggregate pipeline figures in a single base currency, you’ll need manual calculation or a connected reporting tool to get there.
“Our USD pipeline report shows different values each time someone updates the exchange rates — we can’t forecast accurately”
This is the direct result of static (non-dated) exchange rates applied to historical deals. Every time the admin updates EUR/USD, every existing EUR deal’s USD equivalent changes. For Salesforce users: enable Advanced Currency Management to lock historical deals to their dated rates. For HubSpot and platforms without dated rates: accept that base-currency pipeline values will fluctuate with rate updates and build your reporting convention around that reality — report pipeline in local deal currency for accuracy, and supplement with a base-currency aggregate report with a clear note that it reflects current rates. Some organisations export deal data to a BI tool like Tableau or Looker, where dated exchange rates can be applied at the reporting layer.
“We have deals in 12 currencies and our sales team is creating deals in the wrong currency”
Currency selection errors usually happen when reps create deals without checking the currency field, especially where the CRM pre-selects a default. A Spanish rep creating a deal for a Spanish customer in USD instead of EUR is a classic mistake. The fix: set the default deal currency to the user’s or contact’s local currency rather than the corporate default. In Salesforce, a rep’s user record has a default currency that pre-fills the deal. In HubSpot, currency is selected at deal creation — add a reminder to the deal creation form or in onboarding materials. Running a weekly report of recently closed deals where the currency doesn’t match the account’s country will catch systematic errors before they compound.
“Our finance team reports in GBP but sales reps in Asia are creating deals in USD — the conversion is confusing everyone”
This is a policy problem as much as a CRM one. Multi-currency organisations often have a disconnect between how sales records deals and how finance expects to see revenue. The fix is a clear currency policy covering three things: (1) what currency should deals be recorded in? — typically, the currency of the contract with the customer; (2) what is the reporting currency for pipeline meetings? — typically corporate currency; (3) who updates exchange rates and how often? — typically the finance team, monthly. Document the policy, train the sales team, and build a shared CRM dashboard that shows pipeline in both local deal currencies and the base currency.
Sources
Salesforce, Multi-Currency and Advanced Currency Management Documentation (2025)
HubSpot, Multi-Currency Setup and Exchange Rate Management (2026)
Zoho CRM, Multi-Currency and Exchange Rates Configuration (2025)
Gartner, Global CRM and Multi-Currency Revenue Reporting (2025)
Fix: Lock Contract Currency at the Point of Proposal
Configure your CRM to store deal amounts in both the transactional currency and the corporate currency for reporting. Lock the contract currency at the point of proposal so exchange rate fluctuations after signature don’t alter the reported deal value.
Fix: Build Currency-Aware Pipeline Reports with Regional Breakdowns
Create separate pipeline reports by currency region alongside a consolidated report that converts everything to corporate currency using current rates. This two-level reporting structure lets regional managers work in their native currency while CFO-level reporting consolidates cleanly.
Which CRMs support multi-currency deals?
Salesforce supports multi-currency with Advanced Currency Management including dated exchange rates. HubSpot supports multi-currency on all paid plans. Zoho CRM, Pipedrive, and Microsoft Dynamics 365 all support multi-currency at mid-tier plans.
What is the difference between transaction currency and corporate currency in CRM?
Transaction currency is the currency in which a deal is priced with the customer. Corporate currency is the single reporting currency your company uses for consolidated financial reporting. CRMs store both values, converting using exchange rates so all deals can be compared in a single view.
How do you handle currency risk in B2B CRM reporting?
Set up dated exchange rates so historical deals reflect rates at the time of the transaction. Create a Locked Contract Value custom field that captures the corporate currency equivalent at signing and never updates with rate changes. Use this for revenue recognition reporting.
Does Salesforce automatically update currency exchange rates?
Salesforce does not update exchange rates automatically by default. Administrators must update them manually or use Apex code or a third-party tool for daily automation. Salesforce Advanced Currency Management supports dated exchange rates but live sync requires a custom implementation.
Exchange Rate Management: The Core Problem
Exchange rate management is where multi-currency CRM gets complicated. EUR/USD moved from 0.96 to 1.12 in a single 12-month period. When rates move like that:
- A deal created in January at EUR 100K converts to $96K USD at the January rate
- By December, that same EUR 100K converts to $112K USD at the December rate
- If the CRM applies only the current rate to historical deals, the January deal now shows as $112K — an increase in USD value that has nothing to do with any commercial outcome
- This creates phantom revenue changes in pipeline reports that don’t reflect real business performance
Salesforce Advanced Currency Management solves this by locking the conversion rate to the date the deal was created or closed. HubSpot and most other CRMs use only the current admin-set rate, which means historical deal values in the base currency shift every time the admin updates the exchange rate.
The best setup is the one that makes the team more accurate without adding unnecessary friction. If the process becomes harder to use, the field design or sandbox approach needs another pass.
Common Problems and Fixes
Solving Multi-Currency CRM Challenges for Global Sales Teams
Problem: Outdated Exchange Rates Skew Pipeline Forecasts
When CRM currency conversion rates are updated manually or not at all, deal values in your forecast can drift significantly from actual values. For organisations with more than 15% of pipeline in foreign currencies, even a 5% rate drift makes the forecast meaningfully inaccurate. Automate daily rate updates via the CRM API or a third-party rate service.