IO Batches - Correction: How to correct a closed batch posting that was added in error or for the wrong amount

How to correct a closed batch posting that was added in error or for the wrong amount

Once a batch has been closed, any postings in the batch may not be changed in any way. If the amount entered in the posting was incorrect or a posting was added that should not have been, the way to fix it is to create a reversing correction batch. This is different from our option to use the Correction Batch button in Contributions as there is no option there to reverse or change an amount. This is done through the normal batch routine.

How to create a reversing correction batch

In a new correction batch (given the same date and name (with "Correction" at the end):

  1. Open a new batch.
  2. Add postings using the guidelines as shown below.
  • To remove the contribution that should not have been posted, add a posting to the correction batch that has the same information as the original: date, donor, fund, and amount except make the amount negative.
    • These two entries that match exactly with the only difference being the minus sign on the removing entry will ensure the original and removing entry do not show up on the donor statement.
      Remove_Transaction.png
  • To correct the amount such as the original amount entered was 100 but should have been 10:
    • follow the exact steps in the first bullet which will remove the incorrect amount entered entirely from the donor's statement.
    • Then, add the new posting for the correct amount.
    • If you only add a posting that makes up the difference, both the incorrect posting and the correction posting will show on donor statements.

Related Articles

To correct information in a closed batch for Donor, Fund, Contribution Date, Contribution Type, Memo, and/or Tax-Deductible Flag, see  How to create a correction batch.

To add additional postings to an existing closed batch see How to add additional postings to a closed batch.

Have more questions? Submit a request

Comments

0 comments

Article is closed for comments.