Hi Lars,

The first thing to check is what the Data Integrity check shows.

The second thing I would check is to make sure the client doesn't have any orphan batch files around in the data. If the batch control wants to create the next batch (say #123), then the data file GL000123I.dat should not exist. But if it does then the program naturally would get confused.

Take a look at the data with Windows Explorer and if you see any batch data files at least a year old, they probably shouldn't be there.

In the case of manual batch entry (journal entries, say) then Adagio will skip orphaned batch files and create the next one it can (which will result in missing batch numbers on the batch status report).