CASE STUDY
Unifying multi-entity data for CRS & FATCA with Bragi
How a multi-entity financial institution pulled five fragmented client systems into a single, trusted view for CRS and FATCA, turning year-end panic into a continuous, exceptions-led process.
Trusted for regulated and high‑stakes data:






From five separate systems to one trusted model
This client was running five separate client administration systems after multiple acquisitions.
Each one stored client, account, and relationship data differently.
Sources: 5 line-of-business client admin systems (different structures, different rules)
Bragi: Daily ingestion → common client/account/relationship/tax model → data-quality checks → exceptions reporting
Destinations:
- CRS and FATCA XML submissions
- Internal validation reports
- Relationship manager packs
- Management dashboards
The challenge
- CRS and FATCA submissions had to be prepared five times over, one per system
- Inconsistent or incomplete tax fields (e.g. missing/incorrect TINs, tax residency, indicia)
- Difficulty determining which clients/accounts were in scope
- Mismatched relationship data across systems
- No easy way to trace reporting outcomes back to source
- Heavy dependence on key individuals from each system, and issues often found late in the cycle
- Country and product/relationship classifications handled differently in each system
Core problem: disparate data and varying data quality, not just the CRS/FATCA rules themselves.
Implementation with Bragi
Bragi ingested data daily from all five LoB systems, creating time-stamped snapshots for full auditability
All feeds were transformed into a single common data model (clients, accounts, products, relationships, tax attributes)
Centralised tax logic was applied once, across the unified model, to:
- determine in-scope clients
- classify reportable account/product types
- resolve relationships across systems
- identify missing or inconsistent data
Systematic data-quality checks ran across all records and fed into daily exception reports for tax and operations Management dashboards tracked issue volumes and remediation progress
In the full case study we walk through the model, the rules engine, and how the team onboarded five systems without a “big bang” migration.
Is this relevant to you?
This case study is especially useful if you:
- Handle CRS and/or FATCA reporting across multiple systems or entities
- Struggle with inconsistent client/tax data and late-discovered issues
- Need a single, auditable view of client and relationship data
- Want tax and operations teams to manage rules and mappings centrally and without needing developer support
PDF DOWNLOAD
Get the full technical breakdown
Download the full case study for a deeper dive into the Bragi implementation: the data model, Static Data Management setup, and how CRS/FATCA XML outputs and internal reports were automated.
No personal data required, instantly view the in-depth case study.