Hi Ishana,

The Payables 9.2A upgrade did not change the batches structure, thus nothing was converted in this area. We are not aware of any problems with batches, so I wonder if this problem may have pre-existed the conversion.

The values for the Next Batch numbers for each batch type are stored in the Company Profile. To investigate, you could point GridView at the data and the Payables 9.2A Company Profile table, and the fields for 'Next Inv Batch #', 'Next Manual Check #', and 'Next Adj Batch #'. If you find that these values already exist in the Payables batch control file, then the data is out of sync. Attempting to create a new batch would give the reported error because the 'Next batch #' is already in the control file and should not be in a normal data set.

Has Year End Processing been done, and was there an expectation that batch and posting numbers should have been reset to 1 and the batch control files cleared? If so, maybe the batch control file was locked on the server and not cleared.

Did you/they have to restore data from a backup? If so, was previous data cleared out before the restoration was performed? Not clearing out old data prior to a restore is a common reason for data being out of sync.

You'll need to determine the state of the data versus what it is expected to be before resolution suggestions can be made. Perhaps files need to be cleared/removed/restored. Perhaps GridView Read/Write is necessary to edit the Next Batch numbers. And so on.