Sales Operations System
Opportunities can be held in different currencies, with conversion to a reporting currency.
Anyone selling across borders needs this, and the detail that bites is not whether currencies exist but whether the platform holds exchange rates and converts for consolidated reporting. A currency symbol on a number field is formatting, not multi-currency.
Yes where an individual opportunity can be held in a currency other than the account default, and the platform converts to a reporting currency using rates it holds.
Partial where several currencies are supported but conversion for consolidated reporting is undocumented, or where rates must be maintained entirely by hand.
No where currency is a display format on a number field, fixed for every record in that field.
A currency symbol is formatting. The test is whether two opportunities in different currencies can be totalled.
No vendor documentation reachable during this evaluation addresses currency selection per record, exchange rates or conversion to a reporting currency.
A currency can be set on an individual deal or as the default for a pipeline, and deals in different currencies can sit in the same stage. Changing a deal's currency does not convert its value, no exchange rate handling or base-currency rollup is documented, and the deal reports are filtered to one currency at a time.
Multiple currencies are switched on in business settings, where a base currency is set and further currencies are added with a conversion rate against the base, each enabled or disabled individually and displayed by symbol or code. The vendor documents this as applying to opportunities and leads.
The currency attribute type stores a currency code, but the vendor states that the code is shared across every value of that attribute and that it is not possible to override the currency for a particular record or entry. A single deal value attribute therefore holds one currency for the whole workspace, and no conversion between currencies is documented. Separate currency attributes can each carry a different default code, but that is a parallel field rather than a per-deal currency.
An organisation sets a home currency and can activate up to ten currencies. Any module carrying a currency field, including pipeline records, contacts, companies and web forms, lets a record be held in a chosen currency, and each amount is displayed in the record currency with the home currency equivalent alongside it. Exchange rates are retrieved daily from openexchangerates.org. The documented constraints are that only an administrator can configure it, the home currency cannot be changed once a second currency exists, mass currency updates are not supported, and the feature cannot be switched off once activated.
A workspace carries a default currency, and the currency of a deal value is changed from the pipeline view, with the vendor stating explicitly that multiple currencies can be used within a single pipeline. The API enumerates twelve supported currencies on the contract currency field, and a symbol can be added for a currency that is not listed. How mixed-currency values are converted for consolidated reporting is not documented.
Each opportunity carries its own `currency` alongside its value, and each user sets a default currency in their preferences that is applied to new opportunities. Where opportunities are held in different currencies, Capsule derives the pipeline value in the user's default currency using current exchange rates.
No vendor documentation on currency handling was found. The opportunity fields documented by the vendor are status, confidence, value with a one-time or recurring period, estimated close, contact, user, comments and custom fields, with no currency selector, and the create-opportunity API request body documents value and value_period but no currency parameter. Absence of documentation is not proof of absence, so this is recorded as unverified rather than as a confirmed gap.
A company base currency is set and further currencies added, after which a currency can be chosen per lead or opportunity value. Copper converts values for reporting, recalculating open opportunities daily and fixing closed opportunities at the exchange rate on the close date, and each user can pick the currency their views and dashboards display in.
Currency appears only as a display format on a numeric custom field: the field's configuration takes a format of currency together with a single three-character currency code, which then applies to every value in that field. There is no per-record currency, no workspace base currency and no conversion documented, so deals held in different currencies cannot be totalled in native reporting.
A base currency is set once at account level and further currencies added against it, each with either an automatically fetched or a manually fixed conversion rate. Deals and contacts carry a Currency field so a deal can be held in its local currency, with the base-currency value recalculated at creation, at stage change and at close.
An account has a primary company currency and can add further currencies with exchange rates. A deal's Currency property sets the currency of its Amount, and HubSpot calculates an amount in company currency. Exchange rates can update automatically for open deals and are locked at close for closed deals.
Currency is selected per opportunity when entering the opportunity value, so records in different currencies can coexist. Price Books support only one currency each, with cloning suggested where more are needed. Vendor documentation does not describe organisation-level exchange rates or automatic conversion to a reporting currency.
Vendor documentation states that the currency chosen in sales settings becomes the default currency applied across all billing, payments and invoices in the account, describing a single account-level currency. No per-record currency and no exchange rate handling is documented.
Dataverse is multi-currency: an organisation has one base currency, an unlimited number of transaction currencies can be defined with exchange rates against it, and each record - opportunity, quote, order, invoice and others - carries its own transaction currency. Every money column is shadowed by a system-calculated base-currency column so values can be aggregated and compared across currencies.
The Numbers column takes a single unit setting for the whole column - none, dollars, pounds, euros, percentage or a typed-in custom unit - applied uniformly to every value in that column. No vendor documentation describes per-record currency or exchange rate conversion, and the vendor community treats mixed currencies as a formula workaround that labels values rather than converting them.
A currency is chosen per deal pipeline, so pipelines in different currencies can coexist in one account, and an account-level default currency is set under My Account. Vendor documentation does not describe setting a currency on an individual deal independently of its pipeline, exchange rates, or conversion of values into a single reporting currency.
Markets hold a default company currency plus additional currencies. A lead is assigned to a market and its attached products take that market's pricing and currency, with per-lead price overrides and the ability to mark a product unavailable in a market. Leads in a non-default currency are converted when reporting across currencies, and reports display in the account's default currency. Users can set a personal default market.
Deals can be held in different currencies and Pipedrive converts won deal values into the account's default currency for reporting, using rates supplied by Open Exchange Rates. Custom currencies can be defined but are excluded from automatic conversion, and the vendor notes the displayed rate is for statistical purposes and may differ from a bank rate.
A quote carries a Currency field that defaults to the home currency and can be changed once additional currencies are configured. Currencies and their exchange rates can be imported from the connected inventory, accounting or ERP system, or entered and maintained manually in system settings where no such system is connected.
Multiple currencies can be enabled with a corporate currency, maintained conversion rates, a currency field on each record and a personal currency per user. Advanced currency management adds dated exchange rates, where the opportunity close date selects the rate.
No monetary or currency column type is documented; deal value is held in a free form column that stores plain text or numbers. A troubleshooting article refers to applying currency formatting to a free form column, but no vendor documentation describes holding records in different currencies or converting between them for reporting.
More than one currency can be enabled in an instance. When a deal is created, a currency is selected in the item details section from all currencies available in the instance, and the deal's amount field then follows that currency. Currency can also be specified when importing deals.
A home currency is set for the organisation and additional active currencies can be enabled, with each record carrying its own currency and all its currency values based on it. Exchange rates are maintained manually or updated automatically from an external rates feed. Reports, list views and dashboards present amounts converted to the home currency. The vendor states multiple currency support is not available in the Forecasts module, which reports in home currency only, and that the home currency cannot be changed again once it has been changed.