The short version. You sign with an accredited provider, start onboarding yourself from EmaraTax, and your provider gives you a Peppol identifier (0235 followed by the first 10 digits of your tax number). Then you send the invoice data to your provider, which turns it into an XML file, generates a unique identifier for it, delivers it to your customer's provider and reports it to the FTA. A tax invoice has 51 mandatory fields. And the legal responsibility stays with you, even though the provider does the sending.
Before the invoice: onboarding
- Sign the contract first. The guidelines require you to finalise the contract and commercial obligations with the provider before onboarding (section 13.2). One provider handles both sending and receiving; you cannot split them (section 6.1). And the contract must be directly between you and the accredited provider, according to the Ministry's FAQ.
- Update your details in EmaraTax. Trade licence, address and contact details, before you start (section 15.3).
- Onboard from EmaraTax, not from the provider. The account admin signs in to EmaraTax, clicks the E-INVOICING tile in the left menu, picks the provider from the list and clicks "Proceed to ASP", which takes you to the provider's portal to finish (section 13.2). If you have no tax registration at all, you generate a Tax Identification Number (TIN) through EmaraTax.
- Get your Peppol identifier. It is your address on the network: 0235 followed by your 10-digit TIN, which is the first 10 digits of your tax registration number (Guidelines, sections 2 and 3). The provider shares it once onboarding is complete (section 15.4). In a tax group, each member onboards on its own with an identifier from its own number, not the group's.
A detail to ask your provider. The guidelines say the TIN is "the first 10 digits of the TRN that you have been issued", while the mandatory-fields document (28 October 2026) says "the first 10 digits of a Corporate Tax TRN". If you hold two numbers, confirm with the provider which one you were registered under.
The invoice itself
- Know the document type. There are six categories (Guidelines, section 10.1), each with a code in the PINT AE specification:
Code 480 is only for supplies wholly outside the scope of VAT, not for exempt or zero-rated ones (section 18.3.1). There is no "provisional invoice" category: every provisional invoice must be an e-invoice (section 10.1). Details in the six categories and self-billing.Document Code Tax invoice 380 Tax credit note 381 Self-billed tax invoice (issued by the buyer) 389 Self-billed credit note 261 Commercial invoice (out of scope of VAT) 480 Commercial credit note 81 - Fill in the mandatory fields. A tax invoice has 51 mandatory fields and a commercial invoice 49 (mandatory-fields document, version 1.1, 28 October 2026). On top of those, some fields become mandatory depending on the case; the guidelines list 8 scenarios with specific requirements (section 10.4). You can check your invoice file in the checker inside your browser, without it being uploaded anywhere.
- Add your customer's identifier. Collecting it is your responsibility, not the provider's (section 5.2, row 5). The specification sets three fixed addresses; an invoice sent to one of them is only reported to the FTA and not delivered to another provider:
- 0235:9900000098 for a customer that has not implemented e-invoicing yet and has no identifier. You also give it a regular tax invoice (PDF) (Guidelines, section 10.2.2).
- 0235:9900000099 for an export to a customer not on the Peppol network.
- 0235:9900000097 for a deemed supply.
- Send the data to your provider. The way you agreed: from your accounting system, a file, or manual entry in its portal. It validates the data and converts it to an XML file with no QR code (sections 5.1 and 5.3), and generates a unique identifier (UUID) that is added to your sequential invoice number, not a replacement for it (section 3). The invoice must go out on time: a VAT registrant on the VAT Law timeline (14 days from the date of supply), a non-registrant within 14 business days (the issuing window).
After sending
- Wait for the two confirmations. Your customer's provider validates the invoice and sends your provider a status message (MLS), the FTA confirms it received the data, and your provider passes both on to you (section 5.1). If validation fails at the customer's provider, a negative status message goes to your provider and to the FTA, and you need to correct and resend. See rejected invoices. The guidelines ask you to make sure confirmations reach you for every invoice (section 15.3).
- Keep records. E-invoices, e-credit notes and their "associated data": 5 years after the tax period for a taxable person, 7 years for real estate records, and 4 more years in a dispute or audit (Guidelines, section 5.4). If you let your provider store them, the legal obligation stays with you (section 16.2.2). Details in storage rules.
Test before your date
The guidelines list six tests before go-live: data transfer to the provider, issue to the customer, exchange confirmation, receiving supplier invoices, reporting to the FTA, and reporting confirmation (section 13.3). Agree now with your provider how errors will be resolved (section 13.4). Testing before your mandatory date carries no penalties (section 11), so a mistake before your date costs nothing.
Read next
The five-corner modelYour invoice's journey to the FTA
1 January 2027What happens on go-live day
The checkerCheck an XML file in your browser
Sources: UAE Electronic Invoicing Guidelines, version 2.0 (26 October 2026), sections 2, 3, 5.1, 5.2, 5.3, 5.4, 6.1, 10.1, 10.2.2, 10.4, 11, 13.2, 13.3, 13.4, 15.3, 15.4, 16.2.2 and 18.3.1 (mof.gov.ae); UAE Electronic Invoice Mandatory Fields, version 1.1 (28 October 2026); PINT AE Billing 1.0.4 on docs.peppol.eu, sections 1.5.1, 1.5.3 and 1.6.1; Ministerial Decision 243 of 2025, Article 6, as amended by Decision 197 of 2026; the FAQ on mof.gov.ae. All read on 19 November 2026.
This content is general information, not tax or legal advice. The official text prevails.