What is changing

• The declared UBL version moves from 2.0 to 2.1.

• UBL 2.1 introduces additional elements compared with 2.0, so documents you receive may contain new fields.

• The updated specification is available at https://tradeshift.com/integrate/

What this means for your integration

Most integrations will not need changes, but two patterns are worth checking before 1 October:

1. Version checks. If your integration validates, asserts, or branches on a specific UBLVersionID value, confirm it accepts 2.1.
   Hardcoded checks for 2.0 will need to be updated.

2. Strict parsing. If your parser or schema validation rejects unrecognised elements, confirm it tolerates the additional UBL 2.1 fields rather than failing the document.

What you need to do

• Review your integration logic against the two points above.

• Test and deploy any required changes before 1 October 2026.

Need help?

If you have questions, or would like support planning and testing the change, contact your Tradeshift representative.