Tax Record Keeping UAE: Four Clocks, Two Price Tags

A Dubai trading company did its spring clean in April. Storage was costing money, the old server was full, and someone found a tidy retention guide online that said five years. Five years sounded official. Five years sounded safe. So the team set one rule for the whole archive and started deleting. What nobody checked was which tax that five-year rule belonged to, because tax record keeping UAE does not run on one clock. It runs on at least four. And the fine for getting it wrong does not run on one price tag either. It runs on two, and the guides your team is most likely to open cross them in both directions.

This is the least glamorous topic in UAE tax, which is exactly why it goes wrong. Nobody argues about an archive at a board meeting. A retention policy gets copied from a summary, pasted into a procedure, and then applied quietly for years, long after anyone remembers which table it came from. The damage only surfaces later, when the FTA asks for a record that was deleted on schedule, on a schedule that belonged to a different tax. This post separates the clocks and the price tags regime by regime, names the guides that cross them, and sets out the one extension almost no retention summary carries: a pending refund can keep a file alive two years past its own expiry date.

Tax Record Keeping UAE: The Four Clocks, Kept Apart

Start with the two clocks everyone agrees on, because agreement ends quickly after them. VAT records: five years from the end of the tax period they relate to. That figure appears in guide after guide, from the FTA-facing checklists to the practitioner summaries, and we found no current account disputing it for ordinary VAT records. Corporate tax records: seven years from the end of the relevant tax period. Same story. The corporate tax penalty schedules state the seven-year duty in the same breath as the fine for breaking it, and the records guide that walks through both regimes side by side lands on the same pair: five for VAT, seven for corporate tax. Two taxes, two clocks, no serious argument. If your archive ran on nothing else, those two numbers would already beat the single five-year rule in our opening story, because a corporate tax file deleted at year five is deleted two years early.

Then real estate walks in and the consensus breaks. VAT records tied to real estate are fifteen years on two current accounts: the side-by-side records guide states fifteen for real estate inside its VAT section, and a long-running VAT audit checklist states the same fifteen-year figure for real-estate records. A current penalties guide draws the same shape in more detail, with ordinary VAT records at five years, capital-asset records at ten, and records relating to real property at fifteen. Against that, two accounts from the same well-known audit firm put real-estate VAT records at ten years: its FTA audit-file guide states ten years for real-estate related records, and its statutory audit guide repeats ten years for VAT records tied to real estate. Ten or fifteen is not a rounding difference. It is a five-year gap on exactly the files with the longest tails in any business: property purchases, fit-outs, development costs, and the input tax claimed on all of them. A destruction policy built on the ten-year telling deletes those files five years before the fifteen-year telling says the Authority's interest ends.

The clock almost nobody prints: a pending refund adds two years

One audit-file account adds a rule the retention summaries mostly leave out. Where a VAT refund claim is still pending, the retention period extends by an additional two years, which that account attributes to Cabinet Decision No. 17 of 2026. Read that slowly, because it changes how a destruction run has to work. A file does not expire on a date printed in a policy. It expires when its own clock runs out and no live claim is holding it open. A business still chasing a refund from a period whose files just hit their retention limit has a live reason those files must survive, and deleting them on schedule would be deleting the evidence for money the business itself is asking the FTA to pay. Before any destruction run, the pending-claims list has to be checked against the deletion list. That check costs an hour. Skipping it can cost the refund and the file in the same week.

The Fine Also Splits, and the Guides Cross It

Now the price tags, because they split the same way and the crossing has already happened in print. On the corporate tax side, the schedules agree with each other. Failure to keep the required records costs AED 10,000 for a violation, and AED 20,000 for a repeat within 24 months. Two separate corporate tax penalty guides state that pair in identical terms, and one adds the smaller neighbouring fine in the same section: AED 5,000 where records in Arabic cannot be produced on request. Clean, consistent, and, on the corporate tax side at least, not really in dispute.

The VAT side is where the argument lives. One group of current accounts prices a VAT record failure at AED 10,000 first time and AED 50,000 on repetition. The side-by-side records guide states that pair and ties it to the administrative-penalty framework of Cabinet Decision No. 75 of 2023 as amended by Cabinet Decision No. 129 of 2025. A major software provider's VAT FAQ states the same AED 50,000 repeat figure, sourced to the Ministry of Finance and the FTA. An audit firm's VAT fines page states it too: AED 10,000 first time, AED 50,000 in case of repetition. Three sources, one pair of numbers.

Then open the other group. A current VAT penalties guide states the record failure at AED 10,000 for a first offence and AED 20,000 for a repeated offence, the corporate tax pair, inside a VAT schedule. A lawyers' guide updated for the rules effective from 14 April 2026 states the same: AED 10,000 for a violation and AED 20,000 where the violation is repeated within 24 months. And a VAT fines table described as in force from 14 April 2026, updated six days ago, lists records not kept at AED 10,000 with AED 20,000 for a repeat within 24 months. So the newer-dated VAT tables carry the lower repeat figure, while the AED 50,000 figure is carried by accounts citing the older decision framework, and at least one records guide attributes its AED 50,000 to a citation that mixes the VAT and corporate tax decisions together. We are not going to pretend that mess resolves into one tidy number in a blog post. It does not. What it resolves into is a working rule: never provision, and never delete, off a blended schedule. Price the exposure per regime, check the current official schedule for the tax you are actually dealing with, and treat any guide that gives you one fine for both taxes as a guide that has stopped doing the work. The full side-by-side account is at the 2026 record-retention guide, and the cleanest corporate tax schedule we found is at the corporate tax penalty schedule. Read them next to each other and the crossing is visible on the screen.

A record you cannot produce is a record you do not have

There is a quieter failure sitting underneath both arguments, and it has nothing to do with dates. Retention is not storage. A record that exists somewhere, on a former employee's laptop, in a mailbox nobody can open, in a scan too poor to read, fails the same practical test as a record that was deleted: when the FTA asks, you cannot produce it. The records guide makes the electronic point plainly: records may be kept electronically provided they stay accessible and readable for the full period, and a dead hard drive does not satisfy the rule. Retrievability is part of the duty. That means the archive has to be searchable by period and by regime, the access has to survive staff changes, and somebody has to test it before an audit tests it for you. We made a version of this point in how one unreconciled bank file splits two tax returns: the file only protects you if it can be found, read and tied to a period when it matters.

Tax Record Keeping UAE: Build the Schedule Per Regime

The fix is boring, which is why it works. Stop running one archive policy and run a schedule with a line per regime and per record class. Ours, for a typical trading or services business, looks like this in practice.

• VAT, ordinary records: five years from period end. Invoices, credit notes, returns, import and export documents, and, since 1 October 2026, the supplier-verification evidence that now sits inside the VAT record set, a duty we covered in the Know Your Supplier rules.
• VAT, real estate: flagged at the longer telling, fifteen years, until your own position is confirmed in writing. The cost of keeping property files five extra years is storage. The cost of deleting them five years early is the claim they support.
• Corporate tax: seven years from period end, on its own line, priced on its own table, AED 10,000 and AED 20,000, never merged into the VAT line because the two files for the same year expire two years apart.
• Any period with a refund claim still pending: frozen. No destruction, whatever the schedule says, until the claim closes and the additional two-year extension described by the audit-file account has run.
• Every line: a named owner, a storage location that survives staff changes, and a production test once a year. Pick a closed period at random and time how long the full file takes to assemble. That number is your real retention position.

Two habits keep that schedule alive instead of laminated. First, tag records with their tax period at the monthly close, while the period is still obvious, rather than reconstructing periods from filenames at deletion time. Retention runs from period end, so a record without a period tag has no clock anyone can trust. Second, put the destruction decision in the same meeting as the filing decision. The team that has just triaged its Q3 errors, the work we set out this morning in the AED 10,000 voluntary disclosure rule, is the team that knows which periods are clean, which are disputed and which are still carrying a claim. Registration records belong on the same schedule, with their own penalty history kept separate, the split we unpicked in the AED 10,000 or AED 20,000 registration argument. And when a business is closing rather than filing, the archive becomes part of the exit itself, as we showed in the wrong-Emirate box trap, where the last periods are the ones nobody can afford to lose.

One Archive, One Rule Is the Expensive Option

There is a pattern running through this month's filing season, and the archive is its quietest example. The visible number gets the attention and the quiet condition carries the risk. A threshold quoted without its exceptions, a total quoted without its boxes, a deadline quoted without its second clock. Retention has the same shape twice over: a period quoted without its regime, and a fine quoted without its tax. Guides compress rules to fit a page, and compression is where the second clock and the second price tag fall off.

An honesty note, in the same spirit as the rest of this post. The retention periods and penalty figures above are presented exactly as the current guides and schedules cited here state them, attributed tax by tax, because they conflict: real-estate VAT retention is fifteen years on some current accounts and ten on others, and the VAT repeat record fine is AED 50,000 on one group of accounts and AED 20,000 on the newer-dated tables. Nothing here asserts that any named business was fined, deleted records early, or holds a file it cannot produce. Before you set a destruction date or provision a repeat exposure, confirm the current figure for that specific tax against the official schedule or take advice that puts the regime, the period and the figure in writing together.

So here is the sentence to keep for the next spring clean. Your archive has four clocks and two price tags. Run it on one of each, picked from different taxes, and the policy itself becomes the risk. Run it per regime, freeze anything a live refund is holding open, and test whether you can actually produce a closed period, and the dullest system in the business becomes one of the strongest pieces of evidence you own.

If you want the schedule built properly, Escrow keeps it per regime and per record class inside the monthly close: VAT at five years, corporate tax at seven, real-estate VAT files flagged at the longer telling until the position is confirmed, no destruction run while a refund claim is pending, and the VAT exposure priced on the VAT table while the corporate tax set is priced on its own. Start with a free accounting system health check at escrowconsultinggroup.com, and bring your current retention policy with you. The first thing we will check is not how long you keep things. It is which tax each line of the policy actually came from.