PINT Mapping: field reference
The PINT Mapping screen sorts every field of a UAE e-invoice into four groups. This page explains each group — what it is, who fills it in and what, if anything, you need to do — and lists every field in it, named exactly as the screen names it.
The four groups at a glance
Read the screen from top to bottom and the work gets lighter as you go: the first group needs nothing from you, the second needs a quick check, and the last two only matter for some invoices.
System-managed Fields
30 fieldsFixed codes, your company's own details and amounts we calculate. They are shown so you can see the whole invoice, not so you can change them.
- Filled by
- TaxStar fills them in
- You do
- Nothing. Read-only.
Mandatory Fields
25 fieldsEvery UAE e-invoice carries these: number, dates, currency, customer, totals and lines. Each row says where in your ERP's invoice the value is read from.
- Filled by
- Your ERP supplies them
- You do
- Point each one at a field in your ERP. Pre-fill does most of it.
Conditional Fields
43 fieldsNeeded by some invoices only — exports, credit notes, payment by bank transfer, free zone supplies. A group you never use can stay empty.
- Filled by
- Your ERP, or a value you set once
- You do
- Set up only the groups that match the invoices you issue.
Optional Fields
10 fieldsExtra details the regulations allow but never require, such as a contract reference or payment terms. Nothing is rejected for leaving them out.
- Filled by
- Your ERP, if you choose
- You do
- Add one only if you want it printed on the invoice.
Type a name or a PINT id from the screen or from an error message, for example or .
How to read a row
IBT-048- The field the invoice needs, in plain words.
- Its PINT id — the official name in the UAE e-invoice standard. Error messages often quote it, so it is how you match a rejection to a row.
- Where to read it from — a field in your own ERP’s invoice. The list is grouped and searchable; the part in brackets is the exact path.
Rows answer in one of four ways, and you can tell which at a glance:
| Row looks like | What you do |
|---|---|
| A searchable list | Pick the field in your ERP that holds the value. Most rows. |
| A short list of codes | Choose one value. It is used on every invoice — for example TL for a trade licence. |
| A text box | Type one value. It is used on every invoice — for example your IBAN. |
| Grey, with a lock | Nothing. The platform fills it in. These are the system-managed fields. |
The quick way through the screen
- Click Pre-fill defaults. Every mandatory row is filled in with the usual place your ERP keeps that value.
- Open System-managed Fields once and check nothing says Not set. If something does, complete your entity's details.
- Read down Mandatory Fields and correct any row that points at the wrong place in your ERP.
- In Conditional Fields, set up only the groups that match invoices you issue.
- Add any Optional Fields you want printed, then click Save mappings. Nothing is used until you save.
The progress badges at the top count what is done, for example 23/23 mandatory. Two mandatory rows — the transaction type and the unit of measure — are not counted, because a safe value is sent when they are left empty.
System-managed Fields
These rows are grey, carry a lock, and cannot be edited. The section is collapsed by default on the screen because there is nothing to do in it. Each row shows the value that will be sent and a tag saying where it comes from:
| Tag | Means |
|---|---|
| Constant | A fixed code the UAE format requires. It is the same on every invoice. |
| Entity registration | Read from your company's details in TaxStar — the name, TRN and address you entered when you added the entity. |
| Computed | Calculated from the amounts and tax on the invoice itself. |
| Derived | Worked out from something else we already know, such as your country. |
| Self-billing | A different fixed code, used instead of the normal one when self-billing is switched on for the entity. |
| Field | PINT id | Source | Value sent |
|---|---|---|---|
| Invoice Details | |||
| Invoice type code | IBT-003 | Constant | 380 for an invoice, 381 for a credit note, 480 when every line of an invoice is exempt or out of scope, and 81 for such a credit note. With self-billing on: 389 and 261. |
| Business process type | IBT-023 | Constant | urn:peppol:bis:billing (urn:peppol:bis:selfbilling with self-billing on) |
| Specification identifier | IBT-024 | Constant | urn:peppol:pint:billing-1@ae-1 (urn:peppol:pint:selfbilling-1@ae-1 with self-billing on) |
| Seller Details | |||
| Seller name | IBT-027 | Entity registration | Your organisation name in the connected ERP, or the entity's company name |
| Seller electronic address | IBT-034 | Entity registration | Your Peppol address — the first 10 digits of your TRN |
| Seller electronic identifier | IBT-034-1 | Derived | The address scheme for your country |
| Seller legal registration identifier | IBT-030 | Entity registration | The first 10 digits of your TRN, unless you set a legal registration on the entity |
| Seller legal registration identifier type | IBT-030-1 | Derived | The registration scheme for your country |
| Seller tax identifier | IBT-031 | Entity registration | Your 15-digit TRN |
| Seller address line 1 | IBT-035 | Entity registration | Area (or street, if area is empty) |
| Seller city | IBT-037 | Entity registration | City |
| Seller country subdivision | IBT-039 | Entity registration | State / emirate |
| Seller country code | IBT-040 | Constant | AE |
| Buyer Details | |||
| Buyer tax scheme code | IBT-048-1 | Constant | VAT |
| Tax Breakdown | |||
| Tax category code | IBT-118 | Computed | From the tax on each line, using your Tax Codes setup |
| Tax category rate | IBT-119 | Computed | From the tax on each line |
| Invoice Line | |||
| Item gross price | IBT-148 | Computed | From the line's price and discount |
| Item price base quantity | IBT-149 | Constant | 1 |
| Invoiced item tax category code | IBT-151 | Computed | From the line's tax |
| Invoiced item tax rate | IBT-152 | Computed | From the line's tax |
| VAT line amount in AED | BTUAE-08 | Computed | The line's VAT converted to AED |
| Invoice line amount in AED | BTUAE-10 | Computed | The line amount converted to AED |
| Currency | |||
| Tax accounting currency | IBT-006 | Constant | AED — added only when the invoice is in another currency |
| Invoice total tax amount in accounting currency | IBT-111 | Computed | On a non-AED invoice, the VAT total converted to AED |
| Accounting currency code | SB-AUTO-70 | Constant | AED |
| Document currency code | SB-AUTO-80 | Computed | The invoice's own currency |
| Item Classification | |||
| Item classification scheme identifier | IBT-158-1 | Constant | HS — sent whenever an HS code is present |
| Service accounting code scheme identifier | BTUAE-17-1 | Constant | SAC — sent whenever a service accounting code is present |
| Reverse Charge | |||
| Item standard identifier (RCM) | IBT-157 | Derived | Each reverse-charge line's item code, or the GTIN you enter for it on Staged Invoices |
| Item standard identifier scheme | IBT-157-1 | Constant | 0160 (GTIN) |
If a row says “Not set”
The value comes from your entity and the entity does not have it yet — most often the area, city or emirate. Edit the entity, fill it in, and the row updates on its own. Until then, invoices are rejected for the missing seller detail.
Mandatory Fields
Every invoice must carry these. Each row is a list of the fields in your ERP's invoice; you pick the one that holds the value. Pre-fill defaults fills them all in with the standard location for your system — pick your ERP below to see what it chooses.
| Field | PINT id | What it is | Pre-filled from (Xero) |
|---|---|---|---|
| Invoice Details | |||
| Invoice number | IBT-001 | Your invoice number. Must be unique per invoice. | Invoice NumberInvoiceNumber |
| Invoice issue date | IBT-002 | The date the invoice was issued. | Invoice DateDateString |
| Invoice currency code | IBT-005 | The currency the invoice is written in, for example AED or USD. | Currency CodeCurrencyCode |
| Invoice transaction type code | BTUAE-02 | Flags special transaction types. Leave it unmapped for an ordinary invoice.Can be left empty: 00000000 (an ordinary invoice) is sent when it is not mapped. | Not pre-filled |
| Payment due date | IBT-009 | The date payment is due. | Due DateDueDateString |
| Buyer Details | |||
| Buyer name | IBT-044 | Your customer's name. | Contact NameContact.Name |
| Buyer tax identifier | IBT-048 | Your customer's 15-digit TRN. Also decides where on the Peppol network the invoice is delivered. | Contact Tax NumberContact.TaxNumber |
| Buyer address line 1 | IBT-050 | The first line of your customer's address. | Street Address Line 1Contact.Addresses[STREET].AddressLine1 |
| Buyer city | IBT-052 | Your customer's city. | Street CityContact.Addresses[STREET].City |
| Buyer country subdivision | IBT-054 | Your customer's state or region. For a UAE customer, the emirate. | Street Region / StateContact.Addresses[STREET].Region |
| Buyer country code | IBT-055 | Your customer's country. | Street CountryContact.Addresses[STREET].Country |
| Document Totals | |||
| Sum of invoice line net amount | IBT-106 | All line amounts added up, before tax. | Sub TotalSubTotal |
| Invoice total amount without tax | IBT-109 | The invoice total before tax. | Sub TotalSubTotal |
| Invoice total tax amount | IBT-110 | The total VAT on the invoice. | Total TaxTotalTax |
| Invoice total amount with tax | IBT-112 | The invoice total including tax. | TotalTotal |
| Amount due for payment | IBT-115 | What the customer still has to pay. | Amount DueAmountDue |
| Tax Breakdown | |||
| Tax category taxable amount | IBT-116 | The amount VAT is charged on. | Sub TotalSubTotal |
| Tax category tax amount | IBT-117 | The VAT charged on that amount. | Total TaxTotalTax |
| Invoice Line | |||
| Invoice line identifier | IBT-126 | An id for each line, unique within the invoice. | Line Item IDLineItems[].LineItemID |
| Invoiced quantity | IBT-129 | How many units the line is for. | QuantityLineItems[].Quantity |
| Unit of measure code | IBT-130 | The unit the quantity is counted in, for example EA (each) or KGM.Can be left empty: EA (each) is sent when it is not mapped. | Not pre-filled |
| Invoice line net amount | IBT-131 | The line total before tax. | Line AmountLineItems[].LineAmount |
| Item net price | IBT-146 | The price of one unit, before tax. | Unit AmountLineItems[].UnitAmount |
| Item name | IBT-153 | The name of the product or service on the line. | Item NameLineItems[].Item.Name |
| Item description | IBT-154 | A longer description of the line. | DescriptionLineItems[].Description |
When you would change a mandatory row
Only when your business keeps a value somewhere unusual — the customer's TRN in a second custom field instead of the first, or the item name in the description. The per-ERP setup each default assumes is on ERP prerequisites.
If a mandatory value is missing when an invoice arrives, the invoice is not sent. It fails validation with a message that names the missing field — see When an invoice fails.
Conditional Fields
Conditional fields are only needed by some invoices. They are arranged in groups, and each group says which invoices need it. A field inside a group becomes required only when the invoice matches the group's condition — so a plain domestic invoice is never held up for an export field.
Some rows reveal others: choosing 30 for the payment means opens the bank details, and choosing Goods as the item type makes the HS code required. Changing that first choice clears the rows it opened.
Click a group to see its fields.
CurrencyNeeded when: Invoices not in AED.1 field
- Currency exchange rate
BTUAE-04Pick an ERP fieldApplies only to invoices that are not in AED. Locked while the entity uses the Central Bank rate — see Exchange rate.
Seller Legal RegistrationNeeded when: Every invoice from a UAE seller. Set once.3 fields
- Seller legal registration identifier type
BTUAE-15Choose a valueWhich document your company's registration number comes from. Required for UAE sellers; most use the trade licence. Choices: TL (trade licence), EID (Emirates ID), PAS (passport), CD (cabinet decision). Default TL.
- Authority name
BTUAE-12Type a valueShown when the type is TL. The authority that issued your trade licence, for example Department of Economic Development. Default Ministry of Economy.
- Passport issuing country code
BTUAE-18Type a valueShown when the type is PAS. Two-letter code of the country that issued the passport, for example AE, IN, GB.
Seller Tax RegistrationNeeded when: Only a seller with no VAT TRN, such as on an out-of-scope invoice.2 fields
- Seller tax registration identifier (TIN)
IBT-032Type a valueEnter the 10-digit Tax Identification Number, which starts with 1. Leave blank if you have a TRN.
- Seller tax scheme code (for TIN)
IBT-031-1Type a valueOnly when you entered a TIN above. Name the scheme it belongs to; it cannot be VAT. Ignored when your company has a VAT TRN.
Buyer Legal RegistrationNeeded when: Invoices to UAE customers. Set once.4 fields
- Buyer legal registration identifier type
BTUAE-16Choose a valueWhich document the customer's registration number comes from. Required for UAE customers; most use the trade licence. Default TL.
- Buyer authority name
BTUAE-11Type a valueShown when the type is TL. The authority that issued the customer's trade licence. Default Trade License issuing Authority.
- Buyer passport issuing country code
BTUAE-19Type a valueShown when the type is PAS. Two-letter country code, for example AE, IN, GB.
- Buyer trade license number
IBT-047Type a valueThe customer's trade licence number. Left blank, 0000000 is sent in its place. To read it from each invoice instead, enter path: followed by the invoice field name.
Payment MeansNeeded when: Every invoice. Not used on credit notes or deemed-supply documents.1 field
- Payment means type code
IBT-081Choose a valueHow the invoice will be paid: 1 (not specified), 30 (credit transfer) or 55 (card). Default 1. Choosing 30 or 55 opens the group below.
Credit Transfer PaymentNeeded when: Payment means type code is 30 (credit transfer).4 fields
- Payment account identifier
IBT-084Type a valueRequired. The account the payment goes to, usually the IBAN.
- Payment account scheme identifier
IBT-084-1Type a valueOptional. What kind of account number you entered above, for example IBAN.
- Payment account name
IBT-085Type a valueOptional. The name the account is held in.
- Payment service provider identifier
IBT-086Type a valueOptional. The bank's BIC/SWIFT code, for example ABORAEADXXX.
Payment CardNeeded when: Payment means type code is 55 (card).1 field
- Payment card primary account number
IBT-087Type a valueRequired. The primary account number of the card used to pay.
Item ClassificationNeeded when: You choose an item type. Choosing one makes the matching code required.5 fields
- Item type
BTUAE-13Choose a valueOptional. Marks the invoice lines as Goods, Services or Both.
- Item classification identifier (HS code)
IBT-158Pick an ERP fieldRequired when the item type is Goods or Both. Map the field holding each item's HS code.
- Service accounting code (SAC)
BTUAE-17Pick an ERP fieldRequired when the item type is Services or Both. Map the field holding each item's service accounting code.
- Item attribute name
IBT-160Pick an ERP fieldOptional. Name of an extra item property, for example Colour. Map this and the value together or not at all.
- Item attribute value
IBT-161Pick an ERP fieldOptional. Value of the item property named above, for example Blue.
ExportsNeeded when: Invoices to a customer outside the UAE.7 fields
- Buyer identifier
IBT-046Pick an ERP fieldExport invoices only. Either this or the legal registration identifier below is enough; neither is needed if the customer has no tax number.
- Buyer legal registration identifier
IBT-047Pick an ERP fieldExport invoices only, and normally already met by the default, the customer's tax number. Either this or the buyer identifier above is enough.
- Buyer electronic address
IBT-049Pick an ERP fieldLeave empty. The customer's e-invoicing address is worked out from their country and tax number. Fill it in only if your system stores the customer's own address.
- Buyer electronic address scheme identifier
IBT-049-1Pick an ERP fieldLeave empty unless you filled in the address above. It is worked out from the customer's country.
- Buyer legal registration identifier scheme identifier
IBT-047-1Pick an ERP fieldLeave empty for UAE customers. For a foreign customer, only if you know which registry issued their registration number.
- Incoterms (delivery terms)
BTAE-22Pick an ERP fieldOptional. The shipping terms, for example CIF, FOB or EXW. If you map it, it must hold a valid Incoterms code.
- Customs / export declaration reference
BTAE-21Pick an ERP fieldOptional. The customs or export declaration number. Shown on the invoice when mapped; nothing requires it.
Disclosed AgentNeeded when: You bill as a disclosed agent on behalf of a principal.1 field
- Principle ID
BTUAE-14Pick an ERP fieldThe principal's TRN: 15 digits starting with 1 and ending 03 or 001. It must differ from your own.
Free Trade ZoneNeeded when: A supply in a designated free trade zone.1 field
- Beneficiary ID
BTUAE-01Pick an ERP fieldThe TRN or TIN of the party the supply benefits.
Summary InvoiceNeeded when: One invoice covering a period of supplies.2 fields
- Invoicing period start date
IBT-073Pick an ERP fieldFirst day the invoice covers, as YYYY-MM-DD. The end date on its own is also accepted.
- Invoicing period end date
IBT-074Pick an ERP fieldLast day the invoice covers, as YYYY-MM-DD, and not before the start date.
Continuous SuppliesNeeded when: The billing frequency is Others.1 field
- Invoice note
IBT-022Pick an ERP fieldA free-text note printed on the document. Required when the billing frequency is Others, to say what that frequency is.
Delivery AddressNeeded when: E-commerce and export invoices.7 fields
- Deliver to address line 1
IBG-15Pick an ERP fieldStreet address the goods or services are delivered to.
- Deliver to country code
IBT-080Pick an ERP fieldRequired whenever a delivery address is given. Two-letter country code, for example AE, US.
- Deliver to address line 2
IBT-076Pick an ERP fieldOptional. A second delivery address line.
- Deliver to address line 3
IBT-165Pick an ERP fieldOptional. A third delivery address line.
- Deliver to city
IBT-077Pick an ERP fieldCity the goods or services are delivered to.
- Deliver to post code
IBT-078Pick an ERP fieldOptional. Postal code of the delivery address.
- Deliver to country subdivision
IBT-079Pick an ERP fieldState or region delivered to. For a UAE delivery it must be an emirate: AUH, DXB, SHJ, AJM, UAQ, RAK or FUJ.
Credit NoteNeeded when: Credit notes only.3 fields
- Credit note reason code
BTUAE-03Choose a valueChoose the reason the credit note was issued: DL8.61.1.A to DL8.61.1.E, or VD (volume discount).
- Preceding invoice reference
IBT-025Pick an ERP fieldRequired unless the reason is Volume discount. The number of the original invoice being credited.
- Preceding invoice issue date
IBT-026Pick an ERP fieldOptional. Issue date of the original invoice, as YYYY-MM-DD.
The exchange rate row is covered in detail on Exchange rate, and the credit note group on Credit notes.
Optional Fields
Optional fields are extra details you may want printed on the invoice. None are on the screen to begin with. Under Available Optional Fields, click a field (or drag it into the box below) to add it, then pick the ERP field it reads from. Remove one with its ✕.
| Field | PINT id | Add it when |
|---|---|---|
| Contract reference | IBT-012 | The invoice is issued under a contract and you want its reference on it. |
| Contract value | BTUAE-05 | You want the contract's total value shown alongside its reference. |
| Frequency of billing | BTUAE-06 | You bill a continuous supply on a schedule. Must hold one of DLY, WKY, Q15, MTH, Q45, Q60, QTR, HYR, YRL or OTH; OTH also needs an Invoice note (IBT-022) saying what the frequency is. |
| Payment terms | IBT-020 | You want written payment terms on the invoice, for example Net 30. |
| Deliver to party name | IBT-070 | Goods go to someone other than the buyer. |
| Deliver to location identifier | IBT-071 | The delivery point has its own identifier, such as a GLN. |
| Deliver to location scheme identifier | IBT-071-1 | You mapped a location identifier and need to say which scheme it uses. |
| Actual delivery date | IBT-072 | You want the delivery date printed separately from the invoice date. |
| Buyer identifier scheme identifier | IBT-046-1 | You mapped a buyer identifier and need to say which scheme it uses. |
| Item country of origin | IBT-159 | You want each item's country of origin shown, often for goods that are exported. |
An optional field you leave out, or map to a field that turns out empty on an invoice, is simply not printed. It never causes a rejection.
“Will be provided at invoice level”
The first entry in every list, in every group. Choose it when your ERP does not hold the value at all. The invoice is then read in and held on Staged Invoices; you type the value there and submit, and only then does it continue to validation and the Peppol network.
On a mandatory row this means every invoice waits for you. On a conditional or optional row, only the invoices that need that field wait. More on Sending invoices.
Tax Category Mapping
The last section on the screen. It is optional: it lets you say which of your ERP's line tax codes mean exempt or out-of-scope supplies. Lines whose code is not listed are treated as standard or zero rated from their rate. Pick the ERP field that holds each line's tax code, then add one row per code.
| Category | Means |
|---|---|
| S | Standard rated (5%) |
| Z | Zero rated (0%) |
| E | Exempt — also needs a reason: DL8.46.1 to DL8.46.4 |
| O | Out of scope / not subject |
| AE | Reverse charge |
| N | Margin scheme |
How your tax rates map to UAE categories in general is set on Tax Codes.
Common questions
Why can't I change a system-managed field?
Because the value is either fixed by the UAE standard, taken from your entity, or calculated from the invoice. Letting it be repointed would only let it go wrong. To change your own name, TRN or address, edit the entity — the row updates on its own.
A system-managed row says “Not set”. What do I do?
That detail is missing from your entity. Open the entity, fill in the missing name, area, city or emirate, and come back. Invoices are rejected while it is empty, so fix it before you send.
My ERP doesn't hold one of the mandatory fields.
Choose “Will be provided at invoice level” at the top of that row's list. Each invoice then waits on Staged Invoices for you to type the value in, and carries on once you submit it.
Do I have to fill in every conditional group?
No. Fill in the groups that match invoices you actually issue. If you never export, the Exports group can stay empty. If you do, an export invoice that needs a missing value is rejected and tells you which one.
What happens if I leave an optional field out?
Nothing. It is simply not printed on the invoice. No invoice is ever rejected for a missing optional field.
I changed the mapping. Are old invoices re-sent?
No. A change applies to invoices processed after you save. An invoice already sent stays as it was; if it was wrong, issue a credit note.
Who can change the mapping?
Admins and Editors on the entity. Approvers and Viewers can open the screen and read it, but cannot save.
Related
How to complete the screen for the first time, and what changing it later does: PINT Mapping. The setup each ERP needs before its defaults work: ERP prerequisites.