Gift Notification for back dated gifts

Erin Gyuleseryan

Hi All,

I have a nightly gift notification set up for our finance team to get notified of gifts entered “past 24 hours” using past time “date added on or after." What we're noticing is that if a credit card gift comes in and isn't processed by our gift entry team that same date, it is not pulling into the notification. I am worried about changing our past time back further than 24 hours if that means it will pull the same gift into multiple notifications. Have others had this problem and found a solution that works for you?

Thanks,

Erin

Alex Wong

@Erin Gyuleseryan
HI, this is likely b/c of RE NXT webview gift batch approval.

SO for example, if someone donated on 11/11/24, that goes into the webview gift batch. gift is not “real" yet, so when you do the notification, this gift is not included.

if you were to approval the batch on 11/12/24, the gift is now “real” but it has a date created of 11/11/24 (instead of it should be 11/12/24), your notification will not pick it up neither b/c it was added in older days (day of transaction instead of day of approval).

there's 2 ways to handle this:

1. approve webview gift batch same day (11:59PM)
2. create an automation for when gift is created (using webhook api), and when it is gift from webview gift batch, recreate a NEW gift (which will have the date of approval instead) and delete the old gift
   1. this is the route i took

Erin Gyuleseryan

@Alex Wong
Do you have screenshots of how you did the second option? I've not used webhook before.

Alex Wong

@Erin Gyuleseryan
https://community.blackbaud.com/forums/viewtopic/586/55393

how to do webhook

I suggest you wait for now and see what RE PUB say about this. BB is aware of this problem and in BBCON has told us that they are fixing this

Erin Gyuleseryan

@Alex Wong Thank you!

Candy Reichert

@Erin Gyuleseryan

I handle it in this way. Before the batch is approved I change it to Do Not Post. This removes the date posted. Then after the batch is approved I do a Global change to the Post date to the date that I took the batch to accounting.
I use Post Date to pull my list.

Erin Gyuleseryan

@Candy Reichert Thank you!

Dan Snyder

@Erin Gyuleseryan While they did not address this directly in the PUB yesterday @Alex Wong is 100% correct that BB is aware and they will be changing that. I'm hopeful it will be changed before the end of the year.

Erin Gyuleseryan

@Dan Snyder Thank you!

Catie Wools

@Erin Gyuleseryan Hi! I'd been having this exact issue and I think there's been an update!

If you use the “List Gifts” option in the connector (I've been using the general NXT one!!), they've added “Added on or after" as a parameter option!

The best way I have found it to work for me is to Initialize a variable, and then set it to one day behind whatever time it is that your trigger goes off, here is the code I've been using for the variable:

addDays(utcNow(),-1)

Then once that variable has been created and set, I use it as my filter for the Added on or after parameter!

Alex Wong

@Catie Wools
FYI: the “added on or after” has been there for a long time now. This does filter on gift date/time added.

However, the issue this post was talking about is the “error” in the date/time added that is recorded on the gift itself, which is the wrong date/time. If you do not use RE NXT webview batch, you will not have any issue using the “added on or after” filter on gift list. However, if you use RE NXT Donation form, JustGiving, Optimized donation form, etc that adds gift into RE NXT webview gift batch, then the problem exists as explained:

Catie Wools

@Alex Wong Ohh ok!! I had just seen it today when working on some flows, that's my bad!

And thank you for explaining why it wouldn't work for this issue, I do not do much with gift posting in my org so I thought that the issue was the same one I was having!! ?

Dan Snyder

@Anthony Gallo Any update on this change?

Anthony Gallo

@Dan Snyder
Very much trying to get this out. The team is working to finish the new automated pledge work. And this is next. We should get to this one very early in 2025 the way it looks right now.

Dan Snyder

@Anthony Gallo Thank you!