Added on February 12, 2019
There is a new version of the Surname Probability table that is used for the Bayesian Improved Surname Geocoding (BISG) proxy methodology in Comply. We made some minor adjustments to the suppressed values in the table as per instructions in the CFPB proxy methodologies. These updated values can help increase the accuracy of the proxy calculations by less than one percent on average. You will want to update the data at your earliest convenience just to be fully up-to-date and get the best results possible. Updating the Surname table in Comply is a simple System Data import. If you use Auto Updates and the Census Bureau/Social Security Proxy Data option is checked, the new table should download automatically to be applied. This option is not normally on by default. To change it, simply go
Added on February 6, 2019
Microsoft is ending support for SQL 2008 and RATA is following suit. Comply 18.1 is the last Comply update that will work with SQL 2008. There are features needed for ongoing development that are only available in SQL 2012 and higher so this move is a necessity. We stopped supporting new installations using SQL 2008 with the release of Comply 17 but we have allowed updates to still use the deprecated version of SQL Server. As far as we know, most, if not all of our clients, have migrated to SQL 2012 or higher. If you are one of the few remaining die-hards, please begin preparations to migrate to a newer SQL Server environment at your earliest convenience. Contact us at (407) 831-7282 if you have any questions or need additional information.
Added on February 5, 2019
Comply 18.1 is now available for download from the RATA Support site. This version incorporates all of the earlier 17 and 18 updates along with other beneficial changes. If you have updated to 18.01 this release is not needed for submission. However, if you can update it wouldn't hurt. Every version of Comply is always a little better than the previous. If you are updating from 18.00 or 18.01 this update should be just a normal update because all of the 18 updates conversions have already been done. If you are updating from a Comply 17 system please read all of the important Comply 18 update info below because this update will run all of the 18 updates as well. If you have questions please call. Check the changes document to see a list of all changes to decide the
Added on January 28, 2019
Thank you as always for using the RATA Comply software and Geocoding services to help with your HMDA and/or CRA submissions. As part of our efforts to ensure that you have the highest quality and most current geocode results for submission, we re-geocode every application that was submitted prior to January 21st to try and improve the precision codes. We go through the file to look for improvements to any geocodes based on the precision codes and then return any improved results in the End Of Year (EOY) geocode update file. This file should be applied to your Comply system at your earliest convenience to assure that these improved results are a part of your submission. The EOY update file will only affect records submitted before January 21, 2019. If you have submitted more geocoding
Added on December 11, 2018
Overall the conversions from Comply 17 to Comply 18 have been very smooth. As we mentioned in the changes document and the download of Comply 18, this update performs some major transformations to the way Fair Lending data is stored, accessed and displayed. We tried to test for all permutations, but there are too many to try and duplicate. Most of the conversions have gone well but we have just been made aware of a scenario that is not converting correctly. If you have multiple period reviews with multiple workspaces under a single Reporting Entity, in certain circumstances these are not being named correctly and they are linking to incorrect data sets. Simply renaming the workspaces will not correct the issue. If you have run the update and this scenario affects your data, do not panic.