This has been happening quite often since upgrading to version 10.  After we 
close a month and re-open a new one, we have found many incidences of 
SALESRCT journal entries that have posted to the previous month AFTER it was 
closed, thus causing many accounting headaches.

If I take one as an example, the source doc shows GL, with reference 
SALESRCT083898.  It was an inventory and a COGS adjustment, which means it 
originated from sales, but the user that posted, is showing the AP clerk.

I assume this is due to an invoice posting with a cost variance for an item 
that was already sold?   Whatever the reason, I cannot locate either original 
document.  As well, why are these adjustments ignoring the modules being 
closed and if it was actually posted on April 16th, which the GL shows, why 
did it back date to 3/31 in the GL?

Hi,

This is the expected behavior, and it does have to do with revaluing 
inventory. If you change your tolerance, or just uncheck the box, the problem 
will go away. You will get a posting to the PPV account, but it will not try 
and back date the entry.

Kind regards,

Leslie

"Luvsql" wrote:

> This has been happening quite often since upgrading to version 10.  After we 
> close a month and re-open a new one, we have found many incidences of 
> SALESRCT journal entries that have posted to the previous month AFTER it was 
> closed, thus causing many accounting headaches.
> 
> If I take one as an example, the source doc shows GL, with reference 
> SALESRCT083898.  It was an inventory and a COGS adjustment, which means it 
> originated from sales, but the user that posted, is showing the AP clerk.
> 
> I assume this is due to an invoice posting with a cost variance for an item 
> that was already sold?   Whatever the reason, I cannot locate either original 
> document.  As well, why are these adjustments ignoring the modules being 
> closed and if it was actually posted on April 16th, which the GL shows, why 
> did it back date to 3/31 in the GL?