01 / VALIDATE
Check before you send.
Review invoice structure, required fields and supported PINT-AE rules. Correct field-level findings in the source data.
AZDAN UAE E-INVOICE
UAE E-invoicing.
Made Simple.
Create invoices in the system you already use. Connect your business to Peppol, validate documents against PINT-AE and follow tax-data reporting to the FTA.
THE CONNECTED EXCHANGE
Follow the invoice.
See the reporting route.
Five participants connect invoice exchange and tax-data reporting. Follow each result separately in AZDAN.
Invoice exchange: C1 → C2 → C3 → C4
C1Your businessSupplier · Existing ERPC2AZDANYour service providerC3Buyer’s providerReceiving service providerC4Your customerBuyer · Receiving system
C2 → C5
Supplier-side tax-data reporting
Supplier-side tax-data reporting
C3 → C5
Buyer-side reporting after successful validation
Buyer-side reporting after successful validation
Invoice exchange and tax reporting can run in parallel. C3 returns an exchange response to C2; C5 reporting responses are forwarded to the supplier and buyer through their providers. If C3 validation fails, it sends a negative status to C2 and C5 instead of a TDD.
See the Ministry of Finance five-corner model ↗ONE WORKSPACE. CLEAR VISIBILITY.
Built around the work
your finance team does.
Prepare documents, resolve exceptions and keep the exchange connected to the source invoice.
02 / TRACK
Every stage. Its own result.
Follow network delivery, receiver responses and FTA reporting separately. Know which stage needs attention.
03 / MANAGE
Several companies. One workspace.
Maintain company profiles and registered identities. Find exchanged documents and review transaction histories.
FITS YOUR EXISTING SYSTEMS
Keep your ERP.
Connect your invoicing.
Keep creating invoices in the software you know. Connect through supported APIs and document formats, directly or through middleware.
Discuss your integration ↗Direct API or middleware
Exchange JSON or UBL XML and bring results back into your systems through signed webhooks and API queries.
Console entry or XML upload
For manual or occasional work, prepare invoices, upload XML and import invoice lines using the CSV template.
The connection approach depends on the interfaces and permissions available in your source system.
FAQ
Your e-invoicing questions, answered.
Practical answers about connecting your systems, preparing invoices and following the exchange.
Book a demo
Do I need to change my ERP?
Keep your ERP, accounting or billing application. Connect using supported APIs, document formats or middleware, depending on the interfaces your system provides.
Can I use the console without an integration?
Yes. Prepare invoices with guided entry or upload UBL XML. CSV support imports invoice lines using the provided template.
Is a PDF a structured e-invoice?
A PDF is a readable presentation. Structured documents such as UBL XML can be processed by systems. A PDF alone does not confirm delivery or FTA acceptance.
What does PINT-AE validation check?
AZDAN checks supported invoice structure, required fields and PINT-AE business rules. Correct field-level findings in the source data before submission.
What is the five-corner model?
The supplier and buyer exchange invoices through their service providers. Tax-data reporting connects the service providers to the FTA alongside invoice exchange.
How do I plan an implementation?
Discuss your source system, legal entities, document types, volumes and inbound requirements with AZDAN to establish the appropriate connection approach.
Does validation confirm delivery?
Validation checks the document. Network delivery, receiver responses and FTA reporting each have separate outcomes.
What does Delivered mean?
Read the transport result alongside the receiver response. Arrival at a receiving access point does not establish payment, business approval or FTA acceptance.
Can I receive supplier invoices?
Yes, when your receiving participant is registered and active for the relevant network. Your ERP integration determines how received documents enter your systems.
How do I correct an invoice?
Follow your organization’s approved correction process. A credit note references the original invoice and has its own exchange record. Investigate the original transaction before resubmitting.
Do I create Tax Data Documents myself?
AZDAN generates the relevant Tax Data Document through its reporting workflow. Follow the reporting result and address any exceptions.
Can I retrieve documents and records?
Find exchanged documents, review transaction histories and retrieve available XML and reporting files. Use audit records for reconciliation and investigation.
Which formats can my integration use?
Send structured JSON for document generation, or compliant UBL XML through the supported API contract. Confirm field mapping and the current schemas before rollout.
How do statuses return to my ERP?
Use signed webhooks and API queries. Retain source and transaction references, handle repeated events safely and reconcile missed callbacks.
Can I manage several companies?
The platform supports company profiles, registered participants and company-based access within a tenant. Confirm the structure and allowances your organization needs.
How is pricing determined?
Discuss your legal entities, document volumes, user access, integration assistance and support requirements with AZDAN to establish the commercial scope.
Does the interactive demo send real invoices?
No. It uses fictional sample data. The demo checks basic fields only; it does not run PINT-AE validation or submit documents to Peppol or the FTA.
Where can I get help?
Use the Tenant Console and its knowledge base for task guidance. Book a demo to discuss your workflow, integration requirements and pricing with the AZDAN team.
Get Started
Your invoicing process. A connected next chapter.
Talk through your current systems, company structure and integration requirements with our team.
