Best Practice - Currency configuration

(4) Share

Report

Posted on by rasmusgj

Hi everyone!

I have a simple yet semi-critical question.

It doesn't seem to be documented, but if I would need to support many currencies especially for 3.1, is there a best-practice approach, or is it something that I would configure individually for each customer based on their preferred practice (also considering maintenance/inflation for each year)?

I understand systemcurrencies cannot be used as the continuous exchange updates would cause issues, but can anyone provide some thoughts or pointers on this, that would be appreciated (just so I do not reinvent the wheel, yet).

Thank you!

Categories:

Sustainability Manager

I have the same question (0)

All responses (7)

Answers (1)

Joke Laukens 142 on at

Like (2)

Report

Ah great question.. I have been wondering about that too.

There is indeed not that much available out of the box, so I assumed that this was something to tackle outside of the sustainability manager.

Was this reply helpful? Yes No
Suggested answer

Ivan (Vanya) Kashperuk on at

Like (1)

Report

See some suggestions here: Scope 3 emissions - Microsoft Cloud for Sustainability | Microsoft Learn

General advice is to explore what would work best based on your policies, Microsoft avoids giving specific recommendations here

Was this reply helpful? Yes No
rasmusgj 47 on at

Like (1)

Report

Thank you @Ivan (Vanya) Kashperuk, I also have read that, but still not entirely sure what that entails.

Does that mean that:
1) If I were to configure currencies, I would need to convert everything to USD as of 2018, since that is the base (read-only) value?

or

2) That I should/could create an entirely new Unit Group called Currency and go from there? Or could that cause issues in the long-term?

I suppose that is my question.

Hope this makes sense :)

Was this reply helpful? Yes No
rasmusgj 47 on at

Like (1)

Report

I just tested with installing the Exiobase 2022 Factor Library, and that actually inserted an EURO 2022 currency in the default unit group, so tells me there is something systematic being leveraged, quite important to be aware of.

Was this reply helpful? Yes No
Lea Kraus 165 on at

Like (2)

Report

Hi @rasmusgj,

I had the same challenge and what we did is to create a separate unit group for this FY.

This way, we were able to use our own conversion rates the finance team provides us and also to set the base unit to EUR. For the next FY we will probably then create another unit group again called "Currency FY26".

But I'm also wondering about long-term consequences or if there is a better way to achieve that.

Was this reply helpful? Yes No
Vahid Ghafarpour 12,166 Super User 2025 Season 2 on at

Like (1)

Report

If any of the responses helped resolve your issue, please take a moment to mark the best answer. This helps others in the community quickly find solutions to similar problems.

To do this, simply click the "Does this answer your question?" button on the most helpful response and like the helpful posts. If your issue is still unresolved, feel free to provide more details so the community can assist further!

Thanks for being an active part of the Dynamics 365 Community!

Was this reply helpful? Yes No
Verified answer

CU30040838-0 13 on at

Like (2)

Report

@Lea Kraus @Joke Laukens @Ivan (Vanya) Kashperuk

Sorry for the delayed response. Actually got some good pointers from my connections at Microsoft.

Basically,

You can create a new unit group if prefered.

You cannot change base unit of default group, but you can actually change the Unit itself to reflect EURO 2022 (for instance) instead of USD 2018 and then set up conversions (might be some drawbacks, but did not think of this).

The idea here is not to have a precise conversion but rather be able to use spend based GHG emissions as this is not a finance system.

Hope this provided some clarify for others, it did for me :)

Was this reply helpful? Yes No