TruaceTracing the truth around AIMonday, September 14, 2026
TRV-2026-0366Version 3 · Sources changed

Written 2026-09-12 06:56:26 UTC · current record

Reason for this version

Source set updated

Canonical text (the exact bytes fingerprinted)

TRUVACE RECORD VERSION
record: TRV-2026-0366
version: 3
kind: sources_changed
reason: Source set updated
timestamp: 2026-09-12T06:56:26.295754Z
status: published
lens: g_space
sector: crime
headline: Financial fraud detection through the application of machine learning techniques: a literature review
dek: Financial fraud negatively impacts organizational administrative processes, particularly affecting owners and/or investors seeking to maximize their profits. Addressing this issue, this study presents a literature review on financial fraud detection through machine learning techniques. The PRISMA and Kitchenham methods were applied, and 104 articles published between 2012 and 2023 were examined. These articles were selected based on predefined inclusion and exclusion criteria and were obtained from databases suc…
gain_title: Literature shows machine learning models are applied to detect financial fraud, with credit card fraud detection models most widely used.
problem_title: (none)
trace_subject: (none)
gain_reading: Literature shows machine learning models are applied to detect financial fraud, with credit card fraud detection models most widely used.
gain_evidence: credit card fraud detection models are the most widely used for detecting credit card loan fraud | Machine learning models and metrics were used to assess performance
problem_reading: (none)
problem_evidence: (none)
quick_read: Published September 3, 2024, this peer-reviewed literature review applied PRISMA and Kitchenham methods to 104 articles from 2012-2023 obtained from Scopus, IEEE Xplore, Taylor & Francis, SAGE, and ScienceDirect to map how machine learning is used to detect financial fraud and its types.

The synthesis matters because it shows where detection research concentrates and where gaps remain: credit card fraud models dominate, real datasets are favored while synthetic data accounts for less than 7%, and contributions cluster in China, India, Saudi Arabia, and Canada with few publications from Latin America, leaving questions about generalizability across regions and fraud types.
limitation: Review coverage is geographically skewed and relies heavily on real datasets with limited synthetic data testing.
tag: Evidence-backed gain
key_points: PRISMA and Kitchenham methods applied to 104 articles published between 2012 and 2023 from Scopus, IEEE Xplore, Taylor & Francis, SAGE, and ScienceDirect. | Analysis indicated a trend toward using real datasets, with synthetic data use below 7% of employed datasets. | Data sources included stock exchanges of China, Canada, United States, Taiwan, and Tehran, with leading contributors from China, India, Saudi Arabia, and Canada.
rundown: The review examined 104 articles from 2012 to 2023 selected via predefined inclusion and exclusion criteria, extracting information on authors, sources, countries, trends, and datasets used in experiments.

Findings highlight that credit card fraud detection models dominate the literature, real datasets are increasingly preferred over synthetic, and data were sourced from exchanges in China, Canada, the United States, Taiwan, and Tehran among others.
sources:
- peer_reviewed | Expert Systems with Applications | https://doi.org/10.1016/j.eswa.2021.116429 | 2021-12-31
- peer_reviewed | Humanities and Social Sciences Communications | https://doi.org/10.1057/s41599-024-03606-0 | 2024-09-03
- peer_reviewed | IEEE Access | https://doi.org/10.1109/access.2022.3166891 | 2022-01-01
prev: 6e6a75a6990eb5afa1e8d9ea17d5529feb5c3249b8cd4b3c6cc35d380a389008
sha256
5c2298a0e6cd3321c905b7cf586b6a282bd89e3dbf3013e1d635b4eb5f30d884
previous
6e6a75a6990eb5afa1e8d9ea17d5529feb5c3249b8cd4b3c6cc35d380a389008
Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-0366 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.