Skip to main content
2026
Search
Search Indirect Tax Help and Support.

This article applies to:

  • Product: ONESOURCE E-Invoicing

Oracle CMK 2.2.0.0 June 30, 2026 release notes

Release notes describe new features and improvements made to ONESOURCE E-Invoicing.

France scope

This release delivers Oracle CMK support for France e-Invoicing and e-Reporting use cases aligned with additional scope for AR, AP, and cross-border flows.
The following functional level capabilities are introduced as part of this release scope.
E-reporting capabilities
International B2B e-reporting success flows are supported (Only approval process). This includes single e-report submission from the ERP system. The status of e-reports are captured in ONESOURCE Pagero systems. In ONESOURCE, e-reports are recorded under Tax Data Reporting. Aggregated reports can be viewed by navigating to Tax Data Reporting > Aggregated Reports, while individual reports are available under the Reports tab within the same section.
  • AR Cross Border scenarios are now supported. These transactions are triggered via CMK, the process is similar to e-invoice flow, where ERP submits the document as Tax Data Reporting.
  • AR Payment E-reporting, AP Cross Border scenarios are now supported via Oracle BIP.
    • For AR transactions: Partial, Single, Cancellation of payments/cash receipts are now supported for Payment Received Lifecycle/Payment E-reporting scenarios.
    • Report Type for ‘Payment E-reporting’ (Not lifecycle status) will be recorded as ‘Payment’ in OEI;
  • Introduced DFFs that flag already-submitted transactions, preventing ‘Payment Received’ lifecycle and ‘Payment E-reporting’ duplication.
    • DFFs - OEI Response and OEI EReporting Last Run Date.
note
E-Report Rejection and rectification scenarios are not included in this release and are planned for future releases.
Seller or buyer established and non-established scenarios compliant for 2026 are supported in this release.
  • Established status is determined based on the availability of a SIREN/SIRET for the seller or buyer.
  • Entities without a SIREN/SIRET but with French VAT registration are considered non-established.
  • Entities without these details are treated as non-France entities.
  • Established and non-established entities are further assessed and reported based on the DROM/COM/TAAF territory classification.
VAT Status and Flow
Seller VAT status
Buyer VAT status
Flow
FR – Non-established
FR (Established)
E-Report AP Cross Border/Self billing
FR (Established)
FR – Non-established
E-Report AR cross-border
FR (Established)
Non-FR
E-Report AR cross-border
FR (Established)
N/A (B2C)
B2C E-Report
Non-FR (EU VAT)
FR (Established)
E-Report AP Cross Border
FR (Established)
FR (Established)
E-Invoicing
Use Case support
The following extended support scenarios are covered from both AP and AR pov as applicable.
  • Invoice to be received and processed by a Third Party on behalf of the BUYER
  • Invoice to be paid to a third party known at the time of invoicing, who also manages the order/ reception, or even invoicing (Distributor/Depositary)
    • AP Inbound for this use case – Yet to be supported by Pagero
  • Advance invoice and final invoice after advance
    • AP Inbound for Final Invoice – Yet to be supported by Pagero
  • "Mixed" invoices mentioning a main operation and an ancillary operation
    • A transaction is considered as ‘Main Operation’ if Invoice Type = M1 and as ‘Ancillary operations’ if product type as ‘Goods’ or ‘Services’
  • Single e-Report submission for B2B international (Only approved flow is supported)
  • Transactions with entities established in the DROM / COM/ TAAF.
Minor enhancement
There’s a change in TR CMK custom roles and privileges for enabling the CMK Integration.
Refer to the configuration guide for more details.