All partnersSource systemsWeGroup × DIAS
DIAS logo

WeGroup × DIAS: The advice and distribution layer for DIAS users.

DIAS stays your back-office system of record. WeGroup adds the Extranet, the customer portal and Smart Buddy on top. Notes, documents and advisory updates flow straight back into DIAS through its API, with the compliance trail attached.

Live
DIAS read and write integration in production
30%
Less time on context-switching for advisors
4 weeks
Typical onboarding for a DIAS-running office
01Why this integration matters

DIAS is the back-office spine for hundreds of Dutch intermediaries, and it stays exactly that. The portfolio lives in DIAS, and we build to sit on top of it, not to touch it.

WeGroup lives on top of DIAS and adds three layers: the Extranet where advisors and (sub)agents work, the white-label customer portal for the end client, and Smart Buddy inside Outlook. Reads and writes run through DIAS' existing API, so the portfolio stays the source of truth without a parallel administration.

For intermediaries running DIAS, this means one consistent advice and distribution layer across the office and a complete compliance trail, without a second administrative track.

02What is technically possible

Extranet, customer portal and Smart Buddy

The Extranet, the white-label customer portal and Smart Buddy inside Outlook all run on top of DIAS, reading the live portfolio.

Bidirectional updates via the DIAS API

Notes, documents and advisory updates flow back into DIAS as the system of record, through its existing API. No rekeying, no batch sync.

Permission-aware

Reads and writes respect the DIAS role and permission model, including team and office boundaries.

Compliance trail attached

Every advisory action gets logged against the DIAS policy, with timestamp and user, ready for review.

03What is in scope

In scope

  • Live portfolio read-out from DIAS into the Extranet, the customer portal and Smart Buddy
  • Bidirectional updates: notes, documents and advisory updates from WeGroup back into DIAS via its API
  • Advice trace logged against the DIAS policy with timestamp and user
  • DIAS permission and office model adopted by WeGroup

Out of scope · stays with the partner

  • DIAS remains the source system for policy administration, renewals and bordereau reporting
  • Commission and billing flows stay inside DIAS
  • Insurer product data managed via DIAS stays the original there
06 · Frequently asked

What changes for the DIAS administrator after integration?

Nothing on the DIAS side. Administration, renewals and bordereau stay exactly where they are. WeGroup reads and writes via DIAS' existing API.

Do we need to replace DIAS to use WeGroup?

No. WeGroup is built to live on top of DIAS. DIAS stays the back-office system of record; WeGroup adds the Extranet, the customer portal and Smart Buddy on top, reading and writing through the DIAS API.

Is the DIAS role model respected?

Yes. WeGroup's read and write actions honour DIAS' role and rights model, including team and office boundaries.

Is this an intended migration to Blinqx?

No. The DIAS integration is independent of the fact that DIAS Software has been brought under the Blinqx umbrella. Existing DIAS installations remain supported by WeGroup.

Run on DIAS? Let us show you the layer above it.

30-minute walkthrough on your own DIAS install, with your own portfolio. No prep work needed.