PINT AE Mandatory Fields Checker — Get the Exact Fields Your eInvoice Needs

The PINT AE mandatory fields are the 51 data points every UAE eInvoice must carry before an accredited service provider will let it onto the Peppol network. The field list itself never changes — what changes is the values you put in it, and that depends on who you are invoicing, where they are established and how the supply is treated for VAT. Get a code wrong and the invoice either fails validation outright or, worse, passes validation carrying the wrong tax treatment. The checker below resolves your scenario in three questions; the reference tables underneath are what your finance team should be working from. If you would rather hand the whole mapping exercise over, that is what our UAE eInvoicing readiness service does.

New to the format itself? Start with our full explainer on what PINT AE is and how the 5-corner model works, then come back here for the field-level detail.

How does the PINT AE mandatory fields checker work?

It maps your scenario onto the field values that actually differ. Three inputs — entity type, supply route and VAT considerations — are enough to determine your buyer-side identifier requirements, your tax category code, your invoice type code and whether the UAE-specific AED fields apply. The 51-field baseline is constant underneath all of it.

The six steps the checker works through

1. Confirm your entity type — free zone, mainland or government. This sets your baseline position and your seller-side identifiers.
2. Identify the supply route — UAE business, UAE government entity, overseas customer, designated zone recipient or consumer.
3. Apply the VAT treatment — select the tax category code that matches reality: S at 5%, Z zero-rated, E exempt, AE reverse charge or O outside scope.
4. Collect the buyer identifiers — request each B2B customer’s TRN and Peppol electronic address and store them against the customer master record.
5. Map the fields in your system — check your software can output all 51 fields, including unit of measure codes and the AED line amounts on foreign-currency invoices.
6. Test with your provider — run test invoices covering credit notes, exports and reverse-charge scenarios before your go-live date.

What are the 51 baseline PINT AE mandatory fields?

Fifty-one fields across six categories, and every one of them must be present and valid. The split is 9 invoice details, 11 seller details, 9 buyer details, 5 document totals, 4 tax breakdown fields and 13 invoice line fields. Miss one and the invoice is rejected at your sending provider before it ever reaches your customer.

Two of these deserve a flag because they are UAE-specific extensions rather than standard Peppol: VAT line amount in AED and invoice line amount in AED. They exist so that FTA reporting works in dirhams even when the invoice is raised in another currency. The dictionary itself is adopted under Ministerial Decision No. 243 of 2025, and a provider offering “generic Peppol” will not produce these fields — ask specifically for the UAE profile, and see our comparison of MoF-accredited service providers before you sign anything.

Which PINT AE tax category code applies to your supply?

The tax category code is the field that carries the most risk. It sits on every invoice line and in the tax breakdown, and it tells the FTA how you have treated the supply. The code list follows the standard used across Peppol implementations, and the code must reflect the actual VAT treatment under the UAE VAT law — not a default that someone set once and never revisited.

The distinction that costs businesses the most money is zero-rated versus exempt. Both show 0% on the invoice, so they look interchangeable to whoever is coding the item master — but a zero-rated supply preserves your right to recover input VAT and an exempt supply does not. Code a batch of zero-rated exports as exempt and you have quietly written off the input VAT attached to them. That error was recoverable when invoices were PDFs and nobody compared them; once transaction-level data reaches the FTA automatically, it is visible. If your VAT returns already involve a partial exemption calculation, treat the code mapping as a tax project rather than a data project.

Which invoice type code should a PINT AE eInvoice carry?

380 for a commercial invoice, 381 for a credit note. The invoice type code sits in the invoice details category and tells the receiving system what kind of document it is looking at. It follows the standard Peppol code list, and using the wrong one causes downstream matching failures in your customer's accounts payable system even when validation passes.

Credit notes are where readiness projects reliably come unstuck. In a PDF world a credit note is a document with the word "credit" on it; in PINT AE it is a structured document carrying type code 381 plus a reference to the original invoice number and date. If your accounting system currently produces credit notes as negative invoices, or as manually edited copies of the original, that has to be fixed before go-live — and it is a bookkeeping fix, not a software one. Our monthly bookkeeping team handles this kind of clean-up as part of the close.

Which PINT AE mandatory fields do free zone companies get wrong?

The field list is identical — the values are where free zone entities slip. There is no separate free zone profile in PINT AE and no exemption from the programme. A DMCC consultancy and a Bur Dubai mainland LLC populate the same 51 fields. What differs is the tax category code on certain movements of goods and, occasionally, the legal registration identifier type.

Three specifics worth checking before you go live. First, designated zone treatment: supplies of goods within or between UAE designated zones can fall outside the scope of VAT, which means code O rather than S — but the rules are fact-specific and turn on whether goods are consumed in the zone, so confirm the treatment per transaction type rather than applying a blanket rule. Second, your legal registration identifier is your free zone licence number, issued by your zone authority, and it must be recorded with the correct identifier type. Third, if you are not VAT-registered because you sit below the AED 375,000 mandatory registration threshold, you still need to establish your eInvoicing position — the phase timetable is driven by revenue, not by VAT status.

One myth to retire: QFZP status has nothing to do with eInvoicing. Qualifying Free Zone Person status determines whether qualifying income accesses the 0% corporate tax rate under strict substance and de minimis conditions. It does not exempt you from issuing structured eInvoices, and it does not change a single mandatory field. The overlap is practical rather than legal: the same audited, IFRS-compliant records that support a QFZP claim are far easier to produce when your invoice data is structured — something our free zone audit team sees every season.

What changes for exports and reverse-charge supplies?

Exports change your buyer fields and your tax category code; reverse charge changes who reports the VAT. Both scenarios keep all 51 mandatory fields in place — they simply carry different values, and both are routinely mis-coded because the person building the item master is not the person who understands the VAT treatment.

The trap in both cases is the same: a nil tax amount does not mean a nil taxable amount. The tax breakdown category still has to carry the taxable amount, the code and the rate, and those values still have to reconcile to the document totals. Invoices that show AED 0.00 in every tax field, including the taxable amount, are one of the most common validation failures we see in testing — and they are the kind of error that reconciles perfectly against a sales ledger while being completely wrong.

What if you invoice in USD instead of AED?

You can invoice in any currency, but you must also restate the line amounts in AED. This is where the two UAE-specific PINT AE fields earn their keep: VAT line amount in AED and invoice line amount in AED. Without them the FTA cannot report your transaction in dirhams, and a generic Peppol profile simply does not have the fields.

Worked example: a USD 30,000 export-adjacent invoice

A Dubai company invoices a UAE-established customer USD 30,000 for consultancy, standard-rated at 5%, converted at 3.6725 AED per USD:

Two practical points. Use a single documented exchange rate source and apply it consistently — ad hoc rates pulled from whatever a team member had open create differences that will surface when your eInvoice data is compared with your VAT return. And check the rounding rules your provider applies at line level versus document level; a half-fils difference repeated across 400 lines becomes a reconciliation item nobody wants to own at month-end.

When do the PINT AE mandatory fields become compulsory for you?

Your date is set by revenue, not by licence type, emirate or free zone. Under Ministerial Decision No. 244 of 2025, businesses at or above AED 50 million appoint an accredited service provider by 31 July 2026 and go live 1 January 2027. Everyone below that appoints by 31 March 2027 and goes live 1 July 2027. Government entities follow from 1 October 2027.

Use the gap between the two dates properly. It is the implementation and testing window, not slack — five months for phase 1, three for phase 2. The data work described on this page (buyer identifiers, unit of measure codes, tax category mapping, credit note handling) is what fills it, and none of it requires you to have signed a provider yet. Businesses that start the master-data clean-up during the voluntary window arrive at their go-live date with a testing exercise instead of a rescue project.

What happens when a PINT AE mandatory field is missing?

The invoice never leaves. Validation happens at your sending service provider before transmission, so a missing mandatory field means the document is rejected at source: your buyer does not receive it, the FTA is not notified, and the sale sits undocumented until someone notices and resends. There is no partial acceptance and no grace for a single blank field.

Worked example: what a rejected batch actually costs

A company issues 60 invoices in the last week of a quarter. Twelve are rejected because the buyer electronic address is missing on newly onboarded customers, and nobody monitors the provider's rejection queue over the weekend. Those twelve represent AED 220,000 of VAT. The return is filed two months late while the position is untangled. The first-offence late filing penalty is AED 1,000. Late payment runs at 14% per annum charged monthly under Cabinet Decision No. 129 of 2025: AED 220,000 × 14% ÷ 12 = AED 2,566.67 per month, so two months adds AED 5,133. Total AED 6,133 — before any eInvoicing penalty, and caused entirely by one unpopulated field.

The operational lesson matters more than the penalty table: somebody has to own the rejection queue daily. In a PDF world an invoice that failed to send still existed; in a structured world it does not. Build the check into the same routine that produces your VAT 201 return, filed within 28 days of your tax period end.

What are the most common PINT AE field errors we see?

Almost all of them are data errors made months before go-live. The technical connection rarely fails; the master data does. These are the six that account for most rejected test batches.

If you want to see what a fully populated structured invoice looks like before you commit to a provider, our free UAE e-invoice generator is a low-commitment sandbox, and if you are running Zoho we have documented the configuration in our Zoho Books eInvoicing guide.

PINT AE field glossary: what do TRN, UNCL codes and electronic addresses mean?

The field names are unfamiliar even to experienced UAE finance teams. This glossary covers the terms that appear in provider mapping documents and in the checker above.

Work through the checker for each invoice pattern you issue, hand the output to whoever owns your item and customer masters, and give them a deadline that sits comfortably before your provider testing window. If that is a job you would rather delegate, our eInvoicing readiness service covers the field mapping, the provider selection and the testing end to end.