HubSpot Ideas

aletocar

Deals forecast report should use company currency in multi currency pipelines

After hubspot announcement of multi currency support, we updated our product gallery to allow for this. After some tinkering, we were on track to use multiple currencies for our deals.

However, now we realize the deal forecast report (on which we rely heavily) does the forecasting based on the deal amount, without taking exchange rates into consideration.

This means that if I have a usd deal (ex rate = 1), uyu deal (ex rate = 0.03), it will sum both amounts as absolute values, which means the forecast is all wrong.

 

With the help of the support team we've created a custom report that adds the forecast for each stage, but it is not exactly the same, and we already use some custom reports, which means adding another is not an option.

 

HubSpot Updates
Re: Deals forecast report should use company currency in multi currency pipelines - changed to: Delivered
October 04, 2018 09:57 AM

6 Replies
guymaor
Member

I agree!

aletocar
Member

Hi! This issue also applies to the Deal Closed vs Goal dashboard. Closed a deal in a currency with ex rate 0.03 to usd and the report went crazy (I´m not that good at closing deals 🙂 )

I'm assuming it goes with any dashboard with the deal amount in its data.

 

@emilytong Could we get some feedback from the Product Team?

 

Thanks!

emilytong
HubSpot Employee

@aletocar - thanks for looping me in! I'll see what I can do to follow up on this request internally to help this idea gain more traction with the Product Team. 

aletocar
Member

By the way, in the amount closed vs goal, you can change the report settings to take the amount in company currency instead of the deal amount for the report. Since the forecast report is not editable, there's no way to make that happen.

 

Thanks @emilytong! Let's make it happen 🙂

aletocar
Member

Hi! This issue has been resolved on our end, and the deal forecast report now takes the company currency to build, instead of the deal amount. This is working for us.

 

Thanks @emilytong and team for the quick fix!

Julia_Bliss
HubSpot Product Team