Release 1.5.0 (29/10/2021)
Guidance notes on the release 1.5.0
Last updated
Guidance notes on the release 1.5.0
Last updated
The platform now supports the delivery and upload of the standard SPS file in CSV format. Previously, the file was only accepted as a .TXT file. Update included in Old File Format for Upload
Remittance status now changes to Completed on the payment date when the funds are actually cleared. Previously, remittance was marked as Completed at the time of remittance creation.
An interim status of "clearing" has been implemented for when it is successfully passed to PTX. It then change to "completed" once the funds clearing period is completed, provided it is not rejected during this period.
Based on feedback from users, we have decided to change our Seller Rec file behaviour.
The previous behaviour was when a record in a file does not match a Buyer in TL (Buyer not present, or CL not enabled) the record is "not committed" and ignored when the Seller Rec File is generated. For example, when a Seller uploads 100 records and 10 are not committed (they get automatically voided when the collection runs) in the rec file returned there would be only 90 records.
With the new behaviour, when a record in a file does not match a Buyer in TL (Buyer not present, or CL not enabled) that record is left as "not committed", unless the record is manually fixed and therefore matched.
Now, when the Seller Rec File is generated all of those "Not Committed" records that get a status of "Void" and the collection runs would be included in the Seller Rec File with a reason code of 'D' Tag 'Not Committed' in the file. For example , if a Seller uploads 100 records and 10 do not match and are not fixed, in the rec file there will be 100 records and those 10 would also be returned with a Reason code of D.
The text instructions on the two factor authentication set up screen has been changed to improve the instructions presented to the end user and support them in setting up their authentication app:
Details of this change have been applied to the page Two-Factor Authentication (2FA) Setup Guide
To improve the speed of display in the Transactions>Bookings page, the 'Due' column has been updated to display the date a record was loaded. A default filter has been applied to load transactions uploaded for the current date and 14 days prior.
Under the Transactions > Bookings view, the Settlement Status list included 'Cycle Complete'. This has now been updated to reflect our current naming conventions, it is now simply labelled as 'Complete'.
Where 'error 404' and/or continued use have taken place when a user's session has expired, users will now receive session expiration warning messages in the platform when their session has timed out.
Within the Task Scheduler module, the time range of seven days which is an applicable option to the data generated in the export set up, was set to include the previous seven days, not including the present day/day the report is run. The change includes the day the report is run within the seven day period.
