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
- Assessment Evidence
Assessment Evidence
Keep provider evidence attached to the application it supports.
OverviewAssessment Evidence Register×
Fraud Detection System · Assessment Evidence
New
Assessment Evidence Register
Assessment evidence
| Application | Evidence type | Provider reference | Received at | Document | |
|---|---|---|---|---|---|
| APP-60147 | ET-454 | PR-127 | 13 Oct | DCM-215 | |
| APP-85538 | ET-662 | PR-841 | 12 Oct | DCM-182 | |
| APP-25255 | ET-310 | PR-880 | 13 Oct | DCM-127 | |
| APP-57941 | ET-896 | PR-135 | 07 Oct | DCM-218 | |
| APP-25350 | ET-839 | PR-147 | 06 Oct | DCM-711 |
6 of 6 records
ET-454Assessment evidence · AE-34120
ApplicationAPP-60147
Provider referencePR-127
Received at13 Oct
DocumentDCM-215
What you can do
Put the source beside the case
Assessment evidence belongs to an application. The Case Analyst records the type of evidence, the provider reference, when it was received and, where available, the document. A reviewer can then compare a stated identity or assessment result with the source material that was actually received. The application link matters: a document placed on the wrong case can make an otherwise careful decision misleading.
Evidence can arrive at different points in review. Keep the received time so the team can see whether a document was available when an earlier decision was made. If a provider corrects a result, add a clear new source reference and review the case again. The Case Analyst should be able to explain which evidence the Credit Reviewer considered for the decision on that application.
How the work is organized
- Case link. Every evidence record points to one application and can be opened from that review context.
- Provider trail. Evidence type, reference and receipt time make an external result identifiable.
- Document review. An attachment can carry the source material for the reviewer to inspect.
What to agree during setup
Agree which provider references the team will accept, how duplicate deliveries are reconciled, and who may attach or replace a document. Choose a naming convention for evidence types that analysts can apply consistently. The source provider remains responsible for its own result; this case record holds what the team received and how it informed review. Set a handoff for disputed evidence so the Credit Reviewer is not asked to infer a result from an unexplained attachment.
Start with an application that has more than one evidence item. Rehearse how a Case Analyst finds the identity source, an assessment document and the time each arrived. Then ask the Credit Reviewer to state whether the evidence is current enough for a decision. This reveals mismatched references before a larger import makes them hard to find.
Check the handoff on an actual case
Open a submitted application and compare its applicant with the source document. Read the provider reference and received time, then inspect the attachment if one exists. If the evidence conflicts with the applicant record, keep the application in review while the Case Analyst resolves the conflict. When a fraud alert is also linked to the case, the Fraud Investigator should be able to use the same evidence rather than create a separate account of what the provider said. After the reviewer decides, the case should retain the evidence that informed that decision.
What your team sees
- Assessment Evidence Register — Provider evidence and documents linked to reviewed applications.
- Submitted Application Decisions — Submitted cases awaiting a reviewer decision.
Follow the work through
Use application review to rehearse evidence collection and alert investigation when evidence changes an alert disposition.
What it keeps track of
Data model- Assessment evidence
- Provider evidence attached to application assessment.
- Applications
- Financial applications routed through review and decision lifecycle.
- Applicants
- Applicant identity and consent intake for financial applications.
- Credit decisions
- Attributed reviewer decisions on submitted applications.
- Fraud alerts
- Application-linked detection alerts awaiting reviewer disposition.
Who uses it
Permissions- Case Analyst
- , Fraud Investigator, Credit Reviewer, Admin.
Set up Fraud Detection System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.