The trigger is an approved credit decision
Regulation V’s risk-based-pricing provisions address certain grants of consumer credit on materially less favorable terms based in whole or part on a consumer report. Section 1022.72 defines the general trigger and methods for identifying affected consumers. The point is easy to miss in a lending workflow focused on approval and denial: an approved applicant can still require a notice.
The comparison is with the most favorable material terms available to a substantial proportion of consumers for the relevant product, subject to the rule’s definitions and exceptions. It is not simply a comparison with the single best advertised rate or a judgment that the offer is unaffordable. The institution must identify the product, material terms, use of report information and applicable notice method.
Risk-based pricing and adverse action are different
A denial or other can trigger a different set of requirements. Regulation V includes exceptions and alternative disclosure approaches in section 1022.74. An institution should not treat a generic credit-score notice, an adverse-action notice and a risk-based-pricing notice as interchangeable documents merely because each contains information about a consumer report.
The operational design should determine which requirement applies to the actual outcome and whether a valid exception or permitted alternative is being used. That decision should be documented and tested. A workflow that sends a denial notice only to rejected applicants can leave a gap for approved applicants receiving less favorable terms. Conversely, sending every available notice without a coherent rule can confuse consumers and mask configuration errors.
Methods and product definitions
Section 1022.72 permits direct comparison and specified alternatives, including a credit-score proxy and tiered-pricing method. The credit-score proxy uses a defined cutoff approach rather than a lender’s arbitrary preference. Product grouping also matters: the rule discusses products with similar features and purposes, so the comparison population needs a defensible definition.
A lender that changes its pricing tiers, model, channel or acquisition strategy should review whether its notice-identification method still works. A cutoff based on an outdated population can produce the wrong recipients. The implementation should preserve the inputs and logic used at the time so a reviewer can reconstruct why a customer did or did not receive the notice.
A hypothetical pricing example
Assume a lender offers the same unsecured installment product at several rates and uses consumer-report information to assign an applicant to a less favorable tier. The applicant accepts the loan. That is not automatically the end of the disclosure analysis simply because the application was approved. The lender must evaluate the Regulation V trigger and its selected compliance method, including any applicable exception.
Now assume a different applicant receives a higher rate solely because a chosen term has a different published price and the report did not contribute to that difference. The legal analysis can differ. These hypothetical examples illustrate why the system should record the basis for the terms and the product comparison, rather than flag every rate above the lowest advertised number or assume every higher price is report-driven.
Timing, content and score information
Section 1022.73 addresses the notice’s content, form and timing, with distinctions for different credit situations. The institution should map the applicable timing to its actual origination and account-management process. Generating a document eventually is not sufficient if it reaches the customer after the required point. Automated delivery should be checked against the contractual and operational sequence.
When a credit score is used, the relevant disclosures can require specific score-related information. The notice-generation system should use the score and factors associated with the decision, rather than a later refreshed score or a generic explanatory list. Consumers need an accurate account of the information implicated in their offer, not a plausible document assembled from whichever data is easiest to retrieve.
Controls and implementation costs
Recommended controls begin with a decision inventory: new credit, account reviews, changed pricing and relevant exceptions. Test each channel, including merchant-assisted and digital applications. Reconcile approved accounts with the population evaluated for notices, then sample both recipients and nonrecipients. Testing only notices that were sent cannot reveal customers who were omitted entirely.
Costs include maintaining comparison populations, versioning score inputs, integrating document delivery and correcting exceptions. A permitted alternative disclosure approach may simplify some operations but has its own conditions and content requirements. The choice should be evaluated with the legal text and actual workflow, not selected solely because a vendor already has a convenient template.
What would change the assessment
Confidence increases when notice decisions can be reproduced, timing is evidenced and product or model changes reliably trigger review. The assessment weakens when the institution cannot identify which score determined pricing, when cutoff calculations are stale or when dealer and direct channels use inconsistent logic. Material pricing changes should reopen the design.
The current provisions reviewed September 29, 2026 show why consumer-report compliance extends beyond denial letters. A sound process follows the full path from report use to offered terms to the required explanation. The practical question is whether the approved borrower received the information required for that particular decision, in the correct form and at the correct time.
Sources
- 12 CFR 1022.72: general risk-based-pricing requirements; current text reviewed September 29, 2026Official text
- 12 CFR 1022.73: content, form and timing; current text reviewed September 29, 2026Official text
- 12 CFR 1022.74: exceptions and alternatives; current text reviewed September 29, 2026Official text