This is a bazaar case. Can Adagio automatically reverse an entry without assistance?

A client has noticed this twice now. The first time they manually did the corrections but it has happened again and it is surely going to be a nuisance if we don't know why this is happening and a way to prevent it.

The client noticed that a batch or batches have been reversed without anyone doing the reversing themselves. November Inventory receipts, adjustments etc were reversed on December 1st. (Please see reversed transactions and description attached)

Can anyone help with this, or let me know if it’s a tech support issue so we can get this rectified at quickly as possible. It is only happening with transactions from Inventory and Order Entry

Version Running is Ledger 9.0D, Inventroy 8.1D, Order Entry 8.1E

Adagio Ledger has an option on the batch to 'auto-reverse' the amounts for the subsequent fiscal period. You can see this by clicking the Rename button on any batch. It appears that this option has been set on some batches, and I don't belive that retrieval from sub-ledgers does this.

The next time batches are retrieved, don't post any of them as part of the retrieve process and look at each one from the Rename screen. Do any of the retreived batches have the auto-reverse property enabled?

I looked at the retrieved batch once you go to rename that option to auto-reverse is not present so it doesn't allow you to auto-reverse retrieved batches.

Hmmm, I would really have expected "auto reverse" to be the culprit here as I can't think of any other way that a user could get this to happen "without them knowing/remembering" that they had caused it. For instance, though the batch could be copied with the "reverse entries" option ticked, this would have created a new batch and they would have had to post it and at some point in the process I think they would have realized that something was awry.

If they print batch listings check the header for the auto reverse status of the batch. Also, if memory serves me well, if the batch posted with the status enabled, this should mean that the original entries and the system generated auto reverse entries should be in the "same" posting journal.

I'm also remembering something about not being able to auto reverse in the last period of the fiscal year so bear that in mind as you troubleshoot.

Best regards, Pete

Could the user have used Provisonal posting?

Provisionlly posted batches automatically "reverse out" with the new posting.

This can be disabled in the Company profile.

Provisional posting isn't enabled, and as discussed before these are sub-ledger transactions retrieved into the GL.

Hello:
The first step in your investigation is to look at the characteristics of the batch(es). Which batch did those reversed transactions belong to? What about the original transactions - same batch or different? What posting sequence(s)?

Then go to Inquiries | View Batch Status. Add columns to display "Auto-reverse", "Ledger", "Date created", "Date last edited" and "Last edited by user". What does that tell you about the batch(es) in question? If Auto-reverse = "Yes" and Ledger = "IC", then take a copy of the client's data and see if you can reproduce that circumstance. Ask them what procedures they follow.

Hi Bruce,
As I had already checked the first part of your suggestion I went on to the second part. I checked the batch status and added the columns as you said and noticed that the sub-ledger batches in question did indeed have YES under auto-reversing, however there were some batches to retrieve and so we did but those are saying NO under auto-reversing.

The client claims to only have retrieved the batches checked them then post, same procedure they always do however this issue has just started it occured once in October nothing in November and now in December nothing in January.

We could not replicate the issue.

I bet someone checked the box, just to see what it did!

LOL Andrew, but the thing about it is that the option to auto-reverse isn't available once the batch has been retrieved.....I asked them the same question if someone enabled it by mistake.

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.