Skip to Content

Internal control, third-party risk and internal audit for a chemicals group, in eramba

A global control catalogue, without copying every control into every company, with audits scheduled per control and supplier risk on the same platform.
17 November 2026 by
Internal control, third-party risk and internal audit for a chemicals group, in eramba
OdooBot
Sector
Chemical industry
Company size
International group
Business lines
GRC and ESG
Solutions
GRC platforms
The challenge

The same controls in many companies, and one team to review them

The group has companies in several countries and an internal audit team that works for all of them. It wanted to bring internal control, supplier risk and internal audit into eramba.

Many of its controls are global and apply to the whole group. Others belong to a single company. If each company has its own copy of a global control, the same control gets reviewed several times and the catalogue grows for no reason.

  • Global controls and company-level controls, with no duplicates
  • Suppliers assessed with the group's own questionnaire
  • Control audits with a date, an owner and evidence
  • Users and permissions managed by the client itself
The solution

Design by workstream, then implementation

Kick-off and planning

A planning session with their team to agree roles, the timeline and the environment where everything would be implemented and tested.

Internal control design

Several review sessions on the internal control design with their team, before building anything on the platform.

Third-party risk

Their supplier assessment questionnaire, brought into eramba, with each supplier's score on the platform.

A global catalogue

Each global control exists only once, and each company's own controls are linked to it where it applies.

Scheduled audits

Each control generates its own dated audits. The control owner certifies it and whoever provides the evidence uploads the files.

Internal audit

Dedicated internal audit and third-party risk sessions with the people in charge of each workstream in the group.

How we did it

Design first, one workstream at a time

The project kicked off in October 2025 with a planning meeting with their team. The design sessions came in November: several for internal control and one for third-party risk. Implementation reviews started in December and carried on until February 2026.

We ran it together with another integrator, who holds the relationship with the client. The eramba licence was bought through us, as a Gold Partner.

Third-party risk came in with the group's own supplier questionnaire, reviewed with their team in February. In April there were sessions dedicated to third-party risk and internal audit.

The design decision that mattered most was the catalogue. Each global control exists only once and each company's controls are linked to it where it applies. That way, what belongs to everyone is reviewed once, and each company answers for its own.

Over the summer the internal control audits were scheduled. Each control has its own calendar, and each date generates an audit: with a quarterly review, that's four a year per control.

The design and the project management were ours, as eramba specialists; the integrator we worked with handled the data loading.

After implementation

The client runs its own platform

The client's IT team handles adding and removing users and managing their permissions. Their internal audit team has one user for preparing training for their people, and another with a control owner's profile, to see the platform as each person will see it.

An internal control platform changes with the organisation. When control owners change, controls can be reassigned in bulk from the platform, without going through them one by one.

The product is at eramba. How we choose a platform with each client is in GRC platforms.

Are your controls repeated in every company?

Send us the list of controls you have. We'll tell you which ones are global and what the catalogue would look like on the platform.