Jaco van der Laan

GenAI for Data Modeling in Financial Services: Why Now Is the Right Time

22/09/2025  ·  Data Architecture  ·  Data Engineering  ·  Data Modeling

article base/genai databricks dbt genai metadata
‹ ›

How AI can transform regulatory complexity into a unified, business-friendly data backbone

Summary

Financial institutions are overloaded with regulatory data models. By using GenAI to extract, align, and code-generate from models like AnaCredit, RRE, and BIRD, we can create a generic logical data model (LDM) for the financial services industry — and bring it alive in dbt.

Key Takeaways

  • Regulatory models (AnaCredit, RRE, BIRD) contain reusable semantics we can mine.
  • GenAI can parse PDFs into structured metadata (YAML + ERDs) and propose cross-model mappings.
  • A generic LDM provides a stable integration layer between raw deliveries and enterprise analytics.
  • dbt on Databricks operationalizes the model with tests, documentation, and repeatable builds.
  • The result: faster compliance, transparent business-friendly mappings, and less duplicated ETL.

The Problem: Too Many Models, Too Little Reuse

Each regulation (AnaCredit, RRE, BIRD, Basel, local supervisory rules) comes with its own logical data model.

Banks respond by:

  • Building bespoke ETL pipelines
  • Maintaining thousands of Excel mapping sheets
  • Struggling with fragmented, fragile reporting layers

This is exactly the trap I described in The Case for a Business-Shaped Integration Layer: delivery-centric models never converge into a sustainable enterprise backbone.

The Idea: A Generic Logical Data Model (LDM)

Instead of reinventing the wheel for every regulation, we can lift core semantics and normalize them into a business-friendly LDM:

  • Core entities: Counterparty, Contract, Instrument, Property, Security, Group
  • Associative entities: Counterparty–Instrument Role, Instrument–Protection
  • Characteristic entities: Instrument Financials, Valuation, Rating
  • Reference entities: Code lists (instrument type, collateral type, sector, rating scale, etc.)

This generic LDM becomes the integration layer, mapping both regulatory deliveries and internal sources into reusable business views.

It builds directly on the principles I outlined in From Coding to Modeling: The Rise of Model-Driven Data Engineering: stop coding pipelines by hand, start designing reusable models.

Why GenAI Fits Perfectly

Generative AI is not a replacement for data modelers — it’s an amplifier.

  • Extract metadata → turn 200-page PDFs into structured YAML (see Metadata as Data)
  • Suggest mappings → detect overlaps like “Counterparty” in AnaCredit vs. “Party” in BIRD
  • Generate scaffolding → create dbt sources, staging models, marts, and tests automatically
  • Explain transformations → provide plain-language mapping explanations (link to Cooking with Data: How Business-Friendly Mapping Brings Clarity to ETL)

This is business-friendly mapping at scale, enabled by AI.

First Results: AnaCredit, RRE, BIRD in dbt

We’ve already tested this vision with three models:

  • AnaCredit → Counterparty, Instrument, Protection
  • RRE → Property, Valuation, Collateral linkages
  • BIRD → Parties, Groups, Securities, Positions, Ratings

Each was parsed into YAML, visualized as an ERD, and scaffolded into a working dbt project on Databricks.

With just a handful of CSV seeds, you can:

dbt seed
dbt run

…and query enterprise-friendly LDM views like ldm__counterparty or ldm__instrument.

This is exactly what I meant in Business-Friendly Mapping Meets dbt: dbt becomes the execution layer for logical building blocks.

Why This Matters

  • Compliance teams: see clear lineage from regulation to warehouse
  • Data engineers: stop reinventing ETL mappings, focus on reusable patterns
  • Business users: finally get human-readable mappings
  • The enterprise: achieves a single, reusable financial data backbone

This vision ties together the threads of Business-Oriented Data Modeling and Model-Driven Data Engineering.

What’s Next in the Series

  1. AnaCredit deep dive: extracting reusable semantics
  2. RRE deep dive: property, collateral, and valuation timelines
  3. BIRD deep dive: parties, groups, securities, positions, ratings
  4. Convergence: a unified financial services LDM
  5. From model to code: dbt implementation patterns
  6. Business-friendly mappings with GenAI
  7. The future of model-driven data engineering