E-Invoicing Accreditation Path

Roadmap + living status report for getting Prime onto the UAE Ministry of Finance approved e-invoicing systems list (Accredited Service Provider). Updated as milestones complete.

Status: In-house build complete · external steps remain Last updated: 2026-06-30 ← Accounting

Where We Are — 2026-06-30

In-house technical build: complete. Prime generates, validates, saves and downloads (XML + PDF) compliant PINT-AE invoices & credit notes end-to-end — multi-currency, allowances/charges, delivery, exemption reasons, EN 16931 validation. ⚡ Open the generator →

What's left is external / commercial only: OpenPeppol membership + AP certification, AS4 transmission via a contracted ASP, ISO/IEC 27001 & ISO 22301, the official PINT-AE Schematron/XSD rule packs, and 2-year-experience evidence. Detail in the tables below.

ISO 27001 / 22301 Readiness →

Recommendation

Two viable paths. Do both, sequenced.

Path B — Partner with an accredited ASP DO NOW

Time to compliance: weeks–months

Prime stays the ERP. Map invoices to PINT-AE and route through a pre-approved ASP's Peppol Access Point via API. Gets the group + clients compliant by the deadlines with minimal compliance burden. What virtually every ERP does.

Path A — Prime becomes its own ASP STRATEGIC

Time to accreditation: 12–18 months

Prime gets on the approved list itself and can sell compliant e-invoicing to other businesses. Long-lead items (ISO 27001, ISO 22301, OpenPeppol membership, 2-yr experience evidence) make this impossible before the 2026/27 deadlines — start in parallel only if e-invoicing is a revenue product.

Key Dates (UAE mandate)

Segment	Appoint ASP by	Go-live
Voluntary pilot	—	1 Jul 2026
Large business (revenue ≥ AED 50M)	30 Oct 2026	1 Jan 2027
Other business (revenue < AED 50M)	31 Mar 2027	1 Jul 2027
Government (B2G)	31 Mar 2027	1 Oct 2027

Non-compliance: AED 5,000/month for failing to appoint an ASP; AED 100 per late invoice (capped AED 5,000/month).

The Model

UAE uses a Peppol "5-corner" model: your ERP → your ASP → MoF/FTA central platform → recipient's ASP → recipient.

PINT-AE — the mandatory UAE Peppol invoice schema. All invoices must validate against it.
Peppol AS4 — the eDelivery transport protocol between Access Points.
Two-tier accreditation (Ministerial Decision No. 64 of 2025):
- Pre-approval (Art. 15) — met baseline eligibility → listed. 41 providers pre-approved (Jun 2026)
- Full accreditation (Art. 16) — passed MoF accreditation testing (volume, uptime, PINT-AE validation, error-free transmission). 0 fully accredited as of mid-2026

ASP Requirements & Prime Gap

Requirement	Status	Detail	Prime gap
Active Peppol certification	To Do	Peppol Access Point, OpenPeppol conformance, AS4	Build join OpenPeppol + certify AP
2 years' experience	To Do	Operating an e-invoicing system, with proof	Likely blocker needs evidence
ISO/IEC 27001	In Process	Information security (audited)	ISMS docs complete — 12 policies + SoA + registers drafted; approval + 3-mo evidence + audit external
ISO 22301	In Process	Business continuity (audited)	BIA + RTO/RPO drafted; tested DR + audit remain
Paid-up capital AED 50,000	Done	Minimum	Easy
Professional indemnity insurance	To Do	Art. 11	Procurable
MFA, encryption (rest+transit), monitoring	In Process	Art. 9 / Peppol security	Mostly there formalize
Trade licence, tax reg, self-declaration	Done	Art. 6/8/10	Have it
PINT-AE generation + validation	In Process	Map Prime invoices to UAE schema	Generation done · validation: JS EN 16931 rules done, official Schematron/XSD external

Done shipped/met · In Process underway · To Do not started

Application Process (Path A)

MoF portal → Services → "Accreditation of E-Invoicing Service Providers" → Start Service
Login via UAE Pass
Submit accreditation request + 15 documents (trade licence, capital proof, tax reg, legal rep authorization, e-invoicing experience proof, Peppol service agreement, ISO certs, technical/encryption design, insurance)
Review: 90 working days · No fees
Portal: einvoicing.mof.gov.ae · Support: 800533336 / info@mof.gov.ae

OpenPeppol Access Point — How to Certify

This is the "Active Peppol certification" requirement. In the UAE the Peppol Authority is the MoF, so OpenPeppol AP certification and the MoF ASP accreditation are the same track — membership + AP cert feeds the MoF agreement.

Steps:

1. Join OpenPeppol — apply for membership (Service Provider category), pay sign-up + annual fee.
2. Sign the Transport Infrastructure Agreement (TIA) with the UAE Peppol Authority (MoF) — due diligence on solvency, legitimacy, senior-staff background checks. This is the MoF ASP accreditation.
3. Technical build — ISO/IEC 27001, support Peppol BIS (PINT-AE), implement an AS4 Access Point (SMP optional).
4. AS4 conformance testing — unit-test in your env → acceptance testing on the OpenPeppol central test bed → interoperability testing.
5. Certified — listed as a Peppol Certified Service Provider; certification fee billed, then annually.

Fees (EUR, by staff count — Prime ≈ S1–S2, 1–50):

Membership	Sign-up	Annual	Cert	Year-1
Access Point only — recommended for an ERP	€1,050	€1,850	€1,500	≈ €4,400
Access Point + SMP	€1,800	€2,750	€2,500	≈ €7,050

Cert fee recurs (adds to annual after year 1) → ongoing ≈ €3,350/yr (AP-only). SMP not required if you use the authority/shared SMP. ISO/IEC 27001 is the long-pole prerequisite — start it in parallel.

Sources

🧩Invoice Template Matching — Prime → PINT-AE

⚡ Open E-Invoice Generator →

Field-level mapping of Prime's invoice model (invoices · companies seller · clients buyer · line items) to the 51 mandatory PINT-AE fields (Peppol BIS Billing 3.0 + EN 16931 + UAE extensions). Foundation for both paths — Path B needs PINT-AE output, Path A needs it plus validation.

PINT-AE group	#	Prime today	Key gaps to close
Invoice details	9	Done	number, dates, type code, currency, PO + invoice period — generated
Seller details	11	Done	name, TRN, address, country + Peppol endpoint (scheme `0235`, override)
Buyer details	9	Done	TRN + address + country on `clients` + Peppol endpoint
Document totals	5	Done	line / tax-excl / tax-incl / payable + VAT in AED
Tax breakdown	4	Done	per-category VAT — code + rate + exemption reason generated
Line items	13	Done	UoM + per-line VAT category/rate + optional item classification

Top gaps:

Peppol electronic addresses (seller + buyer endpoint IDs, scheme 0235) — entirely new.
Buyer master data: capture TRN + full address + country on the clients record.
Tax model: break VAT out by category (standard 5% / zero-rated / exempt / out-of-scope) + rate, at document and line level.
Line items: add unit of measure + per-line VAT category/rate + item classification.
TRN handling: 15-digit VAT TRN + 10-digit Corporate-Tax TIN — format + validate.

Next: extend the invoices / clients / companies data model for the gap fields, then build a PINT-AE XML generator + EN 16931 validation.

PINT-AE — Remaining to Production

Gap list for the generation + validation workstream (overall status: In Process). Ordered by priority — field capture is the blocker; everything else depends on the data being there.

#	Area	What's missing	Status
1	Field capture	~~buyer TRN/address/country~~ · ~~line UoM + VAT category~~ · ~~Peppol endpoint (override)~~ · ~~tax-exemption reason~~ · ~~persisted to `einvoices`~~	Done
2	Real validation	~~EN 16931 BR-* calc/VAT rules + code-list checks~~ (JS validator, 19 tests); remaining: official PINT-AE Schematron + UBL 2.1 XSD	In Process
3	Document coverage	~~credit/debit notes~~ · ~~payment means/terms~~ · ~~notes~~ · ~~invoice period~~ · ~~allowances/charges~~ · ~~delivery~~ (rounding/prepaid optional)	Done
4	Multi-currency	~~VAT total also in AED when currency ≠ AED (BT-111)~~	Done
5	Wiring & ops	~~Generate + XML download~~ · ~~save XML + status~~ (`einvoices`) · ~~human-readable PDF~~ · ~~test suite~~ ; remaining: AS4 transmission via ASP external	In Process

Progress Log

Most recent first. New milestones appended here as we complete them.

2026-06-30

ISMS documentation set completed

All 12 ISO 27001 policies + Asset/Risk/Supplier registers drafted on the ISO Readiness page; gap assessment re-scored to 18 implemented / 59 partial / 10 gap / 6 N/A. The in-house ISMS documentation is now complete — what remains is people/operational/external: appoint an ISMS owner, management-approve the policies, operate ~3 months for evidence, close ~10 operational gaps (tested restores, vuln scanning, EDR, internal audit), then the Stage 1/2 audit by an accredited body.

2026-06-30

ISO 27001 / 22301 readiness workspace created

Built ISO Readiness — a living tracker with a first-pass gap assessment of all 93 ISO 27001:2022 Annex A controls (18 implemented · 41 partial · 28 gap · 6 N/A), an ISO 22301 BIA + RTO/RPO for the 5 critical services, a 12-policy library, and a draft master Information Security Policy. Moves both ISO requirements from To Do → In Process. ~70% of certification effort (the ISMS documentation/evidence) is in-house; the audit itself is external.

2026-06-30

Document coverage completed — allowances/charges, delivery, Peppol override

Added document-level allowances (discounts) + charges (per-category VAT, reflected in totals + AllowanceTotalAmount/ChargeTotalAmount per EN 16931 BR-CO), delivery (date + address), and an explicit Peppol endpoint-ID override on seller/buyer — with an "Adjustments, Delivery & Identifiers" card in the generator. 17/17 new tests pass. This exhausts the in-house code items: field capture + document coverage are now Done. Only external dependencies remain — official Schematron/XSD, AS4 transmission, ISO 27001/22301, OpenPeppol membership, 2-year-experience evidence.

2026-06-30

Invoice period (BG-14) + discoverability

Added billing-period (BG-14) start/end to the engine + generator UI. Added an E-Invoice · PINT-AE tile to the Accounting home so the generator is reachable from the module index (not just this page). That exhausts the code-side items we can build in-house — the rest is external (official Schematron/XSD rule packs, AS4 transmission via a contracted ASP, ISO 27001/22301, OpenPeppol membership, 2-year-experience evidence).

2026-06-30

PINT-AE engine v2 + persistence + PDF

Major round on the generator: multi-currency (VAT also in AED, BT-111), credit/debit notes (UBL <CreditNote> + BillingReference), tax-exemption reasons for zero/exempt/out-of-scope, payment means/terms + notes, and a strengthened validator (EN 16931 BR-S/Z/E + calculation + code-list checks) — 19/19 unit tests pass. In the UI: Save (persists to einvoices via the saveEinvoice callable, with validated/draft status), a saved list with XML re-download, and Print / PDF (human-readable tax invoice).

Done: multi-currency; generate / download / save / list / PDF; engine doc-coverage (credit notes, payment, notes).
Remaining → then external: allowances/charges + invoice period; official Schematron/XSD; AS4 transmission via a partner ASP.

2026-06-30

End-to-end E-Invoice generator shipped

New page Accounting → E-Invoice (e-invoice.html + e-invoice.js): pick a seller company + buyer client (live from Firestore), build invoice lines with unit-of-measure + VAT category per line, see live totals, then Validate → Generate → Download the PINT-AE UBL XML via pint-ae.js. First working end-to-end path from Prime data to a compliant e-invoice file.

Closes: per-line UoM + VAT capture; the "Generate e-invoice + XML download" wiring.
Next: persist generated XML + status on a sales-invoice record, human-readable PDF, then AS4 transmission via a partner ASP (Path B).

2026-06-30

Field capture — buyer e-invoicing details shipped

Added VAT TRN, address, city, country to the client record (Control → Clients form + saveControlClient function + direct write), stored flat on the clients doc so pint-ae.js consumes it as the buyer party. Closes the "buyer details" gap (was Weak → now Partial; only the Peppol endpoint ID remains).

Remaining field capture: per-line unit-of-measure + VAT category/rate on invoices, invoice-type code, tax-exemption reason, Peppol endpoint IDs.

2026-06-30

OpenPeppol AP certification path mapped

Documented the 5-step route to "Active Peppol certification": join OpenPeppol → sign the TIA with the UAE Peppol Authority (= MoF, so it merges with the ASP accreditation) → ISO 27001 + AS4 Access Point build → AS4 conformance testing (central test bed) → certified. Fees for Prime's size (AP-only): ≈ €4,400 year-1, ≈ €3,350/yr ongoing. ISO/IEC 27001 is the long-pole prerequisite — start in parallel. See the OpenPeppol Access Point section above.

2026-06-30

PINT-AE generator + validator built

Shipped Accounting/js/pint-ae.js — a pure module that generates a Peppol BIS Billing 3.0 / EN 16931 UBL 2.1 invoice in the UAE PINT-AE profile (customization urn:peppol:pint:billing-1@ae-1, endpoint scheme 0235, VAT reported in AED) from Prime's invoice / company / client shapes, plus validatePintAe() that flags every missing mandatory field. Smoke-tested: multi-category VAT (standard 5% + zero-rated) totals + valid XML.

Closes (generation layer): tax breakdown by category, per-line VAT + unit of measure, Peppol endpoint IDs, AED tax currency, TRN/TIN handling.
Next: capture the gap fields in the UI (buyer TRN/address on clients; line UoM + VAT category on invoices), then wire a "Generate e-invoice (PINT-AE)" action + XSD/Schematron validation.

2026-06-30

Invoice template matching (PINT-AE) — first pass

Mapped Prime's invoice model (invoices / companies / clients + line items) to the 51 mandatory PINT-AE fields across the 6 groups. Seller details + document totals are well covered; buyer details, tax breakdown, and per-line VAT/UoM are the main gaps, plus the Peppol electronic-address identifiers.

Outcome: see the Invoice Template Matching table above.
Next: extend the data model for the gap fields → build a PINT-AE XML generator + EN 16931 validation.

2026-06-30

Initial investigation completed

Researched the UAE MoF e-invoicing ASP accreditation framework (Ministerial Decision 64/2025, Peppol 5-corner, PINT-AE, AS4, two-tier pre-approval vs full accreditation). Documented requirements, gap assessment for Prime, mandate timeline, and the Path A (become ASP) vs Path B (partner) decision.

Outcome: recommended Path B now + Path A as a parallel strategic program.
Next: decide direction; then either shortlist pre-approved ASPs with APIs (Path B) or scope the ISO 27001/22301 + OpenPeppol program (Path A).