In database view we generate and create EFT transmission files in Batch for direct debit payments. We send these files directly to our bank for processing the payments from our donors’ bank accounts. We need to be able to do the same process in webview.
Thank you so much, Anthony! Great news and I appreciate you taking the time to respond and reassure us.
Thank you, Anthony! This is awesome news!!! : )
The only method you are missing is the one off create a single gift workflow which we will support throughout. The only item we are not planning will affect your workflow and that is the batch EFT processing of credit card transactions. We are working with our payments teams to figure out alternatives here.
Anthony, thanks for your quick response. I (and I'm assuming others) might be confused about the differences between EFT via Credit Card and EFT for manual batch processing. Can you detail the process for each so that we can make sure we are planning for any process changes that we need to do? Thank you.
We go into batch, automatically generate transactions, and create EFT transmission files. We do one batch for credit cards and another for direct debit. I'm actually not familiar with any other way to process credit cards or direct debit in database view.
Correct, this is planned and we just started development on it. The one piece we have no plans to bring forward is EFT via Credit Card. We plan to support all payment methods including CC and DD for manual one off gift in the back office for single and batch entry, all external payments methods for recurring gifts payments or pledge installments via API and import. We will support EFT for manual batch processing in web view. This work is planned to be finished before BBCON.
We're the Diocese of Toledo, and we're in the redemption phase of a capital campaign, processing roughly $400,000/month in credit card and direct debit payments via Batch/AGT in database view. We can't simply convert these pledges to recurring gifts as a workaround — doing so would distort the pledge/payment reporting our stakeholders and senior leadership rely on, and we need this process to continue through 2029.
I opened a support ticket asking directly whether this was on the roadmap, and Blackbaud support's response was that this functionality is not currently available in NXT, and there are no active development plans to support running EFT or auto-generating transactions/payments in batch the way it works in database view. This was also confirmed by Anthony Gallo on the June 9 "Inside Track to the Unified View" webinar.
For organizations like ours that rely on this for active campaign processing, "no current plans" is a significant gap, not just an inconvenience. Adding our vote and urging Blackbaud to prioritize this — and asking for more transparency on timeline, since several of us are trying to plan around a sunset we don't have a clear date for.
Before creating files we need to be able to add/edit bank relationships in web view, which is still "Undecided" on Blackbaud's Feature Grid. Please see and vote for https://renxt.ideas.aha.io/ideas/RENXT-I-9080
Janet, we do exactly the same. Any information from anyone, what is Blackbaud's fix/suggestion for this?