Release 1.22.0 (28/06/2023)

Guidance notes on release 1.22.0

Improvements

Duplicate Booking Management

Duplicate booking management has been restored with additional improvements for both Buyers and Sellers in the Transactions>Bookings grid.

Buyers will be warned of potential duplicate transactions in the Transactions>Bookings grid, prompting you to check if transactions are valid for payment.

Transactions will be flagged and highlighted in orange for partial matches and red where it looks to be a full match for a previously loaded transaction. Details as below:

• When more than one transactions exists anywhere on the platform for the same combination of Booking Ref, Buyer, Seller, Trans type, currency code and Original Amount, TL will underline the transaction in Red

• When more than one transactions exists anywhere on the platform for the same combination of Booking Ref, Buyer, Seller, Trans type and currency code, but with a different Original Amount, TL will underline the transaction in Orange

To validate the highlighted items, hover over text on red/orange underlined items will read:

Red = 'Duplicate(s) invoices with same Booking Ref/Amount exist(s)

Orange = 'Duplicate(s) invoices with same Booking Ref but different Amount exist(s)'

Duplicate Booking Management - Handling Previously Rejected and Void Transactions

If a transaction has been previously rejected or ignored (voided) by a Buyer, it will not be flagged as a duplicate when reloaded by the Seller as no previous payment has been lodged against the previous iteration of the booking. However, if a booking is loaded in duplicate in the same cycle (review window) and the Buyer has rejected it, the duplicate versions will still be flagged to ensure the Buyer is aware of the potential conflict.

See the duplication logic page for more details.