Validates adverse action notices for Reg B compliance (12 CFR §1002.9). Checks reason count limits (max 4), prohibited vague codes (CFPB Circular 2023-03), required content fields, and FCRA §615(a) credit-score disclosure rights when a credit report was used. Table: REG-B-ADVERSE-ACTION-2024-CFPB-CIRC-2023-03.
Reg B §1002.9FCRA §615(a)CFPB Circular 2023-03Notice ValidationAdverse Action
🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
ⓘ Not legal or compliance advice. Verify all outputs against current CFPB, Federal Reserve, and ECOA publications before use in production decisions.
Notice Metadata
The credit decision that triggered the adverse action notice requirement under Reg B §1002.9.
Score model whose reason codes appear on the notice. FICO and VantageScore have different vague-code lists per CFPB Circular 2023-03.
Reason Codes (up to 4)
Enter the reason codes from the notice. Reg B §1002.9(b)(2) permits up to 4 principal reasons. CFPB Circular 2023-03 prohibits vague codes such as z_other, other, and no_reason_given.
Credit Score Disclosure (FCRA §615(a))
If yes, FCRA §615(a) requires the notice to include the score, range, key factors, date obtained, and CRA contact information.
Required Notice Content Checklist
Check each field that is present in the notice. Missing required fields are flagged as violations.