PTG UAE E-Invoicing Tool 04
Upload an ERP JSON payload, a text-based PDF invoice or a UAE invoice XML to identify and map source data against the published MoF mandatory-field requirements and selected PINT-AE 1.0.4 rules, using source-specific evidence classification.
Start Field Verification → View Verification Method
THREE-IN-ONE VERIFICATION
Upload → Extract → Classify Evidence → Map / Derive → Flag Review Items → Verify Structured Fields → Remediation
{ }
ERP JSON
Source Mapping
Invoice Field
Coverage
</>
PINT-AE XML
Mapping Check
Official Verification Basis
The official MoF Mandatory Fields document provides separate mandatory-field lists for an electronic Tax Invoice and a commercial Electronic Invoice (XML) and states that it should be read together with the UAE e-Invoicing Guidelines, Ministerial Decisions and PINT-AE.
49 listed mandatory fields for an electronic Tax Invoice and 51 for a commercial Electronic Invoice (XML).
MoF baseline fields are checked separately from PINT-AE conditional rules triggered by the transaction.
Field coverage and mapping readiness here; full Schematron and validator testing remains Tool 06.
Verification Method
Choose Tax Invoice or Commercial Electronic Invoice (XML), document type and relevant transaction context.
Use ERP JSON for source mapping, PDF for source-document coverage, or XML for structured PINT-AE mapping verification.
The tool normalizes source labels and checks them against the relevant MoF mandatory-field register.
Identify missing required fields, conditional PINT-AE reviews, unmapped source data and remediation priorities.
Interactive Field Verification
The verification engine now applies different evidence rules to JSON, PDF and XML. PDF mode no longer treats every detected label as “Found & Mapped”: it distinguishes explicit printed evidence, legitimate derivations, items requiring professional review and fields that cannot be evidenced from a human-readable PDF.
Official MoF field baseline with ERP-neutral semantic mapping, source-specific evidence classification and repeated-line coverage.
| No. | Official MoF Field | Domain | Status | Detected / Derived Value | Evidence & Mapping Note |
|---|
Official MoF field baseline with ERP-neutral semantic mapping, source-specific evidence classification and repeated-line coverage.
| No. | Official MoF Field | Domain | Status | Detected / Derived Value | Evidence & Mapping Note |
|---|
Result Interpretation
Can the ERP or integration payload expose the required source data in a consistent, mappable structure?
Does the existing invoice document visibly contain the information needed to support structured e-Invoicing?
Has the required data reached the expected PINT-AE / UBL structures in the generated XML?
Does the final XML pass complete syntax, Schematron, code-list, arithmetic and applicable business-rule validation?
Professional ERP & PINT-AE Review
PTG can review ERP source fields, customer and company master data, invoice-line data, tax configuration, transformation logic, PINT-AE business terms, XML mapping and ASP integration requirements and prepare an implementation-ready remediation register.
No. The PDF upload is used only to assess visible source-document field coverage. The MoF definition requires an Electronic Invoice to be issued, transmitted and received through the Electronic Invoicing System in a structured electronic format capable of automatic processing.
JSON is used to assess whether the ERP/source payload contains mappable data. XML is used to assess whether those values have reached the structured UBL/PINT-AE locations expected by the implementation.
No. Coverage only indicates that the fields checked by this tool were detected or mapped. Full PINT-AE validation also requires applicable business rules, code lists, arithmetic, syntax and Schematron validation.
The tool separately reviews selected PINT-AE rules whose requirement depends on transaction context, such as credit notes, free-trade-zone flags, reverse charge, exempt VAT lines, passport registration type or use of an invoicing period.
This browser prototype is designed for text-based PDFs. Image-only or scanned invoices may return incomplete results and should be checked manually or from the source ERP data.
