A microservices platform that unifies emissions reporting, electricity price compensation, master data, and regulatory document generation around one shared, validated source of truth.
This platform was built for a government authority responsible for administering emissions trading and industrial electricity price compensation programs. Regulated installations have to report their emissions and fuel consumption for compliance, while energy-intensive organizations can apply for compensation payments to offset the indirect cost of carbon pricing on their electricity bills - and both programs depend on the same underlying organization and installation records staying accurate and consistent.
Administering emissions trading and electricity price compensation means handling several distinct, interdependent responsibilities at once: collecting and validating installation-level emissions and fuel-consumption data, managing compensation payments for energy-intensive organizations, keeping organization and installation master data consistent across every program, and issuing formal regulatory decisions that have to be signed, tracked, and defensible.
Each of those responsibilities has its own data model, validation rules, and workflow - and all of them depend on the same underlying records staying aligned. Without one shared platform, keeping organization and installation data consistent across reporting, compensation, and compliance workflows, and generating signed regulatory notices consistently, becomes a coordination problem in its own right, on top of the compliance work itself.
|
PROBLEM Emissions reporting, compensation, master data, and regulatory document generation each have their own data and workflow, but all depend on the same underlying records staying consistent. |
CONSEQUENCE Without one shared platform, keeping data aligned across programs and issuing signed, defensible regulatory decisions consistently becomes its own coordination burden. |
Unitech DACH built a centralized platform that brings emissions reporting, electricity price compensation, master data management, and the regulatory workflows that connect them into one system, built around a shared, versioned source of master data and a common validation and document-generation layer.
| BEFORE | WITH THE PLATFORM | |
|---|---|---|
| Master data | Maintained separately for each program | One shared, versioned source reused across all programs |
| Data validation | Handled program by program | Rule-based plausibility checks applied consistently before data is accepted |
| Regulatory decisions | Produced individually per case | Generated from templates and signed via qualified electronic signature |
| Payments & address data | Coordinated separately with external systems | Directly integrated with the address and payment systems via built-in connections |
The platform is built as a microservices architecture, with each business domain - emissions reporting, electricity price compensation, master data, forms, and plausibility checks - delivered as an independently deployable service. Each service follows a CQRS pattern, separating the logic that changes data from the logic that reads it, so the read and write sides of each domain can be built and scaled independently. Services communicate over REST APIs and, where a process can run asynchronously, over a message broker - the compensation service, for example, uses message-based communication to avoid blocking on downstream steps.
On the frontend, a shared monorepo lets multiple Angular applications reuse common libraries, API contracts, and UI components, so additional special-purpose applications can be built on the platform without deep knowledge of its internals. Every service owns its own PostgreSQL database with versioned schema migrations, and a shared identity provider handles authentication and role-based access control across the whole platform. Internationalization (German and English) was built in from the start. Testing runs across unit, database integration, and end-to-end browser tests, with static code analysis as part of the delivery pipeline.
|
€5bn Yearly EU savings from the once-only principle |
44% Faster administrative procedures (SMEs) |
53% Lower administrative costs (SMEs) |
5 days Saved per user per year with eID & e-signature |
Centralizing emissions reporting, compensation, master data, and regulatory document generation onto one platform - built around shared master data and rule-based validation - is designed to reduce the coordination overhead of keeping four interdependent programs consistent, and to make regulatory decisions faster to produce and easier to defend, since they're generated from validated data through a built-in, auditable workflow.
Research on digital government supports this approach. The European Commission estimates that applying the once-only principle - collecting data once and reusing it across public services - can save up to €5 billion per year across the EU (European Commission, 2018). A 2024 Commission study projects that once-only data exchange cuts the time of administrative procedures for SMEs by 44% and their cost by 53%. In Estonia, eID and digital signatures save each user around five working days a year, roughly 2% of working time (Estonian e-government figures, ITU, 2017).
Figures are published industry benchmarks, not measured results of this project. Sources: European Commission, TOOP: reducing red tape for citizens and businesses (2018); European Commission, Study on benefits of the Once-Only Technical System for SMEs (2024, projected values); Estonian e-government figures presented at ITU (2017).
|
DEPLOYMENT OPTION Also available as a ready-to-use virtual appliance — a pre-configured virtual disk image with every required component already installed and set up — for organizations that want a fast, self-contained rollout with minimal in-house setup work. A key differentiator for customers who value deployment simplicity. |
INDICATIVE INVESTMENT Typically a fraction of the cost and time required to build and maintain a comparable system in-house. |
Angular, NgRx, Nx Monorepo, TypeScript - Java 17, Spring Boot, Spring Data JPA, Keycloak - PostgreSQL, RabbitMQ - Docker, GitHub Actions, SonarQube.