What is our primary use case?
Our main use case for HighRadius Accounts Payable is to improve our accounts payable process. We started the UAT session in 2023, where HighRadius onshore team, offshore team, and technical team participated. We tested our live scenarios to determine what test cases would be needed if we went with HighRadius. We tested over 100 cases, but approximately 10 to 20 cases failed due to there being no capability in HighRadius.
How has it helped my organization?
HighRadius Accounts Payable is very useful for our organization. Before HighRadius, we had 10 to 12 members on the team. After implementation of HighRadius, only 2 to 3 members are required to handle the work, with the remaining members being released from the organization because of the automation process. This automation works well, though not at 100 percent, because we have exception cases that the system cannot fully automate. We need 1 or 2 team members to handle these exception cases, such as payments that need to go to GL, bank verification, or other special descriptions. These cases fail in HighRadius because the system cannot perform the assignment and verification with other teams.
HighRadius Accounts Payable has positively impacted our organization. As I mentioned, we had 10 to 12 members before implementation. After the implementation, we reduced 8 to 9 members from the team because the system can automatically handle accounts receivable and accounts payable processes. Less human intervention is needed overall, with human intervention required only for exception cases.
Regarding time saved and productivity improvements, when we receive 100 to 150 volumes per day depending on business inputs and requirements, the system can automatically process 70 to 80 percent of the payments. The remaining 20 percent requires human intervention, which does not take more time. For example, if one person working for eight hours was previously required to complete the process, that person is now only needed for 1 to 2 hours to handle the exceptions. The remaining 80 percent is automated, which is beneficial.
What is most valuable?
HighRadius Accounts Payable's best features include its automatic integration with banks. There is no need to log in as a user to the bank and pull information manually. Bank statements are automatically available within HighRadius itself. Most cases are automatically applied, but when the system cannot identify certain cases, we need to feed the system with the correct directions. We also have the opportunity to adjust the percentage of automation for exception handling. For example, if one case fails, we can set up the system to apply future similar payments to the correct account, using vendor records and vendor recognition. This allows us to guide the system to apply payments in the future without human interaction, which is one of the good benefits of HighRadius Accounts Payable.
HighRadius Accounts Payable is very helpful for accounts payable and accounts receivable processes across any domain, including collections. All functionalities for accounts receivable and accounts payable are good in this system, but I do not think it will automate the process for Record-to-Report.
The governance and security of HighRadius Accounts Payable is good. We have proper approval from the CFO and everyone because HighRadius picks bank statements without human intervention, which involves sensitive data. Governance and security with CFO approval are necessary here, and the system is good in this regard. There have been no data breaches, so HighRadius is strong in terms of security.
The accuracy and reliability of output from HighRadius Accounts Payable is high because of human error reduction. The system performs well, and we see 98.99 percent accuracy.
What needs improvement?
A specific example of a test case that failed during UAT for HighRadius Accounts Payable relates to the cash applications process when receiving payments from customers. We have two types of customer or vendor payments: miscellaneous payments and customer or vendor direct payments. Direct payments need to be applied to customer or vendor invoices, and those cases passed as expected. However, miscellaneous payments need to be posted to the journal entry rather than customer or vendor invoices. HighRadius Accounts Payable lacks the capability to handle these cases, so manual intervention is needed for them.
HighRadius Accounts Payable can be improved in cases where once payments are loaded into the system, users can easily filter exceptions where the system is unable to perform the work. Users can then focus on those cases, perform cross-checks and double-checks, and verify that the payments are applied correctly. This method would improve accounts payable processes.
An improvement is needed when we receive payments that need to be tagged to multiple vendors or multiple customers. We can add multiple vendors or customers in one instance, but if we receive the same scenario in the future, we must add multiple vendors and customers into HighRadius again. This process needs improvement from HighRadius.
For how long have I used the solution?
We have worked with HighRadius Accounts Payable for almost four years, from 2022 to 2026.
What do I think about the stability of the solution?
HighRadius Accounts Payable is definitely stable.
What do I think about the scalability of the solution?
The scalability of HighRadius Accounts Payable is good. It works well even during month-ends when we receive many volumes in the system. HighRadius has good capability to handle large volumes. On normal days, we process 100 payments, but during month-ends, we receive more than 200 payments. The system performs well in this scenario. However, regardless of the volume received, the automation percentage remains at 80 percent, meaning 40 cases require human intervention.
How are customer service and support?
Customer support for HighRadius Accounts Payable is good. We have pre-templates available within HighRadius itself that we can utilize. The system automatically picks up customer responses and sends emails to customers automatically, providing reminders on the frequency required by our organization. The customer-facing aspect is good.
Which solution did I use previously and why did I switch?
Before HighRadius Accounts Payable, we manually downloaded and reviewed all entries and all credit and debit entries. We would then start processing and collect details from our mailbox. After HighRadius implementation, the solution automatically picks up everything and is ready to use. The system automatically downloads bank statements, reads the information, and automatically segregates transactions according to descriptions, which is a good improvement.
How was the initial setup?
Setting up automation rules and guiding the system for future exceptions in HighRadius Accounts Payable is straightforward. It took only 10 days to set up everything from initial configuration through UAT to going live. When setting up the system for future exceptions, we can cover 90 percent of automation with only 10 percent of human intervention needed to achieve good process delivery. When we use any global financial system such as SAP or Oracle as required by our clients, HighRadius helps us push the data from HighRadius to that system. Interface issues can occur in these scenarios, but we can resolve them with the help of HighRadius support team.
What was our ROI?
I have definitely seen a return on investment with HighRadius Accounts Payable as it has saved our money and employees.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing for HighRadius Accounts Payable is good because the setup is already predefined in HighRadius. According to our design, the system picks up the cases and prices itself according to the standard predefined category and setup cost. The setup cost is not too high; it is less expensive. However, if we opt for additional features based on business requirements, the cost will increase according to HighRadius management involvement.
Which other solutions did I evaluate?
Before choosing HighRadius Accounts Payable, I evaluated other options. We previously used Excel VBA scripts and macros for the allocation purposes. The macros function is limited for automation compared to HighRadius Accounts Payable. HighRadius has good capabilities for automations. Macros can automate only 10 to 20 percent of processes, whereas HighRadius achieves 70 to 80 percent automation.
What other advice do I have?
I rate HighRadius Accounts Payable 7 out of 10 because we have exception cases where human intervention is needed. These human interventions are difficult to identify, which is why the system is unable to automate these cases. For example, if something goes from a vendor account to a GL account, it definitely fails in HighRadius. This is the reason I provided a rating of 7 out of 10.
HighRadius Accounts Payable is deployed in my organization as a private cloud solution. Users cannot log in if they use other VPNs. If someone connects through a different VPN or network, HighRadius will not work. It only works when using our office private VPN, so the security is good.
The cloud provider we use for our private deployment of HighRadius Accounts Payable is Google Cloud.
I would advise others considering HighRadius Accounts Payable that it is good because many organizations have moved from their old processes to HighRadius because of its good automation capabilities and the ability to reduce manual labor. This is why most companies have agreed to adopt and start using HighRadius Accounts Payable.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Google