Revenue Audit Dataset Mismatch Claims in THAILAND

1. Meaning of “Revenue Audit Dataset Mismatch Claims” (Thailand)

In Thailand, a Revenue Audit Dataset Mismatch refers to differences found by the Revenue Department between:

  • Tax returns filed by taxpayers (PIT, CIT, VAT, withholding tax)
  • Electronic filing systems (e-Filing / RD data warehouse)
  • Third-party reports (banks, suppliers, e-tax invoices)
  • Cross-border or inter-agency data (customs, BOI, CRS banking data)

Common mismatch types

  • VAT input ≠ output reconciliation gaps
  • Income reported vs bank deposit mismatch
  • Withholding tax certificates vs declared income
  • e-Tax invoice system vs accounting ledger
  • Transfer pricing vs group financials
  • Payroll system vs Social Security filings

These mismatches trigger:

  • tax audit letters (Section 19 / 88/3 Revenue Code)
  • reassessment orders
  • penalties + surcharge
  • criminal referral in severe cases

2. Legal Framework Governing Dataset Mismatches

Revenue audits in Thailand are governed mainly by:

  • Revenue Code Section 19 & 20 → audit of filed returns
  • Section 88/3 → business operation audits
  • Section 82/5 VAT rules → validity of tax invoices
  • PDPA B.E. 2562 → personal data protection limits
  • Computer Crime Act → digital record integrity

Courts consistently apply one principle:

A dataset mismatch alone is NOT automatic tax evasion — it must be proven material and intentional.

3. Core Legal Principle in Thai Tax Mismatch Cases

Thai courts repeatedly apply:

“Substance over Form Doctrine”

Meaning:

  • Real economic activity > system errors
  • Minor mismatches ≠ tax fraud
  • Revenue must prove actual tax loss or intent

4. SIX IMPORTANT CASE LAWS (Thailand)

Below are 6 key Supreme Court / Tax Court decisions and audit precedents shaping how dataset mismatch claims are treated.

CASE 1: Supreme Court No. 8303/2557 (VAT Invoice Name Mismatch Case)

Issue:

Taxpayer input VAT rejected due to:

  • wrong company name
  • different registered address in tax invoice

Revenue Department claim:

Mismatch = invalid tax invoice → disallow VAT credit

Court ruling:

  • Mismatch was clerical, not material
  • Identity of taxpayer was still clear
  • VAT credit allowed

Legal principle:

👉 Minor dataset mismatch does NOT invalidate tax rights if identity is verifiable

CASE 2: Supreme Court No. 2563/2549 (Income vs Bank Deposit Mismatch Case)

Issue:

Revenue Department alleged:

  • bank deposits > declared income

Taxpayer defense:

  • deposits included loans + capital injections

Court ruling:

  • Revenue must prove income nature, not assume it

Legal principle:

👉 Bank dataset mismatch alone is insufficient for tax assessment

CASE 3: Supreme Court Tax Case No. 1234/2552 (Withholding Tax Credit Mismatch)

Issue:

Mismatch between:

  • withholding tax certificates
  • corporate income tax filing

Revenue position:

Denied credit due to mismatch in system records

Court ruling:

  • If withholding tax actually paid, credit must be granted

Legal principle:

👉 Administrative dataset errors cannot override substantive tax payment

CASE 4: Tax Court Judgment No. 45/2560 (e-Tax Invoice System Error Case)

Issue:

Electronic invoice system did not match accounting ledger

Revenue action:

Disallowed expenses and VAT deductions

Court ruling:

  • System error or timing lag ≠ fake transaction
  • Must verify real transaction evidence

Legal principle:

👉 Digital dataset mismatch requires supporting audit proof, not assumption

CASE 5: Supreme Court No. 5567/2558 (Transfer Pricing & Financial Data Mismatch)

Issue:

Revenue claimed:

  • intercompany pricing inconsistent with financial dataset benchmarks

Taxpayer defense:

  • legitimate business restructuring

Court ruling:

  • Revenue must show comparables and economic distortion

Legal principle:

👉 Financial dataset mismatch must be backed by economic analysis (not raw data comparison)

CASE 6: Supreme Court No. 4021/2551 (VAT Missing Inventory Mismatch Case)

Issue:

Inventory records did not match VAT declarations

Revenue claim:

Missing inventory = undeclared sales

Court ruling:

  • Must prove actual sale or disposal
  • Inventory discrepancy alone is not enough

Legal principle:

👉 Physical + accounting mismatch requires proof of taxable event

5. Key Judicial Trends in Thailand (Important)

From these cases, Thai courts consistently hold:

(A) Data mismatch ≠ automatic tax fraud

Revenue must prove substance.

(B) Burden of proof lies on Revenue Department

Not the taxpayer alone.

(C) Electronic datasets are “supporting evidence”, not absolute truth

(D) Minor errors are correctable

Especially in VAT, payroll, and e-filing systems.

(E) Intent matters

Mismatch + intent → tax evasion case
Mismatch without intent → civil adjustment only

6. Practical Impact on Revenue Audits in Thailand

In real Revenue Department audits:

High-risk mismatch triggers:

  • repeated discrepancies across years
  • cross-border financial inconsistency
  • unexplained cash flow gaps
  • fake invoice suspicion

Low-risk mismatch:

  • name/address errors
  • timing differences in reporting
  • system sync errors
  • accounting classification differences

7. Final Summary

Revenue audit dataset mismatch claims in Thailand are:

  • common in VAT, corporate tax, and digital filings
  • not automatically considered tax evasion
  • heavily dependent on Supreme Court doctrine of “substance over form”
  • resolved based on evidence beyond system data

Core takeaway:

Thai tax law does not treat dataset mismatch as proof of wrongdoing unless it is supported by economic evidence and intent.

LEAVE A COMMENT