How the FTA e-invoicing test submission process works for UAE businesses

What is the FTA e-invoicing test submission process?

The FTA e-invoicing test submission process is a structured validation stage where UAE businesses send sample invoices through the Peppol-based e-invoicing network before mandatory go-live. It confirms that your systems produce correctly formatted PINT AE documents, that your accredited service provider (ASP) transmits them properly, and that the Federal Tax Authority (FTA) can receive and validate them without errors.

Testing is a critical checkpoint in the broader FTA compliance UAE journey. Businesses that skip or rush this stage risk rejected invoices, workflow disruptions, and potential penalties once enforcement begins. The pilot phase is scheduled for Q2 2026, giving early adopters a window to resolve issues well before the January 1, 2027 Phase 1 deadline.

Why test submissions matter before go-live

The UAE adopted a Peppol 5-corner Decentralized Continuous Transaction Control and Exchange (DCTCE) model. Under this model, every invoice passes through an ASP access point, reaches the FTA for validation, and then continues to the buyer's access point. A single formatting error can break this chain.

Test submissions let you catch problems in a safe environment. No penalties apply during testing. No real tax data is at risk. But the validation rules mirror production, so any error you fix now is one fewer surprise after go-live.

Common issues uncovered during testing

• Schema errors: Missing mandatory fields in the Universal Business Language (UBL) 2.1 structure that PINT AE requires.
• Tax Registration Number (TRN) mismatches: The sender or receiver TRN does not match FTA records.
• Incorrect tax calculations: VAT amounts that do not reconcile with the 5% standard rate or applicable exemptions.
• Character encoding failures: Arabic text fields that break during transmission.
• Duplicate invoice identifiers: Reuse of invoice numbers that the network rejects as duplicates.

Step-by-step: completing the test submission process

While the Ministry of Finance (MoF) and FTA will publish final technical specifications during the pilot, the process follows a predictable sequence based on the DCTCE architecture and Peppol standards. Below is a practical walkthrough.

Step 1: Appoint your ASP

Before you can send any test invoice, you need an appointed ASP linked to your TRN on the EmaraTax portal. If you have not done this yet, follow the FTA ASP appointment process on EmaraTax. Phase 1 businesses (annual revenue AED 50M or above) must complete ASP appointment by October 30, 2026.

Step 2: Configure your ERP or accounting system

Your accounting software needs to produce invoices in the PINT AE format. This is a UAE-specific profile built on the Peppol International (PINT) standard. Popular platforms like Zoho Books, QuickBooks, Xero, SAP, Oracle NetSuite, Microsoft Dynamics 365, and Odoo will need either native updates or middleware connectors to output compliant documents.

Key configuration items include:

• Mapping your chart of accounts to the required tax category codes.
• Setting your Peppol participant ID (linked to your TRN).
• Enabling UBL 2.1 XML output with the PINT AE customization ID.
• Configuring your ASP's access point endpoint.

Step 3: Run internal validation

Before sending anything to the FTA, validate your XML documents locally. Peppol publishes validation artefacts (schematron rules) on docs.peppol.eu. Run every test invoice through these rules. Fix any errors before proceeding.

Step 4: Submit test invoices through your ASP

Your ASP transmits the test invoices to the FTA's corner of the 5-corner model. The FTA validates each document against its own rules, which include UAE-specific checks beyond the base Peppol schematron. Expect validation responses that flag:

• Structural compliance (correct XML schema).
• Business rule compliance (valid TRN, correct tax rates, mandatory fields).
• Network-level compliance (valid Peppol participant IDs, correct document type).

Step 5: Review validation responses and fix errors

Each test submission returns a response indicating acceptance or rejection. Rejected invoices include error codes and descriptions. Work with your ASP and your ERP vendor to resolve each issue. Re-submit until you receive consistent acceptance responses.

Step 6: Confirm go-live readiness

Once your test invoices pass validation consistently, you are ready for production. Review the FTA e-invoicing readiness checklist to confirm that every operational, technical, and legal requirement is met before your mandatory go-live date.

Test submission timeline and deadlines

The table below maps the key dates for each taxpayer group. Use it to plan your testing window.

Milestone	Phase 1 (AED 50M+ revenue)	SMEs (under AED 50M)	Government entities
Pilot testing opens	Q2 2026	Q2 2026	Q2 2026
ASP appointment deadline	October 30, 2026	TBA	TBA
Recommended test completion	November - December 2026	April - June 2027	July - September 2027
Mandatory go-live	January 1, 2027	July 1, 2027	October 1, 2027

Starting your test submissions early gives you time to iterate. Businesses that wait until the last month before go-live risk running out of time to fix complex integration issues.

Penalties for non-compliance after go-live

Cabinet Decision 106 of 2025 sets penalties ranging from AED 2,500 to AED 50,000 per violation. Violations can include failing to issue e-invoices, issuing non-compliant e-invoices, or not appointing an ASP by the deadline. Successful test submissions do not guarantee compliance, but they dramatically reduce the risk of post-go-live violations.

Checklist: test submission readiness

Use this checklist to track your progress before entering the test phase.

1. ASP appointed and confirmed on EmaraTax. See how to appoint an ASP on EmaraTax for instructions.
2. ERP or accounting software configured for PINT AE output.
3. Peppol participant ID registered and linked to your TRN.
4. Internal validation passed using Peppol schematron rules.
5. At least 3 document types tested: standard invoice, credit note, debit note.
6. Arabic and English bilingual fields verified.
7. Validation response from FTA reviewed and all errors resolved.
8. Staff trained on error handling and resubmission procedures.
9. Go-live readiness confirmed against the full FTA e-invoicing readiness guide.

How the test environment differs from production

Data isolation

Test submissions use sandbox endpoints. No test invoice reaches a real buyer or appears in FTA tax records. Your ASP maintains separate test and production environments, so there is no risk of mixing test data with live transactions.

Validation strictness

The test environment applies the same validation rules as production. This is intentional. The goal is to surface every possible error before real invoices flow through the network. Some ASPs may offer a "pre-validation" layer that checks documents before sending them to the FTA sandbox, giving you faster feedback loops.

Connecting testing to the full onboarding journey

Test submissions are one stage in a larger FTA e-invoicing onboarding process. Before testing, you complete ASP appointment and system configuration. After testing, you move to production go-live and ongoing compliance monitoring. Treating these stages as a connected sequence, rather than isolated tasks, keeps your project on track and within the FTA compliance UAE framework.

EInvoice Direct includes an accredited service provider at no extra charge and handles the technical integration with your existing accounting software. To see how it fits your business, get UAE e-invoicing pricing today.