allow possible transactions from multiple-match constituents to be added to revenue batches with a validation error instead of excepting them out of the batch.

In importing transactions from a third-party credit card vendor for remote events, we often do not have more than the constituent name from the credit card transaction. If the name is common, the row does not get imported into the revenue batch but gets listed as an exception. The users have to then enter the entire row by hand. It would be better if the row could be added to the batch with a validation error for review and research. This would ensure the batches would balance and reconcile with the payments received. 

  • Corina Cervantes
  • Nov 16 2016
Organization Name (Please enter full organization name) Texas Christian University
Reported Version 4.0
  • Attach files