Multi-currency: what is supported today

Selling in more than one currency raises two separate questions: what currency is a record in, and what currency do you report in? Those have different answers here.

This article is deliberately conservative about what to rely on.

Who this is for

Admins and finance in businesses that trade in more than one currency.

Before you start

• Admin access to workspace settings.
• A clear decision about your reporting currency.

Verify before you commit a process to it
The workspace currency and per-record currency on deals are solid. Multi-currency behaviour is not uniformly complete across every module, so before you build a billing or reporting process that depends on mixed currencies, test it in the specific modules you use rather than assuming it works everywhere the same way.

Work with currency

1. Set the workspace currency
   This is your reporting default. It has to be one of the supported currencies, because it is carried end to end rather than being a display symbol.
2. Know what inherits it
   Deals, quotes and products that do not set a currency explicitly inherit the workspace one, so most records get the right answer without anyone choosing.
3. Set a currency on the record where it differs
   A deal carries its own currency. Set it when the deal is genuinely in a different one rather than converting in your head.
4. Remember existing records keep theirs
   Changing the workspace currency does not rewrite records that already carry one. It changes what new records inherit.
5. Test your specific reporting need
   Before relying on cross-currency totals in a report or an invoice, check the actual output on real records.

What you get

• One reporting currency for the workspace.
• Automatic inheritance, so most records need no decision.
• Per-deal currency where the deal genuinely differs.
• A tested view of what works for your case rather than an assumption.

Frequently asked questions

Can I change the workspace currency later?

Yes, but records that already carry a currency keep it. The setting governs what new records inherit rather than rewriting history.

Can a deal be in a different currency from the workspace?

Yes — a deal carries its own currency, so you record it in the one it was actually agreed in.

Are cross-currency totals reliable everywhere?

Test the specific modules you depend on. Multi-currency support is not uniformly complete across the product, and this is a case where checking beats assuming.

Which currencies can I choose?

Those the product supports end to end. The setting validates against that list rather than accepting any three-letter code.