Once the scope and deadline questions are settled, the next layer of e-invoicing complexity is technical: what goes in the invoice data fields, how dates and currencies must be formatted, what happens when a buyer isn't on the Peppol network, and how to handle disclosed agents, mixed tax rates, and data storage requirements.
This article addresses the most common technical questions from our E-Invoicing Service client engagements, using real scenarios from practice.
Invoice Date Format — ISO 8601 Is Mandatory
"Our legacy ERP outputs DD/MM/YYYY — can the ASP convert it?"
A client's team prepares invoice dates in DD/MM/YYYY format because that is how their legacy system works. They assume their ASP can reformat it downstream.
Invoice dates in the PINT-AE XML format must follow ISO 8601: YYYY-MM-DD. This is not a preference — it is a schema requirement. Submitting dates in any other format will cause validation failures at the schema level.
31/12/2026DD/MM/YYYY — legacy format
2026-12-31YYYY-MM-DD — ISO 8601
The practical implication: ERP teams must configure the date output format at source — before the invoice reaches the ASP. Relying on the ASP to silently correct date formats introduces risk. If your ERP outputs DD/MM/YYYY today, this must be in your pre-go-live remediation list.
🛠 Fastlane handles ERP field mapping including date format validation as part of E-Invoicing onboarding.
View E-Invoicing ServiceForeign Currency Invoices — Three Additional Fields
"We invoice in USD — do we just ignore the AED exchange rate fields?"
A business invoices in USD but reports taxes in the UAE. The ERP team says they will keep the invoice currency in USD and ignore exchange rate fields because "the tax is simple."
When the invoice currency differs from AED, the PINT-AE Data Dictionary requires additional fields to be populated:
| Field | Required When | Purpose |
|---|---|---|
InvoiceCurrencyCode | Always | The currency in which the invoice is denominated (e.g. USD, GBP) |
TaxCurrencyCode | Non-AED invoices | Must be AED — the currency in which tax is reported to FTA |
TaxCurrencyExchangeRate | Non-AED invoices | The exchange rate applied to convert invoice currency to AED for tax calculation |
Omitting these fields when invoicing in a non-AED currency will cause the invoice to fail validation. The FTA needs the exchange rate to verify the AED-equivalent VAT amount — it cannot calculate this itself from invoice data alone.
Buyer Without a Peppol Participant ID
Exporting to a French customer with no Peppol ID
A UAE exporter provides services to a customer in France. The French customer does not have a Peppol Participant Identifier. The client asks: "Can we still issue the electronic invoice, and what do we put for the buyer endpoint?"
Yes — the Supplier can still issue the e-invoice. The Peppol network includes a fallback mechanism for buyers who are not registered participants:
➜ The Supplier's ASP can transmit the invoice as a structured PINT-AE XML file alongside a PDF rendering of the invoice.
➜ The Supplier should coordinate with their ASP to confirm the exact fallback procedure supported — this varies slightly by ASP implementation.
➜ The buyer endpoint field should be handled according to the ASP's guidance for non-Peppol recipients — do not leave it blank or populate it with placeholder data without confirming with your ASP first.
This scenario is expected to be common for UAE exporters dealing with non-GCC international buyers during the early phases of the mandate.
Mixed Tax Rates on a Single Invoice
"Do we need separate invoices for standard-rated, zero-rated, and out-of-scope items?"
A retail business wants to issue a single electronic invoice covering standard-rated goods, zero-rated items, and an out-of-scope component. The owner asks whether separate invoices are mandatory for each tax treatment.
Separate invoices are not required. A single PINT-AE e-invoice can include line items with different tax categories. The requirement is that each line item carries the correct tax category code:
| Tax Treatment | Tax Category Code | Tax Rate |
|---|---|---|
| Standard-rated supply | S | 5% |
| Zero-rated supply (exports) | Z | 0% |
| Exempt supply | E | 0% |
| Domestic reverse charge | AE | 0% (buyer self-accounts) |
| Out-of-scope | O | Not applicable |
The invoice totals section must correctly aggregate the tax amounts per category. This is where ERP mapping errors typically surface — systems that apply a single default tax code to all lines will fail schema validation on mixed-rate invoices.
Disclosed Agent Billing — Critical Additional Field
"We'll just use the seller's TRN everywhere to keep things simple"
A client using disclosed agent billing says they will simply use the seller's TRN throughout the invoice and ignore agent-specific fields.
In disclosed agent scenarios, the invoice must clearly identify both the actual supplier and the agent's role. The critical additional field is the agent's own VAT registration number — this must be correctly populated and must correspond to a valid registered entity.
Using only the seller's TRN without identifying the agent creates a validation risk: the FTA's system may flag the invoice for inconsistency between the declared supplier identity and the Peppol sender credentials. In disclosed agent arrangements, the invoice data must reflect the actual commercial structure, not a simplified version of it.
Data Storage — Does It Have to Be Inside the UAE?
"Our servers are outside UAE — does that make us automatically non-compliant?"
A client stores all invoice data on cloud servers outside the UAE and believes Article 11 of the e-invoicing framework requires UAE-based storage.
Invoice data may be stored outside the UAE — the framework does not impose an absolute UAE-only storage requirement. However, certain conditions must still be met regardless of storage location:
➜ FTA access: The FTA must be able to access, retrieve, and audit the invoice data on demand.
➜ Data retrievability: Invoices must be retrievable in full, in the correct format, within a reasonable timeframe.
➜ Retention period: Records must be retained for the required period under UAE VAT law.
➜ Security and integrity: Data must be stored securely and in a tamper-proof manner.
Businesses using cloud storage with overseas servers should document their FTA access pathway and confirm with their ASP that retrieval mechanisms are in place.
Imported Services (Overseas Reverse Charge) — No UAE E-Invoice Required
"Do we need to generate a UAE e-invoice for services we import under reverse charge?"
No. Imported services subject to reverse charge from an overseas supplier do not require a UAE e-invoice to be generated in the EIS. There is no UAE-based supplier to issue the invoice — the overseas supplier raises their own invoice under their home country's rules.
The UAE business receiving the service self-accounts for VAT on the import under reverse charge rules, but this does not trigger an EIS e-invoice obligation. The distinction is important: domestic reverse charge between two UAE VAT-registered parties does require an e-invoice; imported services reverse charge does not.
Common Technical Errors to Avoid
| Common Error | Correct Approach |
|---|---|
Date formatted as 31/12/2026 | Must be 2026-12-31 (ISO 8601) |
| Foreign currency invoice with no exchange rate field | Populate TaxCurrencyCode (AED) and TaxCurrencyExchangeRate |
| Single tax code applied to all lines on a mixed-rate invoice | Each line item must carry correct tax category code (S / Z / E / AE / O) |
| Leaving buyer endpoint blank for non-Peppol buyers | Use ASP fallback procedure — do not submit blank or placeholder data |
| Using only seller TRN in disclosed agent billing | Include agent's VAT registration separately in designated field |
| Assuming overseas server = non-compliant storage | Storage location flexible — FTA access and retrieval conditions must be met |
| Treating imported services reverse charge as requiring UAE e-invoice | No UAE EIS invoice required for imported reverse charge services |
- Date format: YYYY-MM-DD only — configure ERP output at source
- Non-AED invoices: populate invoice currency, tax currency (AED), and exchange rate fields
- Mixed tax rates: use correct PINT-AE tax category code per line item — do not default all lines to one code
- Buyer without Peppol ID: use ASP fallback mechanism — XML + PDF rendering
- Disclosed agents: identify both actual supplier and agent with correct VAT registrations
- Data storage: location flexible but FTA access, retrievability and retention conditions must be met
- Domestic reverse charge: in scope, invoice required. Imported services reverse charge: no UAE e-invoice needed
Reviewed by the Fastlane Compliance Team, Dubai
Reviewed against UAE Electronic Invoicing Guidelines v1.0 (February 2026), PINT-AE Data Dictionary, and UAE E-Invoicing Public Consultation documentation. Fastlane Management Consultancy — FTA registered, TRN: 104218042400003.
March 2026 · Full E-Invoicing Service →Frequently Asked Questions
📖 Back to Part 1: Who Must Comply? Scope, Tax Groups & Exclusions →
Read Part 1