Skip to content
- Blog
- EN
The client was a financial services company working in invoice financing, with around ten employees. The business was running across several separate platforms. That meant a lot of manual work for a small team, and day-to-day operations that were slower and harder to control than they should have been.
The problem we solved
The company had reached the point where the setup was slowing everything down and decided to invest in a consolidated platform that would bring the main parts of the business into one system.
The new platform had to carry the full process: sellers registering and passing KYC, uploading invoices for financing, operations teams reviewing and managing those invoices, estimating risk, setting financing parameters, and preparing the transactions to be executed later through a payment service.
What we built
A consolidated platform covering three areas: a seller client application, an admin and back-office application for operations, and an investor platform.
On the seller side, users could register, go through KYC and upload invoices for financing. On the operations side, the back-office team could review uploaded invoices, estimate risk, set financing parameters and move invoices through a status-based workflow, with validation rules enforced at each status change so that an invoice could not move forward without the right information. The system also calculated transactions intended to be executed through a payment service, though that integration was not reached during the project. The investor platform supported the two seed investors, both large companies, and allowed individuals to register as investors and earn annual interest, with monthly investor payments calculated by the platform.
The plan evolved as the project grew. At the start, the core of the team was on the client side, including the CTO, business analyst and project manager. Over time we enlarged the team in Moldova and took on more ownership of the work. It was also Jivy Group’s first project delivered in Java. The platform ran on AWS infrastructure with Kubernetes, and we were responsible for moving production data from the old third-party system into the new one.
What was harder than expected
The data migration. Moving production data out of the old third-party system required a long set of mapping rules, careful decisions about how existing records should fit a new model, and a lot of validation to avoid errors that would be expensive to find later.
The second difficulty was the invoice interface. The workflow had many statuses, validations and required fields, and making it clear for the people using it every day, without loosening any of the business rules underneath, took more effort than expected.
The deadline sat over all of it. The business needed the platform quickly, and the technical and operational complexity was high.
Outcome
We delivered the whole platform rather than one slice of the workflow. Several disconnected tools were replaced by a single system covering seller onboarding, KYC, invoice upload, back-office review, status validation, risk and financing parameters, investor registration and investor payment calculations. Work that had moved between separate platforms with a lot of manual handling became one consolidated workflow.
The payment service integration was planned but not reached before the engagement ended. For us, the project was a first delivery in Java, and deeper experience in AWS and Kubernetes infrastructure, large-scale data migration, and fintech platforms that have to serve operations teams and investors at the same time.