MineralTree reports that it is frustrating that CPX cannot alert anyone when the remittance email address is bad - regardless of whether it was a misspelling, someone left the company, on maternity leave, etc. There has got to be a better way of keeping up with this rather than someone reaching out to these suppliers individually, which is what has been occurring over the past couple of weeks and it's taking way too much time. Too many payments are expiring causing extra work to reach out to the client to have them void and reissue, submit tickets to the engineering team to block the payments, only to repeat the process if the payment expires again because it's still a bad email. This causes the client to lose faith in the program and want to start unenrolling vendors since it's causing them extra work.
They can't continue reaching out to each vendor when their payment is about to expire to find out we had the wrong email. The Notification/Flagging and Reporting of Bounced Virtual Card Payment Remittance Emails feature will be a great help!
Ebony Hamlet
Can PPS implement a failsafe if the email with the remittance doesn't work? Can CPX pull payments that are supposed to go to proxy from reports or something? Just because email isn't always reliable.. like what if there is a system issue with the emails? Who would know?