Workflow rules are not audited and we often get questions about "why is my workflow doing XYZ". We can only tell them what the workflow was and what it currently is set to, but we need to be able to tell clients WHO changed it and WHEN.

Option to provide different approvers for the different bank accounts for her one client.

Bank definition should not include clearing accounts as it allows for mistakes when setting up bank accounts. Instead the clearing account should be moved to the client level.

Record of last time each type of file was downloaded/processed so we can confirm that everything is processed or identify what files were missed.

When you check the "For the Benefit of" on the additional payment information for vendors, it isn't clear what's transmitted. Instead of labelling the memo line as "Memo", we should change the label to say "Originator to Beneficiary Information". ...

If a user account is accessed from an unusual IP or at an unusual time, an email alert should be sent to the user to reset their password

Mexico uses "CLABE" https://en.wikipedia.org/wiki/CLABE#cite_note-clabeabm-1 and AgilLink should have a method to help the user formulate the proper account number if trying to pay a Mexico Vendor via International Wire.

AgilLink should be a single tenant environment where each client has their own set of virtual servers. This will minimize the risk of data exposure, loss, and needing to spin up new physical servers as demand for the product grows. Virtual servers...

AgilLink should provide error codes along with a database of errors codes & help messages so users and support staff can better resolve errors as they occur.

On the home screen, between where you would balances and the bar graph charts for open AP, we should put a calendar where client activity is visible. The calendar should display events according to user preferences and can include things such as: ...