These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Fraud Detection System
- Features
- Applicant Intake
Applicant Intake
Keep identity and consent with each applicant before application review.
OverviewApplicants Verification Queue×
Fraud Detection System · Applicant Intake
New
Applicants Verification Queue
Approval conditions
| Applicant number | Name | Consent signed at | Identity verification reference | Status | |
|---|---|---|---|---|---|
| APP-91930 | Applicant 802 | 06 Oct | IVR-302 | Pending | |
| APP-59626 | Applicant 221 | 08 Oct | IVR-667 | Pending | |
| APP-97308 | Applicant 805 | 24 Oct | IVR-714 | Pending | |
| APP-46390 | Applicant 972 | 15 Oct | IVR-553 | Pending | |
| APP-55738 | Applicant 351 | 09 Oct | IVR-888 | Pending |
6 of 6 records
Applicant 802Applicants · APP-91930
PendingConsent signed at06 Oct
Identity verification referenceIVR-302
What you can do
Start with the person behind the application
A financial application begins with an applicant record that the team can recognize later. The Case Analyst records the applicant number and name, checks the identity verification reference, and records when consent was signed. These details give the reviewer a stable starting point when an application or alert needs another look. A person with a pending verification remains visible in the queue; the Case Analyst should not treat a submitted application as proof that identity review has finished.
When an applicant is verified or declined, keep that outcome on the same record. The change should be understandable beside the consent date and identity reference. If the provider sends a corrected identity result, investigate the source and update the case deliberately. The team should agree who is allowed to make that correction and who checks it before related applications proceed.
How the work is organized
- Verification queue. Pending applicants appear with the identity reference and consent date needed for review.
- Application link. Each application points to its applicant, so a credit decision can be traced back to the same person.
- Case context. A reviewer can inspect the applicant while examining assessment evidence or a fraud alert on a related application.
What to agree during setup
Choose the trusted identity source, the meaning of a signed consent time, and how staff handle a changed verification result. Decide who enters applicant records and who can mark a person verified or declined. Match existing applicant numbers before importing applications so the same person is not given competing case histories. Keep source references intelligible to the team that will answer a later audit question.
For a pilot, use an applicant with a pending result and a second one whose identity has been verified. Have a Case Analyst explain why the latter can move into application review and what evidence supports the change. This gives the Credit Reviewer a clear point of reference when the linked application reaches a decision.
Check the handoff on an actual case
Take an application with a named applicant and open its identity record. Read the consent time and verification reference, then compare them with the source result. If the identity result is declined, keep that state visible while the Case Analyst resolves the case. If it is verified, the reviewer can continue to the application and its assessment evidence. A Fraud Investigator following an alert should reach the same applicant through the application link, rather than relying on a name copied into a note.
What your team sees
- Applicants Verification Queue — Pending applicants with the identifiers and consent details needed for verification.
- Applications Review Queue — Submitted and reviewing applications linked to the applicant record.
Follow the work through
See applicant and application review for the next handoff, and implementation for a pilot sequence.
What it keeps track of
Data model- Applicants
- Applicant identity and consent intake for financial applications.
- Applications
- Financial applications routed through review and decision lifecycle.
- Assessment evidence
- Provider evidence attached to application assessment.
Who uses it
Permissions- Case Analyst
- , Credit Reviewer, Fraud Investigator, Admin.
Set up Fraud Detection System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.