Release 1.4.0 (07/10/2021)
Guidance notes on the release 1.4.0
Last updated
Was this helpful?
Guidance notes on the release 1.4.0
Last updated
Was this helpful?
When a transaction is associated to a Commercial Link (CL) that has a status of 'pending' it will now display in a clearer fashion to both Buyers and Sellers. This change will encourage the Sellers and Buyers to focus on the pending link and the need to change the CL to live status prior to the start of the next settlement.
In the transactions import view, when a Seller loads a transaction that has a pending CL, a yellow warning icon will appear under 'Tag' and it will highlight the 'Commercial Link Description' by underlining it in yellow. If the user hovers over the warning tag it will display a message relating to the error. It is important to note that the application of the new tag and highlight to such transactions does not impact the commitment of transactions loaded by sFTP and email delivery methods. For the notifications related to Email Data Delivery Success & FTP Data Delivery Success, if the file contained transactions related to a Pending CL the notification will contain a warning message to the Seller. The CL owner will have to set the CL to LIVE to resolve. Details can be found in Grid Warnings.
In a future release, further changes will be made so that when a Buyer reviews these CL pending transactions in the 'Bookings' view, they will be greyed out and the yellow warning tag will also display.
Users can now use filters on the Tag column to allow users to filter out bookings containing tags and therefore allows them to accept all of the transactions that have no warnings and then go back to work on the ones that do.
When manually uploading a transaction file that has already been uploaded on the platform, a warning will be displayed to the user informing them that the file has already been uploaded in the past. The user can then confirm if they want to proceed with the transaction upload.
Remittance status will now change to 'Completed' on the payment date when the funds are cleared. The current logic marks the remittance status as 'Completed' at time of remittance creation.
An interim status of 'Clearing' will now be applied once the submission of payment is made, before changing to 'Completed' once the funds clearing period is complete (providing he payment submission is not rejected during this period).
Users will now have the ability to configure the notifications for each module. Previously, users have only been able to configure notifications by type for the whole platform, in this enhancement users can now update the notification configuration by type, per module. Below is an example of the amended display in Notifications Configuration:
An option to 'send copy to all company administrators' checkbox has been added to the Task Scheduler report configuration export. - When selected, copy of all exports will be sent to the admins as well as any other emails and FTP (if enabled). If not selected, the exports will be sent only to the emails and/or the FTP folder defined in the task. The checkbox is not selected by default:
Additionally, in browser downloading has been enabled for scheduled tasks. Where a task has been scheduled, a user can now target the specific report and download a copy of the data to their machine with immediacy:
If FTP delivery is not enabled, then any files delivered to the FTP folder will now be rejected and a notification will be sent to the admin users of the company with a warning reading: "The SFTP delivery attempt DD:MM:YY HH:MM:SS has failed because FTP delivery is not enabled. If you want to use Secure FTP delivery please enable the feature in your Travel Ledger account settings (Settings / Data Delivery)."
Fix applied to display the times within scheduled calendar and task items in the local time to match the settings applied at configuration. Previously this was defaulting to UTC.
Three of the export templates were not generating any data when run by Seller companies: Basic Seller Rec - Standard Remittances Transactions. This bug has now been resolved and these reports run for Seller companies.
If a Seller head office uploaded transactions on behalf of a branch, the Branch ID was displaying in the 'Partner ID' column. The correct behavior has now been restored, the Branch ID is now displaying in the 'Buyer ID' column.
A notification is now generated rather than rejecting the file or the records. This allows the Seller a few day to resolve with the Buyer before collection
Each module will have its own expandable configuration display, under which users can chose which types of notifications are received in the platform and by email. These settings are now set module by module. The default settings in all modules is to receive 'Alerts' by email and in the platform. 'Warnings' and 'messages' will not be sent by email or in platform as default, these would need to be configured manually by the user. See for the updated information.
All notifications that detail failed or failing processes are branded as 'Alerts'. See the for updated information.
Normal type users can now use Task Scheduler to set up scheduled reports. Support can be found in the page.
With this additional functionality, it is now possible to set up tasks without enabling sFTP or email delivery. A user can save a report without any delivery methods applied and run it manually at their leisure by downloading. See the page for further details.
