We use multiple recurring percent batches monthly and it would be very helpful to get this in FENXT. I know you say not many use this, but this is a core step in our monthly closing to allocate expenses between funds/orgs.
We also use the recurring percent batch every month with 12 entries or so monthly. It is very helpful and would be challenging if it was taken away. It would greatly impact our position on staying with Blackbaud when database view is taken away.
We have about a dozen recurring percentage batches set up that allow us to code our coprorate credit card transactions each month with ease and efficiency. Without this feature, all credit card users that must allocate expenses will be forced to split purchases up to 5 different ways in our credit card receipt reporting system. We have found that when required to go to this extreme, most users don't allocate any expense code at all, and the payables team must then spend hours of their time doing it on behalf of the card holder. This not only slows down our processes, but being forced to manually calculate the allocation greatly decreases our efficiency. Please retain this option.
We also use the recurring percent batch every month with 12 entries or so monthly. It is very helpful and would be challenging if it was taken away. It would greatly impact our position on staying with Blackbaud when database view is taken away.
Is it me or instead of added functionality the FE NXT limits our ability to work?
We have about a dozen recurring percentage batches set up that allow us to code our coprorate credit card transactions each month with ease and efficiency. Without this feature, all credit card users that must allocate expenses will be forced to split purchases up to 5 different ways in our credit card receipt reporting system. We have found that when required to go to this extreme, most users don't allocate any expense code at all, and the payables team must then spend hours of their time doing it on behalf of the card holder. This not only slows down our processes, but being forced to manually calculate the allocation greatly decreases our efficiency. Please retain this option.