Collect Ideas

Thanos · ‎12-30-2019

Currenty the Lockbox App if a payments fails the UI shows the reason it failed. There is also a "Generate failed" button that gives you a file with all the payments that have failed. It becomes very difficult to troubleshoot when the number of payments that failed is large since you need to go in the UI one by one to understand the reason. It would help if the failures file had the reason code in it.

vgorkanti · ‎10-12-2020

Hi, Currently Accounts section of Collections window allows to enter the negative number of days with which we can see the current invoices for that account too, i.e aging days with negative number of days. Above can't be done from Invoices section. We have use case where collector wants to enter notes on current invoice and to find the current invoice, they have to go from accounts only to find that invoice. Thanks,

rmauriello · ‎07-14-2020

Hi, We need to chooce the timing for Bank Transfer Electronic Payment, because the payment hub needs at specific hour to send to bank. It's a good idea the ability to choose the start time of payments as in the payment runs. Thanks, Regards, Rina

Serg · ‎01-22-2020

If those response codes were stored in the Comments field, along with other CPR sourced data, it would open the possibility of designing batch workflows for different type of payment failures.

Happy Business Starts Here

Vision

Products

Zuora Central Platform

Products

Zuora Marketplace

Solutions

By Industry

By Role

Customers

Resources

Resources

Subscribed

Support

Company

Collect Ideas

Configurable Lockbox - Enhanced troubleshooting (Reason code in "Failures" File)

Collections window Invoices section should allow to show current Invoices.

[Installment] Choose the time to start the electronic payment

On CPR: Store the mapped response code into the failed payment record

Customer Statements