Insurance Claim Fraud Scenarios

This dataset contains synthetic insurance claim records enriched with detailed event features and labeled fraud scenarios, designed for advanced machine learning-based fraud detection. Each record includes customer, policy, incident, and claim details, along with structured fraud indicators and event-level metadata, making it ideal for developing and benchmarking fraud detection algorithms.

  • last updated 29 Jul 2025
  • by GoMask
The brief that made it

Training and benchmarking ML models for insurance fraud detection

Sample rows

preview · 8 of 200 rows · all 23 columns
claim_idstringclaim_statusstringclaim_amountfloatfraud_labelbooleanincident_typestringpolicy_idstringcustomer_idstringclaim_datedateincident_datedateincident_location_streetstringincident_location_citystringincident_location_statestringincident_location_postal_codestringincident_location_countrystringfraud_scenariostringreported_delay_daysintegernumber_of_previous_claimsintegerpolicy_start_datedatepolicy_end_datedatecustomer_ageintegercustomer_genderstringcustomer_occupationstringevent_featuresstring
CLM00001approved1750.45falsecollisionPLC10001CST900012024-03-052024-03-031200 Market StSan FranciscoCA94103USAblank202022-10-012025-09-3029femaledesigner{"impact_speed":26,"police_report":true,"damage_estimate":1600}
CLM00002paid670falsetheftPLC10002CST900022024-01-182024-01-1545 Pine AveChicagoIL60611USAblank322023-02-142025-02-1334maleengineer{"stolen_item":"laptop","police_report":true,"witness_count":0}
CLM00003approved38000falsefirePLC10003CST900032022-06-212022-06-20789 Maple BlvdTulsaOK74105USAblank152019-01-012024-12-3162femaleretired{"fire_department_report":true,"damage_level":"major","injuries":0}
CLM00004submitted550falsecollisionPLC10004CST900042023-07-102023-07-0822 Grand AveNew YorkNY10013USAblank202021-12-012024-11-3024femalestudent{"impact_speed":10,"police_report":false,"damage_estimate":500}
CLM00005approved9000falsetheftPLC10005CST900052024-04-182024-04-1788 Ocean DrMiamiFL33139USAblank112023-05-012026-04-3028maleinvestment_banker{"stolen_item":"bicycle","police_report":true,"witness_count":2}
CLM00006approved22000falsenatural_disasterPLC10006CST900062023-11-222023-11-1515 Hillcrest RdSan DiegoCA92103USAblank762022-01-012024-12-3170malepensioner{"event_type":"flood","damage_level":"moderate","evacuation":true}
CLM00007under_review1200falsecollisionPLC10007CST900072023-05-122023-05-112458 Roosevelt RdPhoenixAZ85009USAblank112022-06-102024-06-0926femalebartender{"impact_speed":34,"police_report":true,"damage_estimate":1000}
CLM00008paid18000falsefirePLC10008CST900082024-01-052023-12-303202 Willow LnSan JoseCA95128USAblank652021-07-012024-06-3059malebusiness_owner{"fire_department_report":true,"damage_level":"moderate","injuries":1}

What the 200 rows show

from the 200-row sample

Rejected (claim status) stands out: 36 of its 37 rows have fraud_label = true, against 22 of 162 for the rest.

  • 29%fraud_label = true
  • 1,800median claim_amount
  • 3incident location countries
  • 3customer genders
  • 6fraud scenarios
  • 25customer occupations
Fraud label rate by claim_statusfraud_label = true
0%50%100%0%submit…0 of 270%approv…0 of 7597%reject…36 of 3779%under_…22 of 280%paid0 of 32
claim_amount199 rows, in bands of 100k
01002001941000000040500k1Mclaim_amount →

Median 1,800, from 0.0 to 1,000,000.

incident_type199 rows with a value · 1 left blank
  1. collision63
  2. theft48
  3. natural_disaster27
  4. fire26
  5. vandalism18
  6. other17
23 columns by typefrom the column list below
  • string 14
  • integer 3
  • float 1
  • date 4
  • boolean 1

Columns

23 columns in four groups
blueprint · 23 columns
columntypedescriptionexample
Text 14 columns
claim_idstringUnique identifier for each insurance claim recorduniqueCLM00001
policy_idstringUnique identifier for the insurance policy associated with the claimPLC10001
customer_idstringUnique identifier for the customer who filed the claimCST90001
incident_typestringType of incident (e.g., collision, theft, fire, natural disaster)6 valuescollision
incident_location_streetstringStreet address where the incident occurredoptional1200 Market St
incident_location_citystringCity where the incident occurredoptionalSan Francisco
incident_location_statestringState or province where the incident occurredoptionalCA
incident_location_postal_codestringPostal code of the incident locationoptional94103
incident_location_countrystringCountry where the incident occurred3 countries · optionalUSA
claim_statusstringCurrent status of the claim (e.g., submitted, approved, rejected, under_review, paid)submitted · approved · rejected · under_review · paidapproved
fraud_scenariostringSpecific fraud scenario label (e.g., staged accident, inflated claim, duplicate claim, false injury)7 values · optionalinflated_claim
event_featuresstringSerialized JSON string containing detailed event-level features (e.g., sensor data, witness statements, repair estimates)optional{"impact_speed":26,"polic…
customer_genderstringGender of the customermale · female · other · · optionalfemale
customer_occupationstringOccupation of the customeroptionaldesigner
Numbers 4 columns
claim_amountfloatTotal monetary amount claimed by the customer0 or more1750.45
reported_delay_daysintegerNumber of days between incident date and claim filing date0 or more · optional2
number_of_previous_claimsintegerTotal number of previous claims filed by the customer0 or more · optional0
customer_ageintegerAge of the customer at the time of claim0 or more · optional29
Dates and times 4 columns
claim_datedateDate when the claim was filed2024-03-05
incident_datedateDate when the incident leading to the claim occurred2024-03-03
policy_start_datedateStart date of the insurance policyoptional2022-10-01
policy_end_datedateEnd date of the insurance policyoptional2025-09-30
True or false 1 column
fraud_labelbooleanIndicates whether the claim is fraudulent (true) or legitimate (false)false

Use it for

  • fraud label29%58 of 199 rowsmean claim amount by …2.2ksubm…9.8kappr…27.1kreje…133.4kunde…

    An insurance dashboard

    The fraud_label rate, claim_amount by claim_status and a breakdown of incident_type. Excel, Power BI or Tableau.

  • Why do 58 of 199 rows have fraud_label = true?

    A root-cause class exercise

    Hand out the rows and one question. The answer is in the data, not in the brief.

  • A software demo

    Believable claims with policy_id, customer_id and claim_date to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 23 columns, your size and your rules. See 20 rows before you pay.

Preview 20 rows free

1,000 rows: $1.99 · 10,000: $12.99One-time. No subscription. All prices

This dataset200 rows23 columns
Yours1,000 rows23 columnsincident_location_street: UK only

blueprint · insurance-claim-fraud-scenarios

Behind this dataset

Same schema. As many rows as you need.

These 200 rows came out of a blueprint — 23 columns with generation rules behind each one. Open it in Data Factory to retune a column, add your own, wire in foreign keys, and run it at the size you actually need.

Rules it was built with
  • Claims include policyholder demographics
  • Fraud scenarios labeled with type
  • Claim value and settlement time tracked
  • Duplicate and exaggerated claims simulated
Rows
Open the blueprint in Data Factory

1 credit per row. Preview 20 rows free. Buy rows for the full run.

Exports
CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
Licence
yours to use, including commercially
API slug
insurance-claim-fraud-scenarios

What should your data show?

Preview 20 rows free
No signup. No card.