Not sure why you get this message if the check is really in back services for this bank. Generate an RvSpy log and we would be glad to review it. [email protected]

I have the same issue how did you fix it?

unfortunately we haven't found a way to prevent the problem. We just have to print the checks to blank paper and print them again.

unfortunately we haven't found a way to prevent the problem. We just have to print the checks to blank paper and print them again.

Possible causes:
1) Database indexes need rebuilding --> SQL or DB Dump / Load. This can be tested by checking to see if the Check / Serial / Bank do in fact exist in the Bank table

2) Person posting A/P batches doesn't have required permissions to insert / update the bank record or status --> try running as ADMIN to ensure this isn't the case

3) Long shot, but I've seen odd things happen when G/L Security is used to restrict access to certain accounts which may allow processing in one module but block in another

Suggested approach:
1) Backup database
2) Run Data Integrity with fix option on - BUT not selecting to delete orphan records
3) Dump / Load the database
4) At this point, you're down to the forensic level of examining rv / db spy logs

Best of luck!