Skip to main content
TaxAI
Toggle menu

UAE corporate tax records: what to keep for seven years

Build a UAE corporate tax records archive that connects accounts, adjustments and returns, using the seven-year retention rule and a practical folder checklist.

A folder of accounting records beside a clock, illustrating long-term document retention.

The purpose of a corporate tax archive is to let another person reconstruct a filed figure and understand the decisions behind it. A return PDF proves what was submitted. It usually does not explain how income was calculated, why an adjustment was made or where the underlying evidence can be found.

The FTA’s record-retention guidance gives the corporate tax baseline of at least seven years after the end of the relevant tax period. The FTA General Guide, record-keeping section also explains the period-based requirement. Use that rule to plan retention, then design the file so retained records remain understandable and accessible throughout that time.

Organise by entity and tax period

A shared folder called “company tax” becomes difficult to use once it contains several years, draft calculations and more than one legal entity. Start with an entity identifier and the tax-period dates. Within that folder, keep a consistent structure that the preparer and reviewer both understand.

Folder Typical contents
Entity and period Incorporation and registration details, financial-year information and relevant correspondence
Books Ledger, trial balance, accounts and reconciliations
Evidence Invoices, contracts, receipts, bank statements and supporting schedules
Tax workings Tax reconciliation, reviewed adjustments and calculations
Decisions Relief assessments, elections, approvals and resolved technical questions
Filing Submitted return, acknowledgement and payment evidence

This is a suggested operating structure, not an exhaustive statutory list. A company with assets, related-party arrangements or unusual transactions will need additional records. Add them where the reviewer can connect them to the relevant working paper instead of burying them in an unrelated email archive.

Trace one expense from the return to the original document

Consider an illustrative professional-services company whose accounts contain AED 72,000 of office costs. Its ledger includes twelve AED 5,000 charges and AED 12,000 of other items. The sum reconciles arithmetically, but a reviewer still needs to see what the costs represent and whether the proposed tax treatment is supported.

Keep a transaction schedule showing the twelve charges, other items, supplier references and links to documents. If an invoice covers a different period or the reviewer changes a classification, record the explanation in the schedule. Do not simply overwrite the account name and leave the original document disconnected from the final treatment.

Suppose the reviewer identifies an AED 2,000 item that requires a tax adjustment. Preserve the accounting amount, adjustment and reason separately. The archive should explain the movement from the accounts to the tax calculation. It should not require a future reviewer to guess whether the AED 2,000 disappeared because of a correction, an omitted invoice or a deliberate tax decision.

The same method works for income, assets and funding. Give every material working-paper line a reference that leads to the relevant transaction list and evidence. Traceability is more valuable than collecting large quantities of disconnected files.

Use identifiers that survive a software change

Choose document names and references that do not depend entirely on one application’s screen layout. A useful filename might include the supplier, invoice reference and date, while the schedule records the entity, amount and related ledger entry. A screenshot with no document number or context is harder to interpret several years later.

For foreign-currency items, preserve the original currency and the conversion basis used in the accounts or working paper. Keep dates labelled clearly: document date, transaction date, accounting period and payment date can answer different questions. Where a supporting calculation uses a particular exchange-rate source or assumption, retain it with the calculation.

If attachments remain in a bookkeeping platform, document how they can be exported and who can access them. Test the export before changing subscriptions or advisers. A download containing only transaction amounts may not include the invoices, audit trail or explanations needed to understand those amounts.

Avoid making one person’s inbox the only index. Shared access should be controlled, but another authorised person should be able to locate the records if the original preparer leaves or becomes unavailable.

Keep the review history, not endless unexplained drafts

Set a clear distinction between working drafts and the approved filing version. Use version dates or identifiers, record the reviewer and retain a brief description of material changes. The aim is to explain the final position without forcing someone to compare dozens of almost identical spreadsheets.

For example, if draft two changes taxable income after resolving an owner-funding classification, note the affected account, decision and evidence reference. Preserve enough history to understand the change. Then identify the version actually used for submission and keep its approval with the filed return.

A question log is useful when preparation spans several people. Record the issue, the information requested, the answer, who approved the treatment and where the evidence lives. Close questions explicitly rather than deleting them once the spreadsheet balances.

Retain relief and inactive-period evidence

A Small Business Relief election still needs evidence of eligibility, including the relevant revenue history. A zero tax result does not make those documents unimportant. Keep the assessment and filed election alongside the underlying accounts so a later review can reproduce the conclusion.

When a company stops operating, changes ownership or appoints a new accountant, agree custody before systems or subscriptions are closed. Identify who will retain the archive, how authorised requests will be handled and how access will be maintained. A handover list should include missing documents and unresolved questions as well as successfully transferred files.

Do not treat seven years as a universal automatic deletion date. VAT, property records, other legal requirements and active disputes may need a different assessment. Record the applicable retention decisions and review them before deleting material that may still be needed.

Test whether the archive actually works

Once a quarter, choose three figures from the latest approved tax file and ask someone other than the preparer to find the calculation and supporting documents. Note broken links, missing attachments, unclear units and unexplained adjustments. Assign repairs and repeat the test after significant software or staff changes.

Keep a separate accessible backup and verify that it can be opened. An untested backup is an assumption about recovery. Include the index and important explanations, not only the source invoices.

Start this process during the monthly bank reconciliation. Resolving differences and collecting evidence as transactions occur produces a much stronger archive than trying to reconstruct a whole year just before filing. The finished file should make a future question answerable with a short evidence trail rather than a search through years of messages.

Sources checked on 26 October 2026. Folder structures, examples and retrieval tests are suggested operating practices.

Sources

Bring your books into focus.

Keep records, questions, and preparation in one workspace.

Start my workspace