- HOME
- Taxes & compliance
- UAE eInvoice retention: periods, storage and audit records
UAE eInvoice retention: periods, storage and audit records

UAE eInvoicing requires certain businesses to issue Electronic Invoices: structured invoice data exchanged electronically and reported to the Federal Tax Authority (FTA), not a PDF or paper copy. Issuing the invoice isn't the end of the obligation. Guidelines v1.1 is the official eInvoicing guidance from the Ministry of Finance (MoF). It requires every Electronic Invoice and Electronic Credit Note to stay in the business's records for a set number of years afterward. It also has to stay retrievable and readable to the FTA on request. That responsibility belongs to the business, even when an Accredited Service Provider (ASP) is the one storing the data on its behalf.
This guide covers how long those retention requirements run, and what a compliant archive has to do. It also covers where the business's responsibility ends and the ASP's begins, and what to produce if the FTA asks for evidence. One thing to know before the table: a single eInvoice can fall under more than one retention rule. Real estate is the clearest case, where the VAT rules run longer than the eInvoicing ones. Where two periods apply to the same record, the longer one decides when you can delete it.
How long must UAE eInvoices be retained?
Guidelines v1.1 sets the base retention period for Electronic Invoices, Electronic Credit Notes, and associated data. Its legal basis is Article 3(1) of the Tax Procedures Executive Regulation, Cabinet Decision No. 74 of 2023. The table below sets out the base periods, the possible extensions, and the separate general VAT figures for comparison.
Record type | Base period | Runs from | Possible extension | Source |
Electronic Invoices/Credit Notes, Taxable Person | 5 years | End of the Tax Period | +4 yrs (audit/dispute/audit notice); +1 yr (voluntary disclosure); +2 yrs (pending refund) | Guidelines v1.1 §5.4 |
Electronic Invoices/Credit Notes, other Persons | 5 years | End of the calendar year created | Same as above | Guidelines v1.1 §5.4 |
Electronic Invoices/Credit Notes, real estate | 7 years | End of the calendar year created | Same as above | Guidelines v1.1 §5.4 |
Records supporting a Corporate Tax return | 7 years | End of the relevant Tax Period | Check Corporate Tax rules | Corporate Tax record-keeping requirements |
Real estate records, general VAT record-keeping (broader than the eInvoice) | 15 years | End of the tax period | Check the VAT rules that apply | VAT record-keeping rules |
Capital assets other than real estate, general VAT record-keeping | 10 years | End of the tax period | Check the VAT rules that apply | VAT record-keeping rules |
An eInvoice can sit inside more than one retention obligation at once. The eInvoicing rules set one period; Corporate Tax and VAT set their own. Where more than one applies to the same record, the longest one governs the date you can delete it.
Which retention period applies to a real estate transaction?
Use the longer period. Guidelines v1.1 sets 7 years for real estate records under the eInvoicing provision, but the VAT rules require real estate records to be kept for 15 years, and records for capital assets other than real estate for 10 years. An eInvoice for a real estate transaction falls under the VAT requirement as well as the eInvoicing one, so 7 years is not the number to schedule a deletion against. Take advice on any transaction that touches real estate, because the VAT treatment decides which records the longer period covers.
Which records must be retained under Article 11?
Article 11 of Ministerial Decision No. 243 of 2025 requires every Person to retain Electronic Invoices, Electronic Credit Notes, and “associated data.” It also requires the Person to keep them producible to the FTA on request. Guidelines v1.1 defines that last term narrowly: “associated data” “refers only to the information required to support the integrity, authenticity, and auditability of an Electronic Invoice or Electronic Credit Note. It does not extend to general business or transaction-related documentation, nor to ancillary commercial information, unless such data is specifically required to confirm the completeness and accuracy of the Electronic Invoice or Electronic Credit Note record.”
That definition limits what counts as “associated data” under Article 11's eInvoicing storage obligation specifically. It doesn't limit the FTA's broader powers to request other accounting, tax, or transaction records during a tax audit under the Tax Procedures Law generally. An eInvoicing archive that satisfies Article 11 is necessary, but it isn't the ceiling on what a tax audit can ask a business to produce.
Where can UAE eInvoice records be stored, and what makes an archive compliant?
“Within the State”, as used in Article 11, doesn't mean physical servers located in the UAE. Guidelines v1.1 treats a business as having met Article 11 where all three of the following hold, and onshore, offshore, and cloud storage are all acceptable provided they do:
Storage conditions, as the Guidelines set them out:
● Invoice records and associated data are retained in an electronic system that preserves their integrity and ensures secure retention.
● The storage infrastructure, whether located inside or outside the UAE, enables the taxpayer to provide the required records promptly upon request.
● The records can be retrieved and reproduced by the FTA in a complete and readable form.
Recommended practice, worth building into your own process:
● Don't rely on a PDF or screen view as the complete record; retain the actual electronic invoice data.
● Suspend routine deletion for records affected by an extension, dispute, or legal hold.
● Preserve access when systems, ASPs, or storage contracts change, and test retrieval and export periodically, rather than assuming the archive still works the way it did when it was built.
In UAE eInvoicing, who's responsible for retention: the business or the ASP?
Who | Responsible for |
The business (the “Person”) | Electronic Invoices, Electronic Credit Notes, and associated data; the Article 11 legal obligation; retrieval and reproduction on request; tracking which extensions or legal holds apply. |
The ASP | Its own transactional logs: technical records with unique transaction identifiers, distinct from business document data, kept under its OpenPeppol Service Provider Agreement and the UAE Peppol Authority Specific Requirements. |
Contractual storage arrangement | An ASP may store the business's Electronic Invoices and Credit Notes by agreement, but this doesn't transfer the Article 11 obligation. The business remains ultimately responsible even when the ASP is doing the actual storing. |
No specific system layer is mandated for storage. Any compliant arrangement works, provided data is retained for the required period, integrity and security are preserved, and records are producible on request. Separately, the ASP must inform the business once an Electronic Invoice or Tax Data Document has been successfully transmitted to the FTA. This confirmation has to happen on an event-driven basis, without undue delay.
What should you do if the FTA asks for eInvoice records?
Work through these steps when a request arrives:
● Confirm the request's scope: the period covered and which transactions it concerns, before pulling anything.
● Suspend routine deletion for records in that scope, in case an extension or dispute later applies.
● Retrieve the Electronic Invoices, Electronic Credit Notes and associated data the request covers, along with any other accounting, tax or transaction records it asks for. The narrower "associated data" definition scopes your eInvoicing storage obligation; it doesn't limit what an audit can ask you to produce.
● Check completeness and readability, and confirm each credit note carries the invoice references that transaction requires. Volume discounts are the exception: where the reason code is VD, PINT AE doesn't require a preceding invoice reference.
● Reconcile the records against accounting entries and, where available, transmission or reporting confirmations.
● Log what was provided, when, and by whom, in case of a follow-up request.
Apply the same discipline before switching ASPs or storage systems. Confirm the new arrangement can still meet the three conditions above. Confirm, too, that historical records remain retrievable, since the Article 11 obligation doesn't pause for a migration.
Zoho Software Trading LLC is an Accredited Service Provider for UAE eInvoicing.
Explore UAE eInvoicing with Zoho Books.
Frequently asked questions
What are the UAE eInvoice retention requirements?
It depends on which rules apply to the record. The eInvoicing base period is 5 years following the Tax Period for a Taxable Person, and 5 years from the end of the calendar year of creation for other Persons, with 7 years for real estate records. Records supporting a Corporate Tax return need 7 years following the end of the relevant Tax Period, and some VAT records run longer still. A tax audit or dispute adds 4 years, a voluntary disclosure in the fifth year adds 1, and a refund application awaiting a decision can add 2. Check every rule that applies before you set a deletion date.
How long must real estate records be kept?
Longer than the eInvoicing rules alone suggest. The eInvoicing provision sets 7 years, but the VAT rules require real estate records to be kept for 15 years after the end of the relevant tax period. Use 15 years for anything real-estate-related, and take advice on the specific treatment.
Must Electronic Invoices be stored on servers physically located in the UAE?
No. Guidelines v1.1 interprets “within the State” as a retrievability requirement, not a physical-location one. Onshore, offshore, and cloud storage are all acceptable provided the records stay secure, accessible, and reproducible to the FTA in complete, readable form.
If our ASP stores our eInvoices, are they responsible for retention instead of us?
No. Delegating storage to an ASP by agreement is permitted, but it doesn't transfer the Article 11 legal obligation. The business remains ultimately responsible. An ASP's transactional logs are a separate, technical record distinct from the business's retained documents.
Can the FTA ask for records beyond your eInvoicing archive?
Not on its own. Guidelines v1.1's “associated data” definition scopes what counts as evidence under the eInvoicing-specific Article 11 obligation. It doesn't limit the FTA's wider power to request other accounting, tax, or transaction records under a general tax audit.
Related guides
● How UAE eInvoicing works: the 5-corner model, end to end
● UAE eInvoicing: EmaraTax onboarding, TIN, TRN, participant IDs and invoice statuses
● UAE eInvoicing credit notes: rules for correcting an Electronic Invoice
● UAE eInvoicing glossary: PINT AE, Peppol, ASP, TIN, MLS and more