Home page
/

Project

Automating 20+ HR Processes

in an international IT holding company with 3,000 employees

About project

About project

About project

HR specialists have long stopped filling out documents manually and now rely on automated off-the-shelf solutions. However, when an organization has multiple large branches or operates as a group of companies, different services need to be integrated. Building a proprietary system from scratch is time-consuming, expensive, and inefficient. At the same time, HR processes still need to be simplified and automated to reduce the risk of human error and free up HR teams to focus on truly important tasks.

The client’s primary HRIS (HR Information System) is HiBob. This is a large customizable platform that provides out-of-the-box functionality such as onboarding, reporting, leave and travel management, and more. In addition to HiBob, the client also uses several specialized systems designed to simplify specific processes, including:

Navan — corporate travel management system (including flight bookings)

Expensify — expense and reimbursement management

Navex One — risk management and compliance

Power BI, SharePoint — reporting

TeamTailor — recruitment

and others.

Some of these systems have out-of-the-box integrations with each other. However, many tasks remained that could not be solved with built-in automation tools — either because the required functionality was missing or did not meet the company’s requirements. As a result, HR specialists and employees had to perform a huge amount of repetitive manual work.

Project in numbers

0regional offices and headquarters

0months of project work

0,000employees

BUSINESS TASKS AND SOLUTIONS

BUSINESS TASKS AND SOLUTIONS

BUSINESS TASKS AND SOLUTIONS

We built multiple integrations between services. Below are the key ones.

  1. Automating internal processes in HiBob

Problem: Not all tasks can be solved with HiBob’s built-in tools. According to the business logic, changing one employee field should trigger updates in several other fields based on specific rules.

Solution: We generalized this logic and implemented a set of processes that map fields according to the client’s rules. We also built a process that checks employee data consistency and sends notifications if certain data fields are missing or incorrectly filled. The client’s holding company includes four companies, each using its own instance of HiBob as the main HRIS — and our processes work with all four instances simultaneously.

Result: Within six months, our system automatically updated more than 70,000 fields, significantly simplifying and automating HR operations.

  1. Coordinated travel management with Navan

Problem: Employees book flights and hotels through Navan. After booking, they must manually enter the travel information into HiBob, because it’s the main HRIS. If a trip is canceled, they must also remove it from HiBob. Employees often forget to do this. Navan does not provide an out-of-the-box integration with HiBob for managing business trips.

Solution: We developed an integration that automatically manages employee trips in HiBob based on bookings created in Navan. The system attaches booking documents (flight, hotel, etc.) and notifies responsible staff via email if trips overlap.

Result: Employees no longer need to manually synchronize travel data between the two systems, eliminating human error in the process.

  1. User provisioning: HiBob → Navex One

Problem: Navex One is a system used by employees, but it does not have a built-in integration with HiBob for managing user accounts. HR staff had to manually create accounts for new employees, delete accounts for employees who left the company, etc.

Solution: We built an integration that keeps Navex One accounts synchronized with HiBob: creating accounts, deleting accounts, updating accounts automatically.

Result: Access management in Navex One now happens automatically and always stays consistent with HRIS data.

  1. User provisioning: HiBob → Expensify

Problem: Expensify manages employee expenses. Similar to Navex One, the system lacks built-in integration with HiBob. However, account management is more complex: each employee has an approval chain for expenses, creating a large relationship graph that is extremely difficult to maintain manually.

Solution: We implemented a set of processes that maintain this graph automatically, creating necessary relationships and recursively removing them when needed.

  1. Advanced reporting: Power BI. SharePoint

Problem: HR specialists needed aggregated data about employees from multiple systems. HiBob cannot generate such cross-system reports, so HR teams had to compile large reports manually, which took significant time.

Solution: We implemented a reporting system that generates various employee reports automatically. Some reports collect employee travel data and send it to Power BI for further automation and analytics. Other reports aggregate employee data from multiple systems (for example, HiBob and Expensify) and store it in SharePoint for HR review.

Result: HR teams now receive the required reports automatically and can react promptly to changes in key metrics.

20HRProcess

RESULTS

RESULTS

RESULTS

As a result, we built a system that

  • automates more than 20 of the client’s business processes
  • eliminates errors in the use of HR services caused by human factors
  • reduces the time employees spend on routine tasks by hundreds of hours every month.

We created a system that supports HR specialists rather than working against them. With it, HR teams can choose tools based on their needs rather than being constrained by the technical limitations of system integrations, as we now handle the automation of the repetitive but important parts of their work.

20HRProcess

TECHNICAL IMPLEMENTATION

TECHNICAL IMPLEMENTATION

TECHNICAL IMPLEMENTATION

To solve these challenges, we developed and maintained a custom integration platform connecting all services used by the client.

The system architecture is fully serverless and makes maximum use of Azure services.

We used Terraform to declaratively define the resources required for the system to operate. Because a large number of resources had to be created — the client has four separate companies, each of which requires two environments with the same processes but different configurations — the entire infrastructure, consisting of several dozen resources, would otherwise have had to be duplicated eight times. However, because the infrastructure was created and maintained using Terraform, we were able to significantly optimize and speed up the delivery of changes and eliminate configuration inconsistencies in the cloud resource configurations.

The serverless architecture of the solution also reduced resource consumption costs by an order of magnitude compared to what a similar server-based solution would have cost.

As a result, infrastructure maintenance costs were minimized, allowing most of the effort to be focused on implementing business logic.

Let's work together!

Attach file