UAE e-invoicing is becoming an operational priority for finance teams, business owners and ERP managers. For companies in Dubai and Sharjah, preparation involves more than choosing a new invoice layout. Your accounting system must provide accurate structured data, connect with an accredited provider, and support the processes your team uses to send, receive and correct invoices.
If your business uses Odoo, Zoho Books or another ERP, start by checking which implementation phase applies to your legal entity. Then review your invoice data and integration options against the UAE requirements. This guide explains the deadlines, the required format and a practical preparation plan.
UAE e-invoicing deadlines for 2026 and 2027
The government has set separate dates for appointing an Accredited Service Provider, or ASP, and implementing the system.
- Business with annual revenue of AED 50 million or more: appoint an ASP by 30 October 2026; mandatory implementation 1 January 2027.
- Business with annual revenue below AED 50 million: appoint an ASP by 31 March 2027; mandatory implementation 1 July 2027.
- Government entity: appoint an ASP by 31 March 2027; mandatory implementation 1 October 2027.
The first row includes a business with revenue of exactly AED 50 million. Ministerial Decision No. 66 of 2026 amended that cohort's provider appointment deadline. The other implementation dates are set out in Ministerial Decision No. 244 of 2025. Amended first-phase deadline · Rollout decision.
Revenue for this purpose is based on gross income during the most recent accounting period, using the relevant financial statements or other documentation accepted by the Authority. It is not a test of your net profit or monthly sales.
Voluntary implementation has been available since 1 July 2026. This is distinct from the Ministry-selected pilot group, which requires written agreement to participate. Voluntary users must still meet the technical requirements. The specific e-invoicing penalties do not apply to voluntary participation; existing tax obligations continue to apply. Rollout decision · Penalty decision, Article 2.
What is the UAE e-invoicing format?
An e-invoice contains structured information that software can process automatically. A PDF attached to an email, a scanned invoice or a Word document does not satisfy that definition. A business may still need a readable invoice copy alongside its structured document, depending on the recipient and transaction. FTA explanation.
The UAE uses PINT-AE, its specification within the Peppol framework. The published technical specifications include Billing, Self-Billing and Tax Data Documents. At the time of this review, each is listed at version 1.0.4. OpenPeppol UAE specifications.
Invoice exchange uses structured XML. Your ERP and ASP can agree how your source data reaches the provider; the provider can validate and convert that data into the UAE exchange format. Businesses should confirm the exact interface, supported document types and validation release with their selected ASP. Ministry of Finance e-invoicing framework.
This distinction matters when assessing software. A VAT invoice template or general Peppol feature does not, by itself, demonstrate that a particular installation supports UAE exchange and reporting requirements.
How the five-corner system works
The five participants are the supplier, the supplier's ASP, the buyer's ASP, the buyer and the Federal Tax Authority. The providers handle validation, document exchange and the tax-data reporting flows. Confirmation messages return information about the exchange and reporting results. Ministry framework · Tax Data Document specification.
For your finance team, that means an invoice needs a visible operational history. Staff should be able to see what was submitted, whether it passed validation, what happened during delivery and whether reporting succeeded. Payment collection and approval of a vendor bill remain separate business processes.
Which Dubai and Sharjah businesses are affected?
The framework addresses business transactions, including dealings between businesses and government entities, subject to the stated exclusions and rollout phases. VAT registration alone does not determine scope. Businesses should therefore assess their activities and transactions before deciding that they are outside the system. Ministerial Decision No. 243 of 2025 · Ministry mandatory-field guidance.
Business-to-consumer transactions are currently excluded until a further ministerial decision determines otherwise. A company with both consumer and business customers should classify those flows separately. The current rollout decision also excludes a person engaged exclusively in B2C transactions until the Minister determines otherwise. Rollout decision, Article 5.
Dubai and Sharjah follow this federal framework. For local ERP projects, the practical questions differ by operation:
- Trading and distribution: Can your system produce consistent customer details, product units, discounts and tax classifications across branches?
- Manufacturing: Can sales, inventory and finance teams keep item data and invoice corrections aligned?
- Construction and project services: Have advances, milestone invoices and retention arrangements been reviewed and tested?
- Professional services: Do recurring invoices use the correct billing periods, contract references and customer entities?
- E-commerce businesses: Can the business distinguish B2B orders from consumer orders before generating the applicable documents?
These are preparation examples, not additional emirate-specific rules.
What invoice data should your ERP prepare?
The Ministry has published field checklists for electronic Tax Invoices and commercial Electronic Invoices. Use them together with the current technical model and validation rules, because requirements vary by document and scenario. Official field checklist.
Your readiness review should cover these data families:
- Document identification: Invoice reference, date, document type, currency and transaction classification.
- Supplier and buyer: Registered names, addresses, routing identifiers and applicable registration information.
- Line details: Product or service information, quantities, units, prices and tax treatment.
- Financial totals: Taxable amounts, tax totals, discounts, charges and amount payable.
- Corrections and references: Credit-note reasons, earlier invoices and relevant order or contract references.
The current PINT-AE model also requires a unique invoice identifier, or UUID. Businesses should agree with their ASP how that identifier is generated, stored and linked to the accounting record. PINT-AE UUID requirement.
Cleaning these records before integration makes it easier to find and resolve errors during testing. A customer address that looks acceptable on a printed invoice may still be incomplete for a structured exchange.
Preparing Odoo for UAE e-invoicing
For an Odoo project, review the version, edition, installed localization, custom modules and proposed ASP connection. Request a demonstration using your actual transaction scenarios before agreeing that the system is ready.
A useful acceptance review should include:
- A sales invoice generated from the normal business workflow.
- A credit note linked to an earlier invoice.
- An incoming vendor invoice handled by accounts payable.
- A failed validation returned to an accountable user for correction.
- Exchange and reporting confirmations linked to the source record.
- Retrieval of the original document and supporting evidence.
Zavior's Odoo integration services and Odoo ERP implementation services provide a starting point for discussing data mapping, workflow changes and a scoped readiness project. The selected ASP's supported interface and your installed software determine the integration design.
Preparing Zoho Books and Zoho workflows
Zoho Software Trading LLC appears on the Ministry's accredited-provider register with accreditation number 121988. Zoho's UAE Books documentation describes workflows for sending invoices and credit notes and receiving supplier documents through the network. Official ASP register · Zoho Books UAE documentation.
Existing Zoho Books users should check their organization details, available setup options, permissions and appointment through EmaraTax. They should also test how invoices produced from CRM deals or other connected applications reach the accounting workflow. Zoho CRM or Zoho One usage alone does not demonstrate that e-invoicing is enabled in the finance system.
Zavior's Zoho solutions services can help frame the workflow and data questions for that assessment. Software plans, transaction charges and feature availability should be checked with the provider when the project is scoped.
Common problems to resolve before implementation
The following issues deserve a place in your test plan:
- Customer records spread across CRM, ERP and spreadsheets with different names or identifiers.
- Tax treatment inferred from a free-text product description.
- Discounts and charges calculated differently in the accounting system and outbound document.
- Credit notes that lose the relationship to their original invoice.
- Submission retries that create duplicate documents.
- Incoming invoices approved automatically without a business review.
- A dashboard that shows submission success without checking later exchange and reporting results.
Assign an owner to each issue. Finance should approve the tax and accounting treatment, the implementation team should document the system behavior, and the ASP should demonstrate its interface and response handling.
What penalties can apply?
Cabinet Decision No. 106 of 2025 provides specific penalties for failures involving implementation or provider appointment, invoice and credit-note transmission, and required notifications. It includes AED 5,000 per month or part of a month for delayed implementation or appointment. Missing invoice transmission can attract AED 100 per invoice, capped at AED 5,000 per calendar month; a separate equivalent category applies to credit notes. Notification failures can attract AED 1,000 per day or part of a day. Official penalty decision.
Apply these amounts to the relevant violation and mandatory timetable. The voluntary-period exemption concerns these e-invoicing penalties; it should not be presented as a general exemption from tax compliance.
Your incident process also needs clear owners. The rules require issuers and recipients to notify the FTA of a system failure within two business days. Relevant changes to registered data must be communicated to the ASP within five business days of receiving the FTA's confirmation. Notification obligations.
A practical preparation plan
Confirm your phase. Record the relevant entity, revenue evidence, transaction scope and applicable deadlines.
Select and contract with an ASP. Use the Ministry's current register and compare the interface, supported scenarios, support arrangements, retention services and commercial terms.
Prepare your data. Review company and customer information, product units, tax classifications, currencies and correction references.
Test the complete workflow. Include outgoing invoices, incoming documents, credit notes, rejections, reporting results and record retrieval. Keep evidence of the results and obtain finance sign-off.
Prepare the team for launch. Agree who corrects rejected documents, monitors outstanding submissions and manages incidents. Appointment is one milestone; operational readiness requires working processes.
Discuss your UAE e-invoicing readiness with Zavior
If your business is preparing for the 2027 rollout, start with a review of your current finance system and invoice processes. Share your ERP version, relevant revenue band, approximate invoice volume and proposed ASP so the discussion can focus on your actual requirements.
Book a UAE e-invoicing readiness consultation.
Information checked on 8 October 2026. Recheck the Ministry of Finance portal for subsequent decisions and specification changes before making implementation commitments.
