Skip to main content

Notifications

Microsoft Dynamics GP (Archived)

Multicurrency Revaluation- Fully applied transactions still outstanding on posting does not get revalued

Posted on by

Hi,

I have a question on the Multicurrency Revaluation in the Financial Management (Routines).

I noticed that the revaluation on both Sales and Purchasing Series does not revalue the outstanding invoices as at the revaluation date (posting date) if these transactions have been moved to history at time revaluation is run. Example, invoice outstanding of C$1,000 as at 31 Dec 2015. Payment applied on 15 January 2016. When user run revaluation on says, 31 January 2016 with posting date and Cutoff Document Date on 31 Dec 2015 , this invoice will not be revalued.

This should not be case as revaluation should applies to all outstanding invoices on the posting date eventhough they have been fully applied at the time revaluation is run.

Does anyone have any idea why is the inconsistency in how Dynamics GP works?

*This post is locked for comments

  • Joyce Wong Profile Picture
    Joyce Wong on at
    RE: Multicurrency Revaluation- Fully applied transactions still outstanding on posting does not get revalued

    Hi Pierre,

    Appreciate for your feedback. I agree that those are the few things we can at the moment. And thanks for suggesting to add this in Microsoft Connect. I have just done that.

    Thanks!

  • Verified answer
    Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Multicurrency Revaluation- Fully applied transactions still outstanding on posting does not get revalued

    Hi Joyce

    I've been using/implementing Dynamics GP since version 7.5 and this always been a problem. It is probably due to the structure of the tables of the Database and the way the stored procedure for the revaluation has been built. In the tables MC020102 and MC020103 which contains the multicurrency information for the receivables and for the payables there is no field to let the system know the date the invoice has been paid, that information is other tables, so what they probably did to calculate the unrealized revaluation is to use the cutoff date and the current originating transaction amount without looking for the paid date.

    The only things I can suggest :

    - Don't enter any payments until the revaluation is done for the sub-ledger

    - Don't revalue the sub-ledger, only revalue at the financial level

    - Go on the Microsoft Connect website and add the suggestion to fix this problem, at every service pack they are trying to include the top suggestions (https://connect.microsoft.com/dynamicssuggestions/feedback/CreateFeedback.aspx)

    Hope it helps

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Community AMA December 12th

Join us as we continue to demystify the Dynamics 365 Contact Center

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,253 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,188 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans