Release 1.10.0 (02/05/2022)
Last updated
Was this helpful?
Last updated
Was this helpful?
The purpose of this development is to present clear information about the funds movement from the collection start time. This will take into account what is expected to happen throughout the various phases of the settlement cycle, so that the companies are aware of what has been collected from them and what is going to be cleared into their accounts. This will be presented in the form of a notification which can be configured to be received in platform and/or by email.
A notification containing information about the collection initiation will be sent to each company with eligible transactions within the cycle and will contain a summary of each company’s balance within a cycle.
The notification will contain 4 parts:
A summary of all remittances created for the cycle in which the company is a Payee (Debit summary)
A summary of all remittances in which other companies have been debited for payments due to the company (Credit summary)
A summary of all failed debit payments of the company receiving the notification (Failed Debits summary)
A summary of all failed debit payments that are due to the company receiving the notification (Failed Credits summary)
When uploaded but uncommitted transactions that have not been deleted from the File import grid return in the Seller Rec files will now apply a Reason code S - Amended by System. This updated reason code will give users a better understanding of the true position of the transactions.
Previously, uploaded but uncommitted transactions that have not been deleted from the File import grid returned in the Seller Rec files with reason code D - Agent Disabled. The code created confusion for both the Sellers and the Buyers as it is not representative of the actual reason for the transactions not being included in a collection.
The Upload tab under Transactions>File Uploads has been improved as part of this release. The upload area has been reduced in size, giving you more space within the grid to review transactions before commitment to the Buyers.
Uploads can be found under the same page as before, but it is now a button in the top right:
Below is a short video previewing the new process:
We have made some improvements to the recently added Partners>Companies List page to make it easier to navigate for users. These changes include; removing pre-filters on CLs to return all results, merging of the Buyer and Seller columns to display roles assigned to company in the field and clarity in the status column options.
We have added new fields to two of the Task Scheduler template exports. Some platform users have reported facing issues with linking their transactions to a remittance. To make this process more user-friendly we have added:
1) The remittances ids will be added to the Transactions export template in Task Scheduler. There will be two new fields:
Collection remittance ID - showing the ID of the remittance generated in the collection phase
Disbursement remittance ID - showing the ID of the remittance generated in the disbursement phase
If no remittance(s) has (have) been generated for a transaction, the field(s) will be blank.
2) The Commercial link description will be added to the Remittance export template in Task Scheduler.
Please await further communication from Travel Ledger before using this feature, it is currently in pilot and will be released to the wider community shortly
This file is (optionally) generated by the Buyer and uploaded into Travel Ledger, initially only manually on the platform, but eventually via email or SFTP. The file contains a record of all transactions in the specified period that the Buyer is accepting, amending, or rejecting (with a mandatory reason code if amending or rejecting).
Uploading this file into Travel ledger gives the Buyer the option to replace manual acceptance/amendment/rejection. A transaction can be updated through the file as many times as necessary/relevant prior to the end of the Buyer review period, as currently applies t in platform actioning of transactions.
The Buyer Upload File is designed to be uploaded after a Buyer has received and reconciled a Buyer Reconciliation download file (or equivalent) in their Back-office system), but it can be generated independently as long as the required data is present.
See Buyer Upload File for additional support and guidance on this feature.
The billing area of the platform is where you can view invoices from Travel Ledger, manage your billing details and Travel Ledger subscription. The Billing Module page explores managing your bills in more detail,.
Please await further communication from Travel Ledger about your first bill.
