Updates, Enhancements and Bug Fixes
Summary
This release includes key updates to the E-Sign process, improving visibility and notification accuracy for internal users handling PSA and BOS documents. Tokenization was extended to NDA draft Word files for early-stage data protection. Forward Flow uploads now reuse existing PSAs, avoiding unnecessary document creation. In Collect, support for headerless files SFTP uploads and agency tracking on strategy pages was added. Comply documents and their uploads now follow the same audited/unaudited classification. On Control Panel user access can now reflect multiple department affiliations. A few bugs were fixed across modules, and automated tests were executed and improved.
Market
- We have improved the E-Sign process. Internal users can now easily track the signature status of both the Purchase Sales Agreement (PSA) and Bill of Sale (BOS). On the Portfolio Details page, users can access the signature records through the PSA and BOS components. Additionally, the PSA signature status is clearly visible in the My Portfolios (Portfolio Overview) page, under the PSA Status column, which now also indicates whether the system is “Waiting for Buyer Signature” or “Waiting for Seller Signature” on Final PSA, depending on the case. The BOS component has also been enhanced to support better tracking. When the Seller is in the signature phase, this section temporarily switches to a table view, making it easier to visualize the steps involved in the signing process. We also updated the email notifications related to the signature flow. In the Control Panel, you can now designate additional email addresses to receive updates about the PSA and BOS signature processes. These updates enhance notification accuracy and visibility, making it easier for users to monitor the signature process.
- We applied tokenization to NDA Drafts (Word files) in the Unmasked Data section, not just the final NDA PDF, to ensure data protection from the earliest stage of the NDA process, not only upon finalization.
- We updated the Upload Forward Flow workflow. If a portfolio is uploaded using a template associated with a Forward Flow agreement that already has an approved Purchase and Sale Agreement (PSA), the system will no longer lead the user through a PSA creation process, since an agreement of that type already exists. Instead, the system will copy the existing PSA from the Forward Flow agreement into the portfolio, and it will not generate a new PSA Custom document. Users experience a faster, more streamlined upload process while maintaining contractual accuracy and control. If users need to edit the PSA, they must contact our staff, as only internal users are authorized to append addendums when necessary.
Fixed Bugs in Market
- We fixed an issue that prevented users from tracking changes in Non-Disclosure Agreement .doc files during negotiations with the unmasked data solicitor.
- We resolved an issue with the DSS Approve button to prevent further malfunctions. Previously, although the button appeared enabled, it would intermittently fail to register user input, behaving as if it had not been activated. Additionally, the Approve Survey did not appear to internal users, even when the client had completed the process.
- Fixed a bug where the date shown upon NDA approval was incorrect — it displayed a future date (the following day) instead of the actual approval date.
- Fixed a bug that caused an error when a Seller attempted to request a Non-Disclosure Agreement (NDA) through the process configured in the Control Panel’s Business tab. The error no longer occurs, and the NDA Unmasked process now flows as expected.
Collect
- We updated the SFTP upload to support processing of the Headerless files. A more structured and versatile SFTP upload process will adjust the system to various client formats.
- We added a new column to the Accounts in Strategy page showing the agency assigned to each account, simplifying account tracking.
- On the Account Details page, when a user clicks a flag warning, the system now displays the reason for that flag, allowing the user to take corrective action related to the asset, if necessary.
Fixed Bugs in Collect
- We fixed an issue where charge-off accounts placed on another strategy without an agency did not update their status. Not anymore.
- We fixed an issue that always displayed an asset type error message when creating a strategy.
- We fixed a bug that sometimes caused accounts in strategies not to be filtered properly, which also made them visible to other users. Not anymore.
- We fixed a bug that sometimes caused the Bulk Create validation page to display a blank screen instead of showing any response. Now, the page properly displays both success messages and errors related to the Bulk Creation Process.
- Fixed an error that occurred on the Parameter Manager page when clicking the “Vendor” filter. The filter do not trigger any screen errors.
- Fixed unexpected behavior with account status when attempting to assign the account to a strategy.
Comply
- In Comply, internal users can create documents to be filled in by clients. These documents can be set as Audited or Unaudited. Now, when a file is uploaded into a document marked as Audited or Unaudited, it will follow the document it belongs to and will be allocated in the same section of the Control Panel. Therefore, when accessing the document through Document Registration, users will also see the files uploaded to that document and so, they can easily find and review all files related to a document in one place, streamlining audits and document management.
- We improved the layout of the Document Setup page and Archive SOP Reason pop-up to enhance visual alignment and design consistency.
- We enhanced the Legal History Questionnaire to ensure that questions displayed to External Users are no longer abbreviated, but instead properly wrapped to the next line.
- Enhanced the bank account saving process in Document Registration within Comply. Now, when a user saves a new account using the fillable form, the system correctly redirects to the updated page instead of the outdated one.
Fixed Bugs in Comply
- We fixed a bug that did not properly handle certification failures. When a certification failed, the system displayed an error message but incorrectly considered the process successful and did not allocate the failure to the Failed Certifications section of the Main Filter. Now, it displays the correct message — “Certification has been completed (failure)” — and properly allocates failures in the appropriate filter.
- Fixed a bug that hid the error messages inside the error boxes when “Financial Audit Document” was selected but the process could not be completed.
- Fixed a bug where clicking a user’s name in the Certification Managers grid incorrectly loaded the first document on the list instead of the specific user’s document.
Control Panel
- We updated Control Panel tables to follow the platform’s standard table format, to ensure consistency in layout, behavior, and user experience across all Control Panel sections.
- We enhanced the Department field on the Internal User Edit Info page in the Control Panel, allowing multiple departments to be assigned to a single user. We also adapted Comply to use this information in specific operations, so that department status can grant or restrict user access accordingly.
- Updated Postal Code on Billing Address. It is no longer a required field.
Release Note 20250520