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; } } }

Really need an answer, from Blackbaud, about NXT recurring gift batches

Sandra Moore

A question I have not yet found an answer to, and that I do not see specifically listed on the agenda for the inside track session on September 8, is will we be able to include gifts that are not actually linked to a recurring gift in NXT recurring gift batches?

There are those who do not want to make gifts into actual recurring gifts because of the complications in managing, updating and rescheduling recurring gifts. This often happens with payroll gifts. Payroll gifts can so easily get "off schedule" because employees go on leave, they take a vacation, they stop donating for a bit, then restart. Thus, organizations often have a system in place whereby they update the recurring gift batch itself according to info received from payroll for that period, rather than opening and changing individual recurring gift records, which would be far more time consuming. Will they still be able to do this in NXT? Thanks!

Find more posts tagged with

Data Entry

Web View

Accepted answers

Anthony Gallo

The initial plan here is to use import for the recurring batches workflow. If you have an existing batch that you typically copy and adjust, export that batch to CSV make the adjustments and import it back in. If you get a file from the bank or your internal department that has the details, you would import that right in. We do not have plans for a native copy feature for batch right now, but that doesnt mean we couldnt go in that direction if the import model doesnt meet your needs. We are just going to see what workflows the new import into batch process solves for and see where we need to go from there.

All comments

Crystal Bruce

Hi @Sandra Moore - thanks for posting. I'm going to tag in @Anthony Gallo to take a look at this and see if he can offer any insight.

Devan Bessinger

Also looking for the same in relation to internal employee payroll deduction gifts.

Anthony Gallo

Sandra Moore

@Anthony Gallo Thank you for your reply. Not a recurring batch we copy, but rather one that is reused over and over, with minor manual adjustments made each time before committing. Is that functionality still going to be available?

Julie VanErsvelde

@Sandra Moore and @Anthony Gallo I also use a recurring batch for our payroll deductions. I set up a new one each fiscal year and then that same batch is committed 12 different times during the year, updating the gift date, post date and people/amounts if necessary. Would really miss this functionality if it is not planned.

Devan Bessinger

Us too.

Dariel Dixon

This is pretty common to use recurring batches for payroll deductions @Anthony Gallo. I think we need to really peel back how recurring batches work in DBV. From my understanding, these recurring batches are just templates, and upon committing become their own batches. I think there should be a way to create that functionality without completely copying the way they work in DBV. Many of us don't get files that are easy to import, but it is more efficient to make the changes using the files as a check and balance. I really hope this is being considered moving forward.

JoAnn Strommen

We have several batches of this type. Used monthly, twice month…

Bernard Nemis

This is basic… very fundamental. Why would BB even opt for an import process. Unless they are developing and will implement a native import feature soon, clients will now depend on APIs and 3rd party platforms.

Sandra Moore

So Anthony @Anthony Gallo - it sounds like many of us are awaiting an answer on this, and we here are likely a drop in the bucket since managing recurring batches this way has been a standard for payroll batches probably about as long as recurring batches have existed. Will what we have been doing become an option in NXT? And if not, when do we get to start testing this batch import process? (Forgive me if we already can and I missed it - my duties still keep me in DB view most of the time). Since this is a process that is so critical to so many organizations, we need it to not be something loaded just before they take DB view away. We need to begin testing and training and updating instructions as soon as possible. Thank you!

Anthony Gallo

We are looking at all options and the import workflow mentioned would be using our own import into batch functionality that is aiming for a Q4 release.

Anthony Gallo

We will be handling recurring batches along with automatically generating transactions and the auto apply to pledges and recurring gifts during Q1 of 2027. Import should be available by the end of 2026 giving us multiple tools to handle these processes.

Sandra Moore

Awesome. Thank you. Looking forward to trying these tools out.