Hotovo was quickly entrusted with the development work for 2opus’s core business – the leading fintech company, plus many other clients. Gradually, more and more applications changed “ownership” to Hotovo, and we became an instrumental part of 2opus’s development team.

We developed a new application for multithreaded batch processing, implementing one of the core business processes, along with other new applications or libraries, as needed and according to requirements. The applications both extended and automated the functionality of Unit4 Financials by Coda and provided integration with external systems, allowing their clients to implement company-specific tasks.

Another important step was updating the applications to Java17 and removing standalone Tomcat servers for each application – with most of them being replaced with embedded Tomcat. Applications also lacked a user interface and mostly utilized provided REST endpoints. This led to a decision to create a central UI that would enhance the functionality, visibility and overall user experience, as well as improve the security.

Short summary of some of the core daily business processes Hotovo was involved in developing:

1. Customer data synchronization between the customer configuration (self-care) system and Unit4 Financials by Coda. Includes data such as bank account number, email, settlement frequency, payment day, kind of reports requested, and more.
2. Batch import of payment summaries from billing systems into Unit4 Financials by Coda.
3. Batch invocation of pay-run generation (proposals), writing to the books and actual payout to customers.
4. Batch report generation (PDF; Balance Note and XML; Electronic Payment Advice) and distribution to customers (via email; SFPT).
5. The team was involved in all phases of the software cycle: requirements gathering, solution designs (which involved close cooperation with 2opus to transform business requirements into technical ones), development, code reviews, documentation, automated and manual testing, release and deployment, and project management.
   

1. Fixed performance issues for the critical pieces of software.
2. Implemented new requirements into existing applications.
3. Implemented new pieces of software for batch processing, according to the requirements.
4. Technical stack has been modernized and united where possible (Spring Boot).
5. Defined clear and united processes for project management, development, release & deployment.
6. Migration of all projects from Mercurial to Git (GitLab), or started versioning if it was missing, enforcing GitFlow workflow and other rules – continuous integration.
7. Enforcing semantic versioning for all projects with respect to the relationship to the main product, Unit4 Financials by Coda.
8. Standardized configuration and logging for all applications.
9. Written exhaustive documentation for all applications, both user guides and technical guides.
10. Updates of all projects to support the new version of Unit4 Financials by Coda.
11. Developed software to gather (and then import) anonymized data from various production systems in order to replicate the use-case in the development process and speed up the development, and to be able to quickly replicate and troubleshoot possible issues in non-production environments.
12. Similar results were achieved for 2opus (now ACE Solutions)’s other smaller customers where Unit4 Financials by Coda is also the core offering.
13. Successful and ongoing cooperation since 2018.
14. High levels of trust, which form a major factor for our continuous and successful partnership.

The future of ACE Solutions & Hotovo's collaboration

There’s no change at all to the partnership with Hotovo following the merger between 2opus and ACE Solutions, and we remain an integral part of their team.

An upcoming project is to centralize the whole ecosystem’s functionality, so the user will see everything they need in one place. This has a lot of implications on the underlying structure of the applications, and the need to adapt the error handling. There is also a discussion about migrating the Coda system to a cloud version, which will bring a lot of changes – especially those related to database communication and possible performance challenges. We’re also discussing the possibility of migrating the whole environment, along with all of the applications, to a cloud-based solution, in which case a lot of refactoring on the older applications will be needed.

1. 4 Back-End & Front-End Developers