• Finance
  • 20 columns
  • 1,000 rows
  • 8 formats

Transaction Monitoring Alerts

This dataset provides comprehensive records of automated transaction monitoring alerts, capturing suspicious activity such as unusual patterns, velocity checks, geographic anomalies, and behavioral red flags. It includes transaction details, customer risk scores, alert types and severities, investigation status, and resolution notes, making it ideal for financial crime detection, compliance reporting, and operational analytics.

  • last updated 1 Nov 2025
  • by GoMask
The brief that made it

Automated fraud and financial crime detection

Sample rows

preview · 8 of 1,000 rows · all 20 columns
alert_idstringalert_severitystringprevious_alert_count_30dintegertransaction_currencystringtransaction_idstringcustomer_idstringalert_datetimedatetimetransaction_datetimedatetimetransaction_amountfloattransaction_typestringalert_typestringalert_statusstringtriggered_rulestringtransaction_countrystringtransaction_citystringcustomer_risk_scorefloatinvestigator_idstringresolution_datetimedatetimealert_descriptionstringresolution_notesstring
ALRT-00001medium3USDTXN-10001CUST-00012024-06-15T09:15:22Z2024-06-15T09:13:17Z2550.75withdrawalvelocityopenRULE_VEL_345USLas Vegas35.2blankblankMultiple withdrawals detected in short period, exceeding account frequency threshold.blank
ALRT-00002low1EURTXN-10002CUST-00022024-06-01T14:11:03Z2024-06-01T13:59:57Z999.99paymentpattern_anomalyclosedRULE_PATT_278FRParis24.7INV-0012024-06-02T10:20:40ZUnusual payment pattern flagged for review, below typical amount for this account.Alert closed after verifying customer activity matched expected behavior.
ALRT-00003high12GBPTXN-10003CUST-00032024-05-28T17:23:19Z2024-05-28T17:22:00Z7500transfergeographic_anomalyunder_reviewRULE_GEO_111GBLondon78.8INV-002blankTransfer initiated from new location in London, inconsistent with customer's previous activity.blank
ALRT-00004low0USDTXN-10004CUST-00042024-06-16T10:55:02Z2024-06-16T10:52:28Z129.5depositvelocityopenRULE_VEL_419USChicago9.3blankblankDeposit frequency exceeded standard threshold for low-risk profile.blank
ALRT-00005critical27CADTXN-10005CUST-00052024-06-10T13:45:29Z2024-06-10T13:44:02Z84500transferbehavioral_red_flagescalatedRULE_BEHAV_824CAToronto95.9INV-0032024-06-11T09:34:13ZHigh-value transfer flagged due to unusual beneficiary and recent high risk score.Escalated to senior investigator for further analysis due to critical severity.
ALRT-00006medium2AUDTXN-10006CUST-00062024-05-18T08:12:57Z2024-05-18T08:11:22Z420.1paymentvelocityopenRULE_VEL_279AUSydney28.2blankblankRapid sequence of payments detected, flagged for velocity anomaly.blank
ALRT-00007critical34CNYTXN-10007CUST-00072024-06-09T21:40:24Z2024-06-09T21:38:45Z5000000depositpattern_anomalyclosedRULE_PATT_512CNShanghai99.1INV-0042024-06-10T14:15:35ZLarge deposit in CNY flagged for pattern anomaly, matches recent high-risk activity.Closed after confirming funds origin with compliance team, flagged for monitoring.
ALRT-00008low0USDTXN-10008CUST-00082024-06-13T12:15:21Z2024-06-13T12:14:01Z89withdrawalotheropenRULE_MISC_105USSalem6.4blankblankSmall withdrawal flagged for pattern check based on customer age and activity.blank

What the 1,000 rows show

from the 1,000-row sample

Critical (alert severity) stands out: mean previous_alert_count_30d is 27.6, against 3.7 for the rest.

  • 2median previous_alert_count_30d
  • 4alert statuses
  • 5transaction types
  • 5alert types
  • 13transaction countries
  • 67transaction cities
Mean previous_alert_count_30d by alert_severity1,000 rows
020400.30low329 rows3.2medium343 rows11.3high170 rows27.6critical158 rows
previous_alert_count_30d1,000 rows, in bands of 5
0295590588137884843382626602545previous_alert_count_30d →

Median 2, from 0 to 41.

transaction_currency1,000 rows · top 10 of 13 values
  1. USD418
  2. CAD72
  3. EUR65
  4. CNY56
  5. BRL55
  6. JPY55
  7. GBP52
  8. SEK44
  9. INR42
  10. ZAR42
20 columns by typefrom the column list below
  • string 14
  • integer 1
  • float 2
  • datetime 3

Columns

20 columns in three groups
blueprint · 20 columns
columntypedescriptionexample
Text 14 columns
alert_idstringUnique identifier for each transaction monitoring alertuniqueALRT-00001
transaction_idstringUnique identifier for the transaction associated with the alertTXN-10001
customer_idstringUnique identifier for the customer involved in the transactionCUST-0001
transaction_currencystringISO currency code for the transaction (e.g., USD, EUR)USD
transaction_typestringType of transaction (e.g., deposit, withdrawal, transfer, payment)deposit · withdrawal · transfer · payment · otherwithdrawal
alert_typestringCategory of alert (e.g., velocity, geographic anomaly, behavioral red flag)5 valuesvelocity
alert_severitystringSeverity level of the alertlow · medium · high · criticalmedium
alert_statusstringCurrent status of the alert (e.g., open, under_review, closed, escalated)open · under_review · closed · escalatedopen
triggered_rulestringName or identifier of the rule or logic that triggered the alertRULE_VEL_345
transaction_countrystringCountry where the transaction originated (ISO country code)US
transaction_citystringCity where the transaction originatedoptionalLas Vegas
alert_descriptionstringDetailed description of the alert and the unusual activity detectedoptionalMultiple withdrawals dete…
investigator_idstringIdentifier for the investigator assigned to review the alertoptionalINV-001
resolution_notesstringNotes or comments entered by the investigator regarding the resolution of the alertoptionalAlert closed after verify…
Numbers 3 columns
transaction_amountfloatMonetary amount of the transaction0 or more2550.75
customer_risk_scorefloatRisk score assigned to the customer at the time of alert (0-100)0 to 100 · optional35.2
previous_alert_count_30dintegerNumber of alerts generated for this customer in the past 30 days0 or more · optional3
Dates and times 3 columns
alert_datetimedatetimeTimestamp when the alert was generated2024-06-15T09:15:22Z
transaction_datetimedatetimeTimestamp of the transaction that triggered the alert2024-06-15T09:13:17Z
resolution_datetimedatetimeTimestamp when the alert was resolved or closedoptional2024-06-02T10:20:40Z

Use it for

  • median previou…21,000 rowsmean previous alert c…0.30low3.2medi…11.3high27.6crit…

    A finance dashboard

    Previous_alert_count_30d by alert_severity and a breakdown of transaction_currency. Excel, Power BI or Tableau.

  • Why do the 158 critical rows have a mean previous_alert_count_30d of 27.6?

    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 alerts with transaction_id, customer_id and alert_datetime to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 20 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 dataset1,000 rows20 columns
Yours1,000 rows20 columnstransaction_country: UK only

blueprint · transaction-monitoring-alerts-2

Behind this dataset

Same schema. As many rows as you need.

These 1,000 rows came out of a blueprint — 20 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
  • Alert ID unique per scenario trigger
  • Scenario types: velocity, amount, geography, structuring
  • Alert priority: low, medium, high, critical
  • Customer risk profile considered
  • Historical behavior baseline
  • Investigation assignment automated
  • SLA for alert resolution by priority
  • Disposition: false positive, true positive, escalate to SAR
Rows
Open the blueprint in Data Factory

1 credit per row. New accounts start with 25 free credits.

Exports
CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
Licence
yours to use, including commercially
API slug
transaction-monitoring-alerts-2

What should your data show?

Preview 20 rows free
No signup. No card.