Ability to Select the Correct Tribute When Multiple Tributes Exist on a Constituent Record When Processing Online Gifts
Allow users to choose the correct tribute when a constituent has multiple tributes (especially during online gift processing)
Description:
When processing online gifts in Raiser's Edge NXT, the gift can be matched to the correct constituent record — including those who have multiple tributes associated with them. However, there is currently no way to select which tribute the gift should be linked to.
If a constituent has more than one tribute record, RE NXT automatically assigns the gift to one of them without giving the user visibility or control. This often results in gifts being linked to the wrong tribute, which affects acknowledgment workflows, reporting, and donor stewardship, and requires manual cleanup.
Current Behavior:
Online gifts with tribute information come into RE NXT.
The gift processor matches the gift to the correct constituent.
If the constituent has multiple tributes, RE NXT automatically assigns the gift to one of them — without displaying which tribute it chose and without giving the user any ability to confirm or override the selection.
It is unclear what logic or matching algorithm RE NXT uses to determine which tribute the gift is attached to, and this behavior is not documented.
As a result, gifts are frequently linked to the wrong tribute, requiring manual correction and causing downstream issues for acknowledgments and reporting.
Requested Enhancement:
Please add the ability for users to view and select the correct tribute during gift processing when multiple tributes exist on the constituent record. This would function similarly to how users select the correct fund or designation when multiple options are available.
Why This Matters:
Ensures donor intent is honored
Prevents incorrect tribute attribution
Keeps acknowledgment processes accurate
Reduces manual corrections and staff time
Supports organizations with high tribute volume or repeat tribute donors
This enhancement would significantly improve data accuracy and workflow efficiency for many organizations.
-
Carlene Johnson ⭐ Community All-Star
- Jan 7 2026
- Reviewed: Voting Open
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +167
Related ideas
Similar to Chris's comment, we will not switch gift processing to NXT until tributes are fixed. The fact that you can't even view tributes in a list, or see who gave to a tribute on a person's file in WebView is a huge missing piece.
We are a hospice organization and this is the sole reason we have not switched our gift processing over to NXT. It is a nightmare to correct and immensely time consuming. I am really hoping this can be addressed.
Because we can’t select the correct tribute during Online Data Review or in WV gift processing, we end up stuck in an endless loop where the batch cannot be committed due to an issue with the (incorrect) tribute the system auto‑assigned. Since WV doesn’t allow us to change the tribute in batch, the only workaround is a multi‑step detour in Database View:
Go to DBV and temporarily remove the end/expiration date from the wrong tribute so the batch will commit
Return to WV and commit the batch
Go back to DBV again, open the gift, manually switch it to the correct tribute
Re‑add the end date to the original (incorrect) tribute
This is a lot of unnecessary back‑and‑forth, introduces risk, and is entirely caused by the inability to choose the correct tribute at the point of processing.
We do so much reporting and stewardship around tributes at my organization on a weekly basis. Right now, this is creating a significant drawback to using NXT for gift entry - and it is stopping me from using it. We send out the Tribute notifications, and this is also an important section of our Annual Report. Tributes are not somewhere we can afford errors or non-functionality because of system limitations.
Tribute is the clunkiest and most poorly designed item in NXT. We need to be able to select the acknowledgee as well as to select, create, and edit all tribute records before approving batches.
Further, tribute is almost non-functional for those of us still using NetCommunity. We ABSOLUTELY need to be able to disregard a "bogus" tribute (donor who made themselves an honorarium because they didn't understand), as well as the items referenced above.
It is stunning that Blackbaud has so little comprehension of the need to be able to manage tributes flexibly and accurately. Few things will annoy a donor more, or disenfranchise a donor more quickly, then if you don't properly honor the person or organization they want to honor---and particularly if it's an IMO tribute for a deceased person.
Further arguments:
If our tribute record is "In Memory Of" and an online donor indicates "In Honor Of", NXT creates a new tribute record In Honor of, with the tribute name of "Donor-entered text:" followed by the tribute name they indicated. Then we have to go into the tribute record in DBV to correct everything.
Additionally, we send tribute acknowledgments to the family whether or not the donor specifies to send an acknowledgment. In NXT, if the donor doesn't specify, no acknowledgment is generated, even if there are multiple relatives listed on the tribute record. We need the ability to select the acknowledgee as well as to select, create & edit all tribute records before approving batches.
I didn't know this wasn't possible! I can't say it better than Carlene and Sunshine, I'm just co-signing its importance.
Please add this functionality. Donors have multiple tributes for a reason, and we need to be able to connect to the correct one to make sure the tribute is acknowledged correctly.
Examples of different tributes a constituent may have:
In honor of the HOH
In honor of the spouse
In memory of the spouse
In memory of child
In honor of a special occasion (birthday, holiday, retirement, birth of child, etc.): Note that these tributes may often be directed to restricted funds, making it imperative that the correct option is selected.
We have several donors that have multiple tributes. I was not aware of this issue. We are moving to utilize WV this year. The user knows the donor's intent and should have the ability to select the correct tribute.
Carlene has said everything necessary. Tribute giving - even in Online Express - is incredibly confusing and time-consuming for every RE customer I have worked with, and they end up not using it. This robs them of potentially valuable information.
While we're at it, can we also NOT require every single tribute to have a constituent record? We all have ways to work around it - which will be even easier if you implement Carlene's stellar idea - but we shouldn't have to develop workarounds.