26 August 2026 · Evidence
What Documents Support a VAT Disclosure?
The Federal Tax Authority Voluntary Disclosure User Guide expects the form to be supported by corrected figures, an explanation of the error, the correction made and documents that let the FTA understand the position. Start with the filed return, ledger extract, invoices or credit notes, and a calculation that reconciles the old and corrected VAT amounts. Keep the pack together.
Exiloz Management & Tax Consultant · Dubai-based FTA-focused advisory · VAT, corporate tax & accounting
Prove what was filed
A useful document pack starts with the thing the FTA already received: the submitted VAT return and its EmaraTax filing receipt. Add the return's ledgers, not just a summary trial balance. The reviewer needs to trace the reported output VAT, input VAT and adjustments back to entries that existed when the return was filed.
The FTA Voluntary Disclosure User Guide asks for the corrected figures, a letter explaining the background and error, the corrections made and supporting documents. It does not turn every business into the same checklist. A retail credit note, an import entry and a missed invoice need different evidence because each changes a different part of the return. The file should show why each item is relevant.
Example, not an FTA amount: the return reported output VAT of AED 62,000, while the sales ledger and credit-note register support AED 58,500 after one credit note was omitted. The correction is AED 62,000 - AED 58,500 = AED 3,500. The pack should include the affected credit note, approval trail and ledger entry, not only the AED 3,500 total.
| Document | What it proves | Where it is used |
|---|---|---|
| Filed VAT return | The figures already submitted | Old position |
| General ledger extract | The entries behind the amount | Reconciliation |
| Invoice or credit note | The transaction treatment | Explanation |
| EmaraTax receipt | The filing and Tax Period | Date record |
Name the record behind each line
Start with the affected Tax Period and work outward. Put the filed return, filing receipt, general ledger extract, sales and purchase registers, tax invoices, credit notes and import declarations in a numbered folder. Use the document number or ledger reference in the explanation so a reader can move from the changed return box to the source.
The object that makes the claim true is the record behind the changed amount. For a missed sale, that may be the tax invoice and customer ledger. For a duplicate input claim, it may be the supplier invoice, payment entry and purchase register. For an import, the customs declaration and import VAT record may matter. Name the document instead of writing that records were reviewed, and give the reference used in the calculation.
The pack should also state what is not being changed. If one return box moves but another was checked and remains correct, say so. This narrows the review and prevents a preparer from silently changing unrelated figures while preparing the Voluntary Disclosure. A reviewer can then test the stated boundary against the filed return.
Make the correction readable
The explanation letter should tell a short factual sequence: what the business filed, how the error was found, which record proves it, how the number was corrected and why the selected FTA route applies. A dated reconciliation is stronger than a broad statement that the accounts were checked. Include the document references in the same order as the calculation.
If you are sending the pack for review, label the file before asking for a signature. The signed explanation, calculation workbook, filed return and supporting invoices should use the same Tax Period and correction amount. A mismatch between the letter and the return creates a new question even when the underlying transaction is clear.
The FTA guide confirms the need for an explanation and supporting documents, but it does not state a universal document count or one accepted file order for every error. That is the genuine evidence boundary. Use the smallest pack that proves the correction, then add records needed to explain an unusual treatment. The reason for each added record should be visible.
Reconcile before opening EmaraTax
The review can be run in a fixed order. First freeze the submitted return and the source ledger used at filing. Next isolate the entries that may be wrong. Then recompute the affected VAT fields, compare old and corrected totals, and prepare the explanation. Only after that should someone type the correction into EmaraTax.
We would not send an explanation letter before the changed line is tied to a document reference. The reason is simple: a persuasive sentence cannot repair a missing invoice, duplicate ledger entry or unsupported credit note. The source document should decide the wording, and the wording should point back to the source document.
If the error crosses more than one Tax Period, keep a separate reconciliation for each period even if the same supplier or customer is involved. The filed returns are separate objects. Combining them into one spreadsheet total can hide which return must be corrected and which date controls the next step. Preserve the underlying exports with each period file. This also makes later questions easier to answer.
Ask for deliverables, not a folder
A request for assistance should name deliverables rather than promise a result. Ask for a return-to-ledger reconciliation, a Tax Difference calculation, a document index, an explanation letter and a submission handover. If the FTA asks for more information later, the business should know which file supports each line. Put the promised handover items in the engagement record.
The mistake we see most is sending a folder of invoices without a map. The FTA can receive many files and still lack the link between the changed VAT amount and the transaction that caused it. A one-page index with document name, date, amount and purpose usually does more work than a second undirected export. Keep the index with the submitted pack and identify its source folder clearly.
After submission, keep the file open. The FTA guide records a Voluntary Disclosure by its reference number and status, and says the form can be edited if the Authority requests more information. Save the submitted return, calculation, explanation, document index and response evidence together. If the FTA asks how a changed box was derived, the answer should be ready from the same chain. A pack that cannot be reopened leaves the business rebuilding its explanation under pressure.
Frequently Asked Questions
For assembling records that support the correction.
Which records should support a VAT disclosure?
The FTA Voluntary Disclosure User Guide points to the information needed to explain the error and correction. A practical pack starts with the filed return, ledger extract, relevant invoices or credit notes, the corrected calculation and records that show why the revised VAT treatment is right.
Do I need an explanation of the error?
Yes, the FTA guide is built around explaining the error, the corrected values and the supporting position. Write the explanation so it connects the source record to the affected return entry, the corrected VAT amount and the document that supports each material change.
Should credit notes be included?
Include credit notes where they explain the VAT difference or show why the original return was wrong. The Federal Tax Authority expects the disclosure to be supported by information that explains the correction, so attach the relevant transaction trail rather than sending an unexplained total.
Can Exiloz prepare the evidence pack?
Exiloz can reconcile the affected return to the ledger, select the relevant invoices and credit notes, prepare the correction schedule and draft the explanation for the FTA Voluntary Disclosure. The Federal Tax Authority remains the authority for the filing requirements.
Is Your Evidence Ready?
Exiloz builds the return reconciliation, correction schedule and supporting explanation for your VAT Voluntary Disclosure.