A careful read of 1026.19(e)(3)(iv)(D) and related Official Interpretations led me to that conclusion, after discussing it with Randy Carey. All of that language pivots on whether there is a change in a rate-related cost as a result of the lock.
When the first version of that provision appeared, it had its own internal deadline for completing a revised LE. And that was because the first version required this particular revised LE, unlike the revised LEs for other changed circumstances, to be sent on the day the rate is locked! When the Bureau later revised that to allow for the same three-business-day period afforded for other changed circumstances, instead of removing the "same business day" requirement from paragraph (D) to let the three-business-day rule referring to the other changed circumstances also refer to paragraph (D), it changed the paragraph (D) deadline to the third business day.
When we had first looked at this provision, we had determined that the revise LE would have to be sent, even if there were no changes to any cost already disclosed, just to update the disclosure under 1026.37(a) of "Yes" to the rate lock question, and the addition of the rate lock expiration date. Frankly, that made sense to us then.
But the language in paragraph (D) and commentary still all hinges on whether there is a change in interest-rate related costs. In fact, at no time in paragraph (D) or the related Commentary is the updated disclosure of rate lock expiration date even mentioned. As we (Randy and I) now interpret this provision, if you do have some changed costs resulting from the execution of a rate-lock, you will have to provide a revised LE within three business days, and you should update the rate lock NO to YES and add the expiration date. But if you don't have any changes in costs resulting from the rate lock with the consumer, there's no need to send a revised LE.
Last edited by John Burnett; 07/12/16 06:20 PM.
_________________________
John S. Burnett
BankersOnline.com
Fighting for Compliance since 1976
Bankers' Threads User #8