OK, now to figure out how that can happen. The only way I can auto-reverse a retrieved batch is to: i) create a new GL batch, ii) use the Copy function to copy the retrieved transactions from the original batch to this new batch, iii) the new batch can be auto-reversed. However the clue that this has happened is that the new batch shows "Ledger" = "GL" (though the transactions keep "IC"). Can you confirm that the "Ledger" column shows "IC" and not "GL" when looking at the batch list? I know that's an unlikely occurrence but we need to rule it out.

Here is a look at the batch status, what I am not seeing is the batch doing the reversal. As noted the original batches which you can see has the sub ledger Source however,it is saying auto reversed and the description states Retrieved.

You won't see a separate batch when "Auto-retrieve" is selected. But if you look at the posting journal, you will see both the original entries and the reversed entries.

Your screen shot leads me to conclude that the reversals aren't a result of user activity (well, they could manually append entries to the retrieved batches but that seems unlikely). At this point we have to look to Support for possible explanations.

Every batch has auto-reversing turned on! This is a first.

Someone needs to record a video or watch the Retrieve process to see what is going on. If this was happening elsewhere, we would have heard about it.

Well I myself did a retrieval and the auto-reversing status was NO so I really can't say what happened at the time with those that are saying YES. I will pass on to Support to see if they can do something so this doesn't happen again.

Until the behaviour is repeatable, there's little Support will be able to do. If you have a subledger with batches waiting to retrieve, you can backup the general ledger and the subledger and upload it to our web site and we'll take a brief look to see if something jumps out.

In any event, no harm will have been done. Unpost the batches, delete the reversing entries (they will be in the batch created by the unpost) and post them properly.