DimArn — ideas that work.
← Euroclear portfolio
Euroclear / Retrospective case study

FundSettle · Orders & reporting.

UI/UX & Applications

How can specialist users review fund orders, handle detailed forms and move between transaction and reporting tasks without losing their place?

Based on archived designs: context, design intent, observable work and available evidence.

Sector perspective & sources
Current sector perspective · 15 November 2026

Why this matters today.

Scale & operating context

Global financial-market infrastructure. More than €43 trillion in assets under custody at the end of 2025; this is custody volume, not company valuation or market share.

Publicly documented scale

Today's priorities

At this scale, operational and cyber resilience are central concerns. The National Bank of Belgium also identifies the move towards a shorter settlement cycle as a major industry priority.

Design perspective

For interface design, this suggests a strong focus on readable data, visible status, clear exception handling and dependable workflows. These are present-day design considerations, not a claim that the historic projects addressed a 2026 programme.

Sources & editorial note

Sector facts come from the sources below. Design implications are editorial analysis. This current perspective is not the original project brief and does not establish historical objectives, methods or results.

01 / Context & contribution

The starting point.

FundSettle brings together fund-order entry, redemption and portfolio reporting. The archived interfaces address specialist users moving between detailed forms and transaction lists.

Design contribution shown
UX/UI interface design
Design consideration
Detailed input and continuity between tasks
02 / Design intent

What to make clearer.

Keep an order readable from entry to review: consistent field groups, recognisable actions and enough context to move between transactions and reports.

03 / Method & feedback

Iterate. Listen. Refine.

Agile / ScrumIterative designFeedback loops

Break the flow into sprint-sized tasks, review form states with business and development teams, then feed comments and exception scenarios into the next design iteration.

A methodological reading, informed by the visible work and professional practice; not a reconstructed log of workshops, tests or sprints.

04 / Observable design

Read the design.

  • A repeated navigation structure across operational screens.
  • Dense tables paired with task-specific forms.
  • Visual emphasis used to distinguish data and actions.

Explore the archived screens and applications. Select an image for a closer look.

UX 15 · Original portfolio material
UX 16 · Original portfolio material
UX 17 · Original portfolio material
UX 18 · Original portfolio material
UX 19 · Original portfolio material
UX 20 · Original portfolio material
UX 21 · Original portfolio material
UX 22 · Original portfolio material
05 / Results & evidence

Define what success means.

Success criteria

Intended improvements to assess, rather than historical performance claims.

  • More orders completed without correction
  • Higher user confidence during review
  • Fewer requests for help with order entry
Documented evidence

Order forms, transaction lists and reporting screens document the interface scope and its recurring navigation patterns.

Archived survey results, approval rates and support statistics are not available for this case.

Your next assignment

Let's work
together.

Discuss your project