Before a core banking go-live, 40 job roles mapped to 611 screens
A bank moving to a new core banking system had job titles matched to access in the old system, but none in the new one. Reusing the old mapping, we built one matrix of 2,368 rows in under three weeks.
From our own project and product work. Client names and identifying details are removed, and some figures are rounded.
The situation
A bank was moving to a new core banking system. Every job title needed the right screens before go-live, with maker, checker and enquiry access kept apart. The old application already matched job titles to access descriptions. The new system's menu list had no job titles linked to it at all.
What we did
- Start from what exists. We took the job title and access description list from the old application.
- Match. For each description, we found the matching screen in the new system's menu list.
- Split. We kept each job title and split its role into Maker, Checker and Enquiry.
- Clean. We removed duplicates and skipped roles already covered by another department.
Results
| Measure | Result |
|---|---|
| Departments covered | 16 |
| User records reviewed | About 720 |
| Job roles mapped | 40, split into 82 maker, checker and enquiry roles |
| Screens mapped | 611 |
| Rows in the final matrix | 2,368 |
| Time taken | Under three weeks |
What changed
- Reuse before rebuild. The old mapping did most of the work; nothing started from a blank sheet.
- Maker and checker apart from day one. Segregation of duties was built in, not reviewed in later.
- One master matrix. The same file serves user creation now and audits later, and the method works for any system migration.
Products and services
Our digital, cyber and IT risk team supports system migrations like this one. See financial services and a bank's access review across 15 applications.