Finance | Project Operations, Human Resources, ...

Year-End Close Is "Messed Up" (I'd Use Another Descriptive Phrase, but There Are Probably Ladies Present)

(0) Share

Report

Posted on by john.ellis

3,530

Hi There:

The client's fiscal year is 12/01 - 11/30.

After they closed 2019 last year, the ending balance in Retained Earnings (R/E) was wrong. I wasn't "here" last year. So, I don't know what happened then. I'm surprised that that situation was not diffused, right away.

Anyway, they wanted this R/E issue resolved prior to closing 2020. So, since they are on an old version of GP, I could not use the Reverse Historical Year button. So, I followed the old KB article on reversing the P/L account that was incorrectly coded as a BS account.

Doing so fixed R/E. But, the "balance sheet" account had a balance.

So, I followed the steps in the KB article to zero-out the "balance sheet" account using a dummy account. I zeroed-out the "balance sheet" account", deleted the dummy account in SQL, and ran Financial Reconcile for the years.

Still, the trial balance was wrong. So, I then used that same KB article to create a one-sided entry to "empty out" the amount in the R/E account using a dummy account which I deleted.

I took care to make sure that the appropriate "history" boxes were unchecked, when necessary.

Then, we closed 2020 as of 11/30/2020.

The client says that, now, all of the beginning balances of the balance sheet accounts for 2021 are completely wrong.

Since he, again, does not have the Reverse Historical Year button, the only thing that I know to do now is to use the journal entry's "Correct" button to reverse some of the entries that we did.

Ultimately, he simply wants to correct the beginning balances of the balance sheet accounts for 2020 and 2021. Without going into the database and deleting GL30000 records for the year 2020 and running Financial Reconcile, I don't know what to do besides use the "Correct" button.

Anyway, come Monday, we are going to test the use of the "Correct" button in a test company with a copy of this data.

Short of all of this, if anyone has any ideas on how to fix this messed up issue on this old version of GP, please let me know.

Thank you! Much appreciated!

John

Categories:

Microsoft Dynamics GP

I have the same question (0)

All responses (6)

Answers (0)

Sort by

Leng Papio 855 on at

Like (0)

Report
Copy link

Link copied!

It is really difficult to give suggestions on something like this because from what you described, it looked like the last year end failed or had some issues.

I am familiar with doing an UNDO year end for older versions of GP (those that do not have the reverse undo feature); I've done it like 4 times already.

In one instance, we determined that a whole one month's transaction of the year being closed did not transfer to historical year... and they figured it out almost after 6 months. Good thing they had a backup of the before yearend data.

I think if you can find someone who can do an UNDO year end (not necessarily me) - this will be your best option, instead of addressing the symptoms.

Reach out if you need me to assist.

Good luck!

Was this reply helpful? Yes No
Suggested answer

Hokuminaria 2,950 on at

Like (0)

Report
Copy link

Link copied!

Hello John,

You are going to need to create a support case or locate someone who can do a Year End Close undo for you. You can also look at upgrading them to be on a version that has this process It was added in GP 2013 R2 and see if this process corrects the issue. One thing i would also like to point out is the Reverse Historical Year is not designed to fix failed closes. At times it can, but it is not guaranteed.

Depending on the version, if they are on anything prior to GP 2013, those version are no longer supported and would need to be on at least 2013 for a case with Microsoft.

We can undo your year end close if you want to create a case for this as the steps we use to do this are not handed out and require us to go through the process with you. This usually takes 10-20 minutes depending on the size of the database.

If you do decide to create a case, please let me know and i would be happy to pick it up and walk through the process with you.

Microsoft Support Engineer | Brandon Jarrett.

Was this reply helpful? Yes No
john.ellis 3,530 on at

Like (0)

Report
Copy link

Link copied!

Hi Brandon:

Yes, I would like to go over this with you. My firm has the "ability" to create an eSupport case. But, in order to have you show me this, is there something that I need to "specify"?

Thanks!

John

Was this reply helpful? Yes No
Hokuminaria 2,950 on at

Like (0)

Report
Copy link

Link copied!

Hey John,

You would need to create a support case using the link below.

serviceshub.microsoft.com/supportforbusiness

You can either request Brandon Jarrett in the Support Case Verbatim or feel free to email me the case number when it is created and i can grab it. You can email me at brjarret@microsoftsupport.com.

Thank you!

Microsoft Support Engineer | Brandon Jarrett.

Was this reply helpful? Yes No
john.ellis 3,530 on at

Like (0)

Report
Copy link

Link copied!

Hi Brandon:

Thanks!

I submitted the ticket and specified you.

John

Was this reply helpful? Yes No
Leng Papio 855 on at

Like (0)

Report
Copy link

Link copied!

John,

Just an advise,... know exactly what Microsoft will ask for this data fixing service. This is not charged against a usual support case.

The last time I was part of support when I got my MCP for GP - Financials version 2013 - the charge was 125/hour USD... this was a long time ago, and this process can't be done in only an hour.

Another thing you need to know is usually they schedule this depending on the availability of an Escalation engineer... it is usually NOT just over the weekend or next week.

When this is done, every transactions in GP must stop until the data is fixed... so usually the companies will opt for a weekend data fixing, which has a higher rate per hour.

I am not discouraging you on this. I am just giving you caution.

Your company seems to be in a hurry to get this fixed.

Scheduling a free Escalation engineer to do the data fixing is usually not easy... they are usually never idle...

Yes, Microsoft will not give out the documented steps on this because it is dangerous for ill-trained users to try.

Just like how Microsoft does not publish scripts. It has to be given out thru a support case, because the tech support needs to explain to the user how to properly use the script that potentially changes data.

I can offer this service because I used to be part of support and am very familiar with the financials tables (and have done this successfully outside Microsoft).

There may be other VAR who has the resource that can do this and not just Microsoft.

You need to know the cost and schedule aspect when you decide on this.

Again, good luck!

Was this reply helpful? Yes No