A possible cause of out of balance batches is trying to delete a batch from an interfacing application. For example, Payroll only sends the debit entries (costs) to Job Cost, so using change entries to reverse a Payroll batch will create an out of batch that is sent to General Ledger. It is better to use Enter Direct Costs and reverse the costs with a GL only line for the credit side of the entry. Before using change entries to delete a batch from an interfacing application, check the batch to determine if the debits equal the credits by running inquiry by batch, finding the batch, drill into the transactions for that batch and add the columns for debit and credit. If they do not balance, then you must use Enter Direct Costs to reverse the costs from the job and make sure to enter debits and credits.

1. From the General Ledger File menu, select Company Settings, GL Settings.
2. Click Processing Options and change the Force Zero Proof setting to No.
3. Correct the out of balance batch by either entering a one sided entry in General Ledger or entering the missing entries in Job cost, Tasks, Enter Direct Costs.
4. Post entries in General Ledger. In the Ranges Select the original out of balance batch and your correction batch and check the box to "Post out of balance batches".
5. Click Processing Options and change the Force Zero Proof setting back to original proof setting.