web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)
Suggested Answer

Currency 3 decimal is required for one entity and 2 decimal is required for other entity in AX 2012

(1) ShareShare
ReportReport
Posted on by 55

Dear All,

We have a requirement at a Client site for which we are looking for a solution. They have 6 legal entities out of which 5 are based in UAE and require 2 decimal places for their transactions. However, 1 legal entity is based in Jordan and for that 1 entity, 3 decimal places are required.

 

Is it possible to manage this scenario in AX 2012? If so, how can we achieve this? It would be really helpful if any of you would have any suggestions which can help us. 

Thanks.

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Vilmos Kintera Profile Picture
    46,149 on at

    Since currency is global, rounding rules for them are global as well.

    If you are talking about fields such as Amount, they can only have a single display length defined by default on their data type. In case you want this to act differently on another legal entity, I am afraid you have to do a lot of work in your environment.

    You have to create 2 designs for each report where display length of decimals matter. Also on every form where you want to show 2 decimals you need to change the FormControl's properties runtime depending on the legal entity in your init() method of the form.

    The typical way of solving this instead of dumping countless development time in the environment is to make them uniform. Either everyone goes with 2, or 3 decimal places.

  • BKAX Profile Picture
    55 on at

    Hi Vilmos,

    Thanks for the update. we will try to convince them either to go with 2 or 3 decimal places . it will help to ignore major customization's.

    Thanks

  • Suggested answer
    Vilmos Kintera Profile Picture
    46,149 on at

    No problem, it is the customer's interest to go with as few customizations as possible for easier support, troubleshooting, maintenance and future upgrades.

    If 3 decimal places are a legal requirement for that single country, then I'd go with the 3 decimal places globally. And because they possibly have different currency codes, the rounding rules set there for 2 decimal places for the rest of the company would end up with correct financial figures on rounded values, but you just see an additional 0 at the end of the figures which does not sound to be too bad.

    If 3 decimal places was just a business decision and has no real impact, ditch that and make the implementation uniform with 2 decimals.

    Anyways, please mark helpful answers as verified.

  • Suggested answer
    guk1964 Profile Picture
    10,888 on at

    Echoing the above comment, I  suggest contact a partner that has already done this in the region.

  • Vilmos Kintera Profile Picture
    46,149 on at

    If the answers above have resolved your issue, take your time to tick the checkbox next to the helpful posts to close the topic.

  • Olivier Massonnat Profile Picture
    on at

    Hi, we are facing the same problem with a Customer on D365 Operations... We are running D365 on multiple countries and telling that it is all or nothing is not an answer for a supposed to be multi-country multi-entity ERP.

    And this is not a localisation issu, as any country in the world can for example open an account in TND (Tunisian Diram) which is a 3 decimal currency (ISO).

    Therefore, if you setup a bank account in TND you should be able to post 3 decimal amounts, PR, PO, Invoice, Payement and also do Bank reconciliation on 3 decimal. Or at least, we should be able to update the Extended Data Type for a single entity or country.

    If anyone knows how please help !

  • Suggested answer
    guk1964 Profile Picture
    10,888 on at

    This has been a problem for Ax since the start.

    You have to either have a separate instance for 3 dec places and then consolidate, or live with the same  dec places for all,  or write branching code.

    I agree neither is satisfactory - I have had too many discussion with Microsoft that have fallen on deaf ears.

  • Mohammed Rayyan Profile Picture
    1 on at

    I think if we able to increases the Decimals places for 3, then we can round the local currency for 2 decimals and the other currencies for 3.

    But the questions is how to make it 3 decimals in D365 ???!!

  • Ludwig Reinhard Profile Picture
    Microsoft Employee on at

    Hello Rayyan,

    For which currency do you need 3 decimal places?

    What is the process that requires those 3 decimal places?

    Best regards,

    Ludwig

  • guk1964 Profile Picture
    10,888 on at

    Vilmos has given the answer - basically there is a lot of work to do- and its best to contact a partner with the relevant experience.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Priya_K Profile Picture

Priya_K 4

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans