Inbound Release Platform v1.4.0

We are pleased to announce the release of Inbound Release Platform version 1.4.0!

Release dates

UAT: 29 October 2026

PRD: TBA

Improvements

• IRP will implement idempotency, ensuring that the submission of the exact same message will always return the same correlation-id from IRP. Due to this change, the format of the correlation-id returned by the IRP API within the synchronous PTV_IRP message will be changed from a 36 character string which has the format XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX to a longer character string that does not contain hyphens.

  • Examples:

    • Current format:
      6E20A3DD-BCE1-3309-7142-580D2571A11B

    • New format: 6E20A3DDBCE133097142580D2571A11B0D10F931446D8C0EDA6A5CE8A57AE5CA

  • While this change does not affect the existing API data contract, integrations that assume that the correlation-id follows a GUID format may need to be updated.
    Please review your integrations to ensure they can accommodate this change.

• RTO transfers phase 2

  • New INSTRUCTION_IRP functionality to trigger the following instructions for a TSD

    • Creation of a REN

    • Creation of a transfer

    • Invalidation of an existing REN

    • Revocation of an intended transfer

    • Important: This functionality will only be supported for TSDs which have been sent towards the TSD v2 endpoint.
      If Ship Agents are intending to use this new functionality, they should ensure their TSDs are being sent towards the v2 endpoint.

  • New transfer approval functionality (TRF_NOTIFY_IRP & TRF_DECISION_IRP) for terminal operators to approve an intended transfer

    • Important: This feature flag will be active on UAT, but inactive on PRD, in order to not disrupt the RTO transfer phase 1 which is currently live on PRD

  • Ingestion of GATE_MOVEMENT messages in context of an RTO transfer

    • Important: This feature flag will be active on UAT, but inactive on PRD, in order to not disrupt the RTO transfer phase 1 which is currently live on PRD

• TSDs which have the end status ‘Temporary storage ended’ will no longer be shown on a RTO snapshot report

• The REN MRN value will no longer be anonymized in the CSR_IRP messages

• Terminal discharges with an unLoCode of type ‘C' (i.e., value starting with 'BEC…’) will now be technically rejected by IRP

• TSD amendments (IETS413_IRP) where the part-BL envelope content is consistent with the original pre-lodged TSD (IETS015_IRP) but with a different order, are no longer rejected business-wise by IRP

• IRP User Interface:

  • The TSD details page now shows whether a TSD is a part-BL or not (i.e., part-load, meaning for the underlying container, there are multiple TSDs involved)

  • The TSD details page now shows an indicator whether it involves a Union flow or a non-Union flow

  • RTO reports are now generated asynchronously, enabling larger datasets and longer reporting periods. Once generated, the report can be accessed and downloaded via ‘Downloads’ in the navigation bar

  • If a TSD receives a provisional IETS045, indicating that the full TSD has been written off, the 'written off by declarant' values are now also updated accordingly

• Bug fixes:

  • Improved PN creation handling

  • Bug fix for cases where an invalid gross mass and number of packages were being shown in the RTO reports

  • Union T2L(F) status overrule checker finetuned for goods which are discharged over the course of several days