What's New In Blackbaud Raiser's Edge NXT® — June 9, 2026

Any chance that Blackbaud is going to add more options to the Payment Methods table?

While the payment method over view is fine - though VERY easily extracted via a Query so doesn't really show anything new - it presents an incomplete picture since it shows only online gifts.

To truly understand donor giving behavior, customers need more options in the payment methods table to reflect modern giving, such as the various flavors of EFT payments like wires and ACH. I believe I have heard users talk about others too.

Maybe I missed this being migrated to NXT, but I am still waiting to be able to use NXT to post gifts directly from RE to FE (both are integrated here) without opening the RE database. I think the original timeline projection for this was late 2025. Is this already possible, or is the "Post to General Ledger" Admin function in the RE database still the only way to do this? Thanks!

We have been having data trouble with webview posting to FE and Anthony and team has been fixing bug that caused it.

I would be careful using this and really look at the entries in RE and FE when you start using it to ensure it is what you intend. (error like out of balance GL JE batch, different amount in credit vs debit, and mismatch amount from the RE post batch).

Yikes, thanks for the headsup, Alex. I was about to try this out, but maybe I should stick to the Database!

Still looking for the Validate (Pre-post) function, which is a dealbreaker if it no longer exists. We want all errors fixed in RE before we bring them over to FE.

I tried this in RE NXT and it leaves a lot to be desired, which I used to have available in the database (or simply don't make sense to me):

1) "Name" seems to be required. Whose name? It already knows that I am logged in.

2) The various settings and choices per posting batch are no longer sticky. I change almost all of them and have for years in RE Database, but they were sticky there. I rarely had to go in and re-set them all. In NXT, every choice has to be re-set with each new post. We post by GL Post date being matched up to when the gifts hit our bank. During busy times of the year, that can be daily, sometimes multiple posts per day. And each time I have to go back and drop down all those settings in NXT, even though they rarely ever need to change after I set them. Please make them sticky again.

3) Where is the Validation Report in NXT? I depended on that so that if something looked off I could print it for our Gift Entry person before posting to FE, in case there were errors. Huge loss of a necessary option.

4) Before I hit the 2nd Post button in NXT, the gifts I clicked +Generate Post on actually show in RE as posted, before I post them. What if I decide not to post it yet, or discover an error? RE thinks it's already posted, but nothing shows up in FE's JE list. RE and FE are integrated so that they will be coordinated during this process, and that seems to be broken.

5) Weird anomalies: I tried to post one gift in RE NXT, that was just an incoming wire tfr - didn't require anything special, it was the only gift that day, no Queries needed, etc. NXT told me no records were found. So I pulled up the RE database on my other monitor, and proceeded to post the same gift there. This time the gift was found, and it posted the way I was used to seeing it, no issues.

6) Slowness: the processing speed in NXT is slooooow as molasses. What takes about 10 seconds in the Database takes a full minute in NXT, including a message letting me know that it will let me know (seriously) when it is done processing. If a server has time to tell you it is still processing a 2-line JE, then it is too slow.

Thanks,
Roberta

Here are some updates to the points made.

1. This field is for you to name the posting process, it could be an ID or just a description. Most clients are using "June 10 - check gifts", or (6.1.2026 gifts). Anything that would be useful to you to come back to since we are saving the data unlike in database view.
2. We have heard this feedback and we have plans to make these fields sticky by user.
3. The validation report is there, if you click into the posting event, there will be a button to Export > Export in PDF and that is the validation report.
4. This is expected and how we lock the gifts before the actual post event occurs. If you generate the post and you see what you are looking for you would click post to finalize that. Which the gifts are in this state we need to prevent them from being edited or changed and by marking them posted, it does just that. If you do not see what you are looking for in the posting event, you can click to reject it to make changes and that frees the gifts back up.
5. This sounds like a bug and something we would want reported to support. Database view should not be pulling different lists of gifts than web view does.
6. The performance is definately different and something we are looking into. There is a direct db connection in db view and in the web we are relying API calls over the web. We might not get to the same speed of the direct connect but we should be able to get much closer.