Adverse action reason codes: what they are and how to use them

What reason codes must do under Regulation B

Regulation B requires that adverse action notices state the 'specific principal reasons' for the adverse action. The reasons must be accurate — they must reflect the actual factors that drove the specific decision, not a generic statement that could apply to any declined application. The regulation provides model reason language in Appendix C that lenders may use; model language does not eliminate the obligation to ensure the selected reason is accurate for the specific application.

The most common examination finding is that reason codes are too vague. 'Insufficient credit experience' or 'unacceptable credit record' are often cited deficiencies when the actual reason was something specific — for example, three NSFs in the most recent 60 days, or existing advance obligations exceeding 40% of average monthly deposits. The code needs to say what actually happened.

How to build a reason code library for your credit product

MCA and small business lenders use underwriting criteria that do not always map neatly to consumer-credit model forms. Building a reason code library starts with your actual underwriting criteria: what specific factors can lead to a denial? For MCA, those might include: insufficient average daily balance, excessive NSF frequency, evidence of advance stacking, time in business below minimum, monthly deposits below program threshold, identity verification failure, or existing obligations exceeding repayment capacity.

Each criterion that can drive a denial should have a corresponding reason code that is specific, accurate, and appropriate for the applicant to receive. The code should describe the actual issue, not a conclusion. 'Average daily balance below required minimum for requested advance' is better than 'insufficient cash flow.'

Common mistakes to avoid

Selecting reason codes at random or by habit — rather than from the actual decision record — is a frequent compliance failure. When a case management system does not link the decisioning criteria to the reason code selection, codes get selected by default rather than accuracy. The adverse action workflow should require the underwriter to select reasons from the specific criteria that drove the decision on that case, not from a generic list.

Using the maximum number of reason codes allowed (four on most model forms) when fewer actually apply is also problematic. Padding the notice with additional reasons not relevant to the decision can mislead the applicant about why they were declined — and creates its own regulatory risk if those reasons were not actually applied.

FAQ

Adverse action reason codes explained — common questions

Related