nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

NXT Online donation form gift batch processing

Steve Clark

After a donation has been made by a donor using the NXT online form, The gift batch needs to be edited an approved. The majority of fields that we use on our gift records are not populated with information that the donor completed when making their gift. This means we have to manually add in data to fields like Campaign, Appeal, Fund, Package, and custom fields etc. (although I appreciate that you can set defaults for Campaign and Appeal, but these don't work for us as our general donation form allows the donor to choose to support a variety of campaigns). Having to complete these fields manually for each online gift will create a lot of extra work for us and creates the potential for more inputting errors (as opposed to Online express where you can match a gift to a pre-existing batch which pre-populates those fields).

I have also noticed that if you enter a package into the gift batch for an online gift, it does not add this to the gift record - only tested this once but that was what seemed to happen.

Find more posts tagged with

Comments

Alex Wong

@Steve Clark
Your observation is right on the money for the current functionality of gift batch.

the upcoming (not sure when, but Q1 Q2 maybe) update to webview gift batching will include a lot of the functionality that a database view gift batch would have, such as default values, “global change" a “column” for all gifts in a batch, custom fields, etc. Also a “grid” like processing to make working in webview gift batch less “clicking” more “tabbing”.

We do not use RE NXT donation forms, we use LO and import gifts using IOM. However, we do use RE NXT Event registration which does the same in putting transaction into webview gift batch, the same is true for JustGiving integration too. Currently I setup automation using Power Automate and webhook API for “when gift is created” and handle all the gift fields that needs to be populated with org-specific gift entry process (i.e. our Comment/Reference field for gift is BByymm-ddC, so programmatically do the yymm-dd into the field). This allows us to simply approve the web gift batch without editing anything, and the gift would be coded to our gift entry standards.

I recognize this isn't something that most would do, but if you wish to, can be explored internally by yourselves/your team, or you can do this with paid service by a Blackbaud partner. I know there are few out there that specific do these custom things for org like yours

Denise Miller

If we're simply processing a "fee" per say, not a gift that we're not needing to track on a form created specifically for one purpose and it not needing to be on the constituent's actual gift record/tile, once the online gift processes through BBMS and we get the gift notification via email and then see the batch approval as pending - are we then able to not approve the batch since the payment physically went through of what we're trying to collect? I just want to make sure that by not approving the batch it doesn't generate some sort of automatic refund behind the scenes. Assuming this would work as it did previously but since we haven't tested it out yet, was curious on that.