SAMA Regulatory Reporting & BI

Why SAMA Regulatory Reporting Is Different

Regulatory reporting is not internal business intelligence with a different audience. The schema is defined outside the bank, the submission windows are fixed, and a field that changes on the regulator’s timetable has to be reflected end to end — source system, model, report — before the next cycle. That constraint shapes every technical decision: message handling has to be tolerant of structural change, and the lineage from a reported figure back to its source has to be demonstrable rather than assumed.

How the Work Was Structured

• Environment review — understanding the existing SAMA Tanfeeth landscape before changing anything in it.
• XML request and response handling — parsing and generating the message structures the reporting services depend on.
• Metadata and business-layer extension — extending the existing model rather than building alongside it, so one definition serves both new and existing reports.
• Presentation layer and BI analysis — building the new reporting services and enhancing existing ones.
• Testing and user acceptance support — regression across existing reports, not only validation of the new ones.
• Operational support — continuing past go-live, through the submission cycles that follow.

What Mattered Technically

Three things carried disproportionate weight on an engagement of this shape. First, extending existing metadata instead of creating a parallel model — parallel models are where regulatory figures start to disagree with each other. Second, treating existing reports as part of the test scope, because a change to a shared business layer reaches further than the requirement that prompted it. Third, keeping performance and data-flow behaviour under review throughout, rather than treating it as a late-stage concern.

Capabilities Used

• Data management and engineering — modelling, metadata, and the pipelines behind the reports.
• Business intelligence and self-service reporting — the presentation layer and analysis work.
• Technology consulting — environment review and solution shaping.
• Embedded specialists — the delivery model used to work inside an existing bank environment.

Related Work

• SME in a Box EDW dashboard
• NEWGEN mortgage and credit card dashboards
• RBG segmentation consolidation

Working on Something Similar?

If you are facing a regulatory reporting change, an existing BI estate that needs extending, or a submission cycle that is becoming harder to hold, tell us what you are working with.