An explanation is part of the financial service
A declined applicant wants to understand what happened and whether incorrect information played a role. An employee responding to that applicant needs a record that explains the same decision. Regulation B’s notice framework supplies the legal baseline; understandable and accurate communication gives the process practical value. [1]
Analysis: a notice can reduce confusion and help identify a data problem, but it is not a promise that changing one input will result in approval. A later application may involve different information, terms or policy. Avoid turning an explanation of the completed decision into unsupported financial advice about a guaranteed next outcome.
This matters across consumer banking, mortgage and retail finance. The operating process can include a platform, a lender, a data provider and a service team. The person sending the explanation should be able to connect it to the actual decision rather than rely on the most convenient template.
The central obligation
Regulation B, which implements the Equal Credit Opportunity Act, makes the explanation of a credit decision part of the decision process. Section 1002.9 generally requires notice within 30 days after receiving a completed application. Its written framework calls for specific principal reasons, or notice of the applicant’s right to request those reasons. This article focuses on completed consumer applications; incomplete applications, counteroffers and business credit have additional provisions.
The official interpretation says reasons must reflect factors actually considered. A notice that merely says an applicant did not meet internal standards, or did not achieve a qualifying score, does not supply the required specificity. The operational implication is straightforward: a lender needs to reconstruct why this application failed under the policy and model version used at the time.
A score explanation is only one part of the chain
A decision can involve eligibility rules, an affordability calculation, a score cutoff, fraud review and an underwriter’s judgment. The interpretation addresses combined systems and automatic denial factors. It also distinguishes the principal reasons for an adverse credit decision from the key factors affecting a credit score. Those are related records, but one cannot automatically stand in for the other.
Analysis: create a decision trace before drafting the notice. It should connect the source data, transformations, rule outcomes, model output, human override and final action. If an override supplies the decisive reason, a score explanation alone may describe a step that did not determine the outcome. A polished explanation cannot repair an incomplete decision record.
Illustrative application
Assume a fictional applicant passes an identity check and the credit-score threshold but fails a documented debt-to-income limit. The relevant explanation is the actual income-and-obligations issue, expressed accurately for the consumer. Selecting “insufficient credit history” simply because that is a readily available model reason would misdescribe this example.
Now change the facts: the debt ratio passes, but a model cutoff causes the decline. The lender must identify the principal factors behind that model-based outcome. A method that ranks globally important variables across the portfolio may not explain this applicant. This is an analytical example, not prescribed notice language or a conclusion about any lender.
From the application to the delivered explanation
The following is a proposed control design. Its purpose is to make errors visible before they propagate to thousands of notices.
Scroll horizontally to see all columns.
| Stage | Evidence to retain | Failure to catch |
|---|---|---|
| Application | Input values, sources and completeness date | Wrong data or an incorrectly started notice clock |
| Decision | Rule and model versions; override rationale | Reasons taken from the wrong decision component |
| Explanation | Principal-factor mapping and approved wording | Generic wording or a factor not actually considered |
| Delivery | Notice contents, timing and delivery record | Accurate explanation sent too late |
| Monitoring | Sample reconstructions and complaint feedback | A mapping defect repeated across a product |
Testing beyond a readable letter
Analysis: sample both approvals near the cutoff and declines, across products and decision paths. Reproduce each decision from the preserved inputs, then compare the proposed reasons with the decisive factors. Include missing data, jointly decisive factors, overrides and changed model versions. Test whether small, irrelevant input changes produce large or implausible reason changes.
A second review should consider whether consumers can understand the wording. That review complements technical fidelity. Simpler words are useful only when they still convey the actual reason. The official commentary notes that giving more than four reasons is generally unlikely to help; that observation is not permission to omit a principal reason or mechanically fill four slots.
New evidence: explaining a hybrid underwriting decision
Affirm’s September 17 announcement describes a proprietary explanation method for its hybrid underwriting system. It is a useful current example of the explanation challenge, rather than independent proof that a particular notice satisfies Regulation B.
Analysis: validate the full decision path, including eligibility rules, transformations, model output, cutoff, overrides and the reason selected for the notice. A faithful explanation of one component may not explain the final decline. Use preserved inputs to reproduce the decision and test the notice against the factors actually considered.
Test missing or corrected bureau information, conflicting policy and model outcomes, joint reasons, and a switch between model versions. Record disagreements and correction ownership. Improvements in conversion or risk ranking do not answer these explanation questions.
Clarity and accuracy need separate measures
Hypothetical: in a sample of 500 denial notices, 20 use a generic reason that does not match the reconstructed decision. The observed mismatch rate is 4% in that sample. It is not a legal tolerance or necessarily a population estimate; the sampling method and concentration in particular decision paths matter.
Analysis: identify whether those 20 cases share a policy rule, model version, override path or data conversion. Correcting only the wording of the sampled notices leaves the production cause unresolved. Equally, rewriting every notice in simpler language does not solve a mapping error that selects the wrong reason.
Measure understandable wording, reason fidelity, timely delivery and effective handling of corrected information separately. A useful explanation can make the service more accountable and reduce repeated contacts while still conveying an unfavorable decision. Customer satisfaction alone cannot establish that the reasons were accurate.
What would change the assessment
An improved model that increases approvals can still create an explanation problem if its reasons cannot be validated. Conversely, a complex model is not automatically unusable because it is complex. The relevant evidence is repeatable decision reconstruction, specific reason fidelity, fair-lending review and effective correction when errors surface.
This article uses the current CFPB-hosted regulation and official interpretation accessed for this revision. It does not treat older AI circulars as an independent statement of current enforcement policy. Revisit the article when the regulation, authoritative interpretation or a material judicial decision changes the notice requirements; preserve the prior research version for comparison.