For everyone reading this thread, we've pinpointed the sequence of steps required to cause the data corruption, so that you can avoid this until a service pack is released that fixes this, which we hope to be this week.

- User A prints the detail listing report (and the GLNUMB data files are not correctly released).
- User B posts one or more batches.
- User A posts one or more batches that have some accounts the same as what user B posted to. It is this step that causes the corruption.

Because the GLNUMB files were not released, it was behaving in the same way like in the old days when Opportunistic Locking was enabled. The posting done by user A was updating the Net Changes files from the starting point of when the report was printed, not from after the batches user B posted.

Thanks for your patience as we work to get the service pack completed and released.

The Ledger 9.3B (2021.03.31) service pack has been released, which fixes this issue. We apologize for the inconvenience and issues that this problem has caused.

Thanks support. Loaded on said client this morning and holding breath.