Microsoft Dynamics 365 Business Central + UAE E-Invoicing: A Live Integration

Business Central Meets the UAE Mandate

Microsoft Dynamics 365 Business Central is one of the most widely deployed mid-market ERPs in the UAE. It is a natural fit for the kind of business that lands squarely in Phase 1 or Phase 2 of the UAE e-invoicing mandate - multi-entity, multi-currency, with a finance team that needs FTA-compliant invoicing without ripping out their ledger.

The challenge is that Business Central does not produce PINT AE natively, and it does not connect to the Peppol network out of the box. That is the gap InvoiceNet closes. Our Dynamics 365 Business Central integration is live and production-ready today.

What Business Central Does Well

Before describing the integration, it is worth being clear about what Business Central already provides:

• Structured invoice records with customer master, items, tax groups, dimensions
• VAT configuration that maps to UAE rates (standard 5 percent, zero-rated, exempt)
• Multi-currency support with exchange rate management
• Credit notes, debit notes, and prepayment invoices as distinct document types
• An extensible API surface that exposes all of the above for external consumption

What Business Central does not do: emit PINT AE XML, sign it, route it through the Peppol network, or report to the FTA in real time. Those are the things InvoiceNet handles.

How the Integration Works

The InvoiceNet integration uses Business Central's standard REST API. There is no proprietary connector to install in your tenant - we connect through Microsoft's published API surface, which means:

• No code deployment into your Business Central environment
• No version lock - works across recent Business Central releases
• Updates to PINT AE specifications are handled on our side, not yours
• Microsoft's authentication model (Entra ID / OAuth) controls access

The Outbound (AR) Flow

1. A user posts a sales invoice in Business Central as they normally would.
2. InvoiceNet picks up the posted invoice through the Business Central API (either polled or webhook-triggered).
3. The invoice data is mapped to PINT AE XML, including TRN, Peppol participant ID, line items, VAT categories, and totals.
4. We validate the document against the FTA business rules and PINT AE cardinality.
5. We apply a XAdES digital signature with a trusted timestamp.
6. The document is routed through the Peppol network to the customer's ASP.
7. Invoice metadata is reported to the FTA in near real-time.
8. The signed XML and an audit record are written back to InvoiceNet's archive, and the document status is updated in Business Central.

The Inbound (AP) Flow

1. A supplier's ASP sends a PINT AE invoice to InvoiceNet via Peppol.
2. We verify the digital signature, check the certificate is current and not revoked, and validate the document against PINT AE rules.
3. The structured invoice is pushed into Business Central as a Purchase Invoice draft, with the supplier card matched and line items mapped.
4. Your AP team reviews, approves, and posts the invoice using their normal Business Central workflow.
5. The original signed XML is retained in the InvoiceNet archive for audit.

What the Integration Covers Out of the Box

• Sales invoices, sales credit memos, and sales prepayments
• Purchase invoices and purchase credit memos (inbound)
• Multi-company / intercompany scenarios within a single Business Central tenant
• Multi-currency invoices with AED-equivalent reporting
• Free zone customer handling, including designated zones
• Standard 5 percent VAT, zero-rated, exempt, and out-of-scope categories
• Dimensions and bookkeeping groups preserved through the integration

What a Typical Implementation Looks Like

For most Business Central customers, going live takes weeks rather than months. The typical sequence:

1. Week 1 - Discovery. Confirm Business Central version, tenant configuration, VAT setup, customer master state, free zone usage, multi-currency policy.
2. Week 2 - Connect. Set up the OAuth app registration, grant InvoiceNet read/write access to the required Business Central entities, run a first round-trip in sandbox.
3. Week 3 - Master data cleanup. Ensure customer TRNs, Peppol IDs, and tax categorisation are correct.
4. Week 4 - Pilot. Run real invoices end to end in sandbox, exchange with a friendly customer who is also on Peppol, verify FTA reporting.
5. Week 5 - Go live. Cut over production, monitor closely for two weeks.

What This Replaces

If you are currently producing PDF invoices from Business Central and emailing them, this integration replaces that. If you are already using a Business Central e-invoicing extension that is not UAE-aware, this replaces or sits alongside it. Either way, your Business Central users keep their existing workflow - the changes happen behind the API.

Why Now

Phase 1 of the UAE e-invoicing mandate becomes mandatory on 1 January 2027, and in-scope businesses must appoint an Accredited Service Provider via EmaraTax by 30 October 2026. Business Central customers that wait until Q3 2026 will compete for implementation capacity with thousands of other businesses. Starting in 2026 H1 with a known, working integration is the difference between a planned go-live and a rushed one.

Next Steps

InvoiceNet's Dynamics 365 Business Central integration is live and available today. Talk to our team for a free readiness assessment of your tenant, an end-to-end demo in sandbox, and a fixed-price implementation quote.