VAT Input Denial and Tax Evasion

An invoice is no longer the whole input-VAT answer

Federal Decree-Law No. 16 of 2025 gives the Federal Tax Authority power to deny input tax where a supply forms part of a tax-evasion arrangement. The Ministry of Finance also says taxpayers must verify the legitimacy and integrity of supplies before deducting input tax. A valid tax invoice remains part of the file, but it is not a complete answer if the transaction itself cannot be explained.

The object that makes recovery credible is the connected file: supplier identity, contract, delivery or performance proof, payment record and business use. If a finance manager sees a supplier with no clear activity, an unusual price and rapid pass-through, recording the TRN alone does not show why the VAT should be recovered. That is the practical shift.

• The FTA looks at the supply and its surrounding facts.
• A TRN check is evidence, not a substitute for evidence.
• Contracts should describe what was actually delivered.
• The ledger should agree with the source documents.

Red flags matter more than the supplier’s invoice design

The rule is most relevant where a business buys through an unfamiliar chain, claims a large input credit or deals with a supplier whose commercial role is hard to see. That does not mean every price variation is suspicious. It means the purchasing file should explain the choice of supplier, the service received and the reason the amount was paid.

A company is not expected to know facts hidden from it, but it should respond to facts placed in front of it. A missing delivery record, an invoice that does not match the contract, or a payment to an unrelated account can change the review. The decision belongs with the transaction file, not with a generic statement that the vendor looked registered.

One red flag is rarely a conclusion. It is a reason to ask for the missing object and record the answer. The purchasing manager may have a legitimate explanation for a price or route, but the explanation belongs in the file beside the contract and approval. That is how a reviewer can distinguish an unusual transaction from an unexplained one.

• Review new suppliers before the first large claim.
• Separate normal commercial risk from visible red flags.
• Record why the supply supports the company’s business.
• Escalate a chain that the purchasing file cannot explain.

Build the file around the supply, not around a checklist

For each material supplier, keep the signed contract, purchase order, invoice, delivery note or completion evidence, payment proof and correspondence that explains changes. Add the supplier’s TRN check and the internal approval. For imported goods, retain the customs and shipping file. For services, keep the work product, timesheets or acceptance record that shows the service was performed.

The file also needs a reason for the amount. A quotation, comparable offer or approval note can explain why the price was accepted. It does not need to prove that the cheapest supplier was chosen. It needs to show that the purchase was real, the counterparty was identified and the amount reached the ledger through a traceable process.

• Supplier identity and TRN check.
• Contract, purchase order and invoice.
• Delivery, performance and payment evidence.
• Approval note explaining unusual value or routing.

Reconcile the risky lines before you sign off

If your next VAT return contains a large input claim from a new supplier, do not start by exporting the invoice list. Start with the ledger lines that carry the largest or least familiar amounts. Tie each one to the contract, delivery evidence and payment. Then ask whether the transaction would still make commercial sense if the VAT line were removed from the discussion.

Where the answer is unclear, pause the claim or isolate the line for review rather than letting a clean-looking return hide a broken file. A note in the working paper should state what was checked, who checked it and what remains open. That note is part of the evidence. It turns a vague concern into a decision that another reviewer can follow.

The review should end with a signed exception list, not a general statement that suppliers were checked. Name the invoice, the missing delivery record or the unmatched payment, then state whether it was corrected, held out or escalated. A short exception list gives the next return preparer something concrete to clear.

• Rank input lines by value and unusual features.
• Tie the return line to the source transaction.
• Record the reviewer and the date of the check.
• Isolate unresolved amounts instead of burying them.

The gap is a finding, not a rounding issue

Worked example, not a statutory amount: the ledger shows AED 48,000 of input VAT, while the supplier invoices and customs file support AED 41,600. The unsupported gap is AED 6,400, calculated as AED 48,000 - AED 41,600 = AED 6,400. The reviewer should identify the two entries behind the gap, correct the period or evidence, and only then decide what amount belongs in the return.

The Ministry of Finance describes the FTA’s power to deny input tax in an evasion arrangement, but it does not state how the phrase ‘should have known’ applies to a particular supply chain in a published UAE decision. That edge remains unsettled. We would not file the full AED 48,000 claim until the AED 6,400 gap is explained, because the amount and the source file must tell the same story.

Do not use the example to invent a denial percentage or penalty. The law supplies the denial power; the arithmetic is only a way to locate the unreconciled line. The decision still depends on the document behind that line and the facts known to the business when it claimed the input tax.

• The number of suppliers drives the review population.
• Imported goods add customs and shipping evidence.
• Related-party or unusual chains need closer explanation.
• Missing work papers add time before filing.