Hi
we are using A/P 9.2A (150310) - we do not use the Bank Rec module.

I've just processed a cheque reversal. When I enter the vendor's account, the reversed cheque appears, but the original invoice has disappeared, and the outstanding balance does not reflect the amount owing on this invoice.

I had Adagio backup the data then performed a DIC, which came back with 2 errors. Then performed a rebuild, which has come back clean, but this one invoice has gone missing.

When I preview the G/L Transactions detail, the cheque appears as a debit to cash, and a credit to A/P control. The a/p reconciled checks posting journal shows the reversal and the orginal invoice number correctly.

Do I need to submit my data for repair, or does anyone have any ideas how to fix this?

The only band-aid solution that comes to my mind is to simply re-enter the invoice with a slightly modified invoice number, and move on. This might fix my immediate issue, but what if there's a software problem?

Marc:

There is a known issue with reversing cheques when the transactions are in history. Hopefully you have a pre-reversal backup that you can restore, as the transaction is gone I'm not sure if the data can be repaired. Alternatively your Adagio consultant can help you sort this out with a manual entry.

Hopefully we will have a fix soon. In the mean time my recommendation is to not run period end in AP until this is fixed.

Hi Marc,

We became aware of a problem when a check is reversed and the invoice to be re-instated is in history on Monday. We will have a Service Pack fixing this issue next week.

In order to resolve the problem, re-enter the invoices that have disappeared and use the AP Clearing account as the expense entry. This will re-instate the invoice in the Payables subledger without affecting the GL. (You may need to enable the "Post to control account" option in the Company Profile in order to enter these invoices.)

I'm sorry for the inconvenience.

Thanks Andrew.
Will do the adjustment as suggested.

A Service Pack has been published that resolves this issue.

Thank you for your patience.