UAE E-Invoicing

Yes, report scheduling to stakeholders is an important feature and can be implemented.

Yes, Azentio ASP locates buyer's PEPPOL ID and sends invoice in required XML format.

One API call per invoice from the client. Background API call details will be shared soon.

Currently no clarity from FTA; expected around mid-October.

We are waiting for FTA clarification.

Yes, we will support division-level workflows for E-Invoicing.

Yes, value-based rejection is an important suggestion for buyer rejection dashboard.

Two emails per transaction: one XML invoice from ASP and one formatted invoice from ERP.

Yes, centralized portal support with ticket tracking via JIRA dashboard will be provided.

We are waiting for FTA clarification.

XML acknowledgements from FTA and invoice copies will be stored securely in multi-tenant storage.

Yes, our solution supports all versions of Orion for E-Invoicing

Yes, we will provide functionality to attach multiple documents along with the invoice.

Yes, storage timelines can be extended on request.

Yes, the updates will be included in 11J version.

No, QR code and digital signature are not currently mandated by FTA.

Yes, standard invoice templates notified by FTA will be incorporated.

Integration acknowledgments and success/failure notifications will be received at all stages (ASP/FTA).

Yes, manual invoice sending option will be available on transaction screen to avoid delivery issues.

Yes, FTA standard invoice print format will be available.

Buyers must have PEPPOL ID as mandated for B2B/B2G transactions under UAE E-Invoicing law.

Cancellation/revocation is possible before final Approval. Before Approval of invoice we can cancel / revoke invoice after Approval it will get integrate to ASP. In the later case, we need to raise credit Note for cancellation.

Invoice XML will contain a UUID which uniquely identifies the invoice for buyer confirmation.

Yes, validation errors appear as hyperlinks listing detailed error messages.

Yes, three webinars are planned- one in each month; dates to be announced soon.

Not mandated by FTA currently, but can be provided if requested similar to KSA.

Yes, invoices can be issued in any currency, but must be converted to AED before submission to FTA.

If buyer is VAT-registered, PEPPOL ID is mandatory and environment will be ready as per UAE E-Invoicing law.

Yes, Incase these line items attract VAT, these transactions will fall under E-Invoicing rules.

No, one invoice can only have one supplier VAT ID; multiple suppliers require separate invoices.

Yes, we can develop a reconciliation report that matches the delivery or movement of goods against the E-Invoices created. This will help ensure accuracy and completeness of transactions between physical goods movement and invoicing data. To provide this, we may require relevant data integration or APIs from your logistics or warehouse systems.

The seller initially issues an E-Invoice for the full 100 units based on the sales order. When the buyer returns the 10 rejected units, it is generally the seller's responsibility to raise a sales return, which is done by issuing a credit note for the returned quantity. The buyer may also raise a purchase return in their system for their internal records, but the credit note from the seller is the official document that adjusts the invoiced amount. This process ensures proper reconciliation between both parties and accurate accounting for the returned goods.

The invoice date is considered the valid date for all processing purposes, rather than the FTA approval date.

Orion will require client's UAT environment for Testing.

Yes,
1. Standalone PC with Internet Access to connect to the cloud API for sandbox and Live for running client comply service.
2. Standard HW: i3 (Server with 2 Core) or higher, 16GB RAM, 500 GB HDD, Win 2016/ Win 10 or above.
3. Drive space to store based files like XML, PDF and QR etc.
4. Open JDK 11 deployment on the application server on premise.

Yes. Orion's E-Invoicing solution is in the process of getting integrated with PEPPOL-certified infrastructure and fully aligns with FTA guidelines, including:
• UAE VAT and TRN validation
• Invoice format compliance (XML Format)
• Secure digital transmission
• Integration with FTA's validation environment

Invoices are validated against:
• PEPPOL BIS 3.0 schema (standard XML)
• UAE-specific FTA rules (TRN structure, tax categories)
• FTA's mock validation environment (sandbox)
Only after passing these validations are invoices allowed into the production environment.

• All transmissions are encrypted using secure HTTPS
• Systems follow ISO 27001-grade data security standards
• Full audit trails and access logs are maintained
• No invoice content is altered during exchange

Invoice is stored in multi-tenant storage.

Yes. Orion continuously tracks regulatory updates and maintains system compliance. Any changes in FTA rules or PEPPOL specifications are automatically updated, requiring no effort from the client side.

Yes. The system:
• Maintains a complete audit trail
• Stores validated copies of all E-Invoices
• Logs all transactions with timestamps
• Supports easy retrieval for audits or FTA inquiries

Invoices that fail validation against FTA or PEPPOL rules are automatically rejected, with detailed error messages provided for correction. Orion's interface allows you to correct and resubmit easily.

You can export:
• Delivery receipts
• Validation logs
• Timestamped records
• FTA acknowledgment messages
These can be presented as evidence of compliance.

If an invoice is rejected (e.g., due to invalid TRN or structure), Orion's platform provides a detailed error log. You can correct and resubmit the invoice directly. The platform ensures traceability and retry capability.

Yes. PEPPOL-compliant invoices are recognized and legally valid under UAE VAT law, equivalent to traditional paper invoices. They meet all tax and archiving requirements.

Orion includes duplicate detection logic using unique invoice identifiers and timestamps to prevent accidental re-submission, ensuring compliance with FTA audit controls.

Yes. Digital signature capability is available and can be enabled based on client needs. While not mandatory in all cases, it provides extra security and can be activated for specific use cases.

The UAE VAT law requires E-Invoices to be stored for at least 5 years. Orion supports compliant long-term archiving, retrieval, and storage options based on UAE regulations.

Orion ensures that each client is properly registered in the PEPPOL Directory with a unique Participant ID. The system manages the lifecycle of these IDs, including updates and deactivation if needed.

If either the FTA platform or PEPPOL network is temporarily unavailable, the Orion system will queue invoices and retry submission automatically once services are restored. No data is lost during the delay, and all activity is logged.

Yes, our e invoicing module is version agnostic. We are providing solution for all versions (10x, 11j, Cloud)

As per FTA we need to store data for 5 years and invoice copies will be stored securely in multi-tenant storage.

All E-Invoices must be issued in structured UBL XML format, in accordance with the PEPPOL BIS Billing 3.0 standard. PDF or paper invoices will not be considered valid for tax purposes.

Invoices are sent through the FTA's validation platform (via the Access Point in the Peppol network). The FTA performs checks on format, TRN, VAT applicability, and mandatory fields before approving the invoice.

Yes. Businesses must store E-Invoices in digital format for a minimum of 5 years, in compliance with UAE tax laws. Orion provides secure E-Invoice archiving with easy retrieval features.

Yes. All tax documents including credit notes and debit notes must follow the same E-Invoicing guidelines and be submitted in XML format via the FTA platform.

An Access Point is a PEPPOL-certified gateway that facilitates the transmission of E-Invoices between the supplier and the FTA. Orion partners with PEPPOL-certified APs to ensure secure and compliant communication.

A valid Tax Registration Number (TRN) issued by the UAE Federal Tax Authority (FTA) is mandatory. Client must ensure business is VAT-registered and your TRN is active.

Yes. Businesses must initiate E-Invoicing enrollment through the EmaraTax Portal. This process involves verifying your TRN and registering for E-Invoicing services.

An ASP is an FTA-approved solution provider (like Azentio) that connects your invoicing system (ERP) to the FTA via the PEPPOL network.
To proceed, Client needs to authorize their ASP Provider within the EmaraTax Portal, allowing them to transmit E-Invoices on your behalf

The E-Invoicing process involves two key stages:
• Testing Phase (Sandbox):
Client will first test their E-Invoice generation and transmission in the FTA's sandbox environment to ensure compliance and stability.
• Production Phase (Go-Live):
After successful testing, client can move to the live production environment to begin real-time invoice submission to the FTA.
ASP (Azentio) will assist with both phases and ensure a smooth transition.

Yes. Orion ERP system must be able to:
• Generate invoices in the FTA-compliant XML format
• Digitally sign invoices
• Integrate with the ASP or Access Point for real-time submission
Orion's team will assist in integrating and testing your system for E-Invoicing readiness.