Good day to you all,

I hope this post finds you all well and in Vancouver, well equipped for old man winter as we have cold and snow!

Something really odd happened this week.

One of our staff ran the cheques in the usual manner but suddenly adjustments from 2001 starting to print on the information section of the cheque.

I am not too sure what they clicked / changed to make this happen.

Thank you all and,

Cheers, JK

John:

Version of AP?
Is Data Integrity Check clean?

This is not a known problem.

Hi,
Actually we have seen this before, and seems to be related to the AP history, and data integrity, after doing AP upgrades.

Not sure as to the actual steps that gave rise to this situation, but our suggestion is to backup AP data, Run Data Integrity, and then do a Period End to flush old (very old) transactions that are still sitting in the Current Transactions file into the AP transaction history. For the cutoff date choose a date that is say 90 days ago from your last month end, and don't clear the AP history (unless you are comfortable with the clearing date). Normally, the situation of not running the Period End means that the site doesn't like to clear history or are unsure of what the Period End will do to the History clearing prompts.

Most situations that we have seen had not run the AP Period End or Year End for a while, so doing this function should flush the old transactions out and will fix the stub details from the cheque run.

Happy Holidays!
Brian

Thank you both for your replies and especially Brian for the detailed explanation.

I will report back to this thread once we move forward.

Again, thank you and,

Cheers, JK

I've passed this on to John, but it doesn't hurt to put a line under the conversation here...

It looks like something bad happened during a previous period end, I'm guessing old details showed up because their 'matched' entries had gone to history and they hadn't.

I was able to correct things by:
1. Running a period end. This brought up a number of error messages stating that the record already exists in history..."ok" through them.
2. Run the integrity check. There were errors regarding transaction counts.
3. Rebuild to correct the transaction counts.