UAE VAT Refund Supporting Documents: VAT311 Checklist

For UAE VAT311 refunds, the support pack starts with the output/input tax report and tax invoices with supporting documents. A practical refund file then ties those documents to the filed VAT return, the ledger, the invoice source files, and any export, import, or zero-rated support before the refund request is submitted through EmaraTax.

The official baseline is concise. The FTA Tax Refund to Registered Tax Payers service card lists an output and input tax report plus tax invoices and supporting documents as required documents for V311 and EX311 refund requests, and states a 25-business-day completion estimate for completed applications. The same service card also notes a longer audit path of 55 working days once requested information has been provided, which is why the refund claim needs evidence that can be followed from the refund amount back to the underlying transactions.

UAE VAT refund supporting documents should answer four review questions: what amount is being claimed, which VAT return and period created the refundable balance, which invoices or transactions support the recoverable input VAT, and where the source records sit if the FTA asks for more detail. If those questions are not answered inside the pack, the reviewer has to reconstruct the file from accounting records, spreadsheets, and loose PDFs.

Reconcile the refund amount before selecting documents

The output and input tax report VAT311 support should act as the control document for the pack. Before selecting invoices, reconcile the claimed refund amount to the filed VAT return and the accounting records. Otherwise the invoice file can look complete while the numbers still fail to tie back to the return.

Start with the refund figure or refundable balance in the VAT return. Tie it to the output/input tax report, then to the VAT control accounts, purchase ledger, sales ledger where relevant, and any carry-forward balance from earlier periods. If the business has adjustments, credit notes, imports, reverse-charge entries, or manual corrections, show where they sit in the calculation rather than leaving them to be inferred from the general ledger.

This is the same discipline used in UAE VAT return reconciliation, but a refund claim needs the tie-out to be more reviewer-friendly. The reviewer should not have to ask whether the input tax schedule agrees to the VAT return, whether a credit note reduced a claimed invoice, or why the ledger amount differs from the report. Those answers should be visible in the reconciliation file.

The most common weak points are small but disruptive: invoice totals that do not match ledger postings, credit notes kept in a different folder, foreign-currency invoices without a conversion reference, import VAT sitting outside the purchase-invoice schedule, and spreadsheet edits that cannot be traced back to a source document. Each mismatch should either be corrected before submission or explained in a reconciling item.

A practical reconciliation output can be short: one summary tab or memo showing the VAT period, refund amount, source schedules used, ledger accounts checked, and reconciling items.

Build the purchase invoice schedule and rank the evidence

Purchase invoices are usually the centre of a taxable-person VAT refund claim because they substantiate the recoverable input VAT that creates or increases the refund position. A reviewer needs more than invoice PDFs. They need a schedule that shows which invoices make up the claim and how each one ties to the books.

A useful purchase-invoice schedule includes the fields a reviewer would otherwise have to pull manually from the documents:

• supplier name and supplier TRN
• invoice number and invoice date
• taxable amount, VAT amount, and gross amount
• currency and conversion reference where relevant
• ledger account and VAT code
• VAT return period
• source file name and page number
• short notes for unusual or material items

That schedule can be built from the same data used in a UAE VAT purchase register from invoices, provided it is reconciled to the ledger and linked back to the source invoice files. The refund pack should preserve that source trail. A spreadsheet row with no file name or page reference is a weak support record because it forces the reviewer to hunt for the document behind the number.

Rank the evidence by refund impact and review risk. Highest-value invoices deserve attention, but so do first-time suppliers, large credit notes, imported goods, export-linked costs, blocked or exempt-use costs, and invoices coded manually outside the normal workflow. For each material invoice, keep the source file, any related credit note, the ledger reference, and the recoverable portion together.

Check invoice validity and transaction-specific support

A refund pack should not rely on an invoice until the invoice is valid enough to support input VAT recovery. The risk is not only that a document is missing. The risk is that the document exists but does not prove the VAT claimed in the refund calculation.

Before submission, check the invoices against the practical field requirements covered in UAE VAT invoice requirements. For VAT311 tax invoices supporting documents, the schedule and source file should support the supplier identity, supplier TRN, invoice date, unique invoice number, tax invoice wording where required, taxable amount, VAT amount, VAT rate, currency treatment, and enough description of the goods or services to understand the transaction. Where recipient details are required, they should agree to the claimant's records.

Credit notes need the same treatment. They should be linked to the original invoice and reflected in the refund calculation. A refund pack that claims the original invoice but leaves a later credit note in another folder overstates the evidence, even if the accounting records are correct somewhere else.

Some defects can be fixed before submission. A missing source file can be retrieved, an unclear scan can be replaced, and a supplier can be asked for a corrected invoice. Other gaps need a different decision: exclude the transaction, adjust the claim, or document why the VAT treatment is still supportable. The pack should show that judgement rather than hiding the issue inside a large schedule.

Not every transaction stands on the invoice alone. Export or zero-rated supplies need the relevant commercial and movement evidence. Imports may need customs or import VAT documents. Unusual charges may need contracts, purchase orders, delivery notes, or service evidence. Payment references are not always the main VAT support, but they help when the transaction looks unusual, material, or disconnected from the normal purchasing cycle. Mixed-use or exempt-use costs should carry a note explaining the recoverable portion included in the refund calculation.

Index the pack so FTA follow-up can be answered quickly

The refund support pack should be indexed before submission. If the FTA asks for clarification, the finance team should be able to point to the file, schedule row, ledger reference, and source document without recreating the claim from the accounting system. The same traceability supports broader UAE FTA audit preparation if the request expands beyond the refund file.

A practical UAE VAT refund document checklist can be organised in this order:

• refund summary showing the VAT period and amount claimed
• output/input tax report used for the VAT311 request
• filed VAT return copy or return reference
• reconciliation memo tying the refund amount to the ledger
• purchase-invoice schedule with source-file references
• invoice and credit-note source files
• import, export, or zero-rated support where relevant
• ledger extracts and VAT control account support
• notes for unusual items, exclusions, adjustments, or judgement-based VAT treatment

Each document in the pack should have a job: calculation support, invoice evidence, ledger tie-out, transaction-specific proof, or exception explanation.

Use cross-references that survive outside the preparer's head. Schedule line numbers should match source files. File names should include enough detail to identify the transaction, such as supplier, date, and invoice number. Multi-page PDFs should carry page references. If a claim includes a large invoice, the reviewer should be able to move from the schedule row to the exact invoice page without opening every PDF in the folder.

Keep the reasoning for exclusions and adjustments with the pack. If part of an invoice was not claimed because it related to exempt use, if a credit note reduced the recoverable amount, or if an import entry was supported outside the normal supplier-invoice file, document that decision next to the transaction. A refund file is stronger when it shows both what was claimed and what was deliberately left out.

The working standard for the file is practical: a reviewer should be able to move from the refund amount to the VAT return, ledger, schedule row, and source document in one traceable path.