We appreciate the ability to create custom reports using data from the Payment Module, which helps us prepare our board report more efficiently. Payment approvers especially value the mobile app's convenience for reviewing and approving payments. Review collected by and hosted on G2.com.
We have a few noted System idiosyncrasies:
1. Bank Account Module (BAM): When a new account is added Core Data - Accounts, the Bank Account module does not automatically populate.
2. Payment Module - Attachment Issue: If a user clicks the back arrow instead of the Menu → Close button while adding an attachment to a payment, the payment is lost and must be re-entered.
3 Payment module - Approval Workflow: A payment must be approved from outside the payment record; otherwise, the transaction is not automatically remitted to the bank, causing processing delays.
4. Payment Module – Status Label: After executing a payment, the system displays the next action as “Terminated,” which can be confusing.
5. Mobile App: Users would like enhanced tools and improved accessibility within the mobile application. Review collected by and hosted on G2.com.
Thank you for updating your review, and for the detailed, practical feedback. We’re especially pleased Kyriba is helping you build custom Payment Module reporting for your board pack, and that your approvers are getting real value from mobile approvals.
We also appreciate you calling out the specific “idiosyncrasies” you’ve encountered - this level of detail is exactly what helps us improve. A couple of the items you noted are tied to how we enforce controls and workflow consistency (for example, approvals are designed to be managed through the approvals workspace to ensure the right authorization path and downstream processing), but we agree the experience should be clearer and more forgiving day to day.
On the remaining points - BAM population behavior, the attachment/back-navigation scenario, and the “Terminated” label - we understand why these can feel unintuitive. We’ll share these with the appropriate teams, and we’d welcome the chance to review your specific setup so we can (1) confirm whether configuration changes can reduce manual steps, (2) help your users avoid the attachment workflow pitfall, and (3) provide clearer guidance on payment statuses to prevent confusion for occasional users.
Finally, on Kyriba Mobile: thank you for the request. If you can share which tools or accessibility improvements would make the biggest difference for your approvers, we can route that feedback more precisely and align it with ongoing enhancements.
