Article 7 of Ministerial Decision No. 243 of 2025 is the shortest operative article in the Decision: "The Electronic Invoice and Electronic Credit Note shall contain all the data fields and particulars, as prescribed by the Ministry." Eleven words of delegation producing, through the UAE E-Invoicing Guidelines V1.1, 51 mandatory fields for an Electronic Tax Invoice and 49 mandatory fields for an Electronic Commercial Invoice. Understanding the Article 7 delegation — and what the Ministry has prescribed in response — is the foundation of any PINT-AE data mapping exercise.

How the Article 7 Delegation Works

Article 7 does not enumerate the required data fields in MD 243 itself. Instead, it delegates the specification entirely to the Ministry. The Ministry discharges that delegation through the UAE Electronic Invoicing Guidelines, currently at Version 1.1 dated 1 June 2026. Section 12 of the Guidelines contains the authoritative mandatory field lists. The legal force of these field requirements derives from Article 7 of MD 243 — the Ministry's prescription under Article 7 is not advisory guidance. Failure to include a mandatory field in an Electronic Invoice is a failure to comply with the Decision.

This delegation structure has a practical consequence: the mandatory field list can be updated by the Ministry without amending MD 243. A new version of the Guidelines or a supplementary technical notice can add, remove, or modify mandatory fields without requiring a new Ministerial Decision. Businesses and ASPs should treat the Guidelines version number as a live compliance reference, not a static document signed off once during implementation.

The PINT-AE Field Architecture

The UAE Electronic Invoicing System operates on the PINT-AE BIS v1.0.2 billing specification, which is a UAE-specific adaptation of the Peppol International (PINT) billing standard. The standard is expressed in UBL 2.1 XML. Every mandatory data field corresponds to a UBL 2.1 element path and a business term code.

The 51 mandatory fields for an Electronic Tax Invoice are divided into header-level and line-level groups. Header-level fields cover the document as a whole: document type code (380 for an Electronic Tax Invoice), invoice date, invoice currency, buyer and seller identification, total amounts, and VAT summary. Line-level fields cover each invoice line: item description, quantity, unit price, line amount, VAT category code, and VAT amount.

UAE-specific extension fields — the BTAE fields — sit within the BT-EX (Extension) block of the UBL structure. These include the UAE-specific identifier for the Peppol Participant, the document level reference to the originating ERP document, and the UAE-specific VAT category sub-classification codes. The BTAE fields are mandatory where applicable. An Electronic Tax Invoice that contains all standard PINT fields but omits the required BTAE extension fields does not satisfy Article 7.

The 49-Field Commercial Invoice

The Electronic Commercial Invoice — document type code 480 — carries a slightly smaller mandatory field set: 49 fields versus 51 for the Tax Invoice. The two fields absent from the Commercial Invoice are the Tax Registration Number of the buyer (not mandatory because the Commercial Invoice applies to non-VAT transactions where the buyer TRN is irrelevant) and the Tax Invoice-specific narrative. All other structural requirements — structured XML format, PINT-AE schema conformance, schematron validation — apply equally to the Commercial Invoice. A Commercial Invoice in PDF format transmitted through an ASP does not satisfy Article 7. The format requirement is the same regardless of the transaction type.

Data Completeness: The Most Common Pre-Go-Live Gap

In practice, the Article 7 compliance challenge is not schema design — ASPs and ERP connectors handle the XML generation. The challenge is data completeness in the underlying master data. Several PINT-AE mandatory fields require data that most ERP systems do not currently hold or hold in a non-standard way.

The Peppol Participant Identifier of the Recipient (buyer's electronic address on the Peppol network) must appear on every outbound Electronic Invoice routed to a Peppol-connected buyer. This field does not exist in any current ERP customer master design. For each customer within scope of the electronic invoicing mandate, the Peppol Participant Identifier must be obtained (typically through the ASP's onboarding process or through the customer's own ASP) and stored against the customer record before invoice issuance begins.

The UAE Corporate Tax TIN — the Participant Identifier format used in the UAE Peppol network — must be held for both Issuer and Recipient on relevant transactions. The Emirate subdivision code (for the Issuer's address) is a UAE-specific field that requires the two-letter UAE emirate code rather than just an address. The item classification code (HS code or commodity code) is mandatory on line items where applicable.

Schematron Validation and Article 7 Compliance

The PINT-AE specification includes schematron validation rules — a machine-readable set of business rules applied against the generated XML before transmission. These rules check not only that mandatory fields are present but that they contain values conforming to defined code lists: VAT category codes, currency codes, unit of measure codes, Peppol identifier scheme codes, and others. A document that fails schematron validation cannot be successfully transmitted through the Electronic Invoicing System. The ASP will reject it at the point of transmission. Article 7 compliance therefore has a technical enforcement mechanism built into the network: a non-conforming document does not move.

This is a departure from the pre-e-invoicing model, where a Tax Invoice with an incorrect field could be issued and circulated before any error was detected. Under the Electronic Invoicing System, the mandatory field and format requirements of Article 7 are enforced at the point of transmission — making pre-transmission data quality validation an operational necessity rather than a best practice.

Implications for ERP Configuration and Master Data

For SAP environments, Article 7 compliance requires: mapping PINT-AE business terms to SD and FI transaction fields, configuring the BTAE extension structure within the output determination framework, populating customer master records with Peppol Participant Identifiers, and configuring VAT condition types to produce the correct PINT-AE VAT category codes. For Oracle environments, the mapping exercise uses DFFs and transaction attributes in AR. For mid-market systems without UBL 2.1 output capability, the transformation is typically handled ASP-side through middleware — but only where the source system produces structured data in a format the ASP can map.

The Article 7 data field obligation is ultimately a data quality obligation as much as a technical one. The schematron rules will enforce technical format. The content of the fields — whether the HS code is correct, whether the VAT category accurately reflects the supply, whether the buyer's Peppol identifier is current — is the Issuer's responsibility, and it is not enforced by the transmission network. That content accuracy obligation traces directly back to Article 7: the invoice must contain all prescribed particulars, not just the correct structure around empty or incorrect values.