The 15-year problem: What happens to UAE e-Invoicing data when contracts expire

UAE retention obligations stretch far beyond the horizon of any software contract. The VAT Capital Assets Scheme under Article 60 of Federal Decree-Law No. 8 of 2017 runs a 10-year adjustment period on buildings and real estate, with supporting records typically held for 15 years. Federal Decree-Law No. 47 of 2022 on Corporate Tax adds a 7-year retention duty under Article 56. The Tax Procedures Law baseline is 5 years, with another 4 years stacked on during an audit or dispute.

ASP accreditation under Ministerial Decision No. 64 of 2025 lasts two years. Commercial ASP contracts typically run one to three years. Retention obligations continue long after either expires.

Penalties for missing records are already structured. Cabinet Decision No. 106 of 2025 sets the e-invoicing-specific fines, and the full UAE e-invoicing penalty and enforcement picture extends further into Tax Procedures Law and Corporate Tax enforcement. Tax Procedures Law penalties for failure to keep records are AED 10,000 for a first offence and AED 50,000 for repeats, with an additional AED 1,000 per day for delayed production of requested documents.

There is no single retention rule for e-invoicing. Four overlapping rules apply, and the longest one wins.

Tax Procedures Law (Federal Decree-Law No. 28 of 2022). Under Cabinet Decision No. 74 of 2023 and Section 5.4 of the UAE Electronic Invoicing Guidelines issued by the Ministry of Finance on 23 February 2026, data relating to the issuance, transmission and receipt of Electronic Invoices must be retained for five years following the Tax Period for a Taxable Person, five years from the end of the calendar year of creation for non-Taxable Persons, and seven years from the end of the calendar year for real estate records

An additional four years are added during a dispute, ongoing audit, or notification of intended audit, and an additional one year from the date of a voluntary disclosure made in the fifth year.

VAT Capital Assets Scheme. Article 60 of the VAT Decree-Law and Articles 57 and 58 of the VAT Executive Regulation apply to capital assets above AED 5 million. The adjustment period is 10 years for buildings and real estate and 5 years for other capital assets. Records supporting the adjustment calculation are retained for the full period, with real estate-linked records generally held for 15 years to cover the adjustment lifecycle and its tail obligations.

Corporate Tax Law. Article 56 of Federal Decree-Law No. 47 of 2022 requires all records and documents supporting a Corporate Tax return to be retained for seven years after the end of the relevant tax period.

AML and DNFBP obligations. Real estate agents, dealers in precious metals, accountants, legal professionals, and corporate service providers retain transaction records for five years under Federal Decree-Law No. 20 of 2018.

The UAE five-corner e-invoicing model assigns validation and transmission duties to Accredited Service Providers. The ASP sits between supplier and buyer, validates the XML against PINT AE, transmits the invoice over PEPPOL, and reports Tax Data to the FTA.

The ASP does not handle permanent archival by default. Article 11 of Ministerial Decision No. 243 of 2025 places the storage obligation on the Person subject to Electronic Invoicing, which is the taxpayer, not the ASP. The MoF guidelines are explicit: “A Business will be regarded as having met the requirements where: (i) invoice records and associated data are retained in an electronic system that preserves their integrity and ensures secure retention; (ii) the storage infrastructure, whether located inside or outside the UAE, enables the Taxpayer to provide the required records promptly upon request; and (iii) the records can be retrieved and reproduced by the FTA in a complete and readable form.”

If the ASP’s archive disappears through accreditation lapse, contract termination, corporate acquisition, or data lifecycle policies, the taxpayer still owes the FTA a complete and readable record. Retention gaps sit alongside other overlooked risks in UAE e-invoicing compliance that surface only once the mandate is live.

Under Ministerial Decision 64 of 2025, an ASP’s accreditation is granted for 24 months and must be renewed. An ASP that loses accreditation cannot continue to validate or transmit on the UAE network. Business continuity falls on whoever holds the historical data and whoever can produce it to the FTA on request.

On the PEPPOL side, OpenPEPPOL defines a participant migration process that moves a PEPPOL ID between service providers using a migration token, governed by the OpenPEPPOL Service Provider Agreement. The tooling is not universally exposed in commercial products. Migration between ASPs handles forward traffic. It does not automatically retrieve or transfer years of historical archives. Those have to be exported, validated, and re-ingested into the new environment, or held in a system the taxpayer controls directly.

The MoF guidance on “within the State” is often misread as a data sovereignty requirement. The February 2026 guidelines clarify the policy intent: “The reference to ‘within the State’ should be interpreted as requiring that Electronic Invoices, Electronic Credit Notes and the associated data be maintained in a way that enables them to be retrieved and provided when requested by the FTA, irrespective of the geographic location of the servers, databases, or cloud-based solutions used to store them.”

This is an accessibility standard, in line with the broader data sovereignty rules for UAE e-invoicing. Retrieval readiness is what the FTA audits, and server location is secondary.

The operational questions are:

Who is the record owner of the XML Electronic Invoice file?

Who holds the validation metadata: UUID, ASP confirmation messages, FTA reporting confirmations?

Where is the archive when the ASP contract expires?

What is the retrieval SLA, and does it match the FTA’s request timelines?

Under the Tax Procedures Law and its Executive Regulation, the FTA can request records at any point during an audit. A delay in providing requested documentation carries AED 1,000 per day, accruing until the records appear. Producing a 10-year-old real estate invoice during an FTA review in 2034 depends on whether the retrieval infrastructure set up in 2026 still works.

Three scenarios trigger the data transition problem.

Commercial contract expiry. Standard SaaS contracts run one to three years. At renewal, a taxpayer may switch providers for commercial, functional, or service reasons. The forward PEPPOL flow can migrate. The historical archive typically does not. Whatever has been stored inside the outgoing ASP’s archive needs to be exported, invoice XML, validation confirmations, ASP confirmation messages, FTA reporting confirmations, and either handed to the new ASP or ingested into an independent archive controlled by the taxpayer.

Accreditation lapse. An ASP that fails to renew accreditation, or fails a renewal audit under Ministerial Decision 64 of 2025, cannot continue on the UAE network. The commercial contract may still be valid, but the ASP cannot perform e-invoicing services. The taxpayer then has two obligations running at once: onboard with a new ASP before the current one goes offline, and securing a copy of everything the old ASP holds.

Corporate events. Provider acquisitions, insolvencies, or strategic withdrawals from the UAE market force data extraction under time pressure. Insolvency is the hardest: administrators often prioritise creditor protection over data continuity, and FTA obligations remain on the taxpayer regardless of administrator decisions.

In every scenario, the same fact determines the outcome, whether the taxpayer holds an independent copy outside the ASP.

SpendConsole is accredited by the UAE Ministry of Finance as an Electronic Invoicing Service Provider under Ministerial Decision 64 of 2025 and is a certified PEPPOL Access Point through OpenPEPPOL. The platform validates invoices against PINT AE, transmits over the PEPPOL network, and reports Tax Data to the FTA in real time.

SpendConsole separates the validation runtime from the archival layer. Every Electronic Invoice processed through the platform is stored in formats the FTA can directly reproduce, held in a structure the customer owns and controls, and recoverable independently of the validation runtime. Transition events, contract changes, renewals, or migration to a new provider, do not touch the historical archive. The archive remains the customer’s record, available for FTA response regardless of what happens at the validation layer.

Retrieval operates under defined SLAs that match FTA request timelines. Validation confirmations, UUIDs, and PEPPOL transmission metadata are retained alongside the invoice itself, preserving the full audit chain through the Capital Assets Scheme adjustment period. Format migrations, hardware refreshes, and vendor changes across that horizon are inevitable, which raises disaster recovery and replication decisions that need to be solved at the same time.

Beyond e-invoicing compliance, SpendConsole’s payables orchestration platform integrates payment execution directly into the invoice-to-pay workflow, ensuring that the traceability chain extends from invoice capture through to settlement.

The five-year, ten-year, and fifteen-year obligations sit on the taxpayer under UAE law. SpendConsole keeps those obligations retrievable across the entire window, without dependency on any service contract renewal.

How long do UAE businesses need to keep e-invoicing records?

The baseline under the Tax Procedures Law is five years from the end of the relevant tax period. Real estate records under the same law require seven years. Capital Assets under Article 60 of the VAT Decree-Law carry a 10-year adjustment period for buildings and real estate and five years for other capital assets, with supporting records typically retained up to 15 years on real estate-linked transactions. Corporate Tax retention under Article 56 of Federal Decree-Law 47 of 2022 is seven years.

Does the ASP handle data retention for me?

No. Article 11 of Ministerial Decision 243 of 2025 places the storage obligation on the Person subject to Electronic Invoicing. The ASP validates, transmits, and reports Tax Data. The retention responsibility, and any penalty for failure to produce records, sits on the taxpayer. Taxpayers need a direct copy of the Electronic Invoice XML, UUID, and associated confirmation data, held independently of the ASP’s own archive.

What happens if my ASP loses accreditation?

An ASP that fails to renew its two-year accreditation under Ministerial Decision 64 of 2025 cannot continue to provide services on the UAE network. The taxpayer must onboard with a new ASP before the transition and secure access to all historical data held by the outgoing provider. The PEPPOL ID can be migrated through OpenPEPPOL’s participant migration process, but archival data needs to be exported separately.

Do records need to be stored inside the UAE?

The February 2026 Ministry of Finance guidelines clarify that “within the State” is an accessibility standard. Records can be held on servers inside or outside the UAE, provided they can be retrieved and reproduced by the FTA in a complete and readable form on request.

What are the penalties for missing e-invoicing records?

Under Cabinet Decision 106 of 2025, failure to implement the Electronic Invoicing System or appoint an ASP is AED 5,000 per month. Failure to issue or transmit an Electronic Invoice is AED 100 per invoice, capped at AED 5,000 per month. Failure to report a system malfunction is AED 1,000 per day. Tax Procedures Law penalties for failure to keep records are AED 10,000 for a first offence and AED 50,000 for repeats, with an additional AED 1,000-per-day fine for delayed document production.

Are FTA audits getting more frequent?

Yes. FTA inspection volume reached 93,000 in 2024, a 135% increase on the prior year. The first half of 2025 recorded 85,500 inspections, 110.7% higher than the same period in 2024, with AED 357.22 million collected in taxes and fines over those six months.

What sectors are most exposed to the 15-year retention horizon?

Real estate developers, construction contractors, asset managers with property holdings, government entities with mixed-use portfolios, and any business with capital assets above AED 5 million sit inside the VAT Capital Assets Scheme 10-year adjustment period. Mining, transport, utilities, and large industrial groups accumulate capital assets that push similar long-horizon retention requirements.

What is the difference between PEPPOL ID migration and archival migration?

PEPPOL ID migration transfers forward invoice routing to a new ASP. Archival migration transfers historical records. PEPPOL has a defined migration process for the first. The second is a separate export and ingestion exercise, and not all commercial service providers expose tooling for historical data migration.

How does this apply to Australia and New Zealand operations?

Australia’s ATO requires five years under Tax Administration rulings, with extensions for fringe benefits and capital gains. New Zealand requires seven years under the Tax Administration Act 1994. Both use PEPPOL for B2G e-invoicing, and the retention obligation sits on the taxpayer, not the Access Point. A group with operations in multiple jurisdictions should design archival to meet the longest obligation in scope, which is usually the UAE’s 15-year Capital Assets Scheme window.

Where can I learn more about SpendConsole’s UAE e-invoicing capabilities?

The UAE E-Invoicing solution page covers PINT AE validation, PEPPOL transmission, FTA reporting, and retention architecture. SpendConsole is listed as a pre-approved ASP by the Ministry of Finance.