Change to Prepayment Report in NXT

I believe Crystal is correct. The prepayment report in Payment Assist now only shows the summary information for each payment with account numbers listed for the bank account and AP but NOT the more detailed breakdown of expense accounts for each invoice that we used to see. Until quite recently, the prepayment report run from Payment Assist would still display this more detailed information if you had the prepayment report parameters set up for a detailed report in database view. We are now unable to see that detailed reporting using the prepayment report available when we select invoices for payment in payment assist.

We can still see that detailed report by running a cash disbursement journal report, but this is both inconvenient and prevents us from using that report effectively because we need to see those details in order to approve the payment run. Support has confirmed that the summary report we are seeing is intended. They were able to help us set up the database view parameters for newer employees in the fall, but now that we have lost access to database view reports, all employees have reverted to the summary version. Support's only suggestion for us was to create a query which is not very helpful because we need to be able to run the report based on the invoices selected for payment, and there is no way to work that filter into a query.

@Shannon Krise, @Crystal Ratering apologies for my earlier confusion. I did find out that the change in the payment process was an intentional design decision made during development and is aligned with the product direction for moving away from Database view. The previous behavior relied on user-defined parameter sets stored in Database View, which are not available in the web view experience. As a result, the pre-payment report uses a standardized report configuration.

Given these differences between the Database View and FENXT payment processing engines, we do not recommend using Database View pre-payment reports as a validation step for payments that will be processed in FENXT, as the reports may not always align exactly with the resulting payment transactions.

The product team did say that we aware this impacts users who have set up their preferred pre-payment parameter set in database view. And that we will review the use case shared and see if there is a way to bring this over without the dependency on COM as we evaluate future enhancements. 

I'd encourage you to go vote on the submissions around this in the IdeaBank — when I searched for "pre payment report", I saw there were 2 different ideas submitted around this already. https://financialedge.ideas.aha.io/ideas/FENXT-I-3883
https://financialedge.ideas.aha.io/ideas/FENXT-I-3403