Today I unposted a batch which was posted earlier in the day. The unposted batch presents in a very different order than the original batch. It looks like the batch is now loosely sorted numerically by GL account number, whereas the original batch was a cheque batch entered in cheque order. We recently installed PTF AL8.0 (2004.02.23). What happened? To be useful, the unpost function must leave the original batch in the original order.

Hi Anneli,

The Unpost Batch function looks at the GL Posted Transactions file to rebuild and generate the new batch. Within this data file is a Batch Number and Entry Number, which are both used to rebuild the new batch. Within each batch entry are Lines (one per GL account) that are basically the lowest level detail. This Line number is not stored in the GL Posted Transaction File, so there is no way for the Unpost function to be able to have the Lines within an Entry sorted in identically the same way they were before posting. The Entries will be sorted as before, but not necessarily the Lines within.

What this means is that the Generated Batch created by Unposting will be sorted by Account/Dept code within each entry. It does not use the Reference, Description or any other field within the batch.

So if I understand from your question, the Lines within an Entry were sorted by Check Number, but now that the Lines have been generated in Account order, the check numbers are no longer in sequence. I do not believe that Unpost can sort Lines in any way apart from account/dept order.

If I am wrong in my evaluation of your question, could you provide some specifics as to the original batch and the Unpost-generated batch? Perhaps something like:

In Batch 3 and Entry 1, Line 1 was for account 5000 and chk#123. Line 2 was for account 1000 and chk#123. Line 3 was for account 5000 and chk#124. Line 4 was for account 1000 and chk#124. When Unposting this batch, the lines for account 1000 were listed first, followed by the lines for account 5000.

Hello Anneli French,

To be useful, the unpost function must leave the original batch in the original order.

I'm confused. Could you explain why this function is only useful if the batch order is preserved?

The original batch was a cheque batch and the cheques were entered in numeric order. As we do not use AP for this particular branch, bank reconciliations are done using the original batch. As the cheques are no longer in numeric order (and most cheques include 2-4 lines of entry), reconciling the bank becomes very time consuming.

Hello Anneli French,

OK - but why were you unposting the batch? If you needed to list those transactions, you could either print a GL Detail Listing sorted in reference sequence, or a Source Journal, choosing the sequence and fields you needed.

Also, why not use AP for this bank, even if you are not entering invoices. You could record these all as miscellaneous payments (and do the required gl distribution) in Payables, then use its cheque reconciliation function.

Further to the above reply, I don't mean to sound ungrateful. I am delighted with Adagio so far and I do understand the difficulty in trying to please everyone all the time. I was thrilled to be able to unpost at all, as sometimes batches don't get adequately reviewed before posting. Regarding the batch I unposted, this was maybe unusual in that the order was important to me, but now I know. Thanks for all you do!!!

Hello Anneli French,

Well, I'm happy that you're a happy customer.

You might like to take a look at the two reports I mentioned. They might have allowed you to check the bank reconciliation without having to unpost. Also, consider doing these entries through Payables, even though you are never printing cheques (it appears). The entry might still be easier. Just set up a separate "bank" or control account for these entries to make it easy to keep them separate.