FORUM PROFILE

Adverse-Action Reasons

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #33493
    GwenM
    Member

    Hello Compliance Experts,

    We need some clarification. In 2016, we narrowed down the denial reasons to mimic the HMDA codes/reasons that were effective in 2018 for consistency and accuracy. For example, only credit history is disclosed as a reason and not the specific problems with a person’s credit history. However, the credit score and the reasons that impact the credit score are disclosed in the FCRA section of the adverse action notice. It seems that credit history is sufficient because the specifics are disclosed below in the FCRA section but another third-party has indicated that this practice does not comply with Reg. B.

    1002.9(b)(2):
    (2) Content of notification when adverse action is taken. A notification given to an applicant when adverse action is taken shall be in writing and shall contain a statement of the action taken; the name and address of the creditor; a statement of the provisions of section 701(a) of the Act; the name and address of the Federal agency that administers compliance with respect to the creditor; and either:
    (i) A statement of specific reasons for the action taken; or
    (ii) A disclosure of the applicant’s right to a statement of specific reasons within 30 days, if the statement is requested within 60 days of the creditor’s notification.
    Commentary:
    (2) Statement of specific reasons. The statement of reasons for adverse action required by paragraph (a)(2)(i) of this section must be specific and indicate the principal reason(s) for the adverse action. Statements that the adverse action was based on the creditor’s internal standards or policies or that the applicant, joint applicant, or similar party failed to achieve a qualifying score on the creditor’s credit scoring system are insufficient.

    What are your thoughts?

    #33525
    rcooper
    Member

    I agree. Disclosing the key factors that adversely affected the consumer’s credit score does not satisfy the ECOA requirement to disclose specific reasons for denying or taking other adverse action on an application or extension of credit. See comment 1002.9(b)(2)-9 below (I bolded a couple of sentences for emphasis.)

    9. Combined ECOA–FCRA disclosures. The ECOA requires disclosure of the principal reasons for denying or taking other adverse action on an application for an extension of credit. The Fair Credit Reporting Act (FCRA) requires a creditor to disclose when it has based its decision in whole or in part on information from a source other than the applicant or its own files. Disclosing that a credit report was obtained and used in the denial of the application, as the FCRA requires, does not satisfy the ECOA requirement to disclose specific reasons. For example, if the applicant’s credit history reveals delinquent credit obligations and the application is denied for that reason, to satisfy §1002.9(b)(2) the creditor must disclose that the application was denied because of the applicant’s delinquent credit obligations. The FCRA also requires a creditor to disclose, as applicable, a credit score it used in taking adverse action along with related information, including up to four key factors that adversely affected the consumer’s credit score (or up to five factors if the number of inquiries made with respect to that consumer report is a key factor). Disclosing the key factors that adversely affected the consumer’s credit score does not satisfy the ECOA requirement to disclose specific reasons for denying or taking other adverse action on an application or extension of credit. Sample forms C–1 through C–5 of Appendix C of the regulation provide for both the ECOA and FCRA disclosures. See also comment 9(b)(2)–1.

    Also, it is always a good idea to stick to the model forms when possible. If you look at the HMDA Getting it Right Guide (p. 23-24) it explains which HMDA codes correlate to the reasons on the AAN model form.

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.