Whenever money amounts are entered into the system, it's important that it's done correctly.
To insure this, ALL money-related transactions in Lynx are entered in "batches" even if it's only one transaction). A batch is defined as a group of like-type transactions. Typically, a batch would be such things as all of the receipts for a day, all of the deliveries for a truck for a day, etc.
How big should a batch be? The rule of thumb is that a batch should be small enough that finding an error is not too burdensome but big enough that you don't have an unreasonable number of batches to deal with.
Experience has shown that a good batch size is about 25 transactions.
The typical sequence of events for batch processing:
1. Group together the batch of like-type transactions to be entered.
2. Run an adding machine tape to get a control total for the batch.
3. Enter each of the transactions in the batch into the system.
4. Check the control total with the equivalent total generated by the system.
5. If there's a difference, go back through each transaction until you find the problem.
6. Key in the correction (thereby generating a new control total).
7. Repeat this until the batch balances.