Skip to main content
Release notes
Search
Search Indirect Tax Help and Support.

This article applies to:

  • Product: ONESOURCE Indirect Tax,ONESOURCE Reconciliations

October 1, 2026 release notes for version OSRE 2026.10.00

Release information

  • Release date: October 1, 2026
  • Release version: OSRE 2026.10.00

What's new: Out-of-scope detection for missing e-invoicing transactions

  • When Root Cause Analysis identifies a transaction missing in OEI, select
    Not in E-Invoicing (Not Expected)
     from the category list to review related scenarios.
  • The new
    No Mandate Obligation
     scenario identifies transaction types that are not subject to the e-invoicing mandate in the taxpayer's country, such as out-of-scope intracommunity transactions.
  • AI Actions dynamically document the checks performed, including confirming that the record exists only in OIC, reviewing the OIC tax code, and verifying the applicable country mandate.
  • Because these transactions are expected to be out of scope, the Questions to Rectify and Corrective Action fields display
    N/A
    .

What's new: Detection of manually entered in-scope transactions missing in OEI

  • The
    Not in E-Invoicing (Not Expected)
     category provides a scenario-level view for transactions that are missing in OEI but remain in scope for e-invoicing.
  • The
    Manually Entered Transactions to VAT Form from a Non-Standard Source
     scenario identifies transactions manually entered into OIC from sources such as Finance emails or customs portals.
  • The scenario displays unmatched transaction IDs and identifies the users who entered them.
  • AI Actions and rectifying questions are generated dynamically from the investigation results.
  • Selecting
    Continue
     displays an advisory corrective action, such as loading the transaction into OP or posting it in the ERP and rerunning the OP report.
  • Recommended actions are optional and are not automatically applied.
  • The Deep Analysis panel displays the corresponding report data, and a subsequent selection of
    Continue
     returns you to category selection.

What's new: Detection of incorrect invoice reference numbers

  • A new
    Incorrect Invoice Reference Number
     scenario is available in the
    Missing in OEI – In Scope
     category.
  • The scenario identifies mismatches caused by ERP posting typos rather than genuinely missing invoices.
  • The AI compares unmatched OIC lines with Pagero records from the same vendor and looks for document numbers that differ by one or two characters.
  • Questions to Identify and Questions to Rectify are generated dynamically based on matching business partner, date, value, and reference-number information.
  • Selecting
    Continue
     displays an advisory recommendation to email the AP/AR department to review, reverse, and correct the entry.
  • No automated correction is applied to the ERP record.
  • The Deep Analysis panel displays supporting company, document, VAT, amount, invoice date, and edit-distance details.

What's new: Data source column in Entity Manager

  • The Entity Manager grid in
    Setup
     now includes a
    Data source
     column.
  • The column appears after
    Entity code
     and before
    Jurisdiction
    .
  • Entities sourced from one system display either
    ONESOURCE Pagero
     or
    ONESOURCE Indirect Compliance
    .
  • Entities shared between ONESOURCE Pagero and ONESOURCE Indirect Compliance default to
    ONESOURCE Indirect Compliance
    .
  • For externally sourced entities, the column displays the external data source name unless the entity also exists in a Thomson Reuters source. In that case, the Thomson Reuters source name takes precedence.

What's changed: Tenant field on connected data source cards

  • Connected Thomson Reuters data source cards under
    Setup
    Data sources
     now display a
    Tenant
     field.
  • The field appears with the existing Creation date and Last updated fields.
  • The Tenant field identifies the external tenant connected to the Reconciliation tenant. For example, a Reconciliation tenant named WFZ connected to ONESOURCE Pagero tenant W75 displays
    Tenant: W75
    .
  • Each connected data source displays its own tenant value independently.
  • The field updates dynamically when the connection changes and remains hidden for unconnected sources.

What's fixed: Exchange rate mismatch detection in AI Chat

  • When Root Cause Analysis identifies an Amount mismatch, AI Chat now identifies an Exchange Rate mismatch when OIC and OEI contain distinct, valid exchange rates.
  • For example, the system identifies an exchange rate mismatch when one record uses 1.08 and the other uses 1.12.
  • The system rules out an exchange rate mismatch when either side has no rate applied, represented by a value of null, 0, or 1.
  • This behavior also applies to multiline invoices with different numbers of exchange-rate values in OIC and OEI.
  • Transactions that do not qualify for the exchange rate scenario remain available for review under other applicable scenarios.

What's fixed: Reconciliation category available when editing templates with two external data sources

  • Previously, the Reconciliation category could disappear when editing a report template configured with two external data sources.
  • The Reconciliation category now displays correctly when editing these templates.
  • You can select and configure Reconciliation fields and options when creating or editing a report template.
  • Existing template configurations remain unchanged after editing and saving.