Mon–Fri · US, EU & APAC hours
UAE FTA E-Invoicing Compliance

Microsoft Dynamics 365 Business Central Integration with UAE E-Invoicing

Connect Business Central to the UAE's Peppol-based e-invoicing mandate — PINT AE invoice generation, Access Service Provider connectivity, and inbound invoice automation, ready ahead of your Federal Tax Authority go-live date.

Microsoft Dynamics 365 Business Central Integration with UAE E-Invoicing

The UAE's E-Invoicing Mandate, In Plain Terms

The UAE is moving to mandatory business-to-business e-invoicing under a decentralized continuous transaction control and exchange (DCTCE) model, run by the Federal Tax Authority. Invoices move as structured PINT AE data through accredited Access Service Providers on the Peppol network — not as PDFs, and not submitted directly to the FTA by the business itself.

For a Business Central, Dynamics NAV, LS Central, or LS NAV environment, that means every sales and purchase invoice needs a compliant path in and out of your ERP: generating and transmitting PINT AE XML on the way out, and validating and posting supplier e-invoices on the way in — with status, rejections, and resubmissions visible the whole time.

Built For

Supported ERP Systems

BCMicrosoft Dynamics 365 Business Central
NAVMicrosoft Dynamics NAV
LSCLS Central
LSNLS NAV
Key Features

Everything UAE E-Invoicing Requires

PINT AE Invoice Generation

Generates outbound sales invoices and credit notes as PINT AE-compliant structured data straight from Business Central, ready for transmission by your Access Service Provider.

Peppol Access Point Connectivity

Connects Business Central to any FTA-accredited Access Service Provider over the Peppol network, so outbound invoices reach the buyer and the FTA correctly and inbound ones reach you.

Inbound Invoice Automation

Receives supplier e-invoices, matches them against purchase orders and receipts, and posts or flags them for review — accept, reject, or query, without re-keying.

Status & MLS Tracking

Tracks submission, acceptance, and rejection status for every invoice, with message-level acknowledgements surfaced back into Business Central so nothing silently fails.

Archival for FTA Audit Readiness

Keeps a tamper-evident record of every outbound and inbound e-invoice, matched to its transmission status, for the retention periods the FTA requires.

Peppol Architecture

The 5-Corner Model

UAE e-invoicing runs on Peppol's 5-corner model — every invoice moves seller-to-buyer through accredited Access Points, while a fifth corner reports the same transaction to the Federal Tax Authority in real time.

  • Invoice created and posted inside your ERP — Business Central, Dynamics NAV, LS Central, or LS NAV.
  • No manual re-entry — it's the same document the business already produces.
  • Sent to the seller's own accredited Access Point for validation.
C1 · SellerCreates invoice in ERPC2 · Seller ASPValidates & convertsC5 · FTA PointReceives tax dataAddress &Capability (SML/SMP)PeppolNetworkCentral DataPlatformC4 · BuyerReceives invoiceC3 · Buyer ASPReceives PINT AEUAE FederalTax Authority
Peppol Network

The secure B2B and B2G e-delivery backbone connecting every accredited Access Point.

Address & Capability Registries

SML/SMP lookup services that resolve which Access Point a business is registered with.

Central Data Platform

Collects, processes, and stores the tax data the FTA receives from Access Points.

PINT AE Specification

51 Mandatory Data Fields

Every UAE e-invoice carries 51 mandatory fields across 6 categories in PINT AE XML format. Business Central needs to populate all of them correctly for an invoice to clear.

51 mandatory fields6 categoriesFormat: PINT AE (XML)
1
Invoice Details9 fields (1–9)
  • 1Invoice number
  • 2Invoice date
  • 3Invoice type code
  • 4Invoice currency code
  • 5Invoice transaction type code
  • 6Payment due date
  • 7Business process type
  • 8Specification identifier
  • 9Payment means type code
2
Seller Details11 fields (10–20)
  • 1Seller name
  • 2Seller electronic address
  • 3Seller electronic identifier
  • 4Seller legal registration identifier
  • 5Seller legal reg. identifier type
  • 6Seller tax identifier
  • 7Seller tax scheme code
  • 8Seller address line 1
  • 9Seller city
  • 10Seller country subdivision
  • 11Seller country code
3
Buyer Details9 fields (21–29)
  • 1Buyer name
  • 2Buyer electronic address
  • 3Buyer electronic identifier
  • 4Buyer tax identifier
  • 5Buyer tax scheme code
  • 6Buyer address line 1
  • 7Buyer city
  • 8Buyer country subdivision
  • 9Buyer country code
4
Document Totals5 fields (30–34)
  • 1Sum of invoice line net amount
  • 2Invoice total amount without tax
  • 3Invoice total tax amount
  • 4Invoice total amount with tax
  • 5Amount due for payment
5
Tax Breakdown4 fields (35–38)
  • 1Tax category taxable amount
  • 2Tax category tax amount
  • 3Tax category code
  • 4Tax category rate
6
Invoice Line13 fields (39–51)
  • 1Invoice line identifier
  • 2Invoiced quantity
  • 3Unit of measure code
  • 4Invoice line net amount
  • 5Item net price
  • 6Item gross price
  • 7Item price base quantity
  • 8Invoiced item tax category code
  • 9Invoiced item tax rate
  • 10VAT line amount in AED
  • 11Invoice line amount in AED
  • 12Item name
  • 13Item description
All 51 fields are mandatory unless otherwise specified, reported in PINT AE XML format. Accurate, complete master data keeps invoices from being rejected.
Business Impact

How It Works

Assess & Choose an ASP

Confirm your mandate phase and appoint an FTA-accredited Access Service Provider before your deadline.

Connect Business Central

We wire up PINT AE generation and Peppol Access Point connectivity directly inside your ERP.

Transmit & Receive

Outbound invoices generate and transmit automatically; inbound supplier invoices validate against POs and post.

Monitor & Reconcile

Status, acceptances, and rejections stay visible in Business Central, with resubmission handled in place.

Application Flow

AR (Sending) Application Flow

How invoices travel from source ERPs through the e-invoice engine to the FTA.

  • Source ERPs: Business Central, Dynamics NAV, LS Central, LS NAV, or any other ERP the sales invoice originates in.
  • Input Invoice Data: Extracted as XLSX, CSV, JSON, or XML, at org / location / warehouse level, as a single invoice or in batch.
  • Input Integration: Delivered onward via REST API, FTP/S-FTP, or direct file upload — whichever the source ERP already supports.
  • e-Invoice Engine (C2): Transforms and validates: data validation, enrichment, buyer ID verification, and PINT AE conversion, with everything archived.
  • AS4 · PINT AE → FTA & C3: Transmitted to the Federal Tax Authority and the buyer's Access Point over AS4.
  • Response Returned: Acceptance, rejection, or query responses come back through the same engine and post to the source ERP automatically.
Invoice data to e-Invoice application & to FTA e-Invoice portalSource ERPsSAPOracleMS DynamicsCustom ERPLn-InforEpicorSysproRamcoSageMultiple ERPsInput invoice dataFormat: XLSX / CSVJSON / XMLCustom or ERP formatOrg / Location / WH dataBatch / bulk processingInput integrationREST-APIFTP / S-FTPFile uploade-Invoiceengine (C2)Transform& validateData validationEnrichmentVerify buyer IDArchivalAS4PINT AEFTA & C3Buyer ASPAS4PINT AEOutput dataFormat: XLSX / CSVJSON / XML / PDFCustom or ERP formatTo ERP / buyer via emailOutput integrationREST-APIFTP / S-FTPFile downloadAt C2: Data validation · enrichment · verify buyer PEPPOL ID · submit PINT AE XML · receive FTA response · archivalResponses from FTA returned to source ERP systems
Application Flow

AP (Receiving) Application Flow

How inbound invoices arrive from the FTA and route into the buyer's ERP.

  • FTA Access Point (C5): The Federal Tax Authority's corner of the network, where inbound purchase invoices first arrive.
  • C3 Access Point: A Peppol-certified access point receives the AS4/PINT AE document and hands it to the e-invoice app.
  • e-Invoice App: Validates, notifies, and generates invoice responses, with full archival and dashboards — available 24×7.
  • Output Invoice Data & Integration: Delivered as XLSX, CSV, JSON, XML, or PDF via webhook, API, FTP/S-FTP, or file download.
  • Buyer ERPs (C4): Business Central, Dynamics NAV, LS Central, LS NAV, or any other buyer ERP receives the cleared invoice, ready to match and post.
Invoice data from the invoice application to buyer ERP (C4)FTA AccessPoint (C5)Federal TaxAuthorityC3 AccessPointPEPPOL-certifiedaccess pointe-Invoice appe-Invoice portalTransform& routeValidationNotificationInvoice responseArchivalDashboardsAvailable 24 × 7Output invoicedataXLSX / CSVJSON / XML / PDFCustom or ERP formatOrg / Location / WHBatch / bulkOutputintegrationWebhook / APIFTP / S-FTPFile downloadBuyer ERPs(C4)SAPOracleMS DynamicsCustom ERPRamcoSysproSageMultiple ERPsLn-InforEpicorC3: Validation of purchase invoice inbound · invoice notification · webhook integrationInvoice response (accept / UQ / reject / paid) · archival · dashboardsPotential 80% time saving with proper setup
Federal Tax Authority Mandate

UAE E-Invoicing Rollout Timeline

A phased mandate under the decentralized continuous transaction control and exchange (DCTCE) model. Voluntary adoption opens 1 July 2026; B2C transactions are excluded.

Phase 1Revenue ≥ AED 50MASP appointed by 30 Oct 2026Go-live 1 Jan 2027
Phase 2Revenue < AED 50MASP appointed by 31 Mar 2027Go-live 1 Jul 2027
Phase 3Government entitiesASP appointed by 31 Mar 2027Go-live 1 Oct 2027
Cabinet Resolution No. 106 of 2025

D365 Zone
UAE e-invoicing fines.

Under Cabinet Resolution No. 106 of 2025, UAE businesses must issue e-invoices through an Accredited Service Provider (ASP). Missing the deadline, filing late, or failing to notify the FTA can trigger the penalties below — every month.

1AED 5,000per month

No ASP appointed, or system not implemented by deadline.

2AED 100per invoice

Late or missing invoice transmission (capped at AED 5,000/month).

3AED 1,000per day

Unreported system failure — FTA or ASP notification missed.

Voluntary adopters = zero fines

Go live before your deadline — full penalty protection. D365 Zone is ready to deploy now.

Under the Hood

Every Submission Tracked, Both Directions

Outbound invoices to the FTA and inbound invoices from suppliers both flow through the same monitored path, so status, rejections, and resubmissions are never a mystery.

  • Phase-Ready Compliance: Onboard onto an accredited Access Service Provider ahead of your mandated go-live date without re-platforming your ERP.
  • Fewer Manual Touches: PO-matched inbound invoices and auto-generated outbound XML cut manual entry and reconciliation work on both sides of the ledger.
  • Penalty Exposure Reduced: Automated transmission and status monitoring reduce the risk of missed deadlines and untransmitted invoices under Cabinet Decision No. 106 of 2025.
UAE e-invoicing outbound and inbound status dashboard
Before You Even Ask

UAE E-Invoicing Questions We Hear Most

Who does the UAE e-invoicing mandate apply to?
All B2B invoicing, in phases based on annual revenue, plus government entities. B2C transactions are excluded from the mandate.
What is PINT AE?
PINT AE is the UAE-localized structured invoice format based on the Peppol International (PINT) specification — the data format your ERP needs to produce for every outbound e-invoice.
Do I submit invoices to the FTA directly?
No — self-submission isn't permitted. Invoices route through an FTA-accredited Access Service Provider (ASP) over the Peppol network, which reports to the FTA on your behalf.
When do I need to comply?
It depends on your phase: businesses with revenue at or above AED 50M must appoint an ASP by 30 Oct 2026 for a 1 Jan 2027 go-live; smaller businesses and government entities follow in 2027. Voluntary adoption opens 1 July 2026.
What happens if we miss a deadline or fail to transmit an invoice?
Cabinet Decision No. 106 of 2025 sets penalties for a missed ASP appointment, for each untransmitted invoice (capped monthly), and for unreported system failures — all avoidable with automated transmission and monitoring.
Does this work for invoices we receive, not just ones we send?
Yes — inbound supplier e-invoices are validated against purchase orders and receipts and posted or flagged for review, so accounts payable is covered alongside accounts receivable.

Ready for UAE E-Invoicing?

Get PINT AE generation, Peppol Access Point connectivity, and inbound invoice automation working inside Business Central, Dynamics NAV, LS Central, or LS NAV before your mandated go-live date.

Get in Touch

Bring UAE E-Invoicing Into Your Dynamics System

Tell us which platform you're on — Business Central, Dynamics NAV, LS Central, or LS NAV — and which mandate phase applies to you, and we'll map out what compliant e-invoicing looks like for your setup.

+1 (707) 731-6403
sales@d365zone.com
📍Office 1406, Vision Tower, Business Bay, Dubai
Reply within one business day — a person, not a sequence