The challenge
A community-based mutual insurance organisation managed death claims through a paper-based process — claim forms received by post or in person, manually entered into registers, reviewed by committees, and settled by cheque. The entire process from claim submission to settlement took an average of 28 days.
The organisation served thousands of member families across multiple branches. The paper system had no audit trail that could stand up to scrutiny, and fraud investigation was almost impossible without digging through physical records.
An additional constraint: many branch offices operated in areas with unreliable internet connectivity. Any solution had to work offline, with periodic synchronisation when connectivity was available.
Why a desktop application
A web application was considered but ruled out due to the connectivity constraint. A desktop application running on branch office computers, with a MySQL database that could synchronise with the head office when connected, was the right architecture for the environment.
What we built
The system was built in .NET / C# with a MySQL backend, running on Windows desktops at branch offices and the head office.
Claim intake
- Member registration and family details stored per branch
- Death claim form digitised — all fields captured, documents scanned and attached
- System validates that the claimant is a registered member and that the policy is current before a claim can proceed
Approval workflow
- Claims route through a configurable approval chain: Branch Officer → Branch Manager → Head Office Committee
- Each approver sees only claims in their queue, with the full claim history and attached documents
- Approval actions logged with timestamp and user ID — tamper-evident audit trail
Fraud prevention
- Duplicate claim detection: the system flags any claim where the same member’s name, ID number, or bank account appears in another open or settled claim
- Claims that show anomalies are escalated to a special review queue rather than proceeding through the standard workflow
Settlement processing
- Approved claims generate a settlement record; the finance team marks settlement as paid and records the cheque or bank transfer reference
- Beneficiary notification letter generated automatically (printable)
Reporting and dashboards
- Real-time dashboards: pending claims by branch, average time-to-settlement, settlement volumes by month
- Fraud detection report: flagged claims and their disposition
- Audit export: full claim history exportable for external audit, formatted to the organisation’s regulatory reporting template
Offline / sync architecture
- Branch offices work fully offline; all data is written to the local MySQL database
- When an internet connection is available, a sync process pushes branch data to the head office server and pulls updates
- Conflict resolution logic handles cases where the same claim record was modified at head office and a branch during an offline period
Results
- Settlement time reduced from 28 days to 11 days — a 60% reduction, primarily from eliminating physical document transit and committee scheduling delays
- Fraud detection — 7 duplicate or anomalous claims flagged in the first 6 months, compared to 1 identified in the previous year through the manual process
- Zero data loss during testing of offline/sync scenarios — the sync architecture handled 14 conflict scenarios correctly in UAT
- Regulatory audit — the organisation’s first external audit post-deployment was completed in 2 days using the system’s export report, compared to 6 days of manual record retrieval in the previous year