11-05-2012 09:24 PM
11-06-2012 04:21 AM - edited 11-06-2012 04:22 AM
Regardless of possible impact on your credit score, I dont see a legitimate basis for deletion of the account delinquencies based on the posted facts.
The account delinquencies were either accurate or they were not, so deletion of their reporting would be based on a showing that they did not occur.
After reporting the delinquencies, they had no obligation to report further unless prior information required updating to maintain its accuracy.
Thus, I see no basis for asserting failure to provide "complete" reporting.
Additionally, even had further reporting been required, the party always has the opportunity to first correct any inaccuracies in prior reporting in a dispute.
Deletion of the disputed reporting is only required if they are unable to either verify its accuracy or correct it so as to now make it accurate.
11-06-2012 04:51 AM
11-06-2012 11:24 PM
+1. While a late is a late, it did occur so it is not inacccurate. Just because there is "no data" reporting, it will not factor as negative. It just means that that file did not recieve or update information for that period. Thus, neither positively or negatively. You do not say what else is in your report, however generally speaking, deleting an entire trade line often hurts your AAOA. .According to a couple of my loan officers, a late payment or two after 4 years are mostly overlooked although they still report for seven years. I went from 8k to 25k on one credit card in the last four days with a 90 day late reporting about three years ago. That 90 day late was of course preceeded by a 60 day late and two 30 day lates, totalling four lates in a row. My account showed an additional late four years ago on a different account. IMHU, from tracking my Fico Score changes, it appears on my account that the lates have damaged most up to four years as I am now in the upper seven hundreds with the simulator showing over 800 in less than eighteen months.. Of course YMMV, best wishes for success!
11-08-2012 03:50 PM
The **bleep** issue has been fixed -- it was a matter of altering our spam filter. Apologies for the inconvenience -- please carry on as you were