Connects to the tools you use
Set up connections through ERP.AI and Proto workflows, with every change logged.
- Fraud Detection System
- Identity verification provider
- Assessment evidence provider
- Repayment provider
- Staff identity
Financial application teams use Fraud Detection System to keep applicants, applications, provider assessment evidence, detection rules and application-linked fraud alerts in one case record. A Case Analyst owns initial review, and a Fraud Investigator examines alerts by disposition, rule and linked application.
Applications in one list
Credit Reviewer approves or declines after examining the case.
Every feature works on the same records. Pick one to see the screen your team works in.
Keep identity and consent with each applicant before application review.
Approval conditions
| Applicant number | Name | Consent signed at | Identity verification reference | Status | |
|---|---|---|---|---|---|
| APP-91930 | Sana Patel | 14 Oct | IDV-2026-10841 | Pending | |
| APP-59626 | Victor Alvarez | 16 Oct | IDV-2026-10842 | Pending | |
| APP-97308 | Mariam Yusuf | 01 Nov | IDV-2026-10843 | Pending | |
| APP-46390 | Leo Fischer | 23 Oct | IDV-2026-10844 | Pending | |
| APP-55738 | Anika Rao | 17 Oct | IDV-2026-10845 | Pending |
Assign each financial application and keep its decision attributable.
Review waits for the case analyst
| Application number | Applicant | Requested at | Requested amount | Assigned to | Status | |
|---|---|---|---|---|---|---|
| APP-70425 | Victor Alvarez | 12 Oct | 860 | Mateo Rivera | Submitted | |
| APP-34709 | Sana Patel | 18 Oct | 290 | Hana Idris | Submitted | |
| APP-24901 | Nadia Karim | 28 Oct | 410 | Iris Chen | Submitted | |
| APP-66264 | Leo Fischer | 03 Nov | 910 | Iris Chen | Submitted | |
| APP-95764 | Dario Moreno | 31 Oct | 200 | Priya Shah | Submitted |
Keep provider evidence attached to the application it supports.
Assessment evidence
| Application | Evidence type | Provider reference | Received at | Document | |
|---|---|---|---|---|---|
| Sana Patel, home repair loan | Identity verification report | BANK-2026-44101 | 21 Oct | identity-review-10841.pdf | |
| Victor Alvarez, vehicle loan | Bank statement | BANK-2026-44102 | 20 Oct | bank-statement-oct-2026.pdf | |
| Jun Park, medical expense loan | Device fingerprint | BANK-2026-44103 | 21 Oct | device-match-44103.csv | |
| Sana Patel, home repair loan | Income document | IDV-2026-10841 | 15 Oct | income-review-10844.pdf | |
| Jun Park, medical expense loan | Address history | IDV-2026-10842 | 14 Oct | address-history-10845.pdf |
Keep rule expressions, versions and lifecycle states reviewable.
Detection rules
| Rule name | Version | Expression | Status | |
|---|---|---|---|---|
| Repeated device across applicants | 1.0 | device_count_30d > 3 | Active | |
| Rapid address change before submission | 1.1 | address_changes_7d > 1 | Active | |
| Income variance against bank records | 1.2 | income_variance_pct > 25 | Active | |
| Multiple applications in one hour | 2.0 | applications_1h > 2 | Active | |
| Repayment account mismatch | 2.1 | repayment_name_match = false | Active |
Investigate application-linked alerts and record a clear disposition.
Credit decisions
| Application | Reviewer | Decision | Reason codes | Approved amount | Decided at | |
|---|---|---|---|---|---|---|
| Jun Park, medical expense loan | Lukas Weber | Approve | Identity mismatch | 960 | 04 Nov | |
| Nadia Karim, home improvement loan | Iris Chen | Decline | Unverified income | 370 | 19 Oct | |
| Nadia Karim, home improvement loan | Amina Saleh | Refer | Repeated device use | 240 | 18 Oct | |
| Mariam Yusuf, education loan | Priya Shah | Approve | Conflicting employer details | 430 | 30 Oct | |
| Anika Rao, debt consolidation | Priya Shah | Decline | Unusual application velocity | 920 | 18 Oct |
Trace provider receipts and allocations against approved application obligations.
Repayments
| Repayment number | Application | Received at | Amount | Provider reference | Status | |
|---|---|---|---|---|---|---|
| RPY-13718 | Mariam Yusuf, education loan | 17 Oct | 130 | BANK-2026-44101 | Confirmed | |
| RPY-11521 | Leo Fischer, equipment financing | 14 Oct | 740 | BANK-2026-44102 | Confirmed | |
| RPY-63115 | Dario Moreno, small business loan | 19 Oct | 440 | BANK-2026-44103 | Confirmed | |
| RPY-49289 | Jun Park, medical expense loan | 09 Oct | 550 | IDV-2026-10841 | Confirmed | |
| RPY-44817 | Leo Fischer, equipment financing | 16 Oct | 60 | IDV-2026-10842 | Confirmed |
Alert to case decision ships ready to use. One step needs a named approval before the work moves on: Decide application (Credit Reviewer).
Check identity and consent before review.
Assign the application and gather source evidence.
Keep the rule expression and version identifiable.
Compare the linked rule and application evidence.
The Credit Reviewer records the outcome and reasons.
Match confirmed provider receipts to open obligations.
Open any application to see its assessment evidence, the roles that work on it, its process stages and its approvals on one page.
Assigned to, Requested at and Requested amount.
Each line is linked to this application.
Case Analyst, Fraud Investigator and Credit Reviewer, each with their own permissions.
Submit application and Review application, with the role that acts.
Decide application, with who decides.
Submitted
| Application | Evidence type | Provider reference |
|---|---|---|
| Sana Patel, home repair loan | Identity verification report | BANK-2026-44101 |
| Victor Alvarez, vehicle loan | Bank statement | BANK-2026-44102 |
| Jun Park, medical expense loan | Device fingerprint | BANK-2026-44103 |
A Case Analyst prepares the application and evidence; a Credit Reviewer makes the credit decision.
Signed in as Credit Reviewer
| Decision | Approver | |
|---|---|---|
| Decide applicationThe Credit Reviewer records the outcome and reasons. | Credit Reviewer | |
| Approve Applications | Credit Reviewer |
Everyone opens Fraud Detection System to the work that is theirs. Pick a role to see what it starts with.
Owns assigned application review and assembles case evidence.
This is the first screen this role sees.
Applicants · Case Analyst
| Applicant number | Name | Consent signed at | Identity verification reference | Status | |
|---|---|---|---|---|---|
| APP-91930 | Sana Patel | 14 Oct | IDV-2026-10841 | Pending | |
| APP-59626 | Victor Alvarez | 16 Oct | IDV-2026-10842 | Pending | |
| APP-97308 | Mariam Yusuf | 01 Nov | IDV-2026-10843 | Pending | |
| APP-46390 | Leo Fischer | 23 Oct | IDV-2026-10844 | Pending | |
| APP-55738 | Anika Rao | 17 Oct | IDV-2026-10845 | Pending |
Examines alerts against their linked application and records a disposition.
This is the first screen this role sees.
Applications · Fraud Investigator
Makes an independent application decision after case review.
This is the first screen this role sees.
Applications · Credit Reviewer
| Application number | Applicant | Requested at | Requested amount | Assigned to | Status | |
|---|---|---|---|---|---|---|
| APP-70425 | Victor Alvarez | 12 Oct | 860 | Mateo Rivera | Submitted | |
| APP-34709 | Sana Patel | 18 Oct | 290 | Hana Idris | Submitted | |
| APP-24901 | Nadia Karim | 28 Oct | 410 | Iris Chen | Submitted | |
| APP-66264 | Leo Fischer | 03 Nov | 910 | Iris Chen | Submitted | |
| APP-95764 | Dario Moreno | 31 Oct | 200 | Priya Shah | Submitted |
Maintains the versioned rule register and reviews rule changes.
This is the first screen this role sees.
Detection rules · Rule Steward
Reviews provider receipts and their allocation to open obligations.
This is the first screen this role sees.
Obligations · Repayment Specialist
Configures users and operational access and resolves record setup issues.
Read case queues, alert outcomes, rule versions and repayment traces.
This quarter
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Submitted | 27 | ||
| Review | 7 | 26% | |
| Approved | 3 | 43% | |
| Declined | 1 | 33% |
Sample totals per stage
Count applications by Status and assigned to to see where review work sits.
Group fraud alerts by Rule and Disposition to compare alert outcomes.
Compare Score with the linked application's credit decision decision.
List rule name, Version and Status for rule change review.
Group Applicants by Status and show consent and identity references.
Show Decision and reason codes by Reviewer and decided at.
Group Obligations by Status and due date with Principal and Fees.
Reconcile repayment amount to repayment allocation principal amount and fee amount by receipt.
See how Fraud Detection System fits your kind of team.
Review applicant identity, suspicious cases and credit decisions in one trail.
Review financial applications with explicit alert and receipt trails.
Keep sourced case evidence and named decisions across financial applications.
Each stage of alert to case decision names the role that acts and the status it records, so a change is never anonymous.
Each stage, the role that acts and the status it records
Ask Proto to prepare case views and checks for your team to review.
Set up connections through ERP.AI and Proto workflows, with every change logged.
Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.
Browse all 12 tablesStart with one team and one process, then add the rest once the basics are running.
Reconcile staff users, applicant numbers and application numbers. Identify the person who owns each submitted case.
Import identity references, assessment documents and received times against the correct application. Review conflicting sources with the case team.
Agree the meaning of rule versions and statuses, then rehearse an unreviewed alert through investigation and disposition.
Have an independent Credit Reviewer inspect evidence and alert outcome, then record a decision with reasons and approved amount where applicable.
For an approved case, compare the obligation with a confirmed provider receipt and its principal and fee allocation.
$0per user
The base account and everyday work in the ERP.AI app are free, for every user.
| Usage | Per $1 |
|---|---|
| Record reads (list, filter, get) | 20,000 |
| Search or aggregate queries | 4,000 |
| Record writes | 4,000 |
| Imported or synced records | 200,000 |
| Workflow runs | 2,000 |
| AI agent runs | 2,000 |
| Scheduled jobs or webhooks | 20,000 |
| File uploads (MB) | 2,000 |
| CSV or PDF exports | 100 |
Click Get started, then use Proto to configure Fraud Detection System for your business. Begin with a verified applicant, a submitted application, a linked alert and a reviewer decision so your team can rehearse the handoffs.
The Fraud Investigator checks the linked rule, application and evidence, then records whether the alert is confirmed or dismissed.
A Credit Reviewer records the decision, reasons, time and approved amount where relevant. The Case Analyst prepares the case and evidence.
The Rule Steward keeps each rule's name, version, expression and lifecycle status identifiable. Review the definition against representative applications before marking a version active.
The application links to an assigned person. The review queue shows that assignment beside the applicant, requested amount and current state.
Assessment evidence records link source references, receipt times and documents to the application they support.
Keep the dismissed disposition linked to its rule and application so the Credit Reviewer can see the investigation outcome beside the case.
The team can record obligations, provider repayment receipts and allocations against that approved application.
Review the provider result and related allocations before changing an obligation. A reversed receipt should not settle the debt.
Yes. Assign work according to the Case Analyst, Fraud Investigator, Credit Reviewer, Rule Steward and Repayment Specialist responsibilities, then rehearse each person's access before live use.
Start free, then use Proto to change fields, steps and approvals before your team goes live.