Assess whether to refer to law enforcement or keep civil (3c396e)
August 31, 2026
SITUATION A fintech that just hit $2B payments volume has mule-account payroll deposit pattern in hand following a clinic billing the same modifier on 80% of visits. Card-issuing fraud analyst must determine whether to refer to law enforcement or keep civil for this Fraud Detection Claims and Benefits Fraud file.
DECISION Card-issuing fraud analyst in a fintech that just hit $2B payments volume must choose To refer to law enforcement, Keep civil using mule-account payroll deposit pattern after a clinic billing the same modifier on 80% of visits. The question on that file is whether to refer to law enforcement or keep civil.
HYPOTHESES TO TEST 1. Authorize To refer to law enforcement now; mule-account payroll deposit pattern already has the discriminator after a clinic billing the same modifier on 80% of visits. 2. Keep Keep civil in force until mule-account payroll deposit pattern is completed after a clinic billing the same modifier on 80% of visits for card-issuing fraud analyst. 3. Treat mule-account payroll deposit pattern as To refer to law enforcement because both readings appear after a clinic billing the same modifier on 80% of visits. 4. Refuse a Fraud Detection close: card-issuing fraud analyst does not have the decision to refer to law turns on in mule-account payroll deposit pattern.
ANALYSIS REQUIRED 1. Quantify loss if the hold is released before mule-account payroll deposit pattern is complete. 2. Test a one-off dispute against the first edge of a scheme around to refer to law. 3. Check mule or round-trip markers in mule-account payroll deposit pattern. 4. For this Fraud Detection Claims and Benefits Fraud file, read mule-account payroll deposit pattern against a clinic billing the same modifier on 80% of visits and write the one fact that would move to refer to law for card-issuing fraud analyst.
RECOMMENDATION Choose To refer to law enforcement / Keep civil on this Fraud Detection / Claims and Benefits Fraud packet (mule-account payroll deposit pattern after a clinic billing the same modifier on 80% of visits). The follow-on Claims and Benefits Fraud action is what card-issuing fraud analyst does next: implement the option, assign an owner, and log the missing fact.
COMMAND RETURNS - Bottom-line Fraud Detection option on to refer to law, then the evidence in mule-account payroll deposit pattern, then the action for card-issuing fraud analyst - Hypothesis scorecard against mule-account payroll deposit pattern: supported / rejected / untestable - Missing page in mule-account payroll deposit pattern after a clinic billing the same modifier on 80% of visits, if any - Regulatory or exam hook Claims and Benefits Fraud would cite
Explore more
More Fraud Detection prompts
- Assess whether the typology is bust-out, first-party, or third-party (666be0)
- Assess whether occupancy was misrepresented at origination (fadb5a)
- Assess whether a SAR narrative is supportable today (36d1d5)
- Assess whether occupancy was misrepresented at origination (b29fa8)
- Assess whether linked accounts should be treated as one case (910cff)
Explore related decision areas
- Assess whether to pause a product pending a lookback (80be64)Fair Lending
- Assess whether loss development requires a rate or a restriction (94b947)Insurance Underwriting
- Whether product recall exposure is priced or excluded from environmentalInsurance Underwriting
See governed multi-model AI on your own prompt
Compare GPT-5, Claude, and Gemini side by side, with human review and a decision record built in.

