When we approve one-time gift batches through RENXT, the gifts are automatically reflected in a donor's record. However, there appears to be no way to apply the one-time gift against an existing pledge in RENXT.
There is a workaround using database view. We can go in and manually apply the one-time payment to an existing pledge. This makes for a cumbersome process. We would like to do this all within REXET (or WebView).
This is a critical gap, especially for nonprofits processing high-volume gift batches. We use Omatic to import gifts into batches, and during peak times we're processing batches with 500+ gifts.
In database view, when approving a gift batch, there's an option to "apply gifts only to matching funds"—which automatically applies one-time gifts against existing pledges during approval and carries forward the campaign and appeal from the pledge to those payments. This feature is essential for batch-level efficiency.
If applying gifts manually in NXT takes 15 seconds per gift, that's over 2 hours of staff time per 500-gift batch. We're not a huge operation, but I'm confident larger nonprofits are facing even more significant time losses.
NXT needs batch-level gift-to-pledge matching during approval, just like the database view. How does Blackbaud recommend nonprofits handle this at scale? What am I missing?