Hi Raymond:

To my knowledge, this has never been resolved. nor is there any indication from Sage development that there are plans to improve the process.  We have one Bank Account for both our AP payments & AR deposits.  It's been a procedural bottleneck for both the AP and AR departments for years.  Our experience has been that only one user can be writing to the Bank Account Register file at a time.  With some Sage tasks, if one user is locking the file, the process initiated by another user will queue up and process when the lock is lifted.  This has not been our experience in this situation. 

When two or more users are accessing the Bank register (simultaneous AP check runs, AR deposit, or attempting to reconcile), we have experienced total system lockups, aborts, extremely slow processing (Background Tasks freezes at 0% complete for extended periods), or entries that eventually process, but don't post (rejected as "file in use", but can be posted in the respective modules afterward), or any combination thereof.  On occasion a multi-task will process, but it appears to be based on the luck of a rare split-second timing.

If the Bank Accounts are different, but they are sharing the same Register file, this doesn't seem to be as much of an issue.  It seems to be tied to a single Bank Account sharing the same Register.  The nearest workaround we have come up with is creating a MS Team for AP & AR.  If an AP specialist is starting a check run, they use the chat to inform the other members they will be "in the bank", then inform the rest of the Team when they are finished.

Thanks Glen!  I appreciate you taking the time to respond.