Assess whether notices match the actual decisioning reasons (50b371)

SITUATION Model-reason-code mapping that does not match notices arrived with a branch that stopped taking applications in one ZIP for HMDA data-quality manager. That is a Fair Lending Redlining and HMDA Data decision on notices match the actual in a credit-card issuer changing line-assignment logic.

DECISION HMDA data-quality manager in a credit-card issuer changing line-assignment logic must choose Remove access or reverse the item / Temporary compensating control / Approve a documented exception / Hold using model-reason-code mapping that does not match notices after a branch that stopped taking applications in one ZIP.

HYPOTHESES TO TEST 1. Model-reason-code mapping that does not match notices reads as Remove access or reverse the item once a branch that stopped taking applications in one ZIP is lined up to the same Fair Lending population. 2. Model-reason-code mapping that does not match notices is closer to Temporary compensating control after a branch that stopped taking applications in one ZIP; Remove access or reverse the item would over-claim this Redlining and HMDA Data extract. 3. Approve a documented exception is still live in model-reason-code mapping that does not match notices for HMDA data-quality manager in a credit-card issuer changing line-assignment logic. 4. Model-reason-code mapping that does not match notices is missing the fact HMDA data-quality manager needs after a branch that stopped taking applications in one ZIP; stop this Fair Lending close.

ANALYSIS REQUIRED 1. Match the adverse-action language to the facts in model-reason-code mapping that does not match notices. 2. Check HMDA coding and underwriting policy against notices match the actual. 3. Compare model-reason-code mapping that does not match notices to similarly situated files, second-review notes, and reason codes after a branch that stopped taking applications in one ZIP. 4. For this Fair Lending Redlining and HMDA Data file, read model-reason-code mapping that does not match notices against a branch that stopped taking applications in one ZIP and write the one fact that would move notices match the actual for HMDA data-quality manager.

RECOMMENDATION Choose Remove access or reverse the item / Temporary compensating control / Approve a documented exception / Hold on this Fair Lending / Redlining and HMDA Data packet (model-reason-code mapping that does not match notices after a branch that stopped taking applications in one ZIP). Lead with the Fair Lending option model-reason-code mapping that does not match notices can support after a branch that stopped taking applications in one ZIP, then the two facts that force it, then the Monday action for HMDA data-quality manager in a credit-card issuer changing line-assignment logic.