Assess whether to refer to law enforcement or keep civil (23d384)
August 31, 2026
SITUATION A clinic billing the same modifier on 80% of visits raised whether to refer to law enforcement or keep civil for card-issuing fraud analyst at a fintech that just hit $2B payments volume. ACH return-reason code R10 spike is incomplete relative to that question, so Hold remains live until the file is complete.
DECISION Card-issuing fraud analyst in a fintech that just hit $2B payments volume must choose To refer to law enforcement / Keep civil using ACH return-reason code R10 spike after a clinic billing the same modifier on 80% of visits.
HYPOTHESES TO TEST 1. Card-issuing fraud analyst can defend To refer to law enforcement from ACH return-reason code R10 spike after a clinic billing the same modifier on 80% of visits in a Fraud Detection challenge. 2. Card-issuing fraud analyst cannot defend To refer to law enforcement from ACH return-reason code R10 spike; Keep civil is what the extract actually supports after a clinic billing the same modifier on 80% of visits. 3. A clinic billing the same modifier on 80% of visits never reached the population in ACH return-reason code R10 spike — reopen intake, do not close to refer to law. 4. Two facts in ACH return-reason code R10 spike after a clinic billing the same modifier on 80% of visits conflict for card-issuing fraud analyst; hold this Claims and Benefits Fraud file.
ANALYSIS REQUIRED 1. Map typology and hold authority card-issuing fraud analyst actually has in a fintech that just hit $2B payments volume. 2. Trace funds, counterparties, and reversals in ACH return-reason code R10 spike through the window opened by a clinic billing the same modifier on 80% of visits. 3. Quantify loss if the hold is released before ACH return-reason code R10 spike is complete. 4. For this Fraud Detection Claims and Benefits Fraud file, read ACH return-reason code R10 spike 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 (ACH return-reason code R10 spike 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 ACH return-reason code R10 spike, then the action for card-issuing fraud analyst - Hypothesis scorecard against ACH return-reason code R10 spike: supported / rejected / untestable - Owner and next date for card-issuing fraud analyst in a fintech that just hit $2B payments volume - What changes to refer to law if a clinic billing the same modifier on 80% of visits is later withdrawn
Explore more
More Fraud Detection prompts
- Assess whether the model score is a false positive from a life event (1b0b2f)
- Assess whether occupancy was misrepresented at origination (6963c1)
- Assess whether a claims ring exists or is coincidental overlap (71b81b)
- Assess whether to refer to law enforcement or keep civil (90e34c)
- Assess whether the typology is bust-out, first-party, or third-party (9bfdfc)
Explore related decision areas
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.

