Fraud and financial crime

Build an explainable credit risk model on DataNature for banks, credit unions and lenders

On DataNature, lenders build credit risk models from governed loan, repayment, account and document data, with point-in-time features in the feature store, interpretable or tree-based models tracked in experiments, reason codes stored with every score, fairness and stability tests recorded in the model registry, and batch or real-time scoring for applications and portfolio monitoring. DataNature Atlas provides lineage from source data to each decision, which supports model risk rules such as OSFI E-23 and SR 11-7 and adverse action explanations.

Published . Last updated

On this page

Credit decisions affect people's lives and are closely supervised. A credit model must predict well, and it must also be explainable, fair, stable and documented. DataNature lets lenders meet both needs on one governed platform, with data kept in-country.

What data goes into a credit model?

DataSourceNotes
Application dataLoan origination system, DocuContext for documentsIncome, employment and amounts extracted and validated
Repayment historyCore banking or loan servicingDays past due, missed payments, restructures
Account behaviourDeposits and cardsBalance stability, salary credits, overdraft use
Bureau dataCredit bureau feeds or Marketplace data productsWhere permitted and consented
Alternative dataMobile wallet, utility or rental paymentsUseful for thin-file customers, with consent

How do you build it, step by step?

  1. Define default and the horizon, for example 90 days past due within 12 months of origination.
  2. Build a point-in-time training table from Gold tables, using only information available at the decision date.
  3. Engineer and register features in the feature store: utilization, payment-to-income, months since last delinquency, balance volatility.
  4. Train candidate models with experiment tracking: a scorecard or logistic regression for interpretability, and gradient-boosted trees for accuracy. Compare discrimination (AUC, Gini), calibration and stability.
  5. Generate reason codes: store the top factors behind each score, so staff and customers can be told why a decision was made.
  6. Test fairness and stability across groups and over time, and document limitations.
  7. Validate independently and record the approval, with the training snapshot and documentation, in the model registry.
  8. Deploy to real-time scoring for applications and batch scoring for portfolio monitoring and early warning.
  9. Monitor population stability, default rates by score band, overrides and drift, and retrain on a set schedule.

How does DataNature support model risk management?

ExpectationHow DataNature supports it
Model inventoryEvery model, version and owner in the registry
Data lineageAtlas traces features and training data to source systems
ReproducibilityTraining snapshots in Iceberg tables with time travel
Validation evidenceMetrics, fairness tests and approvals stored with each version
Ongoing monitoringDrift and performance tracking with alerts
ExplainabilityReason codes stored with every score
Access controlPersonal and sensitive data masked by role during development

In Canada, OSFI Guideline E-23 sets model risk expectations for federally regulated institutions; in the United States, SR 11-7 guides banks. This is general information, not legal advice. See OSFI E-23 explained.

How do predictions reach decisions?

  • Loan officers see the score and reason codes in their workflow, with DocuContext supplying verified document fields.
  • AI360 Studio combines risk with propensity for pre-approved offers.
  • Voir drafts credit memos with cited figures for an officer to review; see credit memo drafting agent.
  • Early warning scores flag existing borrowers whose risk is rising.

Frequently asked questions

Should we use a scorecard or machine learning?

Many lenders use both: an interpretable scorecard for decisions and a machine learning model as a challenger, adopting it once explainability and validation are proven.

Can the model use alternative data?

Yes, with consent and a clear link to creditworthiness. Test that it does not introduce unfair outcomes.

Sources

How does DataNature Atlas keep this secure and compliant?

Investigators see what they need; analysts see masked identifiers; every score and decision is auditable. DataNature Atlas is the platform's governance module:

  • Knows your data: a catalog with automated PII detection and classification across Bronze, Silver and Gold.
  • Controls access: role-based grants plus attribute-based policies, row filters and column masks (null, redact, partial, hash, year only).
  • Governs AI: Voir agents are scoped principals; masks, row filters and PII guardrails apply to every tool call and answer.
  • Proves it: lineage from source to metric to decision, and an audit log of who or what accessed which data.
  • Stays local: Atlas runs inside your deployment, so policies, lineage and logs never leave your jurisdiction.

These controls support GDPR, PIPEDA, Quebec Law 25, CCPA, HIPAA and sector rules such as OSFI E-23. Read DataNature Atlas in depth or see security and compliance.

See it on your own data.

Book a demo

Demos and quotes are handled by Dlytica, the company behind DataNature.