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

This article applies to:

  • Product: ONESOURCE Indirect Tax,ONESOURCE Indirect Tax Compliance

R2026.10 | October 1, 2026

Business challenge
How OIC can hELP
Product Updates in this release
Hungarian VAT-registered clients had to submit VAT transactional data electronically to NAV outside of OIC, adding a manual, disconnected step.
A new Listing sheet lets clients upload, validate, and submit transactional data to eVAT directly from OIC
New Hungary eVAT (eÁFA) capability enabling generation, validation, and submission of VAT transactional data directly from OIC.
SAF-T report failures gave no explanation, leaving users unsure if action was needed.
Failure messages redesigned in plain language, indicating what happened and whether action is required.
Clearer, action-oriented SAF-T failure messages across SAF-T report scenarios.

Legislative updates

Hungary eVAT (eÁFA):
eVAT is a new system introduced by the Hungarian Tax Authority (NAV) that requires taxpayers to submit their VAT transactional data electronically, in place of filing a traditional periodic VAT return.
We implemented this by creating a Listing sheet where all transactional data will be uploaded, from which validation and submission to eVAT will occur.
Clients with a Hungarian VAT registration can generate, validate, and submit their VAT transactional data to eVAT directly from OIC, rather than managing this requirement outside the platform.
From a functional perspective, the initial release will support the mandatory sections of the eVAT schema (declarationInfo, vatAnalytics and declarationSummary) required for reporting, as well as selected currently optional sections, including:
  • Declaration Statement / return statements used to request VAT refunds
  • Attachments
The field mapping document shared below covers the mandatory data elements required to support eVAT reporting. In future releases, the mapping may be extended if we decide to support additional currently optional elements, such as sheetList (Melléklapok).
Regarding the overall workflow:
  1. Transactional data is uploaded into the eVAT reporting sheets within OIC.
  2. The system validates the data and generates the required eVAT submission structure (XML output).
  3. To enable machine-to-machine (M2M) filing, the taxpayer must authorize their tax number and register a NAV technical user in the Thomson Reuters e-Filing Manager.
    1. The technical user credentials include:
      1. Username
      2. Password
      3. XML Signature Key
      4. XML Exchange Key (replacement key)
  4. Once configured, OIC will be able to transmit the eVAT submission directly to NAV through the M2M interface. This workflow aligns with the NAV eVAT integration approach and supports direct submission from OIC.
Clients need to ensure the following fields are mapped:
Transactions Field Mappings
  • EntityCode
  • InvoiceID
  • ReportingDate
  • InvoiceDate
  • TransactionTypeCode
  • DocumentType*
  • DSPLTransactionDate
  • CorrectionFlag**
  • CustomerVATNumber
  • CustomerJurisdictionID (Country Code)
  • SupplierVATNumber
  • SupplierJurisdictionID (Country Code)
  • SupplierName
  • CustomerName Partner Address (detailed):
  • PostalCode
  • City
  • StreetName
  • PublicPlaceCategory
  • CustomsRepresentativeNumber (if required)
  • TransactionAmountNet
  • TransactionAmountTax
  • IrrecoverablePercentage
* Document Type must be one of the following values: INVOICE, RECEIPT, CUSTOMS_DECLARATION, OTHER, DAILY_SUMMARY.
** CorrectionFlag should be marked as true (“1”) only where the modification results in a VAT payable increase under section 153/C of the VAT Act. This field corresponds to box 31 and code MP31 of the return.

VAT returns/listings

Ireland Vies change:
As part of this change, a new hidden column, “Indicator (1)”, has been added to the ESL sheet. This ensures that when no amount is present in the Indicator field, the corresponding value in the ESL CSV output is represented as an empty value rather than a blank field, avoiding gaps between delimiters.
The Ireland VIES CSV output has been updated to align with the current Revenue RPF requirements.
The CSV headers have been updated to ensure compatibility with the latest import template. In addition, the reporting logic for Service and Triangulation transactions has been revised. These transaction types are now reported in a single Transaction Type field, with “S” used for Service transactions and “T” for Triangulation transactions. For all other transaction types, the field remains blank.
Transactions with a zero value are no longer included in the VIES CSV output.
These changes ensure that the generated VIES CSV file conforms to the current Revenue submission requirements and can be processed through the RPF workflow.
OSS return:
A new column has been added to the OSS return template: Member State of Dispatch. It captures the country code combined with the VAT number as a single value (e.g. ES123456789) for supplies dispatched from a Member State other than the Member State of Identification.
Singapore GST Group Return Enhancement: Enhanced the Singapore GST Group Return Box 3 (Exempt Supplies) calculation logic to align with GST Group reporting requirements.
Previously, exempt supplies were totalled at individual GST member level before aggregation into the group return. The updated logic now:
  • Aggregates exempt supplies by exempt supply category across all GST group members.
  • Applies category-level absolute value calculations at GST Group level.
  • Calculates the final Box 3 value using the sum of the aggregated exempt supply categories.
  • Ensures Singapore GST Group Returns are generated in accordance with expected regulatory treatment for exempt supplies.
Slovenia Sales and Purchase Ledgers
:
The Sales Ledger reports both sales and reverse charge purchases. For sales ,it should report the customer information in the counter party fields. For reverse charge purchases, it should report the supplier information in the counter party fields. At present in cases where both customer information and supplier information is imported the supplier information is reported for sales transactions. This is incorrect. After the changes sales transactions will always report the customer information and reverse charge purchases will always report the supplier information.

E-filing and coverage expansion

SAF-T
Updated the AT SAF-T schema to address inconsistencies in the SourceDocuments section, including the SalesInvoices, PurchaseInvoices, and Payments subsections. This change improves consistency and the overall user experience.Once implemented, the output will include the ExchangeRate element in the DocumentTotals subsections of Payments, PurchaseInvoices, and SalesInvoices:
JPK_MAG(2) Revised Warehouse Reporting Structure
: An update has been implemented support for the revised JPK_MAG(2) warehouse reporting structure, required by Polish authorities from January 2027. The report has been redesigned to align more closely with how warehouse movement data is recorded and maintained across different inventory accounting methods.
This update introduces a unified field structure that applies consistently across all warehouse movement types, replacing the previous movement-specific field mapping. As a result, customers benefit from improved data accuracy, simpler ongoing maintenance, and closer alignment with the latest reporting requirements.
note
For Warehouse and Physicalstock data, the OriginalLineNumber2 field must currently be populated manually in the import specification. This field is planned for inclusion in the Import Wizard in the next release.
Norway SAF-T:
 An update has been implemented to support the new Norway SAF-T Financial schema version 1.40, published by the Norwegian Tax Administration (Skatteetaten). The updated schema becomes mandatory for financial reporting periods beginning on or after 1 January 2027 and may be adopted earlier on a voluntary basis.
This enhancement aligns SAF-T Financial reporting with the latest regulatory requirements while maintaining backward compatibility with existing versions for prior reporting periods. The update supports evolving reporting needs, including enhanced handling of monetary amounts, additional currency-related information, and VAT reporting requirements, helping organizations maintain compliance and improve reporting accuracy.
Romania SAF-T Opening and Closing Balance Reporting:
 reporting solution now aggregates opening and closing balances more accurately across the Annual, Double Entry Accounting, and On Demand reports. This update refines the underlying reporting logic to ensure balances are calculated consistently across all supported scenarios. As a result, customers can expect greater data reliability, smoother reconciliation activities, and more accurate SAF-T submissions.
Clearer SAF-T Report Failure Messages
When a SAF-T report fails, the report screen now displays a clear, plain-language explanation of the issue. Previously, no reason for the failure was provided. The updated messages explain what occurred and indicate whether the user needs to act-such as importing missing data or contacting Support or whether the system will resolve the issue automatically.
Examples of the new messages:
  • “This report requires ‘{data source}’ data, which has not yet been imported for this entity and reporting period. Please import the required data and run the report again.”
  • “This report is too large to complete in a single run. Please run it again using a shorter date range, or contact Support for further assistance.”

Imports

Enhanced File Format Validation for Imports
File import validation has been enhanced to restrict source data imports to supported file formats only. Effective from the October release, users can upload only
.csv, .xls, .xlsx, .txt, and .psv
 files. Any attempt to upload an unsupported file type will be rejected with an appropriate validation message, and the import process cannot be submitted until a valid file is selected. This enhancement strengthens upload security and ensures compliance with approved file format standards.

ONESOURCE touchless compliance AI

ONESOURCE Indirect Compliance powered by CoCounsel is now available, which streamlines tax compliance through AI-driven exception resolution, e-invoicing reconciliation, and strong human-in-the-loop controls. ONESOURCE Indirect Compliance powered by CoCounsel extends the approach launched for US and Canada with the ONESOURCE Sales and Use CoCounsel tool to global indirect tax reporting, by automating the preparation of VAT returns and VAT listings across multiple countries and regimes. It brings together ONESOURCE Indirect Compliance, ONESOURCE Pagero E-invoicing, and ONESOURCE Reconciliations into a single coordinated workflow, to help customers generate ready to review returns and filings for indirect tax compliance. OIC CoCounsel is now live in production.
For enablement or more information, please contact the Thomson Reuters support team or your account manager.
UX Enhancements:
AI Workflow Tracking Dashboard
 - access an overview of your compliance operations and complete AI workflows with the new OIC CoCounsel landing page.
CoCounsel Task Review Dashboard
 - have complete oversight of all actions completed by OIC CoCounsel Agents and utilize Human in The Loop workflows to approve or override any AI decisions.
Compliance Control Panel
 - manage your AI workflows for each jurisdiction and configure the AI activity to match your process needs.
Embedded E-invoicing Reconciliations
 – leverage the ONESOURCE reconciliation tool to automatically cross-validate your data imported to ONESOURCE Indirect Compliance against Pagero e-invoices, with advanced customization and compatibility with 3rd party e-invoicing tools and other sources scheduled for H2 2026.
Initial Scope for AI workflows and scenarios:
Capabilities in scope for all supported jurisdictions:
  • Data quality
  • Unmapped tax code
  • Tax Rate Discrepancy
  • GL reconciliation
  • Exception reports (duplicate invoice, gross amount, invoice-date mismatch, tax-only, zero-value tax)
  • Automated box number report
  • Return error summarisation
  • E-file and exports (within CoCounsel)
Capabilities with jurisdiction-specific scope:
  • E-invoice reconciliation — In scope for Italy and Spain. Runs with country-specific logic for Poland and Romania. Not applicable for the UK or Australia.
  • Tax ID — VAT/GST ID format check — In scope across EU jurisdictions.
  • Tax ID — VIES validation (EU) — In scope across EU jurisdictions.
  • Tax ID — ABN validation — Applies to Australia only.
  • RO VAT prefill — Applies to Romania only.

Content Template Versions

VAT3HU15_12_473_TPL.XML
VAT3HUGRP15_12_363_TPL.XML
VAT3IE14_9_273_TPL.xml
VAT3IEGRP14_9_173_TPL.xml
VAT3OS21_1_69_TPL.xml
VAT3SG14_8_75_TPL.XML
VAT3SGGRP14_8_66_TPL.XML
VAT3SI16_4_214_TPL.XML
VAT3SIGRP16_4_177_TPL.XML