When receiving recurring gift transactions or pledge payments using a direct debit, you can send a prenotification to the sponsoring bank. A prenotification verifies that the electronic transfer is set up properly, but it does not actually transfer the funds from the donor's account.
Note: The Prenotify button is only available for U.S. versions of The Raiser's Edge.
1. To include prenotifications for existing records in the batch, you must have several items entered on the constituent's existing gift record:
a. Specify a payment method of Direct Debit
b. Mark the EFT? checkbox to include electronic payments (direct debit or credit card) when you use the Automatically Generate Transactions/Payments menu option in a batch
c. Select Active in the Status field if the gift is a pledge or recurring gift
2. Click the Prenotify button to set up a prenotification
3. Mark the Send prenotification checkbox and specify the number of days to prenotify the bank of your transactions. The prenotification must be sent at least ten days prior to the live transaction of funds from the donor.
4. Once you automatically generate payments for the pledges and recurring gifts in the database, you can view gifts in the batch that need a prenotification sent to the bank. Remember that prenotifications do not appear in the batch.
5. Prenotifications are processed using a transmission file. In the transmission file, you can include prenotifications for pledges or recurring gifts and requests for live transactions as long as the prenotifications and requests for live transactions are for different pledges or recurring gifts. You cannot process a prenotification and a live transaction for the same gift in the transmission file.
6. If a prenotification and a live transaction are included in a batch for the same pledge or recurring gift, a screen appears when you create a transmission file. From the screen, you can choose whether to process the prenotification or the live transaction for the gift. Mark either the Remove live or Remove prenote checkbox and click Remove Now.
7. Once you decide what to include in the transmission file, you can now send the transmission file to the sponsoring bank via floppy disk or email attachment. You and your bank should decide the best way to communicate this information.
8. If, in the transmission file, you include requests for live transactions, The Raiser's Edge detects if rejection codes are entered for the pledge and recurring gift payments included in the transmission file. The Raiser's Edge will include in the transmission file only pledge or recurring gift payments from the batch with a blank Rejection code field.
9. The sponsoring bank then sends the transmission file back to you. If you included requests for live transactions in your transmission file, you can now commit those transaction payments to the database. If you sent prenotifications in the transmission file, and there are gift payments that do not have valid account numbers, you can open the batch and add any information you want in the Rejection code field of a batch to specify that a gift has been rejected. For example, if you enter “Gift Rejected” in the Rejection code field, a message appears asking you to add the information to the Rejection Codes table for the Rejection code field.
10. As long as the Rejection code field for a gift has an entry, The Raiser’s Edge will not commit that gift to the database.