In Beyond when using the Update Credit Reporting File feature, the program will now verify the age of the person before including their account in the credit reporting file. The programs verifies the age by checking the following fields:
Note: the Spouse and Comaker date of birth is only checked if they are joint reporting alongside the main debtor.
If the program determines any of the included parties are a minor it will now follow one of two different paths of logic:
This will allow minors to not be reported going forward and, if a minor has already been reported, it will be flagged to be deleted so that it won’t report in the future. In the event that time passes and the minor becomes 18 years old and eligible to report, their account(s) will need to be manually updated and set their credit flag back to a “R” to attempt to report them again.
The Credit Reporting Non Licensed State Table has been changed to allow a state to be blocked, not blocked, or blocked specifically for medical debt. This screen now features a dropdown in place of the old checkbox to select what level of blocking you would like to use for that state.
The new dropdown has three options to pick from:
Note: If you previously had states that were configured to be blocked before this change, after updating Beyond the previously blocked states will be defaulted to the “block entire state“ option. This ensures if a state was already being blocked before that it will remain fully blocked after the update.
A new tab has been added to the Master Screen called Vendor History:
Viewing this tab will show you all of the actions or mappings that have been performed on any accounts belonging to the master as a result of a return file from a vendor set up in the DAKCS Hub being processed:
For updates from a vendor return file, it will list the field, and the field value that triggered the updates. If the vendor is a communication vendor, the phone number will also be populated in the Data column.
For field mappings from a vendor return file, the Data column will show how many columns were mapped for that account.
If the person printing Beyond Letters didn’t have proper table access to all tables needed to complete Beyond Letters, they would get a permissions error. This has been fixed so that only the menu option permission needs to be set.
DAKCS is rolling out a new feature inside of Advanced Inquiry within Beyond. This new feature is called “Export Vendor File” and can be found under the new “Vendors” category in the “Additional Processing” screen when running an Advanced Inquiry. This new option will allow users to run a query and automatically export the results to a vendor file that will be used with the Vendor Integration feature within the DAKCS Hub.
To use the Vendor Export Feature, users will first need to click the “Additional Processing” option with the query they wish to use to export records. Users can build their queries if desired but DAKCS will also provide a sample System Query with the standard layout for each supported vendor.
Note: A query must contain both the account number and the master number when using the “Export Vendor File” feature. These fields are located in the account table and master table respectively.
After the query runs and generates its results, you must select the option “Run on a Schedule”. The “Vendor Export File” is only available with scheduled query runs.
Note: You can combine the “Export Vendor File” feature with other Additional Processing options if you need to do more on the accounts at that time.
After selecting the “Export Vendor File” checkbox and pressing Next, the Vendor Layout screen will be displayed. This screen will allow users to pick a Vendor Layout that the query exported for.
Note: It’s important to ensure the query used for the vendor export matches the layout that the vendor is expecting. Making changes to the layout without consulting your vendor may cause issues processing the file if the layout does not match what the vendor is expecting on their end.
From here the query can be set up as normal on whatever schedule is desired. When the query runs, it will automatically generate an export file and transmit it to and from the vendor by the DAKCS Hub.
If you want to learn more about this feature and the vendor tool, feel free to contact the Customer Success team.
If the consumer does not have an email address and the action is setup to send the Flow Document to email only, the scheduled action would stay in the action queue as an error. This has been resolved to properly use the fallback logic to request the fallback letter or run the fallback action.
When posting a payment and using the ALT+T shortcut, if no payment type was selected an error was thrown. This has been resolved and a warning pops up asking you to select a payment type.
When a consumer or any of it’s comakers had consent changes, it was causing the time it takes to load the account work screen to be longer than it should. This has now been resolved and the account work screen will load faster in this scenario.
Previously when saving a file to a Remote Client Vault with a scheduled query, it was not using the provided file name.This has been resolved and the entered file name is being honored.
Previously, duplicate contact preference records may have been entered. This is now resolved to ensure a single record is created.
We are adding the ability to reset consent in the event it is granted/revoked when it should not have been. This will all be done by utilizing the Update Consent action node in either schedule queries or from the action line. This feature is to be used with extreme caution.
The Update Consent action event now has a new property to prevent consumers with existing Revoked or Opted-Out consent to be preserved and not overwritten. The Preserve Revoked And Opted-Out flag on the action event can be set to True so that any existing consent that is already set as Revoked or Opted-Out will not be changed.
Also with the Update Consent action event you can reset consent back to Not Set. A new drop down value is available for each of the different communication methods, phone calls, text messaging, and sending email.
The Consent Screen has been updated to show None if no consent has been gathered for a consumer. If you reset a consumer’s consent using the Update Consent action event, this will show as Not Set. Also when viewing consent history if you reset consent to Not Set, you will see that change.
DAKCS is rolling out a new category of queries known as System Queries. These queries are specially crafted by DAKCS and come with predetermined order and formatting.
The purpose behind System Queries is to facilitate the use of DAKCS's upcoming Vendor Integration tool. By implementing these queries, DAKCS aims to streamline collaboration with vendors and offer a foundational structure for interactions with these vendors.
Although these queries come with a set structure, users have the liberty to add fields to the end of the list, according to their needs, and do a save-as with the modifications for their use. This customization option ensures that users can adapt their data files for vendor communications, tailoring the information sent as necessary. However, any changes made will necessitate coordination with the vendor regarding the data layout requirements.