Case Study 25-1: The Clean Jacket — Priya Catches a Red Flag (Done Right)
A fully worked F&I office walkthrough showing the deal jacket, the six-law checklist in motion, and a red flag resolved the professional way. All people and figures are illustrative composites consistent with this book's canon (Tier-3). Not real individuals or companies.
Setup
The store: Summit Auto Group, used department. The F&I manager: Priya Nair (our canonical ethical, fast, disclosure-first F&I manager). The salesperson: Jordan Banks (our green pea), who sold the deal. The customers: The Rivera family — Marco and Elena Rivera, mid-30s, one child — buying a 3-year-old midsize SUV, certified pre-owned.
The deal as it arrives in F&I (from the floor):
| Line | Amount |
|---|---|
| Selling price (CPO SUV) | $27,500 |
| Doc fee | $599 |
| Title & registration (est.) | $401 |
| Sales tax (6%, on price, no trade) | $1,650 |
| Down payment (cash) | $3,000 |
| Amount to finance (pre-products) | $27,150 |
Marco's stated credit puts him in the prime tier (recall the illustrative tiers from Chapter 22: prime ≈ 660–779). It's 7:40 p.m. on a Thursday. The child is asleep on a lobby chair. Everyone is tired and happy.
What Happens
Step 1 — Priya reads the documents (she always does)
Before she touches the lender portal, Priya assembles and reads the deal jacket. Not skims — reads. Three things don't line up:
- Addresses don't match. The credit application lists Maple Court. The driver's license says Birchwood Lane. The proof of insurance Marco texted shows a third street.
- Income vs. pay stub. The application's income line is noticeably higher than the stapled pay stub supports when she does the quick monthly-to-annual math.
- SSN history. The basic format check on the Social Security number passes, but the address history attached to the credit file includes none of the three stated streets.
Individually, none of these is automatically fraud. Together, they are exactly the red flags the Red Flags Rule (Chapter 25, §25.4) requires her to notice and act on.
Step 2 — The bad option (which she does not take)
The lazy/greedy move is obvious and available: it's late, the portal is open, the customer is prime, a few keystrokes funds the deal and books the commission. The little voice that says something's off gets shushed because the deal is good.
Priya does not shush it. A red flag is a reason to slow down, not speed up.
Step 3 — The professional verification (warm, no accusation)
Priya steps into the lobby, sits with the Riveras, and frames it as routine:
Priya: "Marco, Elena — almost done, you're going to love this SUV. I just want to confirm a couple of details so everything's exactly right and your loan funds without a hitch. Totally normal. Can we double-check your current address and your income line together?"
No accusation. No "your numbers look fake." Just verification, framed as service. Here's what surfaces:
- The addresses: The Riveras moved six weeks ago. Marco hadn't updated his license; the insurance binder still showed the old place; he'd written the new address on the application from memory but transposed "Maple" for "Maplewood." Innocent — a recent move plus a lagging license. They show Priya a utility bill and the lease at the new address.
- The income: Marco listed his and Elena's combined household income on a line the application wanted as his individual income. His pay stub is for his job alone. Once Priya separates them — his income on his line, Elena's part-time income noted appropriately — the math reconciles cleanly.
Ten minutes. The picture is now consistent and supportable.
Step 4 — Priya runs the six-law checklist (silently, by habit)
This is the part a customer never sees. Priya's process is the compliance program:
| Law | What Priya does on this deal |
|---|---|
| TILA | Builds the RISC so the APR, finance charge, amount financed, total of payments match exactly what Marco agreed to. |
| ECOA | Treats Marco by the same prime-tier standard and product menu as any prime customer — no markup or product change based on anything but the deal. |
| FCRA | Confirms Marco's signed authorization (permissible purpose) is in the jacket; the credit pull was legitimate. Prime tier → no adverse action; risk-based pricing handled per policy. |
| GLBA | The pay stub and SSN are handled securely — nothing left face-up, nothing texted in the clear beyond what the customer themselves sent, file controlled. Privacy notice provided. |
| Red Flags | The whole verification above is the Red Flags response: flags noticed, resolved, and documented before funding. |
| OFAC | The automated OFAC screen ran clean. |
She also documents the corrections — a note in the file explaining the address transposition and the income-line clarification, with the supporting bill/lease referenced. If anyone ever questions this deal, the jacket explains itself.
Step 5 — The menu (Chapter 24), then the RISC
Now Priya does the other half of her job — the F&I products — exactly as in Chapter 24: screen turned, every product priced, "buy nothing" shown as legitimate. For a CPO SUV the Riveras plan to keep, they take a vehicle service contract to extend coverage past the CPO warranty and decline the rest. Those products get financed into the RISC, which now shows an honest, accurate TILA box. She names every document as she places it: "This is your buyer's order — it matches the desk. This is the privacy notice. This is your loan contract, the RISC; this boxed section is the federal Truth-in-Lending disclosure — here's your APR, here's the total finance charge, here's what you'll have paid at the end." Then title, registration, odometer disclosure.
Step 6 — Delivery and the result
Jordan does a proper delivery (Chapter 15 — phone paired, child's seat checked, photo, a thank-you note that night). The deal funds Friday morning without a hitch. The Riveras leave understanding what they signed.
Two years later they buy their daughter's first car from Priya and have sent two referrals. The "kept gross" and the relationship — not a packed payment — are where the money actually came from (theme #3).
Analysis: What Worked, and Why
1. She read the documents. The entire case turns on a habit that looks like nothing: reading the jacket before funding. The red flags were in the file. A skimmer funds the deal blind.
2. A red flag slowed her down, not sped her up. The tired-Thursday pressure pushes toward "just fund it." The Red Flags Rule exists precisely to counter that pull. Priya treated "this doesn't add up" as a stop sign.
3. She verified warmly, not suspiciously. Most red flags resolve into innocent explanations (as these did). Accusing the Riveras would have poisoned a good deal and a future referral. Framing verification as "so it funds without a hitch" kept it service, not interrogation (theme #5).
4. She documented the resolution. This is what separates a defensible deal from a merely funded one. The note in the jacket means the deal explains itself to any future auditor, lender, or lawyer.
5. Compliance and ethics were the same act. Running the six-law checklist was taking care of the Riveras. The legal floor and the right thing pointed the same direction — which is the chapter's whole thesis.
The counterfactual that matters: had the inconsistencies been the fingerprints of synthetic identity or income falsification instead of an honest move and a misread line, Priya's ten minutes would have caught a fraud that could have forced a lender repurchase, triggered a compliance failure, and put her license at risk. She didn't know in advance which it was. That's the point. You verify every time, because you can't tell the innocent mismatch from the fraudulent one without checking.
Discussion Questions
- List every document Priya read or produced and match each to the law it serves. Which single document carried the most legal weight, and why?
- Priya framed verification as "so your loan funds without a hitch." Draft two other warm, non-accusatory ways to ask a customer to verify a mismatched address or income. Why does framing matter so much here?
- Why is documenting the resolution as important as resolving the issue? What does the note protect, and whom?
- Suppose the income line had not reconciled — Marco's verifiable income genuinely didn't support the payment. What are Priya's ethical options, and how do they connect to the Devon Wallace ethical-subprime path in Chapter 26?
- The Riveras produced two referrals over two years. Tie this concretely to theme #3 (ethics are profitable): how does a clean, documented, well-explained F&I experience generate more lifetime gross than a packed payment would have?
Your Turn (Mini-Task)
Take this exact deal jacket and redact one document — pick the credit application, the privacy notice, or the odometer disclosure. Write a short paragraph on (a) which law that missing document implicates, (b) what could go wrong downstream because it's missing, and (c) the step Priya's process would have used to catch the gap before funding. Then add the missing document to your Deal-Jacket Map from the Chapter 25 Project Checkpoint, with a one-line "what missing looks like" note.