Currently, the only way to restrict access to a batch is at the time the batch is created. Our company uses separate payment batches for checks, credit card payments and EFTs. Once the checks are printed we post, but with EFTs and credit cards, we print a pre-register for review by the controller then post the batch. Unfortunately, people have a bad habit of adding transactions to the EFT batch after the fact causing extra work for the person trying to post the batch - we match the totals to the original report signed by the controller.

We could really use a way to identify which batch is which kind so we don't accidentally put checks into an EFT batch too.