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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Creating 2017 in the W...
Microsoft Dynamics GP (Archived)

Creating 2017 in the Wrong Year.

(0) ShareShare
ReportReport
Posted on by Mark Lindgren 490

Have a client that create period 2017 in year 2012.

They forgot to create a new year.  They took the default year which is 2012 and change the first day of the year to 01/01/2017 and last day of the year 12/31/2017.

They then posted some GL transaction with transaction Dates of January 2017. Jan 3rd 7th and so on.

We then made the correction to year 2012 and recreated 2012 for Jan 1, 2012 and last day 12/31/2012.

We also created the new year with Jan 1,2017  and last day 12/31/2017.

We then ran reconcile, in GL utilities,  to the year 2012, 2016, and 2017.

The transactions are still in year 2012. The reconcile said to transfer them.

Can we transfer the 2017 Transaction stuck in year 2012 to year 2107?

If not can we close the year with them there?  Do we need to delete them?

Thank You,

MSL

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Bill Campbell Profile Picture
    Bill Campbell 12 on at

    Mark question for you - how many transactions are we looking at?  

    I know that if I have a JE that was entered to the wrong period in the GL then I would use the Correcting feature in the GL Transaction entry screen.  

    You open the Transaction entry window - General Transactions - click on Correct (top ribbon bar) and then follow the direction provided.  I would think that you would want to choose the action - back out and create new.  Then enter the JE Year and the Number - the JE is then presented on the screen and you then enter the (1) the back out date - should already be there (2) enter the new posting date.

    Post updates here along the way, and be sure to send us the results here and let us know what you did to resolve this matter.

  • L Vail Profile Picture
    L Vail 65,271 on at

    What happened to 2013, 2014, and 2015? Also, was 2012 a closed year? How about the others?

    Kind regards,

    Leslie

  • Verified answer
    Mark Lindgren Profile Picture
    Mark Lindgren 490 on at

    Bill and Leslie,

    Thank You for your responses.

    I hate forgetting the little things, but yes 2012,2013, 2014, and 2015 are historical years.

    We corrected the fiscal periods.

    Bill, we could not make correction in GL transactions because 2012 is a historical year.

    Microsoft support suggested we reopen each year back to 2012 then make the correction in GL transactions, and reclose each year.

    We declined that option, even though it probably would have worked.

    We chose to delete the dated 2017 entries in the bucket year 2012 and run a reconcile for 2012.

    We reversed out the 2015 year end transactions.

    We then reentered  the 2017 entries in the year 2017.

    Everything is back to normal.

    Hope I didn't forget anything.

    Thank You,

    MSL

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…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Community Member Profile Picture

Community Member 4

#2
Victoria Yudin Profile Picture

Victoria Yudin 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans