Solution

Customer portals for self-service integrated with SAP and CRM

Invoices, contracts, meter readings, orders: a good customer portal answers what today ends up in the call centre and the sales back office. The prerequisite is clean integration with SAP, CRM and billing. That is exactly the integration we build.

Illustration with sample data: customer portal with invoice and meter reading, connected to CRM and billing

Starting point

A well-connected portal takes the load off the call centre and back office

The front end of a portal is quickly designed. The difficulty lies behind it: the data sits in SAP, in the CRM and in specialist applications, often of varying quality and with their own rules.

Without the connection, the portal shows outdated information and the requests end up back in the call centre. The portal becomes an additional channel instead of reducing the workload.

Customer service employee of an energy utility wearing a headset, the screen showing a customer account with electricity consumption, example displayAI

Typical signs

  1. Meter readings, address changes or orders are transferred into SAP by hand.
  2. Customers call because they cannot find invoices or contract data online.
  3. The existing portal is based on a legacy application that hardly anyone can still extend.
  4. Business and private customers need different permissions, views and processes.

Scope of services

From login to SAP integration, we deliver the entire portal

  • Portal architecture

    Roles, permissions, data flows and tenants, coordinated with your SAP and CRM team.

  • Self-service functions

    Onboarding, invoices, payments, contracts, meter readings, orders and documents.

  • Integration with SAP, Dynamics and Salesforce

    Via REST APIs and middleware, with clean data synchronisation and error handling.

  • Portal and app from a single source

    Web and mobile use the same interfaces and show the same data.

  • Multi-tenant platforms

    Several brands, companies or customer groups on a shared technical foundation.

  • Replacing legacy portals

    Step-by-step migration, so your customers can keep using the portal during the switchover.

Operation

After go-live, we keep running your solution

Maintenance, security updates and further development after go-live, hosting in Switzerland (Infomaniak) or in the EU, developed in our development centre, certified to ISO 9001, 14001, 27001 and 45001. We build nothing that we would not also run ourselves.

  • ISO27001ISO 27001: Information security
  • ISO9001ISO 9001: Quality management
  • ISO14001ISO 14001: Environmental management
  • ISO45001ISO 45001: Occupational health and safety

Systems

Systems we integrate

We work with what you already run and only recommend a switch if it pays off.

All systems at a glance
Development
  • React
  • Java
  • .NET
  • REST API
  • PHP
  • Next.js
  • Symfony
Commerce
  • Payment providers
Enterprise Systems
  • SAP
  • Microsoft Dynamics
  • MS SQL
  • Salesforce
CMS
  • Adobe Experience Manager
  • Kentico
  • TYPO3
Cloud
  • Infomaniak
  • Azure
  • Kubernetes
  • AWS

and many more

Approach

From the first conversation to operation in four steps

  1. Analysis

    We map processes, systems and data quality and clarify which requests can be shifted to self-service.

  2. Architecture

    We define roles, interfaces and data flows together with the people responsible for your SAP and CRM.

  3. Implementation

    In stages, with functions you can use early on and tests against the real interfaces.

  4. Operation

    Monitoring, security updates, further development and hosting in Switzerland or the EU.

Projects

Swiss projects with customer portals

Named references from Switzerland. Further REEA Group projects from international markets follow below.

More REEA Group projects from international markets
Monitor showing an energy portal with electricity consumption in kWh, example displayAI
  • Customer portals & self-service
  • Energy & utilities
  • REEA Group project

Customer portal and cloud migration for an energy supplier

2channels on one platform: self-service portal and app, connected to SAP and Dynamics

  1. Problem

    The customer portal was based on a legacy PHP application that could hardly be extended any more. Self-service for web and app was required.

  2. Solution

    Java microservices on Azure with Kubernetes replace the legacy application and connect SAP and Microsoft Dynamics. Content comes from Adobe Experience Manager.

  3. Integration
    • Java microservices
    • Azure
    • Kubernetes
    • Adobe Experience Manager
    • SAP
    • Microsoft Dynamics
  4. Result

    Customers handle onboarding, invoices and payment themselves, on the web and in the app.

Read case

More references

References

What clients say about working with REEA

Clients from Switzerland and international projects of the REEA Group. The testimonials are verified client reviews on Clutch.

View all reviews

  • Müller + Krempel AG, BülachDigital Sales Specialist

    What we found most impressive about the company is their pragmatic, friendly, and solution-oriented approach.

  • A. Kuster Sirocco AGWebshop Manager

    They always satisfy our requests and can resize the team according to our needs in almost no time.

  • ALBIRO AGIT Coordinator

    The quality of the work delivered was impressive.

  • Web agency in BaselExecutive

    It’s a great pleasure to work with the entire team.

Starter offer

Your starting point is the Portal Architecture Workshop

Half a day on site with your business and IT leads. We work out the target picture for your portal, the necessary interfaces and a phased plan with a rough effort estimate.

Request an appointment

FAQ

Frequently asked questions

That depends on the number of connected systems, the roles and the self-service functions. In the portal architecture workshop, we develop the target picture and a rough effort estimate. This gives you a solid basis for your budget and decision.

With SAP, Microsoft Dynamics and Salesforce, as well as billing, document and payment systems that offer an interface or can be connected via middleware. Where no interface exists yet, we develop it.

Yes. We replace legacy applications in stages, for example with microservices in the cloud, and switch functions over one after another. This keeps the portal usable for your customers throughout the changeover.

Not necessarily. One platform can serve several customer groups, brands or companies, each with their own permissions and views. Whether that makes sense in your case is something we clarify in the architecture phase.

On request in Switzerland with Infomaniak or in the EU, for example on Azure or AWS. Our development centre is certified to ISO 9001, 14001, 27001 and 45001.

Your system, our connection

A plan for your integration in 60 minutes

In the free Integration Check we map your system landscape, show the three most important starting points and prepare a cost estimate.