Oracle E-Business Suite and Fusion Cloud ERP: mapping your data
How Oracle Receivables transactions, tax setup and customer sites map to PINT AE fields.
In both Oracle E-Business Suite (EBS) and Oracle Fusion Cloud ERP, e-invoices come from Receivables transactions. Tax comes from the tax engine (E-Business Tax in EBS, Oracle Fusion Tax in Fusion). The setup objects are similar.
Where each e-invoice field comes from
| E-invoice field | Where it lives in Oracle | What to check |
|---|---|---|
| IBT-031 Seller TRN | Party tax profile of the legal entity / first-party establishment | 15 digits, starts 1, ends 03 |
| IBT-034 Seller Peppol ID | Connector setting or descriptive flexfield | 0235: + 10-digit TIN |
| IBT-039 Seller emirate | Legal entity / location address | Emirate code |
| IBT-048 Buyer TRN | Customer party tax profile or site tax registration | Present for VAT-registered buyers |
| IBT-049 Buyer Peppol ID | Descriptive flexfield on customer account or site | Buyer TIN, or a 99000000xx receiver |
| IBT-047 / BTAE-11 Licence and authority | Flexfields on the customer | Authority filled with licence |
| IBT-050–IBT-055 Buyer address | Customer account Bill-To site | City, emirate code, country |
| IBT-001 Invoice number | Transaction number from the transaction source | Automatic numbering, unique |
| IBT-003 Type code | Transaction type class: Invoice → 380, Credit Memo → 381 |
Each type mapped |
| IBT-009 Due date | From payment terms | Present when amount is payable |
| IBT-154 Item description | Line description (inventory item or memo line) | Not blank |
| IBT-130 Unit code | Line unit of measure | Map UOM codes to Rec 20 (H87, EA, XBX) |
| IBT-157 GTIN | Item cross-reference or flexfield | Valid GTIN for reverse-charge goods |
| IBT-151 Tax category | Tax rate code on the line | One rate code per category |
| IBT-121 Exemption reason | Tax exemption / exemption reason | DL8.46.1–DL8.46.4 |
In Fusion, use the setup tasks such as Manage Transaction Types, Manage Transaction Sources, Manage Tax Regimes, Manage Tax Rates and Tax Recovery Rates, and Manage Party Tax Profiles.
Tax category mapping
Create a UAE tax regime and VAT tax, then tax statuses and rates.
| Category | Tax status / rate code | Rate | Note |
|---|---|---|---|
| S | AE VAT STANDARD |
5% | Default for domestic taxable sales |
| Z | AE VAT ZERO |
0% | Separate status from exempt |
| E | AE VAT EXEMPT |
0% | Link the exemption reason code |
| O | AE VAT OUT OF SCOPE |
0% | Or no tax line; map to O |
| AE | AE VAT REVERSE CHARGE |
5% | Needs buyer TRN, GTIN and goods type |
Use tax rules (for example by product fiscal classification or customer) to pick the right rate, rather than editing tax on each line.
Special scenarios
- Exports: Transaction type
00000001; Ship-To site outside AE. See Exports. - Deemed supply: A dedicated customer with Peppol ID
9900000097. See Deemed supply. - Credit notes: Credit the original transaction so the reference carries over. Map the credit memo reason to
DL8.61.1.A–EorVD. See Credit notes. - Foreign currency: Maintain daily rates. The XML needs the rate and AED totals. See Foreign currency.
Before go-live
- Legal entity party tax profile holds the TRN; address has emirate code.
- Customer Bill-To sites have TRN, Peppol ID and emirate.
- Tax rates separate S, Z, E, O and AE.
- Transaction types mapped to
380/381. - UOM codes mapped to Rec 20.
- Credit memo reasons mapped to approved codes.
- Flexfields defined for transaction type flags and goods type.
- Test in a non-production instance with each scenario.
Field names vary by version and configuration; confirm the mapping with your implementation partner.