Skip to content
Harmonize IT

Case study · EU public institutions

Case study: SAP integration for an EU institution

For a European public institution, we integrated a Java Spring Boot and Angular business application with the institution's SAP system and an electronic signature service. Financial data now flows between the two systems automatically, with full traceability and no double entry.

Last updated:

Context

A European public institution manages part of its operational and financial processes in a custom business application built with Java, Spring Boot and Angular. The institution’s accounting and budget execution run in SAP, the system of record for all financial data.

The two systems had grown side by side. Users prepared files in the business application, then re-entered the financial elements in SAP. Documents that required a formal signature followed a separate, largely manual circuit.

Challenge

The institution wanted a single, reliable flow from the business application to SAP, and a signature step that was both legally valid and fast. Several constraints made the project demanding:

  • SAP is the source of truth. The integration could not bypass SAP’s own controls or create inconsistent states between the two systems.
  • Strict audit requirements. Every financial exchange had to be traceable: who sent what, when, and what SAP answered.
  • Long-running, multi-step processes. A file could be created, validated, sent, rejected, corrected and sent again. The integration had to handle each state without manual repair.
  • A shared environment. SAP is used by many teams, with fixed release windows and limited test slots. Mistakes are expensive to correct.

Solution

We worked as an extension of the institution’s development team, on design and on delivery.

A dedicated integration layer. Instead of calling SAP directly from business code, we built an integration module in Spring Boot that owns all exchanges. It translates the business application’s model into SAP’s interfaces, validates data before sending, and exposes a simple internal API to the rest of the application.

Reliable, replayable exchanges. Each call to SAP is recorded with its payload, status and response. Calls are idempotent, so a retry after a timeout cannot create a duplicate. Failed exchanges are visible in a monitoring screen where a functional administrator can inspect and replay them.

Clear status for users. In the Angular interface, users see where their file stands: draft, sent, accepted by SAP or rejected, with the reason returned by SAP in plain language. Errors are corrected at the source rather than by email.

Electronic signature. We integrated an e-signature service (DocuSign) into the workflow. Documents are generated by the application, sent for signature to the right signatories in the right order, and the signed version is stored with the file together with its evidence trail.

Testing against reality. Because SAP test slots were limited, we built contract tests and a simulator for the SAP interfaces, so most scenarios could be validated continuously in the CI pipeline before each shared test window.

Outcome

  • Financial data is entered once. The double entry between the business application and SAP has been removed.
  • Every exchange is logged, traceable and replayable, which answers the institution’s audit requirements.
  • Signature moved from paper-based circuits to an electronic workflow that is tracked in the application.
  • The integration layer was designed as a reusable component, giving other applications of the institution a tested path to SAP.

This project is typical of our Architecture & Modernization work: connecting an existing application to core enterprise systems without disrupting either. The application itself was delivered with our Enterprise Software Engineering practice.

Expertise behind this project

More case studies

KYC and compliance

KYC platform for a global investment bank

Building the Java Spring Boot microservices and Angular front end of a know-your-customer platform for a global corporate and investment bank.

  • Java
  • Spring Boot
  • Angular
  • REST microservices

Financial SaaS

Multi-tenant financial SaaS with CQRS and DDD

Designing a multi-tenant financial SaaS platform on AWS with CQRS and Domain-Driven Design for a European financial software vendor.

  • Java
  • Spring Boot
  • Angular
  • CQRS

Have a similar challenge?

Tell us about your project, your contract need or the team you want to extend. We reply within two working days.