1. Fraud Detection System
  2. Data model
Reference

The tables behind Fraud Detection System

Fraud Detection System ships with 12 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.

Tables
12
Features
6, plus shared settings
Change it
Add fields and tables in Proto

How the model is organised

Case intake

Applicants identifies the person; Applications carries the numbered request and assigned person; assessment evidence carries provider references and documents.

Investigation

Detection rules holds the versioned rule, while fraud alerts links that rule to the application and its disposition.

Decision

Credit decisions records reviewer, decision, reasons and approved amount against Applications.

Financial continuation

Obligations and Repayments link back to Applications; repayment allocations links each receipt to an obligation.

People and parties

People links staff to Users; Parties records customers, merchants and institutions involved in case operations.

Every table, by feature

Applicant Intake

3 tablesAbout this feature
  • Applicants

    Applicant identity and consent intake for financial applications.

  • Applications

    Financial applications routed through review and decision lifecycle.

    Linked to Applicants, People
  • Assessment evidence

    Provider evidence attached to application assessment.

    Linked to Applications

Application Review

6 tablesAbout this feature
  • Applications

    Financial applications routed through review and decision lifecycle.

    Linked to Applicants, People
  • Applicants

    Applicant identity and consent intake for financial applications.

  • Assessment evidence

    Provider evidence attached to application assessment.

    Linked to Applications
  • Credit decisions

    Attributed reviewer decisions on submitted applications.

    Linked to People, Applications
  • Fraud alerts

    Application-linked detection alerts awaiting reviewer disposition.

    Linked to Detection rules, Applications
  • People

    Attributed operational staff linked to authenticated ERP•AI users.

    Linked to Users

Assessment Evidence

5 tablesAbout this feature
  • Assessment evidence

    Provider evidence attached to application assessment.

    Linked to Applications
  • Applications

    Financial applications routed through review and decision lifecycle.

    Linked to Applicants, People
  • Applicants

    Applicant identity and consent intake for financial applications.

  • Credit decisions

    Attributed reviewer decisions on submitted applications.

    Linked to People, Applications
  • Fraud alerts

    Application-linked detection alerts awaiting reviewer disposition.

    Linked to Detection rules, Applications

Detection Rules

4 tablesAbout this feature
  • Detection rules

    Versioned rule definitions used to detect suspicious application activity.

  • Fraud alerts

    Application-linked detection alerts awaiting reviewer disposition.

    Linked to Detection rules, Applications
  • Applications

    Financial applications routed through review and decision lifecycle.

    Linked to Applicants, People
  • Assessment evidence

    Provider evidence attached to application assessment.

    Linked to Applications

Fraud Alerts

6 tablesAbout this feature
  • Fraud alerts

    Application-linked detection alerts awaiting reviewer disposition.

    Linked to Detection rules, Applications
  • Detection rules

    Versioned rule definitions used to detect suspicious application activity.

  • Applications

    Financial applications routed through review and decision lifecycle.

    Linked to Applicants, People
  • Applicants

    Applicant identity and consent intake for financial applications.

  • Assessment evidence

    Provider evidence attached to application assessment.

    Linked to Applications
  • Credit decisions

    Attributed reviewer decisions on submitted applications.

    Linked to People, Applications

Repayment Control

5 tablesAbout this feature
  • Applications

    Financial applications routed through review and decision lifecycle.

    Linked to Applicants, People
  • Credit decisions

    Attributed reviewer decisions on submitted applications.

    Linked to People, Applications
  • Obligations

    Approved application repayment obligations and balances.

    Linked to Applications
  • Repayments

    Provider repayment receipts linked to applications.

    Linked to Applications
  • Repayment allocations

    Principal and fee allocations from confirmed repayments to obligations.

    Linked to Repayments, Obligations

Shared and settings

2 tables
  • Parties

    Customers, merchants, and institutions involved in financial case operations.

  • Users

    Users

    Linked to Users

Keys and references

Applications.Applicant points to Applicants and Applications.assigned to points to People. Both assessment evidence.Application and fraud alerts.Application point to Applications. Fraud alerts.Rule points to detection rules. Credit decisions.Reviewer points to People. Repayment allocations connects Repayments and Obligations; each financial parent links to Applications. Preserve application, applicant, obligation and repayment numbers during migration so staff can reconcile old cases with provider references.

Migration order

  1. Load Users, People and Parties, then reconcile staff identities.
  2. Load Applicants and their identity and consent details.
  3. Load Applications with applicant and assignee links.
  4. Load assessment evidence and detection rules, checking provider references and rule versions.
  5. Load fraud alerts and credit decisions against the correct application.
  6. Load Obligations and Repayments, then repayment allocations after both parents reconcile.

Set up Fraud Detection System your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started