UAE e-invoicing readiness that turns the data you already hold into valid PINT AE.

The mandate replaces the PDF with structured data.

Under the UAE Electronic Invoicing System, your system issues invoices and credit notes in the PINT AE format. They travel between Accredited Service Providers in a five-corner model: you, your ASP, your buyer's ASP, your buyer, and the Federal Tax Authority, which receives the tax data. The Ministry of Finance is explicit that PDFs, Word documents, images, scanned copies and emails are not e-invoices.

Ministerial Decision No. 243 of 2025 sets the rules. They reach any person doing business in the UAE, VAT-registered or not, unless the person or the transaction is excluded. Ministerial Decision No. 244 of 2025 keeps transactions with consumers outside the system until the Minister decides otherwise.

The decision asks four things of the business that issues the invoice.

• Issue and transmit each e-invoice or e-credit note within 14 days of the date of the transaction, or within the VAT Law's timeline if you are registered for VAT (Article 6).
• Issue an e-credit note when a transaction is cancelled, its price is reduced, consideration is returned, or an administrative or numerical error is corrected (Article 6).
• Store e-invoices, e-credit notes and their data within the State for the period the Tax Procedures Law sets (Article 11). The Ministry's reading of that is set out below.
• Tell the FTA about a system failure within 2 business days (Article 12), and tell your ASP about changes to your registered data within 5 business days (Article 5).

PINT AE is published by OpenPeppol, and the current version is 1.0.4, released on 2 June 2026 by the UAE Peppol Authority. It defines two transactions, Invoice and Credit Note, each with a semantic model, syntax binding, code lists, business rules and Schematron validation files. The Ministry prescribes the data fields themselves under Article 7.

The largest businesses go live on 1 January 2027.

Ministerial Decision No. 244 of 2025 sets the phases. Ministerial Decision No. 66 of 2026 moved the ASP deadline for the largest businesses from 31 July to 30 October 2026 and left their go-live date unchanged. The UAE e-invoicing timeline tracks every date.

Revenue means gross income in your most recent accounting period, per your financial statements (Ministerial Decision No. 244 of 2025, Article 1). The ASP deadline has moved once already, so confirm your dates with your tax adviser.

These projects stall inside your own system.

Your ASP carries the invoice across the network. Producing it correctly falls to your system, and these are the cases that hold it up.

• Fields your ERP never captured, so the data cannot be emitted at all.
• Customer and supplier TRNs that are blank, wrong or formatted four ways, and TINs never derived from them. Your participant identifier is 0235 followed by your 10-digit TIN, the first 10 digits of your TRN. In a tax group, each member uses its own.
• Buyers who are not on the network yet. Until they are, the Ministry's guidelines have you send the e-invoice to the predefined endpoint 0235:9900000098 and issue a readable tax invoice as well.
• Advance payments. The tax invoice is issued when the advance is received, and the final invoice then covers only the balance.
• Provisional invoices, which have no category of their own. Each must be an e-invoice, adjusted later by an e-credit note or a further e-invoice.
• Special treatments. The domestic reverse charge covers electronic devices, precious metals and stones, oil, gas, hydrocarbons and metal scrap. Invoices between members of a VAT group are in scope, with a 24-month grace period from 1 January 2027, so your system has to tell them apart.

A year of ordinary invoices holds cases like these, which is why we test on yours instead of a sample file.

The engagement delivers six things you can check.

• A field-by-field gap report.

  Run on a month of your real invoices, and yours to keep whatever you decide.

• Clean master data.

  Supplier and customer TRNs, TINs, addresses and tax codes corrected before an ASP can reject them.

• Your invoice model mapped to PINT AE.

  Credit notes and awkward cases included, validated against the published Schematron rules.

• The connection to your ASP.

  Proven in its sandbox first for every message type, from invoice and credit note to rejection and acknowledgement.

• A rejection queue and a correction path.

  A bounced invoice is corrected and resent before it becomes an unpaid one, and a monthly reconciliation checks the flow against your VAT records.

• An evidence pack.

  The test set, the results and a record of what was checked.

The work starts from a month of your invoices.

1. Extract and measure.

   We export a month of your real invoices and test them against the required fields. The gap report is yours even if you stop there.

2. Clean the master data.

   TRNs, TINs, addresses, tax codes and customer categories. Expect it to be the longest step, since 20 of the Ministry's 51 mandatory fields for a tax invoice come from your company, customer and address records.

3. Map and emit.

   Into PINT AE, validated against the schema and the business rules, with the edge cases from your own history.

4. Connect to your ASP.

   Sandbox first, every message type.

5. Run both ways.

   Live invoices produced in parallel and compared until the differences are zero.

6. Cut over and watch.

   Rejection-rate alerts run from the first day.

The proposal dates each step once the scope is written, and the pace follows your data.

Your ASP and SolaryxDev do different work.

The two are often sold as one service, so the table splits them.

The FTA must be able to reach your archive.

Article 11 of Ministerial Decision No. 243 of 2025 says e-invoices, e-credit notes and their associated data are stored within the State for the period the Tax Procedures Law sets. For a taxable person that is 5 years after the tax period they relate to, and longer during an audit or a dispute with the FTA.

The Ministry's guidelines read "within the State" as a test of access. The records must keep their integrity and reach the FTA complete and readable when it asks, irrespective of where the servers are. Your ASP may store them for you under contract, and the legal obligation stays with you.

Our hosting defaults to Germany, with the UAE on request or your own servers as options. For a system that issues e-invoices, the proposal names where the archive lives and how it is produced on request, and your tax adviser confirms the arrangement.

Today we can show the method and our books.

Mandatory go-live starts on 1 January 2027, and we have not yet taken a client live on PINT AE. Our own books run on ERPNext v16. A gap report on your own invoices shows the method at work. Core ERPNext has no built-in PINT AE support as of September 2026, and this work closes that gap for ERPNext users.

If your ERP or your ASP's connector already produces valid PINT AE, the gap report shows it and the engagement stops there.