UAE E-Invoicing Integration

Custom or in-house system: UAE E-Invoicing Integration Guide

Custom and in-house systems offer the most flexibility and the widest integration surface. UAE PINT AE compliance hinges on mapping your data model to UBL 2.1 and connecting to the access point of a MoF Accredited service provider. This guide covers the options and a typical rollout.

How Custom or in-house system connects to PINT AE

Custom and in-house ERP systems present the broadest integration surface, as they lack standardised API contracts, requiring the MoF Accredited ASP to develop a bespoke connector against the system's available data endpoints. The primary technical risk is ensuring complete PINT AE field mapping — particularly mandatory fields such as the buyer's VAT registration number, tax category codes, and line-level allowance structures — which are rarely captured in legacy invoice schemas.

Integration approaches

API-first integration

Expose invoice data through an API and integrate with the ASP's endpoints for transformation, validation, signing, and AS4 transmission. Best for real-time submission and acknowledgements.

File-based batch (SFTP)

Generate a structured export (CSV/JSON/XML) on a schedule for the ASP to transform into PINT AE. Pragmatic where adding APIs to a legacy system is costly.

Direct UBL generation

Generate PINT AE UBL 2.1 in-house and use the ASP purely as the Peppol access point, highest control, but it puts the schema-conformance burden on your team.

Typical deployment timeline

  1. 1

    Confirm the chosen provider appears on the official MoF accredited list.

  2. 2

    Inventory the data your system holds against PINT AE mandatory fields (gap analysis).

  3. 3

    Choose API-first, file-based, or in-house UBL generation.

  4. 4

    Map every mandatory business term, especially buyer TRN, tax categories, and line-level allowances/charges.

  5. 5

    Validate generated documents against PINT AE rules in a sandbox.

  6. 6

    Confirm monitoring and reconciliation, then go live.

Go-live checklist

  • Gap analysis complete: every mandatory PINT AE field has a source.
  • Seller and buyer TRNs captured and validated.
  • Tax category and allowance/charge structures mapped.
  • ASP connectivity (API or SFTP) and credentials confirmed.
  • Robust error handling and retries for failed transmissions.

MoF Accredited providers that support Custom or in-house system

Listed as stated by the provider, in alphabetical order. All providers are on the official UAE Ministry of Finance accredited list.

Browse all MoF Accredited providers

Frequently asked questions

Can a custom system comply with UAE e-invoicing?

Yes. A custom system can comply via an API or file integration with a MoF Accredited ASP, or by generating PINT AE UBL 2.1 in-house and using the ASP as the access point.

What is the biggest risk with a bespoke integration?

Incomplete field mapping. Legacy schemas often miss mandatory PINT AE fields such as the buyer's TRN, tax category codes, and line-level allowance structures, a gap analysis up front avoids rework.

What does the UAE require on the wire?

PINT AE (UBL 2.1) exchanged over the Peppol AS4 network through an accredited provider.

How do I confirm my deadline?

Run the free readiness assessment to confirm your phase, dates, and a neutral provider shortlist.

Find the right provider for Custom or in-house system

Answer a few questions to confirm your compliance phase and deadline, and see a neutral shortlist of MoF Accredited providers based on your own inputs.

Other integration guides

Not sure which ASP is right for you?

Find Provider