UAE & Compliance

PINT AE Explained: The UAE E-Invoice Data Standard, Field by Field

Every UAE e-invoice is a PINT AE document underneath. This is the field-by-field guide finance and ERP teams need before go-live.

Gautam Borad

Founder at Predflow

PINT AE invoice showing seller TRN, invoice line, tax category and tax total fields

Every UAE e-invoice is a PINT AE document underneath. This is the field-by-field guide finance and ERP teams need before go-live.


PINT AE invoice showing seller TRN, invoice line, tax category and tax total fields

PINT AE is the data standard behind every UAE e-invoice. The name stands for the UAE specialisation of the Peppol International Invoice model (PINT). When your ERP sends an invoice to your Accredited Service Provider (ASP) from 2027, the ASP checks the data against PINT AE rules before passing the invoice to your buyer's ASP and reporting tax data to the FTA. An invoice missing a required field or carrying a wrong code gets rejected.

This guide walks through PINT AE field by field: what the standard covers, the main field groups with example values, an annotated XML sample, document types, the errors behind most rejections, and where ERP data usually breaks during mapping.

What Is PINT AE?

What is PINT AE? PINT AE is the UAE version of the Peppol International Invoice model. PINT AE defines the fields, codes and business rules every UAE e-invoice must follow. Accredited Service Providers validate each invoice against PINT AE before sending the invoice to the buyer, and the Ministry of Finance data dictionary lists 51 mandatory fields for tax invoices.

Peppol is an international network and set of standards for exchanging business documents. PINT is the Peppol International Invoice model, a common core of invoice fields shared across countries. Each country adds its own rules on top. PINT AE is the UAE version.

Under the UAE five-corner model, the supplier's system sends invoice data to the supplier's ASP. The supplier's ASP validates the data and sends the e-invoice to the buyer's ASP, which delivers the invoice to the buyer. The FTA receives tax data from the ASPs, which makes the FTA the fifth corner.

Key facts about PINT AE:

  • The Ministry of Finance data dictionary lists 51 mandatory fields for tax invoices and 49 for commercial invoices.

  • The syntax is UBL XML, the same structure used across the Peppol network.

  • Field names follow the PINT convention. Shared fields carry IBT and IBG identifiers. UAE-specific fields carry BTAE identifiers.

  • Each participant gets a Peppol electronic address under scheme 0235, based on the 10-digit tax identification number.

  • Validation runs automatically through Schematron business rules before an invoice moves across the network.

Read the 60-day e-invoicing readiness plan for who is in scope and when.

Which Fields Does a PINT AE Invoice Need?

The data dictionary groups fields by purpose. The table below lists the main groups, whether the group is required on a standard tax invoice, and an example value. Check exact field names and cardinality against the published specification before you build your mapping.

Field group

Example fields

Required?

Example value

Invoice metadata

Invoice number, issue date, invoice type code, currency

Yes

INV-2026-10452, 2027-01-14, 380, AED

Transaction type

Eight-position flag code for special cases

Yes

00000000 for a standard supply

Seller identity

Legal name, TRN, electronic address, postal address

Yes

Sample Seller LLC, 100000000000001, 0235 address

Buyer identity

Legal name, TRN where registered, electronic address, address

Yes for B2B

Sample Buyer LLC, 100000000000002

Line items

Line ID, item name, quantity, unit code, net price, line amount

Yes, one or more lines

1, Steel pipe 2 inch, 50, EA, 120.00, 6,000.00

Line tax

Tax category code and rate per line

Yes

S, 5

Document totals

Sum of lines, allowances, charges, total without tax, tax amount, payable amount

Yes

6,000.00, 300.00, 6,300.00

Tax breakdown

Taxable amount and tax amount per category

Yes

S: 6,000.00 taxable, 300.00 tax

Tax total in AED

Tax amount in accounting currency when invoice currency differs

Conditional

Required when the invoice is in USD or EUR

Payment terms

Due date, payment means, bank account

Conditional

2027-02-13, credit transfer, IBAN

Preceding invoice reference

Original invoice number and date

Required on credit notes

INV-2026-09877, 2026-12-02

Tax Category Codes

Each line carries a tax category code from the UNCL5305 list. The common ones:

Code

Meaning

Rate

S

Standard rated

5%

Z

Zero rated

0%

E

Exempt

Not applicable

O

Outside the scope of VAT

Not applicable

AE

Reverse charge

0% on the invoice, buyer accounts for VAT

A free-text tax code in your ERP, such as "VAT5" or "Std", needs a mapping to one of these codes.

Transaction Type Flags

The transaction type is an eight-position code. Each position switches on a special feature of the transaction, such as a free zone supply, a margin scheme, a deemed supply, a continuous supply, disclosed agent billing, e-commerce, a summary invoice or an export. A standard domestic B2B sale sets every position to zero. Wrong flags cause validation failures or wrong tax treatment, so map them from real transaction attributes in your ERP rather than setting one default.


How a PINT AE E-Invoice Travels

Infographic in text: How a PINT AE E-Invoice Travels. The UAE five-corner model, with validation at every ASP.

  1. Supplier ERP: Produces invoice data with 51 mandatory fields.

  2. Supplier ASP: Validates against PINT AE rules.

  3. Buyer ASP: Receives over the Peppol network.

  4. Buyer ERP: Posts the structured invoice.

  • Corner 5: the FTA: Receives tax data from the ASPs in near real time. No PDF, no email attachment.

  • Most rejections come from data: Wrong TRN, missing tax category code, rounding, no AED tax total, duplicate numbers, missing credit note reference.

An Annotated PINT AE XML Sample

The sample below shows three parts of a simplified PINT AE invoice: the header with the seller block, one invoice line, and the tax total. Element names follow UBL. Values are illustrative. Confirm every identifier and code against the current specification and your ASP's documentation.

<Invoice>

  <cbc:CustomizationID>urn:peppol:pint:billing-1@ae-1</cbc:CustomizationID>

  <cbc:ID>INV-2026-10452</cbc:ID>                    <!-- invoice number -->

  <cbc:IssueDate>2027-01-14</cbc:IssueDate>

  <cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>     <!-- 380 = tax invoice -->

  <cbc:DocumentCurrencyCode>AED</cbc:DocumentCurrencyCode>

 

  <cac:AccountingSupplierParty>                      <!-- seller block -->

    <cac:Party>

      <cbc:EndpointID schemeID="0235">1000000000</cbc:EndpointID>

      <cac:PartyTaxScheme>

        <cbc:CompanyID>100000000000001</cbc:CompanyID>   <!-- seller TRN -->

        <cac:TaxScheme><cbc:ID>VAT</cbc:ID></cac:TaxScheme>

      </cac:PartyTaxScheme>

      <cac:PartyLegalEntity>

        <cbc:RegistrationName>Sample Seller LLC</cbc:RegistrationName>

      </cac:PartyLegalEntity>

    </cac:Party>

  </cac:AccountingSupplierParty>

 

  <cac:TaxTotal>                                     <!-- tax total -->

    <cbc:TaxAmount currencyID="AED">300.00</cbc:TaxAmount>

    <cac:TaxSubtotal>

      <cbc:TaxableAmount currencyID="AED">6000.00</cbc:TaxableAmount>

      <cbc:TaxAmount currencyID="AED">300.00</cbc:TaxAmount>

      <cac:TaxCategory>

        <cbc:ID>S</cbc:ID><cbc:Percent>5</cbc:Percent>

      </cac:TaxCategory>

    </cac:TaxSubtotal>

  </cac:TaxTotal>

 

  <cac:InvoiceLine>                                  <!-- one invoice line -->

    <cbc:ID>1</cbc:ID>

    <cbc:InvoicedQuantity unitCode="EA">50</cbc:InvoicedQuantity>

    <cbc:LineExtensionAmount currencyID="AED">6000.00</cbc:LineExtensionAmount>

    <cac:Item>

      <cbc:Name>Steel pipe 2 inch</cbc:Name>

      <cac:ClassifiedTaxCategory>

        <cbc:ID>S</cbc:ID><cbc:Percent>5</cbc:Percent>

      </cac:ClassifiedTaxCategory>

    </cac:Item>

    <cac:Price><cbc:PriceAmount currencyID="AED">120.00</cbc:PriceAmount></cac:Price>

  </cac:InvoiceLine>

</Invoice>

Your team does not need to write XML by hand. Your ERP or your ASP connector produces the file. Your team does need the ERP to hold the right data for every field.

Which Document Types Does PINT AE Cover?

Type code

Document

When to use

380

Tax invoice

Standard B2B supply within scope

381

Tax credit note

Reduce or cancel a tax invoice

480

Commercial invoice, out of scope

Supplies outside UAE VAT scope

81

Credit note, out of scope

Reduce a commercial invoice

Self-billing also fits within PINT AE, where the buyer issues the invoice on behalf of the supplier under an agreement.

Corrections follow a strict rule: you cannot reverse an invoice with negative lines. Issue a credit note with a reason and a reference to the original invoice. Credit notes carry the type code 381 and the original invoice number and date.

Why Do PINT AE Invoices Get Rejected?

  1. Wrong TRN format. Fewer than 15 digits, spaces, or a TRN for a different entity. Clean your vendor and customer masters first. Our bulk TRN verification guide covers the method.

  2. Missing tax category code. A line with no S, Z, E, O or AE code fails validation.

  3. Rounding mismatches. Line totals rounded one way and the document total another. The sum of lines must equal the total.

  4. No AED tax amount on foreign currency invoices. An invoice in USD needs the tax total in AED.

  5. Duplicate invoice numbers. Two branches or two ERP series issuing the same number.

  6. Credit note without a preceding invoice reference. The original invoice number and date must be present.

  7. Wrong transaction type flags. A free zone or export supply flagged as standard, or the reverse.

  8. Invalid unit codes. Free-text units such as "pcs" or "ctn" instead of standard codes.

Mapping Your ERP Fields to PINT AE: Where the Mapping Breaks

Most of the work in a PINT AE project is data, not technology. Three areas break most often.

Free-Text Tax Codes

ERPs set up years ago often hold tax codes typed by different people: "5%", "VAT 5", "Standard", "SR". Each needs mapping to a PINT AE code, and some lines need splitting where one code covered two treatments.

Missing Buyer TRNs

Customer masters built for PDF invoicing often lack the buyer TRN, or hold the TRN in a notes field. Every B2B e-invoice needs the buyer TRN where the buyer is registered.

Multi-Currency Invoices

Invoices in USD or EUR need the exchange rate and the tax amount in AED. ERPs storing only the document currency need a new field or a calculation in the connector.

Predflow builds agents to handle this clean-up on your ERP: reading the customer and vendor masters to flag gaps, mapping tax codes, and triaging rejections from your ASP after go-live. A person approves every change. Read more about UAE e-invoicing requirements.

Where PINT AE Meets Your Sales Documents

PINT AE covers the tax invoice, but the data starts earlier. The buyer reference, item descriptions, prices and discounts on an e-invoice usually come from the quotation and the customer's LPO. Errors made at quote or order stage travel into the e-invoice and cause rejections or disputes later.

Two fields deserve attention. The purchase order reference lets your customer's AP team match the invoice to their LPO. Item descriptions should match what the customer ordered, since the buyer sees them in structured form and their systems often match on them. Read our guide to quotation format, proforma and tax invoices for how the documents connect before the invoice.

Build one test case per invoice type you issue. A standard sale, a zero-rated export, a free zone supply, a foreign currency invoice and a credit note against a partial return cover most UAE trading companies.

How Does Predflow Help With PINT AE Readiness?

Predflow is an AI agent development company. Predflow builds and runs AI agents for businesses in the UAE, India and the US, on the ERP and tools each business already uses, to save time and cost on repetitive work. Predflow builds agents which map tax codes to PINT AE categories and triage rejections from your ASP, with your finance team approving each change. On invoice processing in SAP, a Predflow agent cut AP processing time by 92%. Read the SAP case study.

Conclusion

PINT AE defines what a UAE e-invoice must contain, from the 51 mandatory fields on a tax invoice to the tax category codes and transaction type flags. Your ASP validates every invoice against these rules before the invoice moves.

The fastest route to clean go-live is to map your ERP fields early, fix master data before testing, and run real invoices through validation before 1 January 2027. Rejections found in testing cost far less than rejections in production.

Sources

Bring 20 invoices to a 30-minute PINT AE field check

We will map your actual invoice fields to PINT AE on the call and show you which ones would fail validation at your service provider. No prep beyond an invoice export from your ERP.

Frequently Asked Questions

Is PINT AE the same as Peppol BIS?

They are different standards. Peppol BIS Billing 3.0 is the European standard on the Peppol network. PINT is the international invoice model, and PINT AE is the UAE version, with UAE fields such as transaction type flags and the TRN. Both use UBL XML, but the rules and required fields differ.

What format does a PINT AE invoice use?

PINT AE invoices use UBL XML, the same syntax used across the Peppol network. Your ERP or ASP connector produces the XML file from your invoice data. Your ASP validates the file before sending the invoice to the buyer's ASP.

Who validates PINT AE invoices?

Your Accredited Service Provider validates each invoice against the PINT AE rules before sending the invoice across the Peppol network. The buyer's ASP receives the validated invoice, and tax data goes to the FTA. Rejected invoices come back to you with error codes for correction.

How many mandatory fields does PINT AE have?

The Ministry of Finance data dictionary lists 51 mandatory fields for tax invoices and 49 for commercial invoices. Some further fields become mandatory under conditions, for example the AED tax amount on foreign currency invoices or the preceding invoice reference on credit notes.

Do I need to build PINT AE XML myself?

Your ERP vendor or ASP connector generates the XML. Your responsibility is the data behind each field, from correct TRNs and mapped tax codes to unique invoice numbers and valid credit note references. Most go-live problems come from master data, not from the XML.

Does PINT AE apply to B2C invoices?

The first phases of UAE e-invoicing cover B2B and B2G transactions. B2C transactions are out of scope until further notice, so consumer invoices do not need to follow PINT AE for now. Businesses selling to both groups apply PINT AE to their B2B invoices only.

More on: