Skip to main content

What banks should prepare - data & governance

Data prerequisites (examples)​

  • Minimum data dictionary for each product (fields, definitions, allowed sources).
  • Quality rules for income, employment, and identity artifacts your channels will send.
  • Bureau / third-party usage register aligned to consent and retention decisions (your DPO leads).
  • Test data pack with no real customer PII for pilot workshops.

Governance prerequisites​

  • Risk & compliance orientation: Compliance & risk for partner banks (control objectives, diligence evidence, privacy/residency questions, incident template).
  • Credit policy owner named for each product line on Decision PRO.
  • Model risk owner for AIS outputs feeding Decision PRO screens.
  • Incident and escalation contacts on the bank side published internally.
  • Change advisory process for “policy version bumps” mirrored in IT change control.

Joint AIS + bank workshops (recommended)​

  • First-line ops: share Troubleshooting (bank view) with branch IT so common HTTPS / session issues are triaged consistently.
  • Half-day journey mapping: intake → decision → exception → reporting.
  • One-hour security review: identity, MFA expectations, session timeout policy (high level).
  • Quarterly roadmap alignment on new modules (collections, new channels, etc.)-subject to deployment configuration.

Next: Security & access · Overview