Key Takeaways
4 insights · 12 min readYour customer not being onboarded does not remove your obligation to issue the e-invoice through your ASP.
A PDF, Word file or scan is not an e-invoice. E-invoices are structured XML exchanged through the system.
For a buyer not yet on the system, the guidelines use the predefined endpoint 0235:9900000098 plus a regular invoice copy.
Once mandatory, a missed e-invoice can cost AED 100 each, up to AED 5,000 a month. Voluntary adopters face no e-invoicing penalties.
No. Your customer not having an ASP does not remove your obligation to issue the e-invoice through your ASP, and a PDF does not count as an e-invoice. Where a buyer has not yet implemented e-invoicing, the guidelines require the predefined endpoint 0235:9900000098 on the e-invoice, plus a regular tax invoice such as a PDF.
In this guide
PDF instead?Why a PDF isn't an e-invoiceYour obligation, their readinessThe defined routeMissing TINAfter their deadlinePenaltiesVoluntary early adoptersGet readyA client recently asked us: “We are fully ready for e-invoicing, but one of our UAE B2B customers has not registered with an ASP or joined the Peppol network. Since they cannot receive the e-invoice, can we just issue a PDF until they register?” It is one of the most practical questions of the whole roll-out, because every supplier will have customers who onboard later than they do. The short answer is no, and the reason is not just the penalty. The Ministry of Finance’s UAE Electronic Invoicing Guidelines separate your obligation from your customer’s readiness and give you a specific route for buyers who are not yet on the system. This guide walks through that route, the gap it leaves, and how to avoid failed invoices caused by missing customer data. To get your customer data ready, start with our UAE e-invoicing service.
Can you send a PDF while your customer joins Peppol?
No, not on its own. The deciding rule is not the penalty but the obligation itself: under the MoF guidelines, a customer’s e-invoicing onboarding status or tax registration status does not affect your e-invoicing obligations for a business transaction. Your duty to issue the e-invoice through your ASP stays, whether or not the customer is ready to receive it.
No. Your customer not having onboarded doesn’t remove your own e-invoicing obligation. You still issue and transmit the e-invoice through your ASP in the way the rules require, and a PDF on its own wouldn’t count as an e-invoice. For a customer who hasn’t implemented e-invoicing yet, there is a defined route: the e-invoice goes to a predefined endpoint and you send them a regular invoice copy as well. Once your mandatory date applies, failing to issue the e-invoice can attract penalties.
Notice the order of that answer. Clients accept a rule they understand far more readily than a penalty they are warned about, and the rule tells them what to do, not just what to avoid.
Why doesn’t a PDF count as an e-invoice?
Because an e-invoice is defined by how it is issued and exchanged, not by being electronic. The guidelines define an electronic invoice as one issued, transmitted and received through the Electronic Invoicing System in a structured electronic format that allows automatic processing. E-invoices are XML, exchanged between ASPs over Peppol, with tax data reported to the FTA.
| Document | Structured data? | Through your ASP and Peppol? | Reported to the FTA by your ASP? | An e-invoice? |
|---|---|---|---|---|
| PDF emailed to the customer | No | No | No | No |
| Scan or Word file | No | No | No | No |
| PINT-AE XML sent by your ASP | Yes | Yes | Yes | Yes |
There is one more trap. The PINT-AE specification allows supporting documents to be attached to an e-invoice, but it states that attaching a copy of the invoice in an image format such as PDF is not in compliance. The PDF copy for a customer who is not onboarded travels separately, not embedded as the invoice.
Does your obligation depend on whether your customer is onboarded?
No. The guidelines put the compliance obligation on the Person who must issue e-invoices, and state that the customer’s onboarding status does not change it. In the five-corner model, you (corner 1) send data to your ASP (corner 2), which reports tax data to the FTA (corner 5) in parallel with delivering to the buyer’s ASP (corner 3). If corner 3 does not exist yet, corners 1, 2 and 5 still do.
✗ Wait for the customer
Keep issuing PDFs until each customer onboards. Your e-invoice count stays at zero for those customers, and once your mandatory date passes each missed e-invoice is a potential penalty.
✓ Issue anyway, by the defined route
E-invoice through your ASP using the route for non-onboarded buyers, send the regular copy, and switch to normal delivery the day the customer appears on Peppol.
How do you e-invoice a customer who isn’t on Peppol yet?
The guidelines give a specific route for buyers who have not yet implemented e-invoicing, for example because they have not joined voluntarily and their own mandatory date has not arrived. In that case, where the buyer has no participant identifier:
- Issue the e-invoice through your ASP — As normal, with all mandatory fields.
- Use the predefined endpoint — Include
0235:9900000098as the buyer’s electronic address, as the guidelines require. - Send a regular tax invoice too — For example a PDF, so the customer can process the invoice and support input VAT recovery.
- Switch when they onboard — Once the customer has a participant identifier, address future e-invoices to
0235:plus their TIN.
The PINT-AE specification lists three predefined endpoints. For these, the document is reported to the FTA and need not be exchanged with a buyer’s ASP:
| Scenario | Predefined endpoint | Use it when |
|---|---|---|
| Deemed supply | 0235:9900000097 | The invoice is for a deemed supply |
| Buyer not subject to UAE e-invoicing | 0235:9900000098 | The buyer is outside the regime, or (per MoF guidelines) has not yet implemented and has no participant ID |
| Export, buyer not on Peppol | 0235:9900000099 | The export buyer has no Peppol address |
⚠️ Don’t borrow the wrong endpoint
Each predefined endpoint has a defined use. Using the export or deemed-supply endpoint for a domestic customer who simply hasn’t onboarded misreports the transaction.
What if you don’t have the customer’s TIN?
Get it; it almost certainly exists. For any business registered with the FTA for any tax, the TIN is the first 10 digits of its TRN. Most UAE companies hold a TRN for VAT or corporate tax, so a customer can have a TIN long before it appoints an ASP. The question to ask is not whether the TIN exists but whether that TIN is registered as a Peppol participant.
| What you know | What it means | What to do |
|---|---|---|
| TIN known, customer on Peppol | Normal delivery | Address the e-invoice to 0235:TIN |
| TIN known, not on Peppol, before its deadline | Not yet implemented | Use 0235:9900000098 and send a regular copy |
| TIN not known | Customer master incomplete | Request TRN or TIN, legal name, licence number and authority |
| TIN known, not on Peppol, after its deadline | Grey area | See the next section; document and escalate |
Missing customer data is the most common reason e-invoices fail, and it is not only the TIN. PINT-AE also expects the buyer’s legal registration number and, for trade licences, the issuing authority. Collect all of it in one request. Our client’s first live implementation failed on exactly these fields, which is why customer master clean-up is a core step in our e-invoicing implementation.
Customer list full of gaps?
Send us your customer export on WhatsApp. We’ll show how many records are missing TINs or licence details, free.
What if the customer’s own deadline has passed and they still haven’t onboarded?
Here the published material is less clear, and we would rather say so than guess. The MoF guidelines describe the predefined endpoint for buyers who have not yet implemented and do not yet have a mandatory requirement. The PINT-AE specification describes the same endpoint for buyers not subject to UAE e-invoicing. Neither text expressly covers a buyer who is in scope, past its own deadline, and still not onboarded.
What does not change is your obligation. Our practical approach for that case:
- Request the details in writing — TIN, legal name, licence number and authority, and the name of the customer’s ASP.
- Verify through your ASP — Ask your ASP to check the Peppol directory for the customer’s TIN.
- Keep evidence — Dated requests and the customer’s replies, in case you need to show you acted.
- Escalate — Raise unresolved cases with your ASP, and with the FTA if needed, for the route to follow.
- Never invent an identifier — No dummy TINs and no borrowed endpoints. A fabricated identifier misreports the transaction.
What are the penalties for not issuing an e-invoice?
Penalties come last in our answer, but they are real. The Ministry of Finance announcement of Cabinet Decision No. 106 of 2025 sets these fines for persons required to apply e-invoicing:
| Violation | Fine |
|---|---|
| Failing to implement e-invoicing or appoint an ASP within the set timeframe | AED 5,000 per month |
| E-invoice not issued or sent within the specified timeframe | AED 100 per invoice, up to AED 5,000 per month |
| E-credit note not issued or sent within the specified timeframe | AED 100 per credit note, up to AED 5,000 per month |
| Not notifying the FTA of a system malfunction in time | AED 1,000 per day of delay |
| Not notifying your ASP of changes to data registered with the FTA in time | AED 1,000 per day of delay |
Worked example: a mandatorily in-scope supplier keeps emailing PDFs to four customers who are not onboarded, totalling 30 invoices in a month. At AED 100 each that is AED 3,000 for the month. At 70 invoices it would be AED 7,000, capped at AED 5,000. The cap limits the monthly fine; it does not make the practice compliant.
If you start voluntarily before your deadline, do penalties apply?
No. A common follow-up comes from businesses that want to start early. For example, a company with AED 8 million revenue, whose mandatory date is 1 July 2027, plans to go live voluntarily in November 2026 and worries about missing a few invoices.
The MoF has stated that persons applying e-invoicing voluntarily are exempt from the penalty decision, and no fines apply until they become mandatorily subject to the system. The guidelines say the same: administrative penalties apply only from the date a person is required to implement e-invoicing mandatorily. Voluntary adopters must still follow the technical requirements, so treat the months before July 2027 as a rehearsal: fix the process now, because from 1 July 2027 every missed invoice counts.
| Period for the AED 8M company | E-invoicing status | Penalty exposure |
|---|---|---|
| November 2026 to 30 June 2027 | Voluntary | None under Cabinet Decision 106 of 2025 |
| From 1 July 2027 | Mandatory | Fines as in the table above |
How should you prepare your customer base before go-live?
- Export your active B2B customers — Everyone you expect to invoice after go-live.
- Collect identity data — TRN or TIN, legal name, licence number, issuing authority.
- Check Peppol status — Run eligibility checks through your ASP or software, and repeat them monthly during the roll-out.
- Set up both routes — Normal delivery to 0235:TIN, and the predefined-endpoint route with a regular copy for buyers not yet onboarded.
- Tell customers your go-live date — Customers who know you’re live tend to onboard faster.
Fastlane builds this into every e-invoicing implementation: a free diagnosis, then a fixed fee per company from AED 299 + VAT on Wafeq, AED 499 + VAT on Zoho Books and AED 799 + VAT on Xero or Tally. That covers the customer data clean-up, Peppol eligibility checks, test invoices to onboarded and non-onboarded buyers, and a 30-minute training session. Our accounting team can keep the customer master current after go-live.
Common mistakes with non-onboarded customers
• Emailing PDFs only — Not an e-invoice; your obligation remains.
• Attaching the PDF as the invoice — PINT-AE says an image copy of the invoice is not compliant.
• Inventing a TIN or borrowing an endpoint — Misreports the transaction.
• Never re-checking Peppol status — Customers onboard during the roll-out; switch them to normal delivery.