SAP S/4HANA and ECC: mapping your data to UAE e-invoices
How billing documents, business partners and tax codes in SAP S/4HANA or ECC map to PINT AE fields.
In SAP S/4HANA and ECC, e-invoices are built from SD billing documents (invoices and credit memos). Tax comes from pricing and tax codes. Customer data comes from the business partner (S/4HANA) or customer master (ECC).
SAP Document and Reporting Compliance is SAP's own e-document framework, with the eDocument Cockpit for monitoring. If you use it, SAP's UAE content creates the XML. If you use an external connector, it reads the same billing data. Either way the mapping below applies conceptually. Check SAP's country availability notes for your release.
Where each e-invoice field comes from
| E-invoice field | Where it lives in SAP | What to check |
|---|---|---|
| IBT-031 Seller TRN | Company code global data (VAT registration number) | 15 digits, starts 1, ends 03 |
| IBT-034 Seller Peppol ID | Configuration of DRC or connector | 0235: + 10-digit TIN |
| IBT-039 Seller emirate | Company code address › Region | Region keys map to AUH…FUJ |
| IBT-048 Buyer TRN | Business partner › tax numbers (VAT registration number) | Present for VAT-registered and reverse-charge buyers |
| IBT-049 Buyer Peppol ID | Tax number, BP identification or custom field | Buyer TIN, or a 99000000xx receiver |
| IBT-047 / BTAE-11 Licence and authority | BP identification numbers or custom fields | Authority filled when a licence is sent |
| IBT-054 Buyer emirate | BP address › Region | Emirate code mapping |
| IBT-001 Invoice number | Billing document number | Number range unique per company code |
| IBT-003 Type code | Billing type, e.g. F2 invoice → 380, G2/RE credit memo → 381 |
Each billing type mapped |
| IBT-009 Due date | Calculated from payment terms | Present when amount is payable |
| IBT-154 Item description | Material description or item text | Not blank, including service materials |
| IBT-130 Unit code | Sales unit and its ISO code (transaction CUNI) | Internal PC often maps to ISO PCE; change the mapping to H87 or EA |
| IBT-157 GTIN | Material master EAN/UPC | Valid GTIN for reverse-charge goods |
| IBT-151 Tax category | Tax code from the pricing condition | One tax code per category |
| IBT-025 Preceding invoice | Reference billing document on the credit memo | Credit memo created with reference |
Tax category mapping
Tax codes are maintained in transaction FTXP. The code is determined from the customer tax classification and material tax classification.
| Category | Tax code example | Rate | How to drive it |
|---|---|---|---|
| S | A1 |
5% | Customer liable, material full tax |
| Z | A2 |
0% | Material or customer classification for zero-rated |
| E | A3 |
0% | Separate code; map to DL8.46.x reason |
| O | A4 |
0% | Out-of-scope classification |
| AE | A5 |
5% | Reverse-charge goods; buyer TRN, GTIN and goods type required |
Keep zero-rated and exempt on different tax codes. A shared 0% code cannot be mapped to two categories.
Special scenarios
- Exports: Transaction type
00000001; ship-to party address outside AE. See Exports. - Deemed supply: A dedicated BP with Peppol ID
9900000097, often with a free-of-charge billing type. See Deemed supply. - Credit notes: Create from the original invoice so the reference is kept. Map the order reason to
DL8.61.1.A–EorVD. See Credit notes. - Foreign currency: Maintain rates (transaction OB08). The XML needs the exchange rate and AED totals. See Foreign currency.
Before go-live
- Company code address has Region mapped to emirate codes.
- Business partners carry TRN, Peppol ID and Region.
- Tax codes separate S, Z, E, O and AE.
- ISO unit codes checked in CUNI; no
PCEorBOXleft. - Every billing type mapped to
380or381. - Order reasons for credit memos mapped to approved reason codes.
- Transaction type flags set per sales scenario.
- End-to-end test in a quality system before production.
Field names vary by version and configuration; confirm the mapping with your implementation partner.