Mandiri E-Claim
Designing an internal system for Bank Mandiri to file, check, and track credit insurance claims and subrogation with insurers.
Internal system- Solutions Analyst
- PT Bank Mandiri (Persero) Tbk
- 2021
- Figma
- Internal / not public


(01) — Context
Context & the challenge
Bank Mandiri insures productive loans such as KUR and KUM with insurers like Askrindo and Jamkrindo. When a loan goes bad, the bank files a claim with the insurer, and after the claim is paid the insurer can pursue subrogation. Each claim needs a set of documents, passes through several people, and has to be filed before it expires. e-Claim (Sistem Pengelolaan Klaim Asuransi dan Subrogasi) is the internal system that runs this process. As Solutions Analyst, I mapped the claim flow and designed the system's screens in Figma.


(02) — My role
My role
As a Solutions Analyst, I worked with the developers and the product team to define the requirements for e-Claim. I built the wireframes and mapped the business process flow so the system is easier for its users, and reviewed documentation and unit tests against the business needs.
(03) — System
System logic & architecture
The system follows a maker-checker chain. A claim moves through fixed tracks, and each track belongs to one role, so a claim is always with exactly one person.
- Roles. User BU prepares the claim, the CO Maker checks the documents, and the CO Checker verifies the claim amount before it goes to the insurer.
- Tracks. Preparation, document checking, verification, sent to insurer, waiting for payment, and paid, with side paths for revision, reject, appeal, payment failed, expired, and cancel.
- Claim types. Host-to-host claims with the insurer, manual claims, and incidental claims.
- Administration. Reporting, reconciliation, user and role management, and system parameters.


(04) — Features
Key features
The main screens of e-Claim, across roles.
- DashboardTask counts by status, claims by track, and the claims closest to expiry.
- My Task and claim listsLists for each status, from on progress to completed, reject, failed, manual, and others, with search and filters.
- Document checkingRetrieve documents the bank already holds or upload the rest, verify each one, then send the claim on or return it for revision.
- VerificationBulk verification of claimed and approved amounts, with the difference shown per debtor.
- Appeal, revision, and paymentAppeals after a reject, document revisions, and payment status pages, including failed payments that need reprocessing.
- Reporting and administrationReports, reconciliation, user and role management, and parameter settings.


(05) — Impact
Impact & outcomes
- flows designed, from login to reconciliation
- 30
- roles in the maker-checker chain
- 3
The design gave the bank one place to run a claim from preparation to payment, with a clear owner at every step. It is an internal system, so no usage or performance figures are listed here.

