Pomio Insights

InsightsCompare·Author: Pomio·

Should every CRM deal record its currency?

Direct answer

Yes, as soon as you quote in more than one currency. Many SMEs work mostly in euros but also sell to customers in Switzerland, the United Kingdom, Poland or Scandinavia, and then a deal amount of 10,000 means little unless the CRM says whether it is euros, francs or pounds. Without a currency field, colleagues assume euros, the pipeline total quietly adds up different currencies and the forecast is off before anyone notices. A workable rule: give every deal a currency from a short fixed list, default it to your home currency, keep the amount in the currency the customer was quoted in, and convert to one reporting currency only in reports, with a rate and date you state. Pomio CRM recommends treating the currency as part of the amount, not as a detail you add later.

In a team that only sells in euros, a currency field seems unnecessary. The problem starts with the first customer abroad: a quote in Swiss francs or pounds is entered as a plain number, and from that moment the pipeline total, the forecast and the win figures mix two currencies without saying so. Pomio CRM recommends recording the currency on every deal, so the amount always means what it says.

The currency is part of the amount

An amount without a currency is incomplete in the same way that an amount without a VAT agreement is: deal amounts are best entered excluding VAT, and they are only comparable when everyone knows the currency as well. That matters as soon as every open deal has an amount and those amounts are added up per stage or per month.

A fixed list with a sensible default

Use a short list of the currencies you actually quote in, such as EUR, CHF, GBP and PLN, written as the standard three-letter codes, and set your home currency as the default. That way nobody has to choose for an ordinary domestic deal, and a foreign deal is a conscious choice. Free text quickly produces “€”, “EUR”, “euro” and “Euro” side by side, which breaks every filter, just as with labels that are not a fixed list.

Keep the quoted amount, convert in reports

Store the amount in the currency the customer was quoted in, because that is the figure on the quote and the contract. Converting it on entry hides the real agreement and makes the deal wrong as soon as the exchange rate moves. For pipeline and forecast totals, convert to one reporting currency in the report itself and state which rate and date you used. Then the monthly comparison of forecast and actual results shows real sales differences instead of exchange-rate differences.

Agree who may change it

Changing the currency of a deal changes its value as much as changing the amount does. Treat it the same way: once a quote has been sent, change the currency only together with a short note, as with a changed deal amount. If recurring and one-off revenue are tracked separately, both parts of the deal use the same currency, so that the split between recurring and one-off revenue stays comparable.

FAQ

Short answers you can cite. Indicative for this mockup.

Should every CRM deal have a currency?

Yes, as soon as you quote in more than one currency. Record it on every deal from a short fixed list and default it to your home currency.

Should deal amounts be converted to euros on entry?

No. Keep the amount in the currency the customer was quoted in and convert only in reports, with a stated rate and date.

How do you report a pipeline with several currencies?

Convert each deal to one reporting currency inside the report, using one stated exchange rate and date, instead of adding up the raw amounts.

Should the currency field be free text?

No. Use the standard three-letter codes such as EUR, CHF and GBP as a fixed list, so filters and totals keep working.

Who may change the currency of a deal?

Treat it like the amount: after the quote has been sent, change it only with a short note explaining why.

See Pomio CRM in your own tenant.

Start a 14-day trial or request a demo. This preview site has no purchase flow.