Will my e-invoice arrive in the UAE?
Type your buyer's TIN (10 digits) or TRN (15 digits), choose what you're sending (PINT AE invoice, credit note or self-billing invoice), and see whether that document can be delivered over Peppol today. You can check your own number the same way.
Look up a company
Only the number you type is sent. We show the e-invoicing provider only: no names, no contact data. Name search asks the official register directly from your browser; we never see or keep the name.
Checking many numbers? Use the bulk check (up to 100 at once). · Which number does each country use on Peppol? See the ID schemes.
UAE: turn a TRN into a Peppol ID
In the UAE, the Peppol ID is 0235 followed by the 10-digit TIN, and the TIN is the first 10 digits of the 15-digit TRN. In a VAT group, each member uses its own TRN, not the group representative's. Source: UAE Electronic Invoicing Guidelines v1.1 (Ministry of Finance).
What the check tells you
The check asks the Peppol network the same questions your ASP's access point asks before it sends:
- Registered? Whether
0235:plus the TIN is registered as a receiver. In the UAE the participant identifier is always 0235 followed by the 10-digit TIN [1][3]. - Does the provider's record answer? Whether the record (SMP) that lists the buyer's capabilities can be read.
- Is your document accepted? PINT AE invoice, credit note and self-billing invoice are separate document types [3], and a registration lists each one the buyer accepts [4].
- Is the provider's certificate valid? Valid, expiring within 30 days, or expired.
- TRN or TIN? If you typed a TRN, we tell you which TIN Peppol uses.
You get a verdict, the exact Peppol ID to give your ASP and, if it can't go over Peppol, what the Ministry's Guidelines say instead. We show no names or contact details, and there is no reverse search.
Why an e-invoice doesn't arrive
- TRN instead of TIN. The TIN is the first 10 digits of the 15-digit TRN [1]. An address built from the full TRN doesn't exist on the network.
- The group's number instead of the member's. In a VAT group each member uses the first 10 digits of its own TRN, not the group representative's [1].
- Buyer not onboarded yet. Go-live is phased, so many buyers aren't registered yet; see the deadlines.
- Credit note or self-billing not registered. An access point must refuse a document type it doesn't serve for that receiver [5]. Self-billing also requires the buyer to be on the e-invoicing system [1].
- Expired certificate. The sending access point must verify the receiver's certificate it fetches from the SMP [5]. An expired certificate stops delivery until the provider renews it.
What to do next
- Collecting the buyer's participant identifier is your job as supplier; looking it up on the network is your ASP's [1]. Copy the Peppol ID from the result and give it to your ASP.
- Buyer hasn't implemented e-invoicing yet and has no participant identifier? You still issue the electronic Tax
Invoice with the fixed buyer address
0235:9900000098, plus a regular Tax Invoice, for example a PDF [1]. - Export to a buyer without a Peppol ID: use
0235:9900000099. Deemed supply: always0235:9900000097[1]. Looking up these addresses shows a placeholder, not a company.
Is it your own company?
Type your own TIN and choose "my own company". You onboard with one ASP for all your e-invoicing [1]. If something isn't green, ask your ASP:
- Is
0235:plus my TIN (from my own TRN, not my VAT group's) registered? - Are the PINT AE invoice and credit note registered, and self-billing if a customer bills on my behalf?
- When does your access point certificate expire, and is the renewal planned?
A system failure that stops you issuing or receiving must be reported to the FTA within 2 business days [2].
More: UAE Peppol / TIN lookup · Scope and exemptions · How UAE e-invoicing works
Checked on 7 October 2026. "Peppol" is used here as a descriptive word only; E-Invoice Map is not affiliated with OpenPeppol, the Ministry of Finance or the FTA. Not tax or legal advice.
Sources
- UAE Electronic Invoicing Guidelines v1.1, 1 June 2026 (MoF; sections 2, 5.2, 10.2.2, 10.3 and the scenario table) (checked on )
- Ministerial Decision No. 243 of 2025 on the Electronic Invoicing System (MoF; Article 12, system failure) (checked on )
- OpenPeppol: Peppol code lists v9.7 (scheme 0235; AE PINT document types) (checked on )
- OpenPeppol: Service Metadata Publishing (SMP) specification 1.4.0 (checked on )
- OpenPeppol: AS4 profile (use of Peppol PKI; receiver not serviced) (checked on )
Last updated: