1. If this is a new batch, skip to step 2. Or if the gift batch is already committed and you're needing an exception batch, open the batch and go to Tools > Edit batch set-up > mark Batch is recurring > click Data Entry.
  2. When ready to commit a gift batch, go to File > Commit completed batch (NOTE: If this a batch of credit cards or direct debits, be sure to charge credit cards and authorize direct debits first! Committing a batch does not charge credit cards or authorize direct debits.)
  3. In the new Commit Gift Batch window, mark, mark Create a new batch of exceptions:
    Commit gift batch setup
  4. Review other batch options as needed.
  5. Ciick Commit Now and follow the prompts to complete the commit.
  6. On the final Commit Complete screen, look for the Exceptions count number. A count greater than 0 (zero) means an exception batch created. If it's more than 0 (zero), click Exception Report:
    Commit complete information
  7. Print or save the Exception Report for the batch. This says why a gift could not commit so it can be fixed in the exception batch. The batch number for the new exception batch is at the top left:
    Batch exception report
  8. Close the report and the Commit Complete screen.
  9. Return to batch to locate the newly created exception batch. The description will say "Exceptions from batch ###" where ### is the batch the gifts excepted out of:  Batch list with exception batch
  10. Open the exception batch. Use the Batch Exception Report to update records as needed to correct the reason the gift did not commit.
  11. Optionally, repeat steps 2 through 10 until no exceptions list in step 6 and Exception Report button is grayed out.

Additional notes
  • The exceptions are generated by there being a rejection code in the rejection code column. If rejection codes do not populate, add rejection codes to generate the exception batch.
  • If a gift output query is generated at the commit, only gifts that successfully commit are in the query. Any gifts included in the new batch of exceptions are not included in the output query from the original batch.
  • The gift type cannot be changed exception batches that come from batches generated using the EFT module.
  • If the exception batch contains credit cards and direct debits that were rejected, charge credit cards and authorize direct debits from the exception batch. Committing a batch does not charge credit cards or authorize direct debits.
  • If the batch was originally generated using the EFT module and a gift is declined after several attempts to charge credit cards and authorize direct debits, delete that row from the latest exception batch to remove the Transaction Pending flag.
NOTE: If a Batch of Exceptions is created when using the EFT module to Automatically Generate Transactions and the batch was committed, this will place a Pending Transaction Flag on each gift in the Batch of Exceptions.  This will prevent the Pledge or Recurring Gift from being brought into any other batches and will prevent other Cash gifts being applied to the Pledge or Recurring Gift with a Pending Transaction.