E-invoicing readiness · by system
Will your accounting system handle PINT AE?
The question every finance director actually has, answered system by system. In almost every case the answer is that you keep the software you have and add an integration — so treat “you need a new ERP” as a sales position until someone has looked at what you run.
Three ways this goes
Every system lands in one of three places.
Whichever it is, you still appoint your own Accredited Service Provider. What changes is how your invoices reach it.
Native
The system produces PINT AE XML itself. You configure it, connect your ASP and test. Cheapest path, least to go wrong.
Connector
The vendor or your ASP publishes a module or API connector. Real work, but a supported path with someone to call.
Middleware
Something sits between your system and the ASP, translating what you output into valid PINT AE. Usual answer for older or heavily customised systems.
System by system
Where the common UAE finance systems stand.
Vendor support for e-invoicing moves month to month, so this describes the integration pattern rather than a version number that would be stale by the time you read it.
| System | Path | What that means for you |
|---|---|---|
| TallyPrime | Native | Recent releases produce PINT AE XML directly. Very common in UAE trading and distribution — check which release you are actually on, since older installations are widespread. |
| Zoho Books | Connector | Connects to an ASP for exchange. Straightforward where your chart of accounts and customer master data are already clean. |
| Microsoft Dynamics 365 Business Central | Connector | Connector coverage via AppSource or your ASP’s own extension. Watch for customisations in the sales document flow. |
| Microsoft Dynamics 365 Finance & Operations | Connector | Supported connector path. Larger estates usually need a proper test cycle rather than a switch-on. |
| SAP (S/4HANA and ECC) | Connector | Certified connectors exist. In practice the work is in the data — customer identifiers, tax codes and document types — not the transport. |
| Oracle (Fusion Cloud and EBS) | Connector | Pre-built connectors available. Same caveat: master data quality decides the timeline. |
| Odoo | Connector | Integrates with an ASP. Odoo estates are often customised, so budget for testing the invoice output rather than assuming it. |
| QuickBooks | Middleware | Typically an add-on or bridge rather than native output. Workable, and widely done. |
| Xero | Middleware | Usually bridged to an ASP. Fine for smaller volumes; confirm how credit notes and multi-currency are handled. |
| Sage 50 | Middleware | Third-party integration. Older Sage installations are the ones most likely to need real work. |
| Custom or in-house system | Middleware | Where we do most of our own work: extract, map to PINT AE, validate, hand to the ASP. Doable, and the earlier it starts the cheaper it is. |
| Excel, Word or a PDF template | Needs a system | The one case where the honest answer is that something has to change. Not necessarily a big ERP — but a system that can produce structured data. |
Positions as published at . Vendor capability changes frequently — confirm with your software vendor and your chosen ASP before you plan around any row. This is general information, not tax or legal advice.
How we get a system ready
Missan is not an Accredited Service Provider — you appoint your own, from the list the Ministry of Finance publishes at mof.gov.ae. We are the layer underneath: getting valid PINT AE out of your finance system and into whichever ASP you choose.
Establish what you actually run. Not what the licence says — what is installed, which release, and what has been customised. This is where most readiness plans go wrong before they start.
Look at a real invoice. PINT AE needs fields many UAE businesses do not currently capture cleanly: proper customer identifiers, tax treatment per line, credit note linkage. Data quality, not software, is the usual blocker.
Pick the integration path. Native, connector or middleware — decided by what you run and what your chosen ASP supports, not by what is easiest to sell you.
Test against real documents. Your awkward invoices, not a clean sample: credit notes, multi-currency, free-of-charge lines, partial deliveries. These are what fail in January.
Make sure the plumbing holds. New outbound data flows need dependable connectivity, identity and retention behind them. An invoice that cannot leave your network is not compliant.
Questions finance teams ask
Do we need to replace our accounting system for UAE e-invoicing?
Almost certainly not. TallyPrime, Zoho Books, QuickBooks, Xero, Odoo, Dynamics 365, SAP, Oracle and Sage can all be made to work, either natively, through a connector, or through a middleware layer that translates your output into PINT AE. The only case where something genuinely has to change is if you invoice from Excel, Word or a PDF template, because there is no structured data to convert. Treat "you need new software" as a sales position until someone has looked at what you run.
What is PINT AE?
PINT AE is the UAE’s structured invoice format — Peppol International Invoice, UAE specialisation. It is XML built on the Peppol PINT specification and the UBL standard, with UAE-specific fields. It is not a PDF, and a PDF attached to an email does not satisfy the mandate however neatly it is laid out.
Can Missan act as our Accredited Service Provider?
No. Missan is not an ASP, and you should be wary of anyone blurring that line. ASPs are accredited by the UAE Ministry of Finance and the official list is published on mof.gov.ae — more than thirty are approved. You choose your ASP; we connect your finance system to it, get valid XML coming out of your environment, and make sure the infrastructure behind it is sound.
How long does the integration take?
For a clean, current system on a supported connector, weeks rather than months. For an older or heavily customised estate, or where customer master data needs work first, plan for longer — and start now rather than in December. The work that takes time is almost never the transport; it is fixing the data the invoice is built from.
What if our ERP vendor says they will handle it?
Good — get it in writing, with a date and a named release. Then ask which ASP they have tested against, and whether your customisations are in scope. A vendor statement that e-invoicing is "on the roadmap" is not a plan you can put in front of an auditor in January.
Related reading
Tell us what you invoice from
Name your system and roughly how many invoices a month, and we will tell you which of the three paths you are on and what it involves — before you commit to anything.
AED 50m or more? Your ASP deadline is 30 October 2026.
The free Missan IT health check covers your finance systems, data quality and the infrastructure behind them — so you go into the mandate knowing what has to change, with time to change it.