Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics GP (Archived)

Wrong Posting Type for Closed Year

Posted on by 20

I have a situation in which a profit/loss account was setup with the wrong posting type (Balance Sheet instead of Profit/Loss) and was posted to a closed year (2008).  It caused a beginning balance to be brought over for the expense account in 2009.  How can I correct the beginning balance in 2009 in Great Plains?  When I try to create a journal entry for 12/31/2008 to correct this, I get an message that says I can't post more than one year prior to the first day of the earliest open year.

*This post is locked for comments

  • L Vail Profile Picture
    L Vail 65,271 on at
    Re: Re: Re: Re: Wrong Posting Type for Closed Year

    Hi Mike,

    Check out the Fiscal Period Modifier, it doesn't 'roll up' like a regular history trx, but it's very helpful if you need to go back and 'fix' things.

    Let me know what you think!

    Leslie

  • Re: Re: Re: Wrong Posting Type for Closed Year

    Hi Leslie,

    I don't think KB 864913 will work because she has closed two years and the system will only allow posting to one year of history.  Do you know the name of the tool in PSTL that might be able to fix this issue?  I typically have had to run queries on the back end for my clients (unsupported, I know) so if there's a tool for it, that would be great.

    Thanks,
    Mike

     

  • L Vail Profile Picture
    L Vail 65,271 on at
    Re: Re: Wrong Posting Type for Closed Year

    Have you tried the procedure described in KB 864913? Do you own the PSTL tools? There is a tool in there that I think will fix your problem regarding the open/closed year issues.

    Kind regards,

    Leslie

  • Re: Wrong Posting Type for Closed Year

    Hi Maria,

     As you've found, GP only allows posting to one year of history.  Since both 2008 and 2009 are closed, you can only post entries to 2009 and so would not be able to fix the issue in 2008 properly through GP itself.  It is possible to fix the issue on the back end database.  This is something you should work with your partner or Microsoft support on as it involves manipulating your data and is very risky. 

    Thanks,
    Mike

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!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

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

#2
Martin Dráb Profile Picture

Martin Dráb 230,198 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans