1. Fraud Detection System
  2. Implementation
Reference

How a Fraud Detection System rollout works

Start with a sourced application, a reviewed alert and a reconciled receipt.

  1. Map identities and cases

    Reconcile staff users, applicant numbers and application numbers. Identify the person who owns each submitted case.

  2. Bring in source evidence

    Import identity references, assessment documents and received times against the correct application. Review conflicting sources with the case team.

  3. Review rules and alerts

    Agree the meaning of rule versions and statuses, then rehearse an unreviewed alert through investigation and disposition.

  4. Decide a case

    Have an independent Credit Reviewer inspect evidence and alert outcome, then record a decision with reasons and approved amount where applicable.

  5. Trace repayment

    For an approved case, compare the obligation with a confirmed provider receipt and its principal and fee allocation.

What the customer provides

Provide applicant and application identifiers, the source of identity verification and consent times, assessment documents and provider references, rule expressions and versions, and examples of alert outcomes. Name the Case Analyst, Fraud Investigator, Credit Reviewer, Rule Steward and Repayment Specialist who will rehearse the handoffs. If repayment is in scope, provide obligation balances and provider receipt history with a known duplicate or reversal example.

Changing it afterwards

When a rule expression changes, keep the earlier version intelligible for its linked alerts. Review a new provider source with a representative application before using it for decisions. Reconcile corrections to receipt status and allocations against the obligation and application, then repeat the handoff rehearsal with each affected role.

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