Year accidentally closed - prematurely

(0) Share

Report

Posted on by Q Factor

107

One of my customers closed his year 2010 (GL) eight months early, thinking that he had not yet closed 2009. I will be paying a visit to clean this up next week, but wanted to see if anyone here has had to "reverse close" a year, and what steps were taken to complete this. My first step will be to see if we can restore a backup from last Thursday, before he ran the closing process. Because this client does not have an IT department, their backups don't run sometimes, so I can't put all of my faith in the existence of a good backup. So I'm thinking that I'll need to do some SQL surgery to correct this issue. Most likely, I'll need to set the value that tells the system the year is closed on the Fiscal Periods Setup window. I'll then need to move 2010 transactions from the GL30000 to the GL20000 table, and the respective summary tables. I'm hoping this will be sufficient and I will then be able to run checklinks and reconciles to put all the transactions into their proper buckets. Any further advice would be welcome! Constance

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (0)

Victoria Yudin 22,768 on at

Like (0)

Report

Re: Year accidentally closed - prematurely

If a restore from a backup is not an option, I strongly recommend paying Microsoft Professional Services to re-open the year for your customer. They have a process already worked out and tested to do this and it will take all the guess work out of it for you. We have had them do this for various customers over the past few years without any problems

Was this reply helpful? Yes No
Q Factor 107 on at

Like (0)

Report

Re: Re: Year accidentally closed - prematurely

Hi, Victoria: Do you know what the fee is for professional services to do this? Thanks, Constance

Was this reply helpful? Yes No
Victoria Yudin 22,768 on at

Like (0)

Report

Re: Re: Re: Year accidentally closed - prematurely

Hi Constance,

The fee depends on the size and number of companies as well as the turnaround needed. For most of our clients, even with multiple companies, the whole process took no more than an hour or two.

Was this reply helpful? Yes No
Q Factor 107 on at

Like (0)

Report

Re: Re: Re: Re: Year accidentally closed - prematurely

Yes, I suspect they have scripts to move the data, but since this is GL only, there are only 4 tables affected by the close. Thanks!

Was this reply helpful? Yes No
Richard Whaley 25,195 on at

Like (0)

Report

Re: Re: Re: Re: Re: Year accidentally closed - prematurely

Yes but how many GL accounts were affected? I vote with Victoria, call MSPS

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

RE: Year accidentally closed - prematurely

I have closed the year premeaturely and need it corrected. Can someone direct me to a link to MSPS? Tried looking for it but found a bunch of support for software MS sells to professionals like attorneys and CPAs.

Was this reply helpful? Yes No
L Vail 65,271 on at

Like (0)

Report

RE: Year accidentally closed - prematurely

I'm normally the last guy on the list to entertain back end adjustments such as you suggest. But as the years have gone by, I have needed to do it. The gl is pretty easy so long as you're not using MDA, inter company, multicurrency or Analytical accounting. Be careful with your Dex IDs.

I have normally done it using table import because it doesn't check business logic. First, I open the year using the pstl tool. PsTL does not move the trx back the open tables, however. Then you have import into open table. Once that works, remove the records from the history tables. I actually remove from the history table first so that I do not run into duplicate key issues. You will want to make sure you change the last closed date also.

It's not rocket science, but you need to have a clear and convincing reason to approach this kind of file surgery. I recommend you seek counsel with an experienced consultant or use Microsoft services to get it done. Many of my trusted colleagues have given you that suggested path.

Also consider any effect this might have on your subsidiary ledgers.

Kind regards and Godspeed!

Leslie vail

Leslie

Was this reply helpful? Yes No