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.
It also takes refreshing the screen after download to have the button available. Always extra steps to get what you need. :)
Can batches be viewed after they are created?
We use the summary report for every gift batch as part of our process with our finance team, so either we need that, or we need to be able to choose which columns appear on the detail report - we don't need the pledge and solicitor information, for example - so if we had the flexibility to remove those columns, or only show what we want, that would be what we need. Having the report "on demand" is definitely a huge plus! Thanks for that....now if we could just have the power to modify/display what we want/need of the details.
GM,
Report is quite crowded much harder to read. Possibly landscape could help.
Gwen Capers-Singleton, M. Acc., bCRE-Pro
Director of Gift Services
VIA Health Partners
Direct: 704.335.4328
Fax: 704.335.4326
Email: singletong@hpccr.org
www.viahp.org
[cid:image001.png@01DD44F6.C2856AB0]
No more watching the Control Report flash before my eyes to disappear forever when I accidentally exit out of that window instead of printing the report? This is GREAT.
On the batch review page there is a Print button and it will allow you to print both reports (control report once approved) at any time. This process does not happen automatically, it is an on demand report and can be done whenever.
Do I need to create a query for the batch to run the detail report, or should that happen automatically when I approve the batch?
@Anthony Gallo. Thank you for clarifying. I hope you plan to also bring over the summary report.
This is incorrect. We built the validation report and the control report (specifically detail and not summary) independently. They are not the same report and should be matching what database view does for each. We built the detail report first as it has all of the information needed from summary and obviously the extra for detail. We are evaluating whether we need to bring both but the detail report at least is not missing anything as would be the case if we just created the summary report.
I just spoke with Support today regarding the Gift Batch Control Report.
I was told the Batch Control Report is an exact copy of the Validation Report, only it is captured at the time the batch is approved and does not change.
I did not realize they were not copying the orginal report. This is NOT the same Batch Commit Control Report that is in DBV. It will never be the same as in DBV. They do not have plans to create a summarized Batch Commit Control Report in WBV that will match the DBV Batch Commit Control Report.
I agree the Batch Control report is very messy. The columns included should layout in Landscape but the report prints on portrait.
I Hope the Batch Control report will include the Same minimal gift information that matches the Dbv report. Date, name, gift amount, fund, and totals for each payment type. (edits made)
I would also hope that we can choose which columns we need included for our individual organizations.
It should not match the Validation report.
I have submitted this problem to Support. After MUCH back and forth they finally said the report needed to be corrected. However, it still is not corrected, nor useable for more than just my Org.
For those that still have problems with your Batch Commit Control Report. Please report it to Support.
I agree the Batch Control report is very messy. The columns included should layout in Landscape but the report prints on portrait.
I Hope the Batch Control report will include the Same minimal gift information that matches the Dbv report. Date, name, foot amount, fund. It should not match the Validation report.
And Total payment type received
The report is very messy and hard to read compared to database view's control report
Once done approving, you have to go back out of the batch and back into the batch to print the control report. The original approval page only shows validation until after it is approved. then you have to go out of the batch, go back into the approved batch and under print select the control report to print. Would be great if didn't have to go out and back in to print the control report. Wasted time.
Thank you, Anthony!!
I just want to clarify here, this has been released. You can view the validation and control report on the batch approval page.
This is the main reason I am still using the database view for committing batches.
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!