# Connecting a custom ERP to UAE e-invoicing without rebuilding it

> Custom ERP e invoicing integration UAE: connect any in-house system to the Peppol network, meet 2027 deadlines, and avoid penalties.

Source: https://einvoicedirect.ae/accounting-software-uae/custom-erp-e-invoicing-integration-uae  
Last updated: 2026-06-05  
Publisher: EInvoice Direct (Massive FZCO), UAE e-invoicing software.

## What is custom ERP e-invoicing integration in the UAE?

Custom ERP e invoicing integration UAE refers to the work of connecting an in-house or heavily modified Enterprise Resource Planning (ERP) system to the UAE Peppol e-invoicing network through an Accredited Service Provider (ASP). The integration converts each tax invoice into PINT AE format and exchanges it on the 5-corner Decentralized Continuous Transaction Control and Exchange (DCTCE) model run by the Ministry of Finance (MoF).

Many UAE businesses run ERP systems built in-house, forked from open source, or extended so heavily that they no longer match any off-the-shelf product. These systems still need to issue compliant electronic invoices from January 1, 2027. This guide explains how to connect them without rewriting the ERP, what data the network expects, and how to plan the project against the official deadlines. For an overview of the wider stack, see our [Accounting Software and ERP Integrations UAE](https://einvoicedirect.ae/accounting-software-uae) hub.

## Why custom ERPs need a different integration plan

Packaged products like Zoho Books, QuickBooks, Xero, Tally, Sage, SAP, Oracle NetSuite, Microsoft Dynamics 365, and Odoo will receive vendor connectors. A custom ERP has no vendor to deliver that connector. The finance and IT teams own the mapping, the testing, and the ongoing compliance work.

The good news: the UAE model is built on Peppol, an open international standard. Any ERP that can produce a structured invoice file or expose an Application Programming Interface (API) can be wired in. The integration sits between the ERP and the ASP, not inside the ERP core.

### What counts as a custom ERP here

- Systems built from scratch on frameworks like Laravel, Django, .NET, or Node.js.
- Heavily forked versions of Odoo, ERPNext, or Dolibarr where vendor updates no longer apply.
- Legacy desktop systems with a SQL Server or Oracle backend and a local invoicing module.
- Industry-specific systems for logistics, contracting, healthcare, or trading that include invoicing.

### What the UAE mandate actually requires

The legal basis is Federal Decree-Law 16 of 2024 and 17 of 2024, with Ministerial Decisions 243 and 244 of 2025 setting out the technical rules. Penalties under Cabinet Decision 106 of 2025 range from AED 2,500 to AED 50,000 per violation. Every Business to Business (B2B) and Business to Government (B2G) tax invoice from in-scope taxpayers must flow through an accredited ASP in PINT AE format.

## UAE e-invoicing timeline for custom ERP projects

Plan the integration backwards from the mandatory dates. ASP appointment for large taxpayers must be done by October 30, 2026, which means contract, scoping, and technical work should start well before that.

| Milestone | Date | Who is affected |
| --- | --- | --- |
| Pilot phase | Q2 2026 | Volunteer taxpayers and ASPs |
| ASP appointment deadline | October 30, 2026 | Businesses with revenue AED 50M and above |
| Phase 1 mandatory go-live | January 1, 2027 | Businesses with revenue AED 50M and above |
| Small and medium enterprise go-live | July 1, 2027 | Businesses under AED 50M revenue |
| Government entities go-live | October 1, 2027 | Federal and local government bodies |

### A realistic 6 month plan

- Month 1: data audit of the ERP invoice schema against PINT AE fields.
- Month 2: pick an accredited ASP and sign the appointment contract.
- Month 3: build the export or API integration in a sandbox.
- Month 4: end-to-end tests with sample buyers and the ASP test endpoint.
- Month 5: user acceptance testing with finance and tax teams.
- Month 6: cutover, monitoring, and exception handling.

## How the 5-corner DCTCE model works for a custom ERP

The UAE follows the Peppol 5-corner model. Corner 1 is the seller's ERP. Corner 2 is the seller's ASP. Corner 3 is the buyer's ASP. Corner 4 is the buyer's ERP or finance system. Corner 5 is the Federal Tax Authority (FTA), which receives a near real-time tax data report.

Your custom ERP only needs to talk to Corner 2, the accredited ASP. The ASP handles validation, signing, network routing, archiving, and reporting to Corner 5. That separation is what makes integration manageable: the ERP team never touches Peppol Access Point code or government endpoints directly.

### Data the ERP must pass to the ASP

- Seller and buyer Tax Registration Number (TRN), legal name, and address.
- Invoice number, issue date, supply date, currency.
- Line items with quantity, unit price, VAT rate, VAT amount.
- Totals: net, VAT, gross, rounding.
- Payment terms, references to contracts or purchase orders.
- Free zone status and Qualifying Free Zone Person (QFZP) flag where relevant.

## Three integration patterns for custom ERPs

### Pattern 1: file export to the ASP

The ERP generates a Universal Business Language (UBL) XML file or a structured CSV per invoice and drops it into a shared folder, an SFTP server, or an object storage bucket. The ASP picks it up, converts to PINT AE if needed, validates, and sends. This is the lowest-effort option and works well for legacy ERPs that cannot expose modern APIs.

### Pattern 2: direct API call from the ERP

The ERP calls the ASP's REST API when an invoice is approved. The response carries the network status, the buyer acknowledgment, and a unique invoice reference. This pattern fits ERPs with active development teams and gives the best user experience because finance staff see the status inside the same screen they used to issue the invoice.

### Pattern 3: middleware bridge

A small integration service sits between the ERP database and the ASP. It reads new invoices from the ERP database or a message queue, transforms them, and calls the ASP. Use this when the ERP cannot be modified at all, for example a vendor-locked legacy system. The bridge is owned by your team or by the integration partner.

| Pattern | Best for | Build effort | User experience |
| --- | --- | --- | --- |
| File export | Legacy or low-change ERPs | Low | Basic |
| Direct API | Actively developed ERPs | Medium | Best |
| Middleware bridge | Locked or unsupported ERPs | Medium to high | Good |

## Field mapping: where most projects get stuck

The mapping spreadsheet is the heart of the project. Each invoice field in the ERP needs a target field in PINT AE. Common pain points:

- TRN stored as free text rather than a validated 15-digit number.
- Buyer master data missing legal name or address required by the standard.
- VAT codes that mix zero-rated, exempt, and out-of-scope without a clear flag.
- Credit notes linked to invoices by description text only, not by reference number.
- Multi-currency invoices without an AED equivalent on the line.
- Free zone designated zone supplies not separated from mainland supplies.

Fix the master data before writing a single line of integration code. Clean data makes the rest of the project shorter and cheaper.

## How custom ERP work compares to packaged ERP integrations

If your business runs both a custom system and a packaged one, you may also need to read the relevant sibling guide. Packaged routes are documented in our [QuickBooks E Invoicing Integration UAE](https://einvoicedirect.ae/accounting-software-uae/quickbooks-e-invoicing-integration-uae), [Zoho Books E Invoicing Integration UAE](https://einvoicedirect.ae/accounting-software-uae/zoho-books-e-invoicing-integration-uae), [Xero E Invoicing Integration UAE](https://einvoicedirect.ae/accounting-software-uae/xero-e-invoicing-integration-uae), [Tally E Invoicing Integration UAE](https://einvoicedirect.ae/accounting-software-uae/tally-e-invoicing-integration-uae), and [SAP E Invoicing Integration UAE](https://einvoicedirect.ae/accounting-software-uae/sap-e-invoicing-integration-uae) guides.

## Choosing an accredited service provider

Only ASPs on the Ministry of Finance's published ASP list can transmit invoices on the network. When evaluating providers for a custom ERP, ask:

- Do they offer both file-drop and REST API ingestion?
- Do they publish a sandbox with test TRNs and sample buyers?
- Do they handle PINT AE validation errors with clear messages?
- Do they archive invoices for the legal retention period required by UAE tax law?
- Do they support credit notes, debit notes, and self-billing where applicable?
- Is support available in UAE business hours and in English and Arabic?

## Risks of doing nothing

Missing the mandate is not just a compliance issue. From go-live, a non-compliant invoice may be rejected by the buyer's ASP, which delays payment. Repeated violations attract penalties of AED 2,500 to AED 50,000 each under Cabinet Decision 106 of 2025. For a business issuing thousands of invoices per month, the exposure adds up quickly.

## Official sources

Use primary sources for the latest figures: the [UAE Ministry of Finance](https://mof.gov.ae), the [UAE MoF e-invoicing portal](https://einvoicing.mof.gov.ae), the [Federal Tax Authority](https://tax.gov.ae), and the [Peppol documentation](https://docs.peppol.eu) for the underlying technical standard.

## Putting it together

A custom ERP can meet the UAE mandate without a full rebuild. Pick the integration pattern that fits your team, fix master data early, sign with an accredited ASP before October 30, 2026, and test against the pilot in Q2 2026. The same playbook also works for businesses moving from a custom build to a packaged product, which we cover across our [Accounting Software and ERP Integrations UAE](https://einvoicedirect.ae/accounting-software-uae) hub and the [Sage E Invoicing Integration UAE](https://einvoicedirect.ae/accounting-software-uae/sage-e-invoicing-integration-uae) guide.

EInvoice Direct is a UAE e-invoicing platform from Massive FZCO, built around the PINT AE format and the 5-corner DCTCE model. An accredited service provider is included with the software at no extra charge, so a custom ERP only needs one integration point to be ready for 2027. To plan your project, [get UAE e-invoicing pricing](https://einvoicedirect.ae/for-businesses#contact).

## Frequently asked questions

### Can a custom-built ERP comply with UAE e-invoicing?

Yes. The UAE mandate does not require a specific ERP product. Any system that can output structured invoice data or call an API can be connected to an accredited service provider (ASP), which then transmits invoices in PINT AE format across the Peppol 5-corner network. The integration sits between your ERP and the ASP, so the core system does not need to be rebuilt.

### When does my custom ERP need to be ready?

Businesses with annual revenue of AED 50 million or more must appoint an ASP by October 30, 2026 and go live on January 1, 2027. Smaller businesses must comply by July 1, 2027, and government entities by October 1, 2027. A pilot phase runs in Q2 2026. Start scoping at least 6 months before your go-live date to allow for data cleanup and testing.

### What format do invoices need to be in?

Invoices must be issued in PINT AE, the UAE profile of the Peppol International Invoice specification. It is a structured XML format based on Universal Business Language (UBL). Your ERP does not need to generate PINT AE directly. The accredited service provider can transform a simpler structured file or API payload into PINT AE before sending it on the network.

### How much does custom ERP e-invoicing integration cost?

Cost depends on the integration pattern, the cleanliness of your master data, and the volume of invoices. A file-drop integration with a small ERP is the cheapest path. A direct API integration with custom workflows costs more but gives better user experience. Pricing for the ASP itself is included with EInvoice Direct, so the main variable is your internal or partner development effort.

### What are the penalties for non-compliance?

Under Cabinet Decision 106 of 2025, penalties for e-invoicing violations range from AED 2,500 to AED 50,000 per breach. Issuing a non-compliant invoice, failing to transmit through an accredited ASP, or missing required data fields can each trigger a penalty. For high-volume businesses, repeated breaches can quickly exceed the cost of doing the integration properly.

### Do I need to connect my ERP directly to the government?

No. Under the 5-corner Decentralized Continuous Transaction Control and Exchange (DCTCE) model, your ERP connects only to an accredited service provider. The ASP validates the invoice, exchanges it with the buyer's ASP on the Peppol network, and reports the required tax data to the Federal Tax Authority. You never call a government endpoint directly from the ERP.

### Can I keep my custom ERP and still scale to thousands of invoices a day?

Yes. Accredited service providers support high-volume API ingestion with queuing and retries. The key is to design the integration so that invoice creation in the ERP and transmission to the ASP are decoupled, usually through a message queue or batch export. That way a network slowdown does not block invoice issuance inside your business.

### What master data should I clean up first?

Start with Tax Registration Numbers (TRN) for every customer and supplier, legal names and addresses, VAT treatment codes, and credit note links to original invoices. Make sure free zone supplies and designated zone supplies are flagged correctly. Clean master data removes most validation errors before they reach the ASP, which shortens the integration project and reduces rejections after go-live.


---
This content is informational and is not tax, legal, or financial advice.
For UAE e-invoicing pricing, see https://einvoicedirect.ae/for-businesses#contact