What's New In Blackbaud Raiser's Edge NXT® — June 10, 2025 10165

What's New In Blackbaud Raiser's Edge NXT® — June 10, 2025

Published

Here are the latest changes in Blackbaud Raiser's Edge NXT for June 10, 2025.

  • Match tribute gifts in Online data review
  • View user role permissions
  • Directly post gift batches to Financial Edge NXT (for some of you)

Match tribute gifts in Online data review
To prevent duplicate honoree and acknowledgee records, you can now review and link tributes in Online data review. You can match the donor, organization, honoree, and acknowledgee separately for a tribute gift. For more information, see Online Data Review.

View user role permissions
To make it easier to review the permissions associated with a role for a user, admins can now view the details in context. If a user doesn't have access to all tasks and permissions associated with a role, admins can select the role from the user's profile or from the Users page to see the tasks and permissions assigned to the user.

For more information, see Users and User Details.

Directly post gift batches to Financial Edge NXT (for some of you)
To track accountability of gifts and streamline processes, you can now easily post gift batches to General ledger to transfer gift information directly to Financial Edge NXT. For more information, see Gift Posting.
News Blackbaud Raiser's Edge NXT® Blog 06/10/2025 4:00pm EDT

Leave a Comment

1 Comments

Hi all – according to this blog post, the Match Tribute Gifts in Online Data Review feature is now turned on. I tested it this morning and wanted to share what I found — and I’d love your feedback or experiences too.

Main suggestion: Please give users the ability to select the correct tribute when multiple exist on a record. Right now, the tool auto-assigns one (in my case, the only inactive tribute out of 18), and there’s no way to change it during the review process.

Here’s what happened:

The gift was for a record with 18 tributes (it’s our school’s main record — we use separate tributes for departments, faculty, classes, etc.).

I couldn’t pick the correct tribute, and it defaulted to an inactive one.

I had to manually activate the incorrect tribute, approve the batch anyway, then fix the gift in database view: remove the wrong tribute, add the right one.

So yes — no duplicate record, but actually more steps and a higher risk of missing the error. At least when a new record was created before, I knew something needed fixing.

Having 18 tributes is rare, but having both an "in honor of" and "in memory of" tribute on a single record is very common. We typically inactivate the “in honor of” when someone passes — and it is quite possible that is the one the system will choose based on my exposure thus far.

I’ve opened a case and added this to the idea bank. If this affects you too, or you have thoughts, please chime in — and vote!

Share: