I posted about this in the partner portal.  Basically support say fiscal year has to be created before doing a reversing entry.  You have to reinitialize GL_PeriodPostingHistory AND run recalculate account balances to fix it.  there is a knowledge base article on that but doesn't say the cause was not having a fiscal year created before doing a reversing entry.

i have a support call and requested it be escalated because I see this as a bug.

Interesting - never had that happen before, but timing is everything, I guess.  I manually fixed the records - never thought about reinitializing the GL_PeriodPostingHistory file (shriek!).  I agree, it's a bug - either the FIscal calendar gets created no matter what tries to use the year, or it doesn't.  AND it's a little more suspicious than that - it also seemed to post CORRECTLY, as well, so it's like it posts twice.

I have used sage for 20 years and this is the first year i have had the issue. But according to support it has always been that way.

If it's always been that way, then it has always been broken. 

We saw this last year once, and a few times already this year.  Reversing entries at year end are a normal business practice, and the repeatable pattern producing bad results should be easy enough to program a fix.

I'm not sure it's worthy of a hotfix (because the correction steps are not too painful), but certainly should be fixed in a PU for supported versions (and in v2021+).

We'll take a look at this. 

John Nichols

Sage

We'll take a look at this. 

John Nichols

Sage