There is a way to resolve this...

RESOLUTION:
If you print and clear the batch status report, yet period end processing is detecting information in the file, this is an indication that there is still un-cleared information in the file. The easiest thing to try first is forward dating Cashbook when you open the program (to a date after the problem batch(es)), and try printing/clearing the batch status report again.

If this does not work, then it could be that the batch control file still contains entries although they are not printing on the report. Following are procedures to rectify this by replacing the damaged batch control files and creating a dummy CB dataset...

To replace a damaged set of Batch control files:
Before you replace the batch control files and remove the corrupt batches, make a backup of the data.
1. Print a Batch Status report for your records. When the Batch Status files are replaced, this information will be lost.
2. Once you have a backup, remove the batch and batch control files. This is the list of files, bc represents the Cashbook bank code and XXX represents the data extension:

CBbcBTI1.XXX - Batch Control File 1 - index
CBbcBTI2.XXX - Batch Control File 2 - index
CBbcBTCR.XXX - Batch Control File - random
CBbcInnn.XXX - Batch File Name - index
CBbcRnnn.XXX - Batch File Name - random

3. Rename the data files for the bank code.
4. You must then create a dummy Cashbook using the original bank code.
5. Copy the empty batch control files to the renamed dataset.
6. Delete the dummy dataset.
7. Rename the live data back to the original data extension.
8. Do a data integrity check again to ensure all is well.

Hope this helps!