Penalties & Disputes
Audit Trails as Evidence in Tax Disputes
Using system audit trails to prove contemporaneous record-keeping in FTA disputes — exports, user logs and integrity.
audit trail tax dispute evidence
An audit trail — the system's log of who created or changed each record and when — proves your books were kept contemporaneously, not reconstructed for the dispute. Export user logs, creation timestamps, and change histories for the disputed periods. A clean audit trail is the best answer to any suggestion that records were backdated.
Basis: Federal Tax Authority, as published by the Ministry of Finance
- What it proves
- Books kept at the time, not rebuilt
- System log of who changed what and when
- What to export
- User logs, timestamps, change histories
- For the disputed periods
- Best use
- Answers any backdating suggestion
- Keep the master file at least 5 years
# What the trail proves
Every tax dispute contains an unspoken question: were these records kept in the ordinary course of business, or assembled after the assessment arrived? The audit trail answers it objectively. Creation dates spread across the period, entries by the right users, corrections logged rather than overwritten — that is the signature of genuine bookkeeping, and reviewers recognize it.
The FTA reviewer and the TDRC decide on papers. They were not present when the events happened, so your documents are the events. Every item below should be legible, dated, and complete — a cropped screenshot with no date raises more questions than it answers.
The standard of proof in practice
Neither reconsideration nor the TDRC is a criminal trial, but the practical standard is the same everywhere: the side with the contemporaneous document wins the factual point. Your own spreadsheet, rebuilt last week, proves nothing; a bank value date or an EmaraTax receipt proves everything.
# Exporting a persuasive trail
Work through this list and assemble each item before drafting the request — the 40-business-day clock does not pause while you hunt for paperwork:
- User activity logs for the disputed periods, showing who entered what and when
- Record creation timestamps across the period — spread out, not clustered
- Change histories showing corrections as corrections, not silent overwrites
- System configuration showing audit logging was enabled throughout
- The software's data-integrity or lock features, documented
- A short explainer of the system for a non-technical reviewer
Presenting each document
Do not dump raw logs — summarize the trail in one page ('records created throughout the period by three users; corrections logged') and exhibit the supporting exports behind it. If the system lacks audit logging, say so and compensate with corroboration; pretending a basic spreadsheet has an audit trail insults the reviewer.
# Filing the bundle
Combine everything into one indexed PDF: a one-page index, tabs numbered to match your grounds, every page numbered. EmaraTax caps upload sizes, so compress without destroying legibility. File the reconsideration within 40 business days of notification; the FTA decides in 40 business days and notifies in 5. If refused, the same bundle — tightened around the strongest ground — goes to the TDRC within 40 business days with the tax paid in full.
If the deadline is close or the amount is large, get help before you file. Call +971 58 541 4616, message us on WhatsApp at https://wa.me/971585414616, email info@taxadvisors.ae, or use the contact form at /contact/.
| Stage | Your deadline | Authority deadline |
|---|---|---|
| Tax assessment review (Article 28) | 40 business days from notification of the assessment | FTA decides in 40 business days, notifies in 5 |
| Reconsideration (Article 29) | 40 business days from notification of the decision | FTA decides in 40 business days, notifies in 5 |
| TDRC objection (Article 32) | 40 business days from notification of the reconsideration decision; tax must be paid in full | Committee decides in 20 business days, notifies in 5 |
| Court appeal (Article 36) | 40 business days from notification of the Committee decision; 50% of penalties secured | Court timetable applies |
# Using what the trail proves across the dispute ladder
Every tax dispute contains an unspoken question: were these records kept in the ordinary course of business, or assembled after the assessment arrived? The audit trail answers it objectively. Creation dates spread across the period, entries by the right users, corrections logged rather than overwritten — that is the signature of genuine bookkeeping, and reviewers recognize it. The same documents serve at every rung, but each forum reads them differently. At reconsideration, the FTA reviewer checks whether the papers disprove the assessment's factual basis — organize around the assessment's findings, answering each in turn. At the TDRC, the Committee reads for the story the refusal missed: lead with the one-page chronology, then the documents the FTA underweighted, and frame the bundle around the refusal's reasons rather than the original assessment. If the case reaches the competent court, the bundle must meet litigation standards — every exhibit formally referenced in the pleadings, translations certified, and the chain of custody clear.
Between rungs, audit the bundle ruthlessly: drop exhibits that proved nothing, strengthen the ones that carried weight, and add anything genuinely new. A bundle that grows smarter at each stage — rather than simply thicker — is the mark of a well-run dispute. Keep the master file for at least 5 years after the relevant tax period, or 7 years for corporate tax records under Article 56 of Federal Decree-Law No. 47 of 2022; the record-keeping obligation outlives the case, and the FTA may revisit the period.
What to add if the dispute escalates
At each new rung, add three things: the previous forum's decision with its stated reasons (the new target), an updated chronology covering what happened since, and any documents created in the interim — correspondence, payment proofs, new computations. Never assume the new forum has read the old file; make each bundle self-contained.
Sources and legal basis
Legislation and decisions3
- Federal Decree-Law No. 28 of 2022 on Tax Procedures
- Federal Decree-Law No. 17 of 2025
- Cabinet Decision No. 74 of 2023 (Executive Regulation of the Tax Procedures Law)
Authorities, systems and registers2
- Federal Tax Authority (FTA)
- EmaraTax
Terms used1
- Tax Disputes Resolution Committee (TDRC)
- Federal Decree-Law No. 28 of 2022 on Tax Procedures and its amendments, consolidated 3 December 2025Federal Tax Authority, as published by the Ministry of Finance
- Reconsideration Request service card (fee, EmaraTax path, response time; page last updated 19 August 2026)Federal Tax Authority
Rates, thresholds and deadlines change. Every figure above is linked to the authority that publishes it — if the two ever disagree, the authority is right and this page is out of date. Tell us and we will fix it.
Frequently asked questions
My books are in Excel — is that a problem?
Not fatal, but weaker than a proper accounting system. Excel files carry creation and modification dates, and emailing versions to the accountant creates a dated trail — gather those. Going forward, move to a system with user logs; the next dispute will thank you.
Do my documents need Arabic translations?
The FTA can require documents in Arabic, and key exhibits read better with a translation attached. Translate the documents your grounds depend on — the contract clause, the bank date, the licence — rather than the whole bundle. A certified translation removes a reason for the reviewer to set your file aside.
What if the audit trail shows errors we corrected?
Show them proudly. Corrections logged as corrections are the hallmark of honest bookkeeping — every real business corrects entries. What damages credibility is silent overwriting or gaps, not visible corrections. Explain the correction pattern in one paragraph and move on.