If you are a CFO or finance head in Dubai, you have probably heard the same sentence in every board meeting this year: "We need to be ready for e-invoicing." What is less clear is who is responsible for choosing the technology, what "ready" actually means, and how to tell a provider that will carry you safely through January 2027 from one that is still figuring out the UAE rules itself.
This guide is built for that decision. Choosing e-invoicing software in the UAE is no longer a routine finance-systems purchase. It is a compliance decision with a legal deadline, a regulated supplier ecosystem, and direct consequences for your cash cycle, your VAT position and your relationships with customers and suppliers. Get it right and e-invoicing becomes a quiet upgrade to your order-to-cash and procure-to-pay processes. Get it wrong and you inherit penalties, rework and a painful mid-project provider switch.
Below, we explain what the UAE framework requires, then walk through the 10 questions we believe every CFO should put to any shortlisted vendor: what to ask, what a good answer sounds like, and what should make you pause. A scorecard, a 30-day selection plan and an FAQ follow at the end.
01Where the UAE e-invoicing mandate stands today
Before evaluating vendors, it helps to be precise about the rules, because vendors will describe them in different (and sometimes self-serving) ways.
The model. The UAE is rolling out a decentralised, Peppol-based "five-corner" model. In simple terms, the supplier and the buyer each connect to the network through their own Accredited Service Provider (ASP), and invoice data is also reported to the Federal Tax Authority (FTA) as the fifth corner. Invoices must be issued in a structured, machine-readable format. The UAE's national specification is PINT AE, built on the Peppol international invoice standard. PDFs and scanned images no longer count as compliant e-invoices under the system.
The timeline. Under Ministerial Decision No. 244 of 2025, as amended in 2026, the phasing is:
- Pilot phase: voluntary participation from 1 July 2026.
- Businesses with annual revenue of AED 50 million or more: appoint an ASP by 30 October 2026 and go live by 1 January 2027.
- Businesses below AED 50 million: appoint an ASP by 31 March 2027 and go live by 1 July 2027.
- Government entities: appoint an ASP by 31 March 2027 and go live by 1 October 2027.
The penalties. Cabinet Decision No. 106 of 2025 sets an administrative penalty of AED 5,000 per month (or part of a month) for failing to implement the system or appoint an ASP on time, and separate daily penalties for failing to notify your ASP of changes to data registered with the FTA.
With that context, here are the ten questions.
02Question 1: Is the provider an Accredited Service Provider in the UAE, and for exactly what?
This is the gate question, and it should come first. Under the UAE framework, the exchange of e-invoices must run through an ASP accredited by the Ministry of Finance. A vendor that merely says it is "Peppol-ready" or "UAE-compliant" is not the same as an accredited service provider in the UAE.
What to ask:
- Are you on the Ministry of Finance's published list of accredited service providers? Is your status fully accredited or still pre-approved or in process?
- Which services does your accreditation cover: issuing, receiving, reporting to the FTA, or all three?
- If you are not yourself accredited, which accredited provider carries your traffic, and what is the contractual relationship between us, you and them?
What a good answer sounds like: A named status you can verify independently on the official MoF list, a clear explanation of the services covered, and no hesitation about showing evidence.
Red flag: Vague language such as "certified," "approved partner" or "compliant with FTA requirements" with no reference to the official list. Another red flag is a vendor that resells a third-party ASP but does not tell you who is actually responsible if something fails on submission day.
A practical tip: do not rely on a sales deck. Check the official list yourself, note the date you checked, and keep it in your procurement file. The list has been growing through 2026, with the number of approved and pre-approved providers rising well above 30, so the market is broad enough that you should never have to settle for an unverified claim.
03Question 2: How deeply does the platform support PINT AE?
PINT AE is the data specification that every UAE e-invoice must follow. It defines mandatory fields, code lists, tax categories and validation rules. Supporting it well is harder than it sounds, because real-world invoices are messy: partial deliveries, advance payments, discounts, free-zone supplies, reverse charge, designated zones, credit notes that reference earlier invoices and more.
What to ask:
- Which version of PINT AE do you currently support, and how are specification updates deployed? Who pays for the change?
- Can you show me a real invoice from our business converted into PINT AE, with every mandatory field populated and validated?
- How do you handle UAE-specific scenarios: free-zone and designated-zone transactions, reverse charge, zero-rated and exempt supplies, credit and debit notes, multi-currency invoices?
What a good answer sounds like: A live demonstration using your data (or realistic sample data), a documented update process with a clear commitment to keep you current when the specification changes, and candid discussion of edge cases they find difficult.
Red flag: A vendor whose demo uses only a clean, standard invoice. Your finance team knows your exceptions better than any vendor does. If the demo cannot handle them, your month-end will.
As a finance head you do not need to read the technical specification, but you should insist that someone on your team (or an advisor) sees the field-level mapping. The most common failure we see in readiness reviews is not the network connection. It is incomplete or incorrect master data feeding the invoice: missing TRNs, inconsistent customer addresses, and wrong tax codes. A good PINT AE software provider will surface those gaps early, not at go-live.
04Question 3: How reliable is the Peppol connectivity, and what happens when delivery fails?
Under a decentralised model, your invoice travels from your system, through your ASP, across the Peppol network to your customer's ASP and finally to your customer. Your relationship with a Peppol provider in the UAE is only as good as that chain's reliability and visibility.
What to ask:
- What are your contractual uptime and message-delivery service levels? What is your measured performance over the last 12 months?
- Can I see real-time delivery status for every invoice: sent, delivered, acknowledged, rejected?
- When a customer's ASP rejects or fails to accept an invoice, how are we notified, who owns the fix, and how fast?
- How do you handle peak loads, such as month-end and quarter-end invoicing runs?
What a good answer sounds like: Specific numbers, an operational status page, and a clear escalation path with named support tiers. Ask for the incident history, not just the uptime percentage.
Red flag: No visibility into delivery status, or an answer that begins with "that rarely happens." For a CFO the key issue is cash. If an invoice is stuck in transit, your customer may not treat it as received, and your payment terms effectively stop running. The software should make failed deliveries impossible to miss.
Also ask about interoperability. Your customers will have chosen their own ASPs. Your provider should be able to demonstrate successful exchanges with a range of other providers, not only with customers on its own platform.
05Question 4: How does it integrate with our ERP and finance stack?
Most UAE e-invoicing projects succeed or fail at the integration layer. Your invoices are created in an ERP, billing system, e-commerce platform or even spreadsheets. The e-invoicing software has to receive that data, transform it, validate it and return statuses, all without forcing your team to re-key anything.
What to ask:
- Do you have pre-built connectors for our ERP (SAP, Oracle, Microsoft Dynamics, Odoo, Zoho, Tally or others)? Who maintains them when the ERP vendor releases updates?
- If we have multiple systems, such as an ERP for finance plus separate billing or CRM tools, can you integrate with all of them?
- Do you provide a well-documented REST API and webhooks for custom workflows? Is there a sandbox for testing?
- Who does the integration work: your team, our team or a partner? What is included in the price and what is billed separately?
What a good answer sounds like: Named reference customers on your ERP, documented API specifications, a sandbox environment, and a realistic project plan with owners on both sides.
Red flag: "We integrate with everything" without a single reference. Or an integration approach that depends on manual file uploads, which turns a compliance project into a permanent operational burden.
For mid-sized Dubai businesses running an all-in-one platform for invoicing, CRM, expenses and VAT, the integration question can be simpler: when invoicing, tax and e-invoicing sit on one platform, there is no interface to break.
06Question 5: What validation and error-handling happens before an invoice leaves our system?
In a structured e-invoicing regime, a rejected invoice is not a minor annoyance. It is an invoice that has legally not been issued. The cheapest place to catch errors is before submission, which is why validation depth is one of the clearest quality differences between providers.
What to ask:
- What validations run before submission: schema validation, business-rule validation, TRN and master-data checks, tax-code consistency?
- How are errors presented to my AR team? In plain business language, or as raw technical error codes?
- Is there an exceptions queue where a finance user can correct, resubmit and track an invoice without calling IT?
- How do you handle corrections: credit notes, replacement invoices, cancellations?
What a good answer sounds like: A pre-submission validation layer that explains problems in terms your team understands (for example, "customer TRN missing on invoice 1042" rather than "BR-AE-07 failed"), plus a self-service correction workflow with a full audit trail.
Red flag: Validation that only happens after the invoice reaches the network. Another is an exceptions process that requires a support ticket for every fix; at month-end volume, that will not scale.
CFO angle: ask for a first-time-right rate from existing customers, meaning the share of invoices accepted without manual intervention. Even a rough benchmark tells you more about operational maturity than any feature list.
07Question 6: How does it handle FTA reporting and our VAT process?
In the five-corner model, invoice data reaches the tax authority as part of the flow. That changes the relationship between your invoices and your VAT return: the authority will increasingly see your transactions in near real time. Your VAT return should reconcile cleanly to the e-invoices you have issued and received.
What to ask:
- How does the platform report to the FTA, and how do I see confirmation that reporting succeeded for each invoice?
- Can I reconcile e-invoices issued and received against my VAT return? Is there a report that highlights mismatches before I file?
- Does the system support your existing VAT workflow, such as the standard return boxes and the FTA audit file (FAF) export?
- How does the platform manage changes in tax rules, such as updated codes or reporting requirements?
What a good answer sounds like: A reconciliation view that ties e-invoice records to VAT return figures, plus a clear commitment to track regulatory change and update the product accordingly.
Red flag: An e-invoicing tool that is completely separate from VAT reporting, leaving your team to reconcile two data sources manually.
08Question 7: What are the security, data residency and audit-trail standards?
Your e-invoicing provider will handle some of your most sensitive commercial data: customer names, prices, volumes, payment terms and TRNs. For a CFO, this is a vendor-risk question as much as a compliance one, and your auditors and board may ask about it.
What to ask:
- Where is our data hosted, and does it stay in the UAE? What is your approach to cross-border transfers?
- Which security certifications and controls do you maintain (ISO 27001, SOC 2, encryption in transit and at rest, penetration testing, role-based access, 2FA)?
- How long is invoice data retained, and can we export it at any time? Does retention align with UAE statutory record-keeping requirements?
- Is there a complete, tamper-evident audit log of who created, changed, approved and sent each invoice?
- What is your business-continuity and disaster-recovery plan, and how often is it tested?
What a good answer sounds like: Independent certifications you can verify, UAE-based hosting where relevant, and an audit trail your internal audit team can actually use.
Red flag: Generic statements such as "bank-grade security" with no documentation.
09Question 8: Does it handle inbound invoices, not just outbound?
Most vendor conversations focus on issuing e-invoices. But the mandate is two-sided: you must also be able to receive structured e-invoices from your suppliers. For many CFOs, the accounts payable side is the larger operational change.
What to ask:
- How are inbound e-invoices received, validated and delivered into our AP process or ERP?
- Can the platform support approval workflows, coding and matching against purchase orders and goods receipts?
- What about suppliers who are not yet ready? Is there a fallback for receiving non-structured invoices during the transition?
- Can you help onboard our key suppliers, with communication templates and support for their questions?
What a good answer sounds like: A real inbound workflow with exception handling and supplier-onboarding support.
Red flag: An outbound-only product, or an inbound process that ends with "we deliver you an XML file."
10Question 9: What does implementation really look like, and who supports us in Dubai?
The 1 January 2027 go-live date for large businesses leaves little slack, and the 1 July 2027 date for the rest will arrive quickly. Implementation plans that look comfortable on paper tend to slip.
What to ask:
- What is the realistic timeline from contract to go-live for a business of our size and complexity? What are the critical-path dependencies on our side?
- Who is on the project team, and will we have a named implementation lead?
- Do you support multi-entity structures, multiple branches and free-zone or mainland mixes? Can we phase entities in?
- What support is available locally: working hours, languages (including Arabic), channels such as phone and WhatsApp, response-time commitments?
- What training do you provide for finance, AR, AP and IT users?
What a good answer sounds like: A phased plan with milestones (data cleanup, sandbox testing, parallel run, go-live, hypercare), clear responsibilities, and local support that can respond during UAE business hours in your language.
Red flag: A fixed timeline offered before anyone has looked at your systems.
Bilingual capability deserves a mention. In the UAE, Arabic and English invoices, statements and customer communications are routine. Make sure the platform supports full Arabic and right-to-left layouts, not only a translated template.
11Question 10: What is the total cost, and how easy is it to leave?
Price discussions in this market have been a theme in 2026. The MoF extended the large-business appointment deadline partly in response to feedback that businesses wanted wider technical options and more competitive pricing. Compare carefully.
What to ask:
- What is the full pricing model: subscription, per-invoice or per-document fees, onboarding and integration fees, additional entities, additional users, sandbox, support tiers?
- What happens to the price if our invoice volume doubles? Are there volume bands, overage charges or minimum commitments?
- What costs sit outside your proposal: ERP-side development, consultant fees, internal project time?
- What are the contract term, renewal and termination conditions? If we later choose another ASP, how do we export our data and transition?
- Are service levels backed by credits or other remedies?
What a good answer sounds like: A transparent, written price schedule that covers the first 24 to 36 months, scenario pricing for growth, and a clear exit clause with data-portability commitments.
Red flag: Low headline pricing with large add-ons, or long lock-ins with no performance remedies.
12A simple scorecard for your shortlist
Once you have collected answers, a structured scorecard keeps the decision objective and defensible to your board, auditors and CEO. Score each provider from 1 to 5 on every question, weight the questions by importance for your business, and total the results.
| # | Question area | Suggested weight | Who should score it |
|---|---|---|---|
| 1 | ASP accreditation status and scope | Gate (pass/fail) | CFO, legal |
| 2 | PINT AE depth and edge cases | High | Finance systems, tax |
| 3 | Peppol connectivity and delivery visibility | High | IT, finance operations |
| 4 | ERP and systems integration | High | IT, finance systems |
| 5 | Validation and error handling | Medium-high | AR team |
| 6 | FTA reporting and VAT reconciliation | High | Tax, financial controller |
| 7 | Security, residency and audit trail | High | IT, risk, internal audit |
| 8 | Inbound invoices and AP workflow | Medium-high | AP team |
| 9 | Implementation and local support | High | Project sponsor |
| 10 | Total cost and exit terms | Medium | CFO, procurement |
Treat question 1 as pass/fail. A provider that cannot demonstrate its accreditation status should not proceed, no matter how attractive the rest of its proposal looks.
13A 30-day plan to choose your provider
If your timeline is tight, this sequence keeps the process fast without cutting corners.
- Week 1 — Scope and shortlist. Confirm which phase applies to your business, based on your revenue and entity structure. Map your invoicing and AP systems, volumes and key exceptions. Check the official MoF list and shortlist three to five providers that are accredited or credibly in the final stages.
- Week 2 — Structured demos. Send every provider the same scenario pack: a handful of your real invoices (including awkward ones), your ERP details and your volume forecast. Ask each to demonstrate your scenarios, not their standard demo. Request security documentation and sample contracts at the same time.
- Week 3 — Reference checks and technical validation. Speak with at least two customers per finalist, ideally on your ERP and of similar size. Have IT review the API documentation and sandbox access. Ask your AR and AP leads to try the exceptions workflow.
- Week 4 — Commercials and decision. Complete the scorecard, build the three-year cost model, negotiate service levels and exit terms, and take a recommendation to your steering group. Agree the implementation plan and named owners before signing.
14Common mistakes CFOs should avoid
- Treating accreditation as a marketing term. Verify it on the official list, every time.
- Focusing only on outbound invoices. Your supplier-facing AP process is half the mandate.
- Leaving master data until last. Clean TRNs, addresses and tax codes before testing, not during it.
- Skipping the parallel run. Test with real transactions before the go-live date, with a clear fallback plan.
- Waiting for a perfect market. The framework is defined, the ASP market is established, and the deadlines are fixed.
15Final thoughts: choose a partner, not just a product
The right e-invoicing software for a UAE business is the one that combines verified accreditation, solid PINT AE and Peppol performance, clean integration with your finance stack, and a team in Dubai that picks up the phone. The ten questions above give you a way to test all of that quickly and fairly, in language your board will understand.
As deadlines approach, the finance leaders who come out ahead will be the ones who treated this as a business-process upgrade with a compliance outcome, not a compliance task with a software invoice attached.
If you want to see how an all-in-one UAE platform approaches these questions, with bilingual Arabic and English invoicing, VAT and FTA workflows, and Peppol PINT AE capability on a single platform, we would be glad to walk you through it.
Book a demo with inFatura and bring your toughest invoices. We will show you exactly how they flow, and answer all ten questions above with evidence, not slides. You can also explore the platform at infatura.ae or read more about Peppol PINT AE on inFatura.
16Frequently asked questions
What is the best e-invoicing software in the UAE?
There is no single best option; the right choice depends on your size, ERP landscape, invoice volumes and exception complexity. Start by confirming that the provider is an accredited service provider on the official Ministry of Finance list, then compare PINT AE depth, integration, support and total cost using the ten questions in this guide.
Do I have to use an accredited service provider in the UAE?
Yes. Under the UAE framework, in-scope businesses must exchange e-invoices through an Accredited Service Provider approved by the Ministry of Finance. You cannot connect to the system directly.
What is PINT AE?
PINT AE is the UAE's national e-invoice data specification, built on the Peppol international invoice model. It defines the mandatory fields, code lists and validation rules every UAE e-invoice must follow.
When does my business need to comply?
Businesses with annual revenue of AED 50 million or more must go live by 1 January 2027, after appointing an ASP by 30 October 2026. Businesses below that threshold must appoint an ASP by 31 March 2027 and go live by 1 July 2027. Government entities follow, with go-live on 1 October 2027. Always confirm against the latest Ministry of Finance and FTA announcements.
What are the penalties for non-compliance?
Cabinet Decision No. 106 of 2025 provides for an administrative penalty of AED 5,000 per month, or part of a month, for failing to implement the system or appoint an ASP on time. Other penalties apply to related failures, such as not notifying your ASP of changes to registered data.
Can I use my existing ERP for e-invoicing?
In most cases, yes, but your ERP will usually need to connect to your ASP through a connector or API that produces compliant PINT AE data. Ask each provider for named references on your ERP and a documented integration plan.
How long does implementation take?
It depends on system complexity, data quality and the number of entities. Many projects need several months from contract to a stable go-live, which is why large businesses facing 1 January 2027 should move now, and why smaller businesses should not wait until the March 2027 appointment deadline.
Does Infatura support Peppol PINT AE e-invoicing? Yes. Infatura includes Peppol PINT AE capability to send and receive e-invoices, with delivery-status tracking for each invoice. It is available on the Business plan, and you can test it during the free trial.
Who is Infatura designed for, and what does it cost? Infatura serves UAE businesses from solo founders and growing SMEs to larger organisations with multiple branches. Plans start at AED 99 per month (Starter), with the Business plan at AED 299 per month and custom Enterprise pricing. Prices exclude VAT.
Is my data secure, and does Infatura work fully in Arabic? Infatura encrypts data at rest and in transit, hosts it in UAE data centres, and supports role-based access, two-factor authentication, SSO and full audit logs. Arabic is native to the platform, with full right-to-left support on every screen, invoice, statement and report.
How do I get started with Infatura? You can start a 14-day free trial with no credit card, or book a demo to see how your own invoices would flow. If you are switching from tools such as Zoho, Wafeq or QuickBooks, Infatura supports CSV imports of customers, products and opening balances, and its team can assist with migration during onboarding.