Amelia closed her eyes.
Lorraine Carter's letter was no longer an isolated story.
Neither was her own experience.
Different customers.
Different backgrounds.
The same message.
You don't belong here.
The bank was supposed to safeguard money.
Instead, some employees appeared to be acting as though the right to receive basic information depended on whether they found the customer sufficiently impressive.
Amelia called Aisha.
"We need to examine how many people were treated this way."
The compliance officer nodded.
"We're already expanding the sample."
Amelia took a breath.
"And I want to know whether any of them were routed toward higher-cost products or third parties without proper disclosures."
Aisha became quiet.
Then said, "That's one of the concerns I was about to raise."
The next morning, the first major discrepancy emerged.
The downtown branch reported an unusually low rejection rate for new accounts.
But the intake records showed hundreds of incomplete applications coded as voluntarily withdrawn.
The distinction had helped Keller's performance reports look exceptional.
An application rejected by the bank could trigger additional review and affect certain operational measures.
An application withdrawn by the customer carried a different implication.
It suggested the bank had been ready to serve the person, but the person chose to leave.
The auditors selected a sample of those records.
Some withdrawals were legitimate.
Customers had changed their minds.
Others failed to provide required documents and decided not to continue.
But a significant number followed a different pattern.
The applicant entered the branch.
An employee made a preliminary assessment using Project Meridian.
The customer was told to pursue another channel.
Then the system recorded that the customer had voluntarily withdrawn.
There was no indication that the applicant understood the bank was treating the encounter as a withdrawal.
And in several cases, employees had entered the code before the scheduled consultation was supposed to begin.
Aisha examined the timestamps.
Then looked toward her analyst.
"Are we certain the branch system records those times automatically?"
The analyst nodded.
"Yes."
"Can they be changed?"
"Not through the ordinary front-end interface. Corrections create additional audit entries."
Aisha leaned forward.
"Then preserve the audit entries."
The analyst nodded.
And began tracing the accounts.
By lunchtime, the team had identified a pattern connecting the questionable classifications to a small group of employees who handled preliminary intake decisions under Keller and Cynthia's supervision.
Sofia's name appeared on several entries.
For a moment, Aisha became concerned.
Then she examined the times.