Transaction Control

In general, the term "Transaction Control" means maintaining an audit trail of transactions that are entered and posted in an application. The system offers different ways to maintain the audit trail. Regardless of which method you choose, all transactions will be entered, printed on journals, and posted by Operator ID and Control Number. Beyond that, you have several options which provide the following alternatives:

1. The Operator ID and Control Number for each group of transactions will be automatically assigned and cannot be changed. The system will not allow any operator to edit another operator's transactions. No control or hash totals will be kept, and no data will be posted to the Transaction Control file.
2. The Operator ID and Control Number for each group of transactions will be automatically assigned but Operator ID can be changed. In addition, any operator will be allowed to edit any other operator's transactions. No control or hash totals will be kept, and no data will be posted to the Transaction Control file.
3. The Operator ID and Control Number for each group of transactions will be automatically assigned but Operator ID can be changed. Here, the operator can optionally restrict access to his or her own transactions. In addition, control and hash totals can be entered and will be balanced against the sum of transactions and each control group can have a unique description. One record will be written to the Transaction Control file for each group of transactions posted, capturing pertinent details about the group. Transaction Control file contents can be printed on reports and/or viewed through an inquiry.

The third alternative described above will provide you with the highest level of transaction control. If desired, it is also possible to treat Operator ID as a user-assigned batch ID, provided the method you choose allows Operator ID to be changed.