Add fraud catalogue
Browse files- catalogue/fraud_catalogue.json +32 -0
- catalogue/fraud_catalogue.md +83 -0
catalogue/fraud_catalogue.json
ADDED
|
@@ -0,0 +1,32 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
[
|
| 2 |
+
{
|
| 3 |
+
"scheme_type": "fictitious_ap_disbursements",
|
| 4 |
+
"title": "Fictitious AP Disbursements",
|
| 5 |
+
"normal_process": "The organisation should only settle payables for goods or services that were ordered, received or accepted, and invoiced under segregation of duties (e.g. different actors for recording vs authorising payment). Vendor identity and payment references should be consistent with normal operating practice.",
|
| 6 |
+
"warning_signs": "Value may leave the entity without a defensible procurement-to-pay trail: missing or weak evidence of receipt or approval, payables cleared without a credible invoice trail, the same actors repeatedly spanning incompatible roles, timing or vendor populations that diverge sharply from the rest of the ledger, or reference behaviour that does not match how the company usually books AP and bank movements."
|
| 7 |
+
},
|
| 8 |
+
{
|
| 9 |
+
"scheme_type": "revenue_manipulation",
|
| 10 |
+
"title": "Revenue Manipulation (Window Dressing)",
|
| 11 |
+
"normal_process": "Revenue aligns with delivery or completion of performance obligations; expenses and provisions are recognised in the appropriate periods; releases of reserves or similar items require defensible economic events and governance.",
|
| 12 |
+
"warning_signs": "Earnings can be inflated by recognising revenue too early, pushing expenses out of the period, or releasing balances that should still reflect risk or obligation. Suspect patterns are **relative**: unusual concentration in time, abnormal mixes of lines or accounts for the same commercial story, or journal narratives and flows that do not cohere with the rest of the order-to-cash and record-to-report activity in **this** database."
|
| 13 |
+
},
|
| 14 |
+
{
|
| 15 |
+
"scheme_type": "vendor_collusion",
|
| 16 |
+
"title": "Vendor Collusion (Kickback + Related-Party)",
|
| 17 |
+
"normal_process": "Procurement and payment follow approved sourcing, pricing, and approval chains; vendors are genuine third parties at arm’s length; segregation limits a single actor from controlling selection, invoicing, and payment.",
|
| 18 |
+
"warning_signs": "Inflated or biased spend, repeated coupling of the same internal and external parties without rotation, payment behaviour that fragments or obscures totals, weak master-data linkage, or indications that beneficiary or party data overlaps with insiders. Signals are contextual: compare to peer vendors, amounts, and approval patterns in the same data."
|
| 19 |
+
},
|
| 20 |
+
{
|
| 21 |
+
"scheme_type": "shadow_payroll",
|
| 22 |
+
"title": "Shadow Payroll (Ghost Employee)",
|
| 23 |
+
"normal_process": "Payroll pays real employees under HR and payroll policies, with accruals and settlements that match the entity’s payroll design (which may include multiple line types, schedules, and banking arrangements you must infer from the data).",
|
| 24 |
+
"warning_signs": "Beneficiaries or pay runs that are structurally odd relative to the population (e.g. accrual shape, timing clusters, banking or institution patterns, recency of employment lifecycle events vs pay activity, or concentration of authorship) can indicate diversion or synthetic beneficiaries. **Plausible HR rows do not rule out fraud** — treat master data as necessary context, not as a whitelist."
|
| 25 |
+
},
|
| 26 |
+
{
|
| 27 |
+
"scheme_type": "inventory_manipulation",
|
| 28 |
+
"title": "Inventory Manipulation (Asset Misappropriation)",
|
| 29 |
+
"normal_process": "Inventory moves should trace to economic events (receipts, consumption, sales, authorised adjustments). Write-downs and adjustments require authorised, documented physical or operational justification.",
|
| 30 |
+
"warning_signs": "Stock increases without credible upstream support, write-offs disconnected from prior stock history, suspicious symmetry or pairing of movements, period-close clustering of adjustments vs norms, or split roles across related postings may indicate inflation, concealment, or misappropriation. Map **this** entity’s inventory-related accounts and references from the ledger before concluding."
|
| 31 |
+
}
|
| 32 |
+
]
|
catalogue/fraud_catalogue.md
ADDED
|
@@ -0,0 +1,83 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
## Known Fraud Scheme Catalogue
|
| 2 |
+
|
| 3 |
+
**Only these 5 scheme types exist in the data** (no other fraud types are injected).
|
| 4 |
+
Each entry describes the **business process**, what “healthy” operations look like in substance,
|
| 5 |
+
and the **kinds of breakdown** that can indicate manipulation. It does **not** name expected GL
|
| 6 |
+
accounts, auxiliary formats, posting templates, or calendar cutoffs — those must come from **your**
|
| 7 |
+
profiling of this dataset (chart of accounts, distributions, joins, and master data).
|
| 8 |
+
|
| 9 |
+
---
|
| 10 |
+
|
| 11 |
+
### 1. Fictitious AP Disbursements
|
| 12 |
+
|
| 13 |
+
**Normal process (substance):** The organisation should only settle payables for goods or services
|
| 14 |
+
that were ordered, received or accepted, and invoiced under segregation of duties (e.g. different
|
| 15 |
+
actors for recording vs authorising payment). Vendor identity and payment references should be
|
| 16 |
+
consistent with normal operating practice.
|
| 17 |
+
|
| 18 |
+
**When something is wrong (conceptual):** Value may leave the entity without a defensible
|
| 19 |
+
procurement-to-pay trail: missing or weak evidence of receipt or approval, payables cleared without
|
| 20 |
+
a credible invoice trail, the same actors repeatedly spanning incompatible roles, timing or
|
| 21 |
+
vendor populations that diverge sharply from the rest of the ledger, or reference behaviour that
|
| 22 |
+
does not match how the company usually books AP and bank movements.
|
| 23 |
+
|
| 24 |
+
---
|
| 25 |
+
|
| 26 |
+
### 2. Revenue Manipulation (Window Dressing)
|
| 27 |
+
|
| 28 |
+
**Normal process (substance):** Revenue aligns with delivery or completion of performance
|
| 29 |
+
obligations; expenses and provisions are recognised in the appropriate periods; releases of
|
| 30 |
+
reserves or similar items require defensible economic events and governance.
|
| 31 |
+
|
| 32 |
+
**When something is wrong (conceptual):** Earnings can be inflated by recognising revenue too early,
|
| 33 |
+
pushing expenses out of the period, or releasing balances that should still reflect risk or
|
| 34 |
+
obligation. Suspect patterns are **relative**: unusual concentration in time, abnormal mixes of
|
| 35 |
+
lines or accounts for the same commercial story, or journal narratives and flows that do not
|
| 36 |
+
cohere with the rest of the order-to-cash and record-to-report activity in **this** database.
|
| 37 |
+
|
| 38 |
+
---
|
| 39 |
+
|
| 40 |
+
### 3. Vendor Collusion (Kickback + Related-Party)
|
| 41 |
+
|
| 42 |
+
**Normal process (substance):** Procurement and payment follow approved sourcing, pricing, and
|
| 43 |
+
approval chains; vendors are genuine third parties at arm’s length; segregation limits a single
|
| 44 |
+
actor from controlling selection, invoicing, and payment.
|
| 45 |
+
|
| 46 |
+
**When something is wrong (conceptual):** Inflated or biased spend, repeated coupling of the same
|
| 47 |
+
internal and external parties without rotation, payment behaviour that fragments or obscures totals,
|
| 48 |
+
weak master-data linkage, or indications that beneficiary or party data overlaps with insiders.
|
| 49 |
+
Signals are contextual: compare to peer vendors, amounts, and approval patterns in the same data.
|
| 50 |
+
|
| 51 |
+
---
|
| 52 |
+
|
| 53 |
+
### 4. Shadow Payroll (Ghost Employee)
|
| 54 |
+
|
| 55 |
+
**Normal process (substance):** Payroll pays real employees under HR and payroll policies, with
|
| 56 |
+
accruals and settlements that match the entity’s payroll design (which may include multiple line
|
| 57 |
+
types, schedules, and banking arrangements you must infer from the data).
|
| 58 |
+
|
| 59 |
+
**When something is wrong (conceptual):** Beneficiaries or pay runs that are structurally odd
|
| 60 |
+
relative to the population (e.g. accrual shape, timing clusters, banking or institution patterns,
|
| 61 |
+
recency of employment lifecycle events vs pay activity, or concentration of authorship) can indicate
|
| 62 |
+
diversion or synthetic beneficiaries. **Plausible HR rows do not rule out fraud** — treat master
|
| 63 |
+
data as necessary context, not as a whitelist.
|
| 64 |
+
|
| 65 |
+
---
|
| 66 |
+
|
| 67 |
+
### 5. Inventory Manipulation (Asset Misappropriation)
|
| 68 |
+
|
| 69 |
+
**Normal process (substance):** Inventory moves should trace to economic events (receipts,
|
| 70 |
+
consumption, sales, authorised adjustments). Write-downs and adjustments require authorised,
|
| 71 |
+
documented physical or operational justification.
|
| 72 |
+
|
| 73 |
+
**When something is wrong (conceptual):** Stock increases without credible upstream support,
|
| 74 |
+
write-offs disconnected from prior stock history, suspicious symmetry or pairing of movements,
|
| 75 |
+
period-close clustering of adjustments vs norms, or split roles across related postings may indicate
|
| 76 |
+
inflation, concealment, or misappropriation. Map **this** entity’s inventory-related accounts and
|
| 77 |
+
references from the ledger before concluding.
|
| 78 |
+
|
| 79 |
+
---
|
| 80 |
+
|
| 81 |
+
**How to use this catalogue:** Use it to frame **hypotheses** and **questions**, not as a
|
| 82 |
+
checklist of built-in tests. All concrete controls, accounts, SQL filters, and thresholds must be
|
| 83 |
+
**derived and validated** against the chart of accounts and facts in the database.
|