Customize New Validation and Control Report in Web view

I am pleased that we now have the ability in to generate these reports in Web View. I was wondering how we go about customizing/configuring what fields are printed and how we can ensure the batch number is in the header as before (See pics below). Also can we auto generate a query for each batch approved in Web View? We had that functionality in database view. We need it to generate a custom reconciliation report for our finance department. Thanks

  • Nicole Francis
  • Jul 27 2026
  • Reviewed: Voting Open
  • Attach files
  • Janet Pellerin commented
    18 Nov 13:11

    Please allow us to edit the validation report or mirror the one we have in DBV. I agree with Julie's comment on the control report too. We only need the basics on there - same as what we have in DBV.

  • Karen Rhodovi commented
    17 Nov 19:14

    To add to this request, some of the fields that are not currently available in the web-view validation report are important to our stewardship processes. For example, gift references, soft-credit attribution, fund numbers and letter codes help us to make acknowledgments relevant to the donor and their specific gift, and to identify the appropriate secondary stewardship opportunities. The ability to customize the fields included on the report would help us maintain workflows that were previously supported through database view.

  • Rachel Waters commented
    17 Nov 17:35

    My team needs additional fields than what's provided in the auto-generated web-view validation report. In particular, there are no fund numbers or letter codes present.

  • Jessica Smith commented
    11 Nov 20:25

    The validation report in Web View is so difficult to read. There is so much information RE is trying to include that it gives you a headache. Please allow us to customize the layout and info. I am game for one gift per page to make the information easier to process. We are a digital organization and rarely print anything but we do view and save PDFs and one gift per page suits us just fine. Others may not like it. This is where allowing us to customize these to our needs is best.

  • Lisa Komp commented
    09 Nov 22:07

    Yes please. We need batch numbers in the control and posting reports!

  • Karis Morrow commented
    06 Nov 16:36

    Please figure this out, I am begging you! This is the messiest looking report ever. Having the Batch Number and Information on the last page only of the validation report is wild. Why would anyone NOT want it at the top of every page? Just let us customize the layout as a template like we do the batches but with the option to include the constituent ID. It's crazy to me that the constituent ID wasn't already built into it. Maybe I'm the only one with 5 John Smiths in my database? Constituent ID numbers save us from so much confusion! PS, on the control report, why is only the amount column right justified when the rest are left justified? And there is no reason why the columns have to be so wide. Unless their last name is Supercalifragilisticexpealidocious, their first and last name should be able to fit on the same line (both control and validation). Feel free to drop their title, I doubt anyone needs a Mr. or Ms. in the mix.

  • Julie VanErsvelde commented
    04 Nov 22:32

    I am using the Validation report in Webview for the first time today. It seems to me that information was added to the Control Report that should have stayed on the Validation report. The Control Report only needs the Name, ConsID, Gift Type, Amount, Fund, and Gift Date. Having each of these fields being able to have wrapping text would be great. The validation report should show every field that is included in the batch, along with installment info for pledge payments, soft credit info, tribute info etc. Same as what we have in DBV.


  • Wendy Bartlett commented
    04 Nov 18:21

    Please add the cardholder name and last four digits to the validation report so we can go back to reconciling our credit cards/direct debit transactions in a timely fashion. There is not enough data to be able to reconcile some of the transactions. It is taking up alot of time trying to hunt down these transactions.

  • Meghan Fagg-Smith commented
    13 Oct 12:00

    We really do need our organization name and the batch number at the top of each report. This helps us and our Finance department so much, and our auditors like it too.

  • Maureen Finch commented
    12 Oct 15:11

    Need to have Fundraiser value included in the batch validation report, one of the key reasons for the validation report to be sent to stakeholders. Instead I am having to add the distribution of a customized financial report that shows fundraiser/solicitor for each gift.

  • Ingrid Coolins commented
    07 Oct 19:51

    Adding to my post. Would also like to see what the split is for. Spell out how much goes to which fund. The report only says "split".

  • Ingrid Coolins commented
    07 Oct 19:18

    Would like to be able to customize the Validation Report to a certain degree. Need to have BATCH # at the top. It's too much info to scroll through to find the number. Also need to see the installment schedule on pledges, as well as applied to when making a pledge payment. Org name at the top would be great too.

  • Ange Scott commented
    06 Oct 19:40

    Agree 100%.
    The NXT Control Report is messy - just lay it out the same way it was in DBV. We don't need solicitor or pledges on there, it has no relevance. We certainly don't need multiple lines for one gift.
    Or at least give us the option of choosing what columns show up on the report, as some are asking for things that others have no absolutely need for

  • Guest commented
    28 Sep 19:34

    The webview validation report looks messy (it is not clearly grouped by the gift) and takes longer to generate.

  • Ellen Aronson commented
    28 Sep 17:41

    Yes, please add the Batch ID back to the header of the Validation Report so it is easily found on each page. Having it only listed at the end of the report is annoying and time consuming to scroll down to verify which report.

  • Stefanie Weiland commented
    25 Sep 15:31

    Yes! We use validation reports to review our batches prior to posting. The current setup in NXT just doesn't suffice.

  • Guest commented
    27 Aug 18:39

    Agree 100% this is not the same as DBV and it doesn't have to be if we have the ability to change the layout. What printed on 2 pages is now 10 pages :(

  • Dina Rieman commented
    19 Aug 20:07

    It seems the validation report is showing summary data and not detail. For example, pledge applied to, tributes, soft credit, fundraiser and opportunities are not shown. In DBV, there is a setting under “User Options” to select detail or summary. At the very least, we should have that same option in web view. Otherwise, we cannot efficiently validate the batch using this report.

  • Laura Perrone commented
    19 Aug 20:04

    The information provided on the DB view detail validation report is critical for ensuring gifts are entered correctly before approving. With the current webview validation reports, we are missing pledge applied to, tributes, soft credit, fundraiser, and opportunities. With this information missing, we cannot truly validate the data in our batch is correct and complete.

  • Catherine Burns commented
    19 Aug 02:30

    Please allow us to select page orientation - For recurring gifts there are extra columns that do not fit in the portait orientation. Instead of change to landscape they are pushed to a second row and given field headers. EVERY gift gets headers for the second row of data, making the report many pages longer than it would need to be if it could be in landscape format with all the columns fitting and the headers displayed only once.


  • Load older comments
  • +74