evidoria

← Back to browse

Good practice Imported

Turkey VDK KURGAN — AI real-time anomaly detection in e-invoices for tax fraud

Türkiye · Ankara · See the Türkiye profile · See the Ankara profile

Evidence: Descriptive / self-reported Top 75% 47/100 · Ask Evidence Copilot about this practice

Turkey's VDK launched KURGAN on 1 October 2025 — an ML system scanning e-invoices, ledgers, and banking records across 13 anomaly criteria. In 2025, VDK's AI-driven compliance programme detected 748 billion TL in undeclared income and assessed 294 billion TL in tax penalties.

748 billion TRY
Undeclared taxable income identified (VDK AI-assisted compliance programme, partial KURGAN attribution) (2025)
294 billion TRY
Tax penalties assessed (VDK AI-assisted compliance programme, partial KURGAN attribution) (2025)
86.8 billion TRY
Additional tax base voluntarily declared via invite-to-explain process (2025)
13 criteria
Anomaly-detection evaluation criteria used by KURGAN
Turkey VDK KURGAN — AI real-time anomaly detection in e-invoices for tax fraud

Details

Maturity
Scaling
Promoter
Turkish Tax Audit Board (Vergi Denetim Kurulu)
Period
2025–present
Keywords
tax administration, fraud detection, compliance enforcement

Context

Turkey's Tax Audit Board (Vergi Denetim Kurulu, VDK) launched the KURGAN anomaly-detection system on 1 October 2025 as the centrepiece of its Fake Document Combat Strategy. Applying machine learning across 13 evaluation criteria, KURGAN cross-references every e-invoice, e-ledger, and banking transaction in near real time, flagging purchase-sale mismatches, warehouse-capacity discrepancies, and patterns indicative of carousel or missing-trader VAT fraud. Turkey's mandatory e-invoicing infrastructure, spanning millions of VAT-registered businesses and billions of documents annually, provides the data substrate enabling KURGAN's nationwide, real-time cross-referencing.

Activities

Rather than issuing automatic penalties, KURGAN sends early-warning letters to flagged taxpayers, giving them the opportunity to correct declarations before formal enforcement — an advisory-first approach intended to raise voluntary compliance alongside detection.

Results

In 2025, VDK's AI-assisted compliance programme identified approximately 748 billion Turkish lira in undeclared taxable income and assessed 294 billion TL in tax penalties, while 86.8 billion TL in additional tax base was voluntarily declared through the invite-to-explain process. Because KURGAN launched on 1 October 2025, full-year 2025 figures reflect a blend of legacy and new-system detection, so attribution of these outcomes to KURGAN specifically remains partial.

Implementation

Indicative cost
Medium (€50k–€500k) — No specific budget or licensing figures published; system builds on existing mandatory e-invoicing/e-ledger infrastructure.
Time to results
Short (< 1 year) — Launched nationwide on 1 October 2025 as part of the Fake Document Combat Strategy; 2025 outcome figures cover the full year but only partially reflect KURGAN's operating period.
Staffing & skills
Turkish Tax Audit Board (Vergi Denetim Kurulu, VDK), Ministry of Finance oversight

Conditions for success

  • Pre-existing mandatory nationwide e-invoicing infrastructure providing the real-time data substrate
  • Advisory-first design (early-warning letters rather than automatic penalties) to raise voluntary compliance

Common failure modes

  • The 13 algorithmic evaluation criteria remain undisclosed
  • No published independent algorithmic audit
  • October 2025 launch date means full-year 2025 figures blend legacy and new-system detection, limiting KURGAN-specific attribution

Where it fits

Governance type
national government
Scale
national tax administration
Income level
upper-middle income (Turkey)

Commonly funded by

National / regional programmes

Indicative funding routes for practices of this type — always check each programme's current calls and eligibility rules.

Do you run this practice? Claim it — verified implementers get a public contact pathway and can propose corrections.

Data sources

Where this practice's information was retrieved from, and when.

Attachments

Similar practices you may find useful