Poland Clearance: Corrective Invoice

New Feature | February 24, 2026

The original invoice KSeF number for Polish corrective invoices is now visible in the Tradeshift UI and the rendered PDF, moving beyond its previous background mapping in the TSUBL. This ensures that the mandatory KSeF original invoice reference is clearly accessible for users to meet audit and compliance requirements.

Create Invoice: Optional Bank Details for Domestic Poland Transfers

New feature | released February 12, 2026

Tradeshift has updated the requirements for Polish domestic bank transfer payment methods, making the Bank code and Bank account number fields optional. This change allows Polish sellers and ScanIO users to add domestic bank transfers (UBL PaymentMeansCode 42 with PL channel) without being forced to provide these two specific data points.

This update enables sellers to save and reuse payment methods more flexibly while ensuring that invoices remain valid and dispatchable for buyers who manage payment data outside of the invoice content. Downstream systems parsing Polish domestic payment means should now expect that the absence of a Bank code or account number is a compliant configuration.

Create Invoice: Malaysia Exchange Rate and Totals Conversion

New feature | February 09, 2026

When an invoice currency differs from the local currency (MYR), suppliers are now required to provide the applicable exchange rate and the corresponding converted totals before submission. This update ensures compliance with Malaysia’s LHDNM e-invoicing rules, which mandate the inclusion of MYR conversion details for all non-MYR invoices.

Finland Tax Rate Update

Functional improvement | February 02, 2026

The VAT configuration for Finland has been updated to replace the 14% rate with the new 13.5% rate.

Reconciliation: Configurable Header and Line-Level Matching

New feature | released February 17, 2026

To address mismatches between KSeF-cleared copies and EDI (live) invoices, Tradeshift has introduced a tenant-scoped configuration that allows users to define the reconciliation scope. Users can now switch between Header-only matching and the default Header + line-item matching.

This flexibility is particularly valuable for buyers who frequently encounter line-level discrepancies due to varied integration behaviors, such as unit quantity flipping, while header totals remain accurate. By opting for header-only reconciliation, organizations can significantly increase match rates by ignoring non-critical line-level differences when appropriate.

ScanIO: Error Visibility in Overview Page

Feature enhancement | released February 10, 2026

This change displays dispatch failure information directly in the ScanIO overview grid, allowing users to triage "DispatchFailed" documents without drilling into each record. A new “Error” column has been added adjacent to the “Status” column, displaying a concise error indicator with a tooltip for longer messages. This accelerates bulk triage such as the quick identification of duplicates and reduces repetitive navigation by allowing users to identify and bulk-handle items based on the error class.

ScanIO: Status Filtering for Document Dashboard

New feature | released February 24, 2026

This update introduces a Status filter to the ScanIO Dashboard, allowing users to quickly identify documents by their operational state without manual scrolling. The filter supports multiple statuses, including Draft/Locked, Sending, Sent, On Hold, Rejected, Enrich, Awaiting Relationship, Cancelled and Error. By enabling direct status scoping, this feature reduces time-to-locate within the "To be reviewed" tab, improving overall throughput and operational clarity.

ScanIO: Enhanced Tag Visibility for Dashboard View

New feature | released February 24, 2026

This update improves tag visibility in the ScanIO dashboard to better manage multiple tags and long tag names without losing context. This change ensures users can reliably identify documents routed via specific business workflows - such as Seller Enrichment - even when numerous tags are applied.

Notification of Sub-Processor Engagement

March 02, 2026

Pursuant to the data processing terms in effect between our companies, we are notifying you that Tradeshift intends to retain the following company as a sub-processor:

Avalara Europe Limited

Lanchester House, 1st Floor, Trafalgar Place, Brighton, BN1 4FU, United Kingdom

Processing location: United States

Role / Services Performed: E-Invoicing & Live Reporting

Description: Provides a cloud-based platform for tax compliance and reporting.