Skip to main content
TrustBill Desktop — Mac, Windows, Android.See downloads

For enterprise finance teams

Enterprise e-invoicing readiness for the UAE's January 2027 deadline.

If your group's UAE revenue is AED 50 million or more, the FTA e-invoicing mandate stops being theoretical on 1 January 2027 — every B2B and B2G invoice must move as signed PINT-AE XML through an accredited service provider. The ASP appointment window closed on 30 October 2026. This page lays out what genuine readiness looks like for an enterprise finance function: ERP surface coverage, multi-entity TRNs, conformance evidence and a submission path that's already accredited.

Where the mandate stands for large businesses

Wave 1 — entities with revenue of AED 50 million or more — is the first cohort under mandatory obligations. The ASP appointment deadline of 30 October 2026 has passed; go-live is 1 January 2027. Penalties under Cabinet Decision 173 of 2026 apply from the go-live date: AED 5,000 for the first implementation violation plus AED 5,000 per month of continued non-compliance, capped at AED 50,000 in any rolling twelve months, plus AED 100 per non-compliant invoice capped at AED 5,000 per month per document type.

The voluntary pilot that opened in July 2026 is closing. Businesses that ran parallel pilots now have production evidence; those that didn't are compressing integration, master-data cleanup and parallel-run testing into weeks rather than months. Ministerial Decision 243 of 2025 established the system; Ministerial Decision 244 of 2025 set the phased schedule that puts Wave 1 first in line.

What readiness actually means at enterprise scale

Readiness is not "our ERP vendor says it supports e-invoicing." It is demonstrated conformance: your invoice population mapped to the full 130-field PINT-AE data dictionary, including conditional fields that only activate for specific VAT categories, currencies and invoice types. A mapping that covers the 51 always-mandatory elements but ignores conditional logic produces rejections at the point of transmission — visible to the FTA in near-real-time.

At enterprise scale the hard parts are the edges: credit notes and debit notes with reason codes, multi-line VAT categories on a single invoice, foreign-currency invoices with exchange-rate documentation, self-billed arrangements, and intra-group invoices across entities with separate TRNs. Each edge case is a field-rule failure waiting to surface. TrustBill's validation layer applies the same conditional rules the ASP network enforces, before submission — so rejections surface in your sandbox, not in the FTA's statistics.

The enterprise readiness checklist

Entity inventory: every UAE TRN in scope mapped — parent, subsidiaries, branches and any tax-group registrations. Invoice-population audit: which systems originate invoices (ERP, billing platform, POS, manual), what share is B2B/B2G, and which document types you issue. Master-data quality: customer TRNs validated, addresses complete, product and service codes consistent across systems.

Integration coverage: each originating system connected to the submission path — not just the primary ERP. Conditional-field conformance: test invoices covering credit notes, multi-rate VAT, foreign currency and exports validated against the full PINT-AE ruleset. Parallel run: at least two weeks of shadow submission where every invoice is also generated as PINT-AE and rejections are triaged. Governance: named owner for rejection handling, a corrections-and-credit-notes policy, and sign-off between finance and IT on go-live.

How TrustBill routes your invoices to the FTA

TrustBill submits to the FTA's e-invoicing network through Microvista Technologies LLC, an FTA-accredited service provider on the Ministry of Finance register (ASP №157529). In the Peppol five-corner model your systems are corner one: invoices leave your ERP through our connectors or API, we convert and validate against PINT-AE, Microvista carries them over the accredited Access Point to your buyer's provider and to the FTA.

For an enterprise that means the accredited submission path arrives bundled — no separate ASP contract, no Peppol certification project, no per-document accreditation overhead. Your integration surface is covered at every maturity level: direct sync for Zoho Books and QuickBooks Online, Excel and CSV upload plus folder-watch ingestion for Tally, Sage, Xero, Odoo and the wider landscape, and a REST API for custom ERP estates including SAP and Oracle.

Enterprise requirements we cover

Multi-entity: separate UAE entities under one TrustBill account, each with its own TRN, invoice series and submission path — group-level visibility without merging ledgers. Roles and audit: controller, approver and viewer roles, immutable audit trail on every status change, exportable evidence for internal and external audit. Bilingual rendering: Arabic and English invoice presentation from the same structured record, matching FTA display expectations.

Volume and pricing: enterprise invoicing volumes are priced on actual document throughput rather than per-seat — one contract covering every entity and connector. The 130-field catalog is public: your integration team can inspect every PINT-AE field, its conditions and its validation rule in the interactive field requirements explorer before a single line of code is written.

Procurement and onboarding timeline

A realistic enterprise onboarding runs three to six weeks: week one is data and entity mapping, weeks two to three are connector setup and sandbox conformance testing, week four onwards is parallel run and cutover. Organisations that started before the October ASP deadline are now in parallel run; organisations starting now should plan compressed timelines with dedicated finance-team capacity.

For procurement review we provide: the Microvista accreditation reference (MoF register, ASP №157529), the PINT-AE field catalog and validation ruleset, security and data-residency documentation, and a sandbox tenant for your integration team's own conformance testing. UAE data residency, no per-invoice charge surprises — pricing is on the public pricing page and enterprise terms are a single contract.

Frequently asked questions

Our revenue is over AED 50M but we haven't appointed an ASP — are we late?+

The 30 October 2026 appointment deadline has passed, so you should move immediately — but the practical exposure is the 1 January 2027 go-live, when penalties for non-transmission begin. An accredited submission path through TrustBill can be stood up in days for standard ERPs; custom landscapes take longer, which is why starting the sandbox phase now matters more than paperwork sequencing.

We run SAP/Oracle/Dynamics — how do we connect?+

Three paths: the REST API for direct integration, folder-watch ingestion where your ERP drops invoice files to a watched location, or the ERP Partner API if you run multiple systems. Your integration team can inspect all 130 PINT-AE fields and their conditional rules in the public field-requirements explorer before scoping work.

We have several UAE entities under one group — separate accounts?+

No. Multi-entity is built in: each entity keeps its own TRN, invoice numbering and submission path under a single account, with group-level visibility. Intercompany invoices route through the same accredited pipeline.

Do we still need a separate ASP contract?+

No. Accredited submission runs through Microvista Technologies (FTA-accredited, MoF register №157529) and is bundled into TrustBill. You sign one contract with us; the accredited rails, Peppol transport and FTA reporting sit underneath it.

What happens when an invoice is rejected?+

Rejections surface with the specific PINT-AE rule that failed — field, condition and expected format — inside TrustBill before submission wherever possible, and from the network post-submission with the same diagnostic. Correct-and-resubmit is a workflow, not a ticket queue: the corrected document is re-validated and re-transmitted through the accredited path.

Is there a pilot or sandbox before go-live?+

Yes — enterprise onboarding includes a sandbox tenant where your real invoice population runs against the full PINT-AE ruleset. Most teams run it in parallel with production invoicing for at least two weeks so rejection classes are eliminated before the mandatory date, not after.

Related resources