Why is this useful?

Gifts imported from third-party integrations can have key fields such as Gift Type, Payment Method, Amount, and Receipt Amount locked, with no option to delete the gift. This limits the ability to correct or remove an imported transaction before approving the batch.

Providing the ability to edit or delete these gifts would create a more consistent Gift Management experience and reduce the need for workarounds, such as moving an unwanted gift to a dummy constituent, approving the batch, and then deleting the record.

Who would benefit from this?

Organizations using Raiser's Edge NXT Gift Management with third-party fundraising or gift integrations, such as Almabase, would benefit. This would be particularly valuable for gift processing and database administration teams that need to review, correct, or remove imported transactions before approving a gift batch.

How should it work?

When a gift is imported into Gift Management through a third-party integration:

Users with the appropriate permissions should have a Delete option for the imported gift before the batch is approved.
We should be able to edit Gift Type, Payment Method, Amount, and Receipt Amount when corrections are necessary.
The presence of a third-party transaction ID should not, by itself, prevent authorized users from editing or deleting the transaction.
The experience should be consistent with gifts that users can currently manage or delete within the same Gift Management workflow.

This would allow organizations to correct third-party gift data directly within Gift Management instead of relying on additional constituent records or post-approval cleanup.