Building an audit trail for an FTA audit when AI keeps your books

When the FTA reviews a VAT return, the request is usually concrete. Show me the tax invoices behind the input tax in Box 9 for this quarter. Show me how you arrived at the zero-rated figure. Explain this adjustment. The auditor is testing whether each number on the return can be walked back to a source document and whether the treatment was reasonable.

That means three things must be linked: the document, the ledger entry and the decision. A scanned invoice on a shared drive with no reference to the posting is only half the evidence. A posting with no document is worse.

In HelloBooks, every bill or receipt the AI reads stays attached to the entry it created. The original file, in Arabic or English, opens from the transaction itself. The AI's suggested coding, the VAT treatment per line and any change a person made afterwards are recorded with a name and a timestamp in the audit log.

This is the part people underestimate. In a manual system, a bookkeeper changes a VAT code and nothing records why. In an AI-assisted ledger, the suggestion and the human override are both visible, so the reviewer can see that the AI proposed standard-rated and the accountant changed it to exempt because the supplier was a bank charging an exempt fee.

Software keeps the links, but a few habits decide whether the trail is useful.

• Write a one-line reason on every manual journal. "Correct Q2 rent coding" is enough; a blank is not.
• Attach the supplier contract to recurring bills for rent, licences and retainers.
• Upload bank statements monthly at least, so every payment matches to a bill or invoice.
• Keep customs declarations and bills of lading with export sales you treat as zero-rated.
• Lock each VAT period after the return is filed, so later edits go through a visible adjustment.

A Sharjah trading company claimed AED 41,250 of input tax in one quarter. The auditor picked twelve bills totalling AED 18,900 of that VAT and asked for the tax invoices and proof of payment. The finance manager asked the AI: 'show me these twelve bills with documents and the matching bank payments'. Eleven came back complete within a minute.

The twelfth was a AED 2,100 VAT charge on a vehicle lease. The AI had coded it as recoverable; the accountant's note on the entry said the van was a two-seater used for deliveries and not available for private use, with the lease agreement attached. The auditor accepted it. Without that note, the conversation would have taken a week.

The AI does not correspond with the FTA, submit anything on EmaraTax or decide how to respond to an audit query. It assembles the evidence fast and shows its reasoning. A person, usually your accountant or tax agent, reviews the pack and replies.

It also cannot fix a missing document after the fact. If a supplier never issued a proper tax invoice, the AI will flag the gap, but chasing the supplier is still your job. That is why the flags matter most at the time of posting, not during the audit. For rules on how long to keep records and in what form, check the FTA's current guidance; our separate post on VAT record keeping covers the detail.