UAE PINT AE rule explorer and SAP Business One field mapper
Look up any PINT AE rule ID from your validator or service provider, read the official rule, and see which SAP Business One field usually feeds it.
Status:UAE e-invoicing is in preparation. Kodenova’s PINT AE integration for SAP Business One is ready / in preparation.
Tool
This explorer explains the published PINT AE Billing 1.0.4 specification. It is not an official tool of the UAE Ministry of Finance, the Federal Tax Authority, OpenPeppol or any Accredited Service Provider, and Kodenova is not an Accredited Service Provider. The official specification and your service provider's validation always prevail. SAP Business One field mappings are typical mappings; confirm them with your localization. UAE e-invoicing is in preparation. Kodenova is an independent SAP Business One, ERP and AI development studio; SAP and SAP Business One are trademarks of SAP SE.
How PINT AE rule IDs work
- IBR-nnn: shared PINT rules that every PINT invoice follows, from any country.
- IBR-nnn-AE: UAE-specific rules. The page for these rules says they must be applied by all UAE senders.
- ALIGNED-IBRP-…: shared rules that the UAE has aligned to its own needs, for example tax categories and the specification identifier.
- IBR-CL, IBR-CO, IBR-SR: code list, calculation and syntax rules.
- IBT, IBG and BTAE: business terms (fields), groups of terms, and UAE-only terms. BTAE-02, for example, is the 8-character invoice transaction type code.
In PINT AE 1.0.4 every Invoice rule is flagged fatal. A fatal rule failure means the invoice does not pass validation.
UAE rules SAP Business One teams hit most
| Rule | What it checks | Typical SAP B1 source |
|---|---|---|
| ALIGNED-IBRP-001-AE | Specification identifier starts with urn:peppol:pint:billing-1@ae-1 | Fixed value in the XML mapping |
| IBR-132-AE | VAT identifiers are a 15-digit TRN starting with 1 and ending with 03 | OADM.TaxIdNum, OCRD.LicTradNum |
| IBR-154-AE | Transaction type code (BTAE-02) is up to 8 characters of 0 and 1 | UDF on OINV |
| IBR-159-AE | Exchange rate is required when the invoice currency is not AED | OINV.DocRate |
| IBR-104-AE | Lines with VAT information carry line amount and VAT in AED | INV1.LineTotal, INV1.VatSum (local currency) |
| IBR-122-AE | Out-of-scope invoices (480) and credit notes type 81 use only E, O or Z categories | VAT group category UDF on OVTG |
| IBR-150-AE | Seller legal registration ID is required with Peppol scheme 0235 | UDF on OADM (trade licence) |
| IBR-158-AE | Credit notes carry a credit note reason code | UDF on ORIN |
| ALIGNED-IBRP-AE-01-AE | Reverse charge lines need a reverse charge VAT breakdown | INV1.VatGroup and the AE category UDF |
Search the tool for the full list of 302 rules.
How the SAP Business One field mapper works
Each rule message names the business terms it tests, such as IBT-151 (invoiced item VAT category code). The mapper links every term to the SAP Business One field that typically feeds it: the A/R invoice header (OINV) and lines (INV1), the invoice address (INV12), the business partner (OCRD), company details (OADM, ADM1) and VAT groups (OVTG). Some UAE terms, such as the transaction type flags, the TIN for the Peppol endpoint and the legal registration type, have no standard field and are usually user-defined fields.
Of the 207 terms the rules reference, 167 have a typical SAP Business One source in the mapper. The rest are optional or rare terms (payee, tax representative, payment card, direct debit) that most SAP Business One setups do not use.
This is a typical mapping; confirm it with your localization. For the 51 mandatory fields with their UBL paths, read our PINT AE data dictionary for SAP Business One.
Where the rules come from
All 302 rules, their messages and flags were read from the official PINT AE Billing specification, version 1.0.4, release date 2 June 2026, maintained by the United Arab Emirates (UAE) Peppol Authority and published on docs.peppol.eu (PDK 1.4.4, 29 July 2026). Term names come from the same specification’s Invoice semantic model.
What is not included: the Credit Note transaction rules, which are published separately, and any rules an Accredited Service Provider adds on top of the specification.
Check a whole invoice
To check a full XML file, use the UAE PINT AE invoice validator. For an overview of UAE e-invoicing with SAP Business One, see PINT AE e-invoicing in the UAE, our e-invoicing integration service and SAP Business One development.
Related pages
- PINT AE e-invoicing in the UAE
- E-invoicing integration
- SAP Business One development
- UAE PINT AE invoice validator
- PINT AE data dictionary for SAP Business One
- All free tools
This explorer explains the published PINT AE Billing 1.0.4 specification. It is not an official tool of the UAE Ministry of Finance, the Federal Tax Authority, OpenPeppol or any Accredited Service Provider, and Kodenova is not an Accredited Service Provider. The official specification and your service provider's validation always prevail. SAP Business One field mappings are typical mappings; confirm them with your localization. UAE e-invoicing is in preparation. Kodenova is an independent SAP Business One, ERP and AI development studio; SAP and SAP Business One are trademarks of SAP SE.
Three steps, no signup
Search a rule or a field
Type a rule ID like IBR-122-AE, a word like "reverse charge", a business term like IBT-048, or a SAP field like LicTradNum.
Read the official rule
Each rule shows the exact message from PINT AE 1.0.4, its flag, and a link to the rule page on docs.peppol.eu.
Map it to SAP Business One
See the business terms the rule tests and the SAP Business One table and field that typically feed each one.
Questions about this tool
What is a PINT AE validation rule?
It is a check that a UAE e-invoice must pass before it is exchanged over the Peppol network. Each rule has an ID such as IBR-132-AE, a message and a test on the UBL XML. PINT AE 1.0.4 has 302 rules for the Invoice transaction, and every one of them is flagged fatal in that version.
What does the AE suffix in a rule ID mean?
Rules ending in AE, such as IBR-122-AE, are specific to the United Arab Emirates. The specification says all UAE senders must apply them. Rules without the suffix, such as IBR-001, are shared PINT rules used by every country that adopts the Peppol international invoice model.
Which SAP Business One fields does PINT AE need?
Most values come from the A/R invoice (OINV, INV1, INV12), the business partner (OCRD) and company details (OADM, ADM1). UAE-only fields such as the 8-character transaction type flags, the 10-digit TIN for the Peppol endpoint and the legal registration type usually need user-defined fields. Confirm the mapping with your localization.
What does IBR-132-AE check?
IBR-132-AE says VAT identifiers, including the seller and buyer VAT numbers, should be a TRN of 15 digits, starting with 1 and ending with 03. In SAP Business One these usually come from the company tax ID (OADM.TaxIdNum) and the business partner tax ID (OCRD.LicTradNum). Spaces and dashes are a common cause.
Is UAE e-invoicing live yet?
No. UAE e-invoicing is in preparation, and Kodenova's PINT AE integration for SAP Business One is ready / in preparation. Check the Ministry of Finance for the current timeline for your business. This tool explains the published PINT AE 1.0.4 rules so your data is ready.
Is my data sent anywhere?
No. The search and the field mapper run in your browser, and nothing you type or paste is sent to Kodenova or any service provider. The tool explains rules; it does not validate or submit invoices. To check a full XML file, use our free UAE PINT AE invoice validator.
Built for SAP Business One teams
Preparing SAP Business One for UAE e-invoicing?
We map your SAP Business One documents to PINT AE, add the missing UAE fields and prepare the connection to the Accredited Service Provider you choose. Tell us about your setup.