Exception batch is blank after committing batch with rejection code exceptions

After committing a batch with rejection codes for some gifts and selecting to create an exception batch, users may find that exceptions from rejection codes are missing from the exception batch. 
This was resolved with a hotfix deployed to Blackbaud Hosting Services customers in early October 2018. 

Previous workarounds: OR
  • If the batch has already been committed and the gifts were not automatically generated:
  1. Open the original batch and mark it as recurring. How to create a recurring batch
  2. Export the batch to Excel if desired to keep a history of the transactions in the batch. To do this, right click on a row in the batch and select Export to Excel.
  3. While in the batch, go to Tools -> Sort and sort the batch based on the Rejection or Authorization code. This means that all rejections/authorizations are grouped together in the batch.
  4. Highlight each row in the batch that has been approved and delete the row. You can do this by right clicking on the highlighted row -> Delete. While gifts with Authorization Codes won't be re-charged, this prevents committing gifts that have already been committed to The Raiser’s Edge.
  5. Go to Tools -> Clear Declined Authorization and Rejection Codes and select Yes to the prompt. This is so you can re-submit the rejected transactions.
  6. Re-submit this batch to the payment processor via Tools -> Create EFT Transmission File
  7. For each successful transaction that should be applied to a pledge or recurring gift, highlight the row and go to Gift -> Apply To -> Pledge/Recurring Gift. 
  8. As needed, either correct any remaining Rejection Code gifts before returning to step 5, or recommit the batch and then return to step 2. 

Steps to Duplicate

  1. Process credit cards in a batch, returning at least one gift with rejection code. 
  2. Commit the batch, selecting the option to Create Exception Batch. 
  3. Once committed, see that the gift was an exception in the Exception Report. 
  4. Close the report. 
  5. Open the exception batch and see that the exception with rejection code is missing. 
  6. Go to the constituent record and see that the gift did not commit. 

Was this article helpful?

Thanks for your feedback! Did this solve your issue?

Comments (optional):

Thanks for your feedback!
We're glad it was helpful but sorry it didn’t solve your issue. If you need assistance, click Chat with Support below.
We’re sorry to hear that. Please tell us why.

 I don't like how this works.

 The answer is confusing.

 The answer didn't match what I was searching for.

Additional Comments (optional):

Thanks for your feedback! If you need assistance, click Chat with Support below.
Thanks for your feedback. Help us make our products even better by sharing details in our Idea Banks or our online Community.
Thanks for letting us know. We'll work on clarifying the information in the article. If you need assistance, click Chat with Support below.
Thanks for letting us know. We'll work on updating the search engine to return more relevant results.