SAP Business One: mapping your data to UAE e-invoices
Where each PINT AE field lives in SAP Business One and what to set up before go-live.
SAP Business One holds most e-invoice data in the Business Partner, Item and Company records. Fields with no standard home, such as the Peppol ID or goods-type code, are usually added as user-defined fields (UDFs) by your partner or connector.
Where each e-invoice field comes from
| E-invoice field | Where it lives in SAP Business One | What to check |
|---|---|---|
| IBT-031 Seller TRN | Administration › System Initialization › Company Details › Accounting Data (tax ID fields) | 15 digits, starts 1, ends 03 |
| IBT-034 Seller Peppol ID | Company Details or a connector setting | 0235: + first 10 digits of the TRN |
| IBT-039 Seller emirate | Company Details › address State | Emirate code, not the full name |
| IBT-048 Buyer TRN | Business Partner Master Data › Accounting › Tax › Federal Tax ID | Filled for every VAT-registered customer |
| IBT-049 Buyer Peppol ID | UDF on the Business Partner | Buyer TIN, or a 99000000xx receiver |
| IBT-047 / BTAE-11 Buyer licence and authority | UDFs on the Business Partner | Authority filled whenever a licence is |
| IBT-050–IBT-055 Buyer address | Business Partner › Addresses (Bill To) | Street, city, State = emirate, Country |
| IBT-001 Invoice number | Document Numbering series on the A/R Invoice | Unique; no reuse after cancellation |
| IBT-009 Due date | A/R Invoice › Due Date (from Payment Terms) | Present whenever an amount is payable |
| IBT-005 Currency | Document currency on the A/R Invoice | Rate exists for the posting date |
| IBT-153 / IBT-154 Item name and description | Item Master Data › Description, or row free text | Never blank, including service rows |
| IBT-130 Unit code | UoM on the row, mapped to a Rec 20 code | Map Box to XBX, Piece to H87 |
| IBT-157 GTIN | Item Master Data › Bar Code | 8, 12, 13 or 14 digits for reverse-charge goods |
| IBT-151 Tax category | Tax code on each row | One tax code per category (below) |
| IBT-084 IBAN | House Bank account | Present if payment means is 30 |
Tax category mapping
Set up codes in Administration › Setup › Financials › Tax › Tax Codes. Use a separate code for each category so the connector can map it.
| Category | Suggested tax code | Rate | Note |
|---|---|---|---|
| S | SR5 |
5% | Only S may carry 5% on a normal sale |
| Z | ZR |
0% | Keep separate from exempt |
| E | EX |
0% | Store the DL8.46.x reason on the code or a UDF |
| O | OS |
0% | Out of scope |
| AE | RC5 |
5% | Reverse charge. Needs buyer TRN, GTIN and goods type UDF |
Special scenarios
- Exports: Transaction type
00000001. The Ship To address must be outside AE with a country code. See Exports. - Deemed supply: Use a Business Partner with Peppol ID
9900000097. See Deemed supply. - Credit notes: Create the A/R Credit Memo with Copy From the original A/R Invoice so the reference carries over. Add the reason code (
DL8.61.1.A–EorVD) in a UDF. See Credit notes. - Foreign currency: Keep rates in Administration › Exchange Rates and Indexes. The XML needs the rate and AED totals. See Foreign currency.
Before go-live
- Company Details hold TRN, address with emirate code and trade licence.
- Every active customer has Federal Tax ID, Peppol ID and Bill To address with emirate.
- Tax codes exist for S, Z, E, O and AE, with no 5% code used for zero-rated items.
- Every sales UoM maps to a valid Rec 20 code.
- Reverse-charge items have a barcode (GTIN) and goods-type code.
- UDFs exist for transaction type flags and credit note reason.
- A test invoice and credit note pass validation in sandbox.
Field names vary by version and configuration; confirm the mapping with your implementation partner.