Consolidated posting is turned on.
When entries are retrieved some of the entries are consolidated.

2 Questions:


1: We had to unpost a batch, however it was not allowed as there were consolidated entries - is there a way to consolidate and still be able to unpost. The only consolidation done is during retrieval, not using maintenance.

2: Also when the retrieval and consolidation is done the date that is used is the end on month (March 31, 2014 in this case). Is there a way to use today's date?

Thanks.

Hi Bill,

1) If the posted details are consolidated in any way, then unposting the associated batch(es) will not be possible. Reconstruction of the batch created through unposting requires information from the posted transaction detail, which is lost when consolidation occurs.

If all you want to do is 'restore' a posted batch, then you can use the Recover Batch process to create a copy of an already posted batch. Note that this will not remove the posted transaction details of the recovered batch (as unposting does).

2) There are no options to consolidate as part of the retrieval. Do you mean that the sub-ledger is consolidated by printing the G/L Transactions report within the respective sub-ledger? Or do you have particular accounts set to be posted Consolidated rather than in Detail, and you post batches as they are retrieved?

I tested with posting GL batches and consolidated accounts, and see that the last day of the fiscal period is used as the 'consolidated transaction date'. Because 'Today' could possibly be a date not in the fiscal period to which posted details are consolidated, I don't believe it would be correct to assign a date not in the fiscal period.

By the way, in today's age of cheap disk space, why are any accounts set to be consolidated? You have run into two drawbacks of doing so.

Bill:

We need to clarify which "consolidation" process you are referring to (there are 3). I interpret from your question that the consolidation happens in the subledger before retrieval to the Ledger. If that is the case, there are 5 options on how to consolidate. Two of them use the actual transaction date and one allows you to specify the date. If the consolidation occurs in the subledger, that batch, once posted in the Ledger, can be unposted like any other batch.

If the consolidation happens in the Ledger itself, using one of the other consolidation options, you cannot unpost the batch. I suspect that is what has happened in your case, based on Support's testing.