Electronic Invoicing Enrichment for Legislative Updates

Enhance the Receivables XML invoice extract to include additional data elements as required by the mandates in several countries. This reduces the need for implementation specific changes.

Electronic invoicing streamlines financial transactions and provides more accurate and transparent data to businesses and tax authorities, contributing to better government compliance. Many countries are mandating electronic invoices in the next couple of years. The electronic invoicing extract needs enriching to support these additional country requirements.

The Receivables XML invoice extract and the UBL 2.1 message contain additional data elements. The Receivables XML invoice transformed message includes additional data and all can be used for the mapping to UBL 2.1 e-invoicing messages.

Available data elements in the Receivables XML Original Message include:

1.Header

  • Transaction Source - Transaction / General Information / Transaction Source
  • Accounting Date – Transaction / General Information / Accounting Date
  • Notes - Transaction / General Information / Notes (see setup and max 4000 bytes). The private Notes are not extracted.
  • FOB - Transaction / General Information / Edit Freight / FOB
  • Exempt from late charges - Transaction / General Information / Payment Check box / Exempt from late charges
  • Default Tax Exemption Handling - Transaction / General Information / Miscellaneous - Default Tax Exemption Handling code and Description
  • Print Date - Transaction / General Information / Miscellaneous / Print Date. Note: The date when the XML was generated.
  • Attachment Title and Description - Transaction / Attachments / Title and Description
  • Payment Status – Not Paid, Paid, Partially paid
  • Product Type – Concatenated Product Type values from transaction lines
  • Internal Notes from Projects

2. Line details

  • Channel - Transaction / Line / Sales Order / Channel
  • Exemption Handling - Transaction / Line / Tax Exemption / Exemption Handling - Exemption Handling Code and Description
  • Certificate Number - Transaction / Line / Tax Exemption / Certificate Number
  • Sales Order - Transaction / Line / Number, Line, Channel, Date
  • Ship-to - Transaction / Line / Ship-to Customer – Name, Address Line 1-4, City, County, State, Province, Postal Code, Country

3. Tax lines details

  • Tax Status Code - Transaction / Line / Detail Tax Line / Tax Status - Tax Status Name and Tax Status Code
  • Legal justification message when the setup is on tax rule level.

4. Memo lines details

  • Memo lines Global Descriptive Flexfields

5. Bill To Customer details

  • Translated Customer Name for Bill to Customer - Customer / Site Details / Account Address Details / Translated Customer Name
  • SIRET Number - Customer / Site / Profile History / Site Profile / Additional Information / Regional Information – Customer Profiles for France / SIRET Number
  • Routing Code - Customer / Site / Profile History / Site Profile / Additional Information / Regional Information – Customer Profiles for France / Routing Code
  • Tax Registration Status for TRN defined on Transaction Header - Customer / Site /Tax Profile / Tax Registration / Create Tax Registration / Tax Registration Status

6. Ship To Customer details

  • Party Site Descriptive Flexfields
  • Concatenate Party Site Purpose

7. Paying Customer details

  • Paying Customer Name – Transaction / Customer / Paying Customer / Name
  • Descriptive Flexfields - Customer / Site / Profile History / Site Profile / Additional Information / Context Value / Descriptive Flexfields
  • Global Descriptive Flexfields - Customer / Site / Profile History / Site Profile / Additional Information / Regional Information – Customer Profiles for France / SIREN Number and Routing Code
  • Customer Account Site Information Descriptive Flexfields - Customer / Site / Site Details / Enter Customer Account Site information / Descriptive Flexfields
  • Address details - Address Line 1-4, City, County, State, Province, Postal Code, Country
  • Tax Registration Number - Customer / Site / Tax Profile / Tax Registration / Edit Tax Registration / Registration Number and Tax Regime Name. The Tax Registration Number is extracted based on following rules:
    • One Tax Registration Number for a Customer Site is defined, exposed is this Tax Registration Number.
    • Multiple Tax Registration Numbers for a Customer Site are defined, and default Tax Registration Numbers is defined, exposed is default Tax Registration Numbers.
    • Multiple Tax Registration Numbers for a Customer Site are defined, and default Tax Registration Numbers is not defined, no value is exposed.
  • Account and Site Primary Contacts – Land Phone, Email and Contact Name

8. Legal Entity details

  • Place of Registration – Manage Legal Entity Registration / Place of Registration

9. Legal Reporting Unit Registration details

  • Registered Name – Manage Legal Reporting Unit Registration / Registered Name
  • Alternate Name – Manage Legal Reporting Unit Registration / Alternate Name
  • Registration Number – Manage Legal Reporting Unit Registration / Registration Number

10. Bank Account details

  • Description - Manage Bank Accounts / Description
  • Account Type, Deposit Type - Manage Bank Accounts / Account Type or Deposit Type

11. Bank Account assigned Legal Entity details

  • Legal Entity Name - Manage Bank Accounts / Legal Entity Name
  • Legal Entity address details - Address Line 1-4, City, County, State, Province, Postal Code, Country
  • Legal Entity primary Contact Name, Land Phone, Email
  • Legal Entity Registration Number and Code
  • Legal Reporting Unit Registration Number and Code

12. Payment Card details

  • Credit Card – Transaction / Payment / Payment Details / Credit Card. Masked Credit Card number.
  • Name on Card - Transaction / Payment / Payment Details / Name on Card

13. Reference to a previous invoice details

  • Previous Invoice Type
  • ID of previous invoice
  • Number of previous invoice line
  • Date of previous invoice

New elements in the UBL2.1 Transformed Message for Legal Entities with Country Code France:

 

Attribute Name

UBL Element Path

XML Path
1

Business process type

/cbc:ProfileID

PaymentStatus and ProductTypeValues - B-Goods, S-Service, 1 -Not paid, 2 - Fully or Partially paid
2

Buyer’s identifier (SIRET)

/cac:AccountingCustomerParty/cac:Party/cac:PartyIdentification/cbc:ID

TransferDocBillToTradeParty/SprfGlobalAttribute1
3

Scheme identifier (SIRET)

/cac:AccountingCustomerParty/cac:Party/cac:PartyIdentification/cbc:ID/@schemeID

Value = 0009
4

Payer’s company name

/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cac:PartyLegalEntity/cbc:RegistrationName

TransferDocPayerTradeParty/PartyName
5

SIREN number

/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cac:PartyLegalEntity/cbc:CompanyID

First 9 characters from the SIRET Number.
6

Scheme identifier

/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cac:PartyLegalEntity/cbc:CompanyID/@schemeID

Value = 0002
7

Payer’s VAT identifier

/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cac:PartyTaxScheme/cbc:CompanyID

TransferDocPayerTradeParty/CustomerTaxRegNumber
8

Payer’s tax identification scheme

/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cac:PartyTaxScheme/cac:TaxScheme/cbc:ID

Value = VAT
9

Payer’s electronic address

/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cbc:EndpointID

TransferDocPayerTradeParty/EmailAddress
10

Payer’s electronic address scheme identifier

/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cbc:EndpointID/@schemeID

Value = EM
11

Payer’s address - line 1

/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cac:PostalAddress/cbc:StreetName

TransferDocPayerTradeParty/ AddressLineOne
12

Payer’s address - line 2

/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cac:PostalAddress/cbc:AdditionalStreetName

TransferDocPayerTradeParty/ AddressLineTwo
13

Payer’s address - line 3

/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cac:PostalAddress/cac:AddressLine/cbc:Line

TransferDocPayerTradeParty/ AddressLineThree
14

Payer’s location

/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cac:PostalAddress/cbc:CityName

TransferDocPayerTradeParty/ City
15

Payer’s postal code

/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cac:PostalAddress/cbc:PostalZone

TransferDocPayerTradeParty/ PostalCode
16

Payer’s country subdivision

/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cac:PostalAddress/cbc:CountrySubentity

TransferDocPayerTradeParty/ County
17

Payer’s country code

/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cac:PostalAddress/cac:Country/cbc:IdentificationCode

TransferDocPayerTradeParty/ CountryCode
18

Payer contact point

/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cac:Contact/cbc:Name

TransferDocPayerTradeParty/ SiteCpName
19

Payer contact phone number

/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cac:Contact/cbc:Telephone

TransferDocPayerTradeParty/ SiteCpPhoneCountryCode TransferDocPayerTradeParty/ SiteCpPhoneAreaCode TransferDocPayerTradeParty/ SiteCpPhoneNumber TransferDocPayerTradeParty/ SiteCpPhoneExtension
20

Payer contacts electronic address

/cac:PaymentMeans/cac:PaymentMandate/cac:PayerParty/cac:Contact/cbc:ElectronicMail

TransferDocPayerTradeParty/ SiteCpEmailAddress
21

Payment account identifier

/cac:PaymentMeans/cac:CardAccount/cbc:PrimaryAccountNumberID

MaskedCcNumber
22

Payment account name

/cac:PaymentMeans/cac:CardAccount/cbc:HolderName

CcHolderName
23

Amount paid

/cac:LegalMonetaryTotal/cbc:PrepaidAmount

PrepaymentAmount
24

Rounded amount

/cac:LegalMonetaryTotal/cbc:PayableRoundingAmount

OrderRoundingAmount
25

ID of previous invoice

/cac:BillingReference/cac:InvoiceDocumentReference/cbc:ID

TransferDocLine/ OriginalTrxNumber
26

Previous invoice type

/cac:BillingReference/cac:InvoiceDocumentReference/cbc:DocumentTypeCode

TransferDocLine/ OriginalTrxType TransferDocLine/ OriginalTrxClass
27

Date of previous invoice

/cac:BillingReference/cac:InvoiceDocumentReference/cbc:IssueDate

TransferDocLine/ OriginalTrxDate
28

Number  of previous invoice line

/cac:BillingReference/cac:BillingReferenceLine/cbc:ID

TransferDocLine/ OriginalLineNumber
29

Identifier of sales order by line

/cac:OrderLineReference/cac:OrderReference/cbc:SalesOrderID

TransferDocLine/ TransferDocSalesOrder/ SalesOrder
30

Invoice sales order line

/cac:OrderLineReference/cbc:SalesOrderLineID

TransferDocLine/ TransferDocSalesOrder/ SalesOrderLine
31

Address line 1

/cac:Delivery/cac:DeliveryLocation/cac:Address/cbc:StreetName

TransferDocLine/ ShipToLocAddress1
32

Address line 2

/cac:Delivery/cac:DeliveryLocation/cac:Address/cbc:AdditionalStreetName

TransferDocLine/ ShipToLocAddress2
33

Address line 3

/cac:Delivery/cac:DeliveryLocation/cac:Address/cac:AddressLine/cbc:Line

TransferDocLine/ ShipToLocAddress3
34

City of delivery

/cac:Delivery/cac:DeliveryLocation/cac:Address/cbc:CityName

TransferDocLine/ ShipToLocCity
35

Delivery postal code

/cac:Delivery/cac:DeliveryLocation/cac:Address/cbc:PostalZone

TransferDocLine/ ShipToLocPostalCode
36

Country subdivision

/cac:Delivery/cac:DeliveryLocation/cac:Address/cbc:CountrySubentity

TransferDocLine/ ShipToLocCounty
37

Country code

/cac:Delivery/cac:DeliveryLocation/cac:Address/cac:Country/cbc:IdentificationCode

TransferDocLine/ ShipToLocCountry
38

Payment account identifier

/cac:PaymentMeans/cac:CardAccount/cbc:PrimaryAccountNumberID

MaskedCcNumber

Process flow to generate UBL 2.1 e-invoicing messages:

  1. Create Receivables transactions with tax lines and all required details.
  1. Run Generate and Transfer XML Transactions process.
  1. Go to Manage Collaboration Messaging History page and open original extract message and the Transformed UBL 2.1. message.

Business benefits include:

  • Additional data elements in the extract help reduce time to implement specific changes to the UBL 2.1 messages.
  • Use the additional data elements in the UBL 2.1. mapping to create custom output files with required data.

Steps to Enable

Setup Notes for Electronic Invoicing for France:

  1. Navigate to the Setup and Maintenance > Manage Receivables Note Type.
  1. Search for Lookup ZMM_NOTE_TYPE with following details:
  • Meaning = Note Type
  • Description = Product specific classification of the note
  • Module = Notes
  • Lookup Configuration Level = Extension
  1. Define new Lookup Code. Note: For France the Lookup Code must be from UNTDID 4451 list. See following example setup:
  • Lookup Code: AAI
  • Enabled: Checked
  • Start Date: 01/01/2024
  • Meaning: General information
  • Description: FR BT-21
  • Save.
  1. Navigate to the Setup and Maintenance > Manage Receivables Note Type Mapping.
  • Select Receivables Transactions as Business Object.
  • Add row and define the Lookup Codes for Notes with following details:
    • In the Mapped Lookup Value define the Lookup Code from previous step.
    • Define Default as Yes or No.
  • Save.

Tips And Considerations

  • Complete the required prerequisite steps in Collaboration Messaging Framework to set up the message exchange between Oracle Cloud Applications and trading partners.
  • A run of the Generate and Transfer XML Transactions process generates and displays the Original Message extract file and the UBL2.1 Transformed Message in the Manage Collaboration Messaging History page.
  • The output file contains the XML File Header, Invoice Header, Invoice Lines, Invoice Tax details and additional invoice information specific to the transaction.

Access Requirements

No additional setup is required.