Suspected Insurance Fraud Reporting Form to State Fraud Bureau

This template is used to package a suspected insurance fraud referral for a state fraud bureau, department of insurance fraud division, or prosecutor. It captures the minimum necessary case information, the alleged fraud indicators, involved parties, and supporting evidence. It also records who reviewed the referral and where it was sent. That makes it easier to submit a consistent, auditable case file.

Use it when a claim, policy, or loss event raises documented fraud indicators that warrant external referral. It fits suspicious billing patterns, staged losses, misrepresentation, inflated damages, or inconsistent statements tied to a claim. It is not meant for routine claim notes or general customer complaints. If the issue can be resolved internally without a referral, this form is usually unnecessary.

A claims investigator, SIU analyst, or designated fraud reviewer typically completes the form, with approval from a supervisor or compliance reviewer when required. The submitter should be the person closest to the evidence, but not necessarily the person making the final referral decision. The approval section helps separate collection from authorization. That separation supports a cleaner audit trail.

It is used on an as-needed basis, only when a case meets your organization’s threshold for suspected fraud referral. Some teams use it for every external referral, while others use it only after an internal triage step. The template works either way because the referral status and approval fields can reflect your workflow. It is not a recurring operational checklist.

Only collect what is needed to support the referral and avoid unnecessary PII. Do not add unrelated medical details, full payment histories, or extra identifiers that do not help the fraud review. If contact information is unknown, note that it is unavailable rather than forcing a guess. The form is designed around data minimization and controlled disclosure.

The template includes submission notice, consent acknowledgement, evidence tracking, and audit trail notes so the referral can be reviewed later. Those fields help show what was known, who approved the submission, and what was sent. That is useful for internal governance and for responding to regulator follow-up. It also reduces the risk of inconsistent or unsupported referrals.

Yes. You can tailor the fraud type list, evidence options, and referral destination fields for auto, property, workers’ compensation, health, or specialty lines. The case identification section already supports jurisdiction and line of business, so the same template can be reused across teams. Keep the required fields limited to what each line actually needs.

This form works well with claims systems, document storage, case management tools, and approval workflows. Linking the claim number and policy number to your source system reduces duplicate entry and helps preserve the audit trail. File attachments should point to the supporting evidence repository rather than duplicating sensitive documents in multiple places. If your process includes routing, connect the referral status to notifications or task assignments.

Common mistakes include over-collecting personal data, writing vague fraud summaries, and attaching evidence without explaining why it matters. Another issue is skipping the approval step or leaving the referral destination blank. Teams also sometimes use free-text fields where structured fields would make review easier. Clear field labels and conditional logic help prevent those problems.

An ad hoc email usually leaves gaps in case identification, evidence description, and approval status. This template standardizes those fields so the referral can be reviewed, routed, and audited more reliably. It also helps teams avoid sending more information than necessary. That makes the submission easier to defend if the case is later questioned.