Peppol and UAE E-Invoicing

Peppol (Pan-European Public Procurement On-Line, now used more broadly) defines how organisations exchange structured documents—such as invoices—through accredited access points and networks. It is maintained by OpenPeppol, an international non-profit association.

The key idea is interoperability: a supplier and a buyer do not need to use the same software or have a direct connection, as long as each is connected to the network through an access point.

Confirm current Peppol documentation on the official OpenPeppol site before designing integrations.

Party one is your business: you create accurate tax invoices in accounting software. Party two is an MoF Accredited Service Provider: it transmits structured e-invoices. Party three is the national e-invoicing network/programme that accepts and status-checks those documents.

Finvora belongs in party one’s stack (books and VAT invoices). It is not party two unless MoF ASP accreditation is actually obtained.

The diagram above shows this flow. The practical point: your accounting software and your ASP can be different companies, and that is normal.

The Federal Tax Authority (FTA) is the VAT authority: tax invoices, TRN, and return evidence live in your books. The Ministry of Finance ASP path is about structured electronic transmission (often discussed with Peppol / PINT AE)—a different compliance layer.

Keeping FTA VAT data clean in Finvora prepares you for ASP transmission later; it does not replace an ASP when the mandate requires network send.

National e-invoicing programmes often reuse Peppol building blocks while adding country-specific invoice profiles. In the UAE, that conversation includes PINT AE and Accredited Service Providers.

Exact network rules and timelines are published by UAE authorities—verify on Ministry of Finance and related portals; do not rely on marketing blogs alone.

Three roles get blurred in vendor marketing: the accounting system that holds your invoices, the access point or ASP that transmits them, and the network that carries them. A single vendor can play more than one role, but only if it actually holds the accreditation for it.

When a vendor says “Peppol-ready” or “e-invoicing compatible”, ask which role they play and request the accreditation or register reference in writing.

Most SMEs will connect through an Accredited Service Provider rather than running a Peppol access point themselves. Keep invoice master data clean in your accounting software so ASP transmission is easier later.

Finvora is not a UAE Ministry of Finance Accredited Service Provider (ASP) for e-invoicing (PINT AE). Workspaces support FTA VAT lines, TRN fields, and return drafts for the books; connect an accredited ASP when the UAE e-invoicing mandate applies.

• Keep legal names and TRNs consistent between customers and your trade licence records.
• Use consistent tax codes and line-level VAT treatment.
• Number invoices sequentially and keep corrections traceable.
• Decide who owns the ASP relationship: your finance lead, your adviser, or IT.

Treat the conversation like any other compliance purchase: ask for proof, not adjectives. The list below fits both ASPs and accounting vendors who claim e-invoicing features.

Write the answers down before you sign. If the answer to the first question is “not yet”, ask what that means for your timeline.

• Are you an MoF Accredited Service Provider, and what is your register reference?
• Which specification version (PINT AE) do you support, and is there a sandbox?
• How do status updates and rejections come back to my accounting system?
• What happens to my data if I switch ASP or accounting software?

Finvora is your party-one system: VAT invoices with TRN, quotations, payments, and a ledger in AED, in English and Arabic. It prepares the data an ASP will need but does not transmit it.

When ASP / PINT AE transmission ships, the intended path is Finvora → integration → ASP → network. Until then, plan your ASP choice separately and do not describe Finvora as an ASP to customers or auditors.