Our accounting department uses FENXT and per auditor requests, needs the control batch report. This currently isn't possible to get out of NXT so our gift processor has to use DB view. Please update so our migration to NXT is able to allow users to actually use it.
The Gift Batch Validation Report is an important tool for reconciliation, auditing, and quality control. Users need the ability to view, print, and retain a validation report after gifts have been approved in Gift Management within NXT.
In DBV the gift batch control reports can be generated in Excel which allows for user formatting to wrap longer comments, while fitting all columns on one page. It is astounding to me that the essential function of gift batch entry has not yet been fully set up with output that mirrors what is available in the dbase. Our organization is not able to migrate to using gift batch entry in NXT until all of the outputs available in DBV are mirrored in NXT. We shouldn't have to explain our uses for these outputs. They are critical for audits, and basic accounting methodologies.
Anthony, currently chatting with support and they don't seem to be grasping the issue, plus when they're pulling reports they aren't having this issue. What I'm seeing is that each column of the Validation Report is allowing for every character to appear - we have long Appeal names and some gifts have LONG comments. Those are showing up in full on the report (as well as the long string of words for Gift Subtype) which is taking up all the room on the report and cutting off columns to the right. The report needs to be formatted to fit all columns on one page, which will cut off the wordier columns and that's okay. I personally don't want Comment on this report at all. I sent Support examples of the same batch's Validation Report pulled from Database and NXT, which clearly shows this issue. Hoping it's fixed soon, having these in NXT would be a huge help!
It is great that the commit control and validation reports are available now. I am going through some past batches that I've updated in web view and the commit report is not available for some of them. Also, for the validation report there are different font types. i agree that it would be helpful to add in the business name for the reports.
Great progress to get this but we need more control over the columns. We work with Fund ID, Campaign ID, Appeal ID not the text descriptions, so we need the option to see these
Looks like I can only print a Validation Report - I don't see a Batch Commit Control Report option. I do see the issue with the Gift Subtype that was mentioned, and the Comments field is getting cut off. Perhaps when the Gift subtype field is fixed, it will remedy this.
We also have columns being cut off on the right side of the report.
I don't see the Batch Control Report (detail) that is mentioned. Where is that located?
We have the issue with gift subtype reported and we are working to fix that now. I do not yet see any bugs related to items being cutoff so please contact support for any issues that look incorrect so we can get those resolved asap.
Anyone else having this issue - many columns are cut off on the report. The PDF just cuts off halfway through the Acknowledgement column. And the "Gift subtype" line is really long and full of junk words "blackbaud.gift.service.serviceclients.giftservice.giftsubtype." I can't use this report yet because of these issues.
So glad this is moving forward - however it is missing the "Query Name" that is automatically created and our "Business Name" - please fix that soon so that we can stop having to do this process in DB View
So glad this is getting done - however, we are still missing some important data fields: Constituent ID, Gift subtype; Adknowledge; Reference; Adknowledge date; Receipt; Receipt date - once these fields are added, we can stop having to process our batches in DB View
Thank you! I haven't been able to test this yet, but I agree with the comment below that we need to be able to print and/or save a PDF of the complete report. Many organizations use this report as part of their reconciliation and/or audit process.
And can you make sure that all the gifts are able to print on one sheet? Currently, you are only able to print what's in view.
We need the batch control report for audit trail purposes. Please add this functionality which is currently available in DBV. This will help us migrate to Gift batch functionality in Webview.
I tried using batch entry in NXT today and wish I wouldn't have. Not having a control report and having to create a query to then be able to get a detail and summary report is silly when I can have the control report in DBV automatically and easily pull a summary report off of the query automatically generated when I batch gifts in DBV. NXT is not fully capable and not having the ability to automatically create a query from an entered batch for later data pulling AND not having basic control reports does not make batch entry in NXT ready for use with a closing deadline for not having access to DBV.
This report is vital for the data entry team and for the finance. ASAP would be great!
Just to express a bit of frustration... this has been promised to be completed with various deadlines over the past 9 months or so, and now looks like it won't be ready until late September? We cannot move forward with the switch over to NXT for batch gift processing until we are able to generate a batch control report. We will have been idling for nearly a year on this. It seems that all these practical issues have been put on hold in order to quickly roll out shiny new AI functionality, which is doubly frustrating. Please confirm that this won't be pushed out further into the future.
I'm genuinely curious. Why does Blackbaud roll out projects and systems before they are 100% complete and then criticize users for not using NXT for everything? This new fee for online donations is a great example. Pushing users to transfer over to the Online Giving pages when the functionality isn't fully complete for the needs of its users. It frustrates your customers and you're losing business because of it.
It does. We are working on the control and validation reports now and I am hopeful we have those by the end of Q2 but they will for sure be done before BBCON.
Developers recently committed to parity with DBV batch by 9/30/26. Does that include this report?