Louise looked at her.
“You too.”
Susan nodded.
“We should have listened sooner.”
That afternoon, Cedar Grove Storage froze every pending auction at the property.
Not permanently.
For review.
Susan required payment reconciliation on every delinquent account that had existed before the renumbering conversion.
At first, Ray called the decision excessive.
He was no longer on site to object.
The review found two other legacy-account problems.
Neither customer had reached auction yet.
One account showed two missing payments that had actually been posted to an obsolete customer profile.
Another had a mailing address corrupted during migration.
Both were corrected.
Susan realized Louise’s case was not only a human mistake.
It was a system problem that had been hidden by manual workarounds.
Julie Parker, the retired office administrator, had noticed the payment mismatch years earlier.
Instead of forcing a full software correction, she had transferred Louise’s payment manually each month.
She had left handwritten notes in a binder.
TRANSFER 3152 CREDIT TO 170.
HARRISON LEGACY AUTOPAY.
DO NOT DELETE TOKEN UNTIL NEW AUTHORIZATION RECEIVED.
But no one had formally updated the account.
When Julie retired, the manual step disappeared.
The system did exactly what it had always been doing.
The problem had simply lost the person quietly correcting it.
Susan called Julie.
She remembered Louise immediately.
“Harold Harrison?”
Julie asked.
“Yes.”
“Oh.”
“That old account.”
Susan closed her eyes.
“You knew?”
“I told IT three times.”
“They said the payment token couldn’t be moved without the cardholder authorizing again.”
“Harold was the original cardholder.”
“He died.”
“Louise didn’t want to change the bank draft.”
“So I transferred it manually.”
“Every month?”
“For years.”
“Why didn’t this get escalated?”
Julie laughed sadly.
“Susan.”
“We were always understaffed.”
“That isn’t an answer.”
“No.”
“It isn’t.”
Susan wrote everything down.
The software had a flaw.
The procedure had a gap.
But neither explained Ray’s behavior.
That required a different review.
Megan provided a statement.
Mike provided one.
Tom was asked whether he would document what he witnessed.
He did.
Louise hesitated.
Then agreed.
Not because she wanted Ray punished.
Because Susan told her:
“If we only fix your account, we can pretend the problem was numbers.”
“It wasn’t.”
Louise understood.
The review found earlier complaints.
Two tenants said Ray had been dismissive during billing disputes.
One elderly customer claimed he had refused to pause lien processing while she waited for a bank letter.
That account turned out to be legitimately overdue, but Susan still noted the manner in which the dispute had been handled.
Another tenant had complained after his unit number changed and gate access stopped working.
Ray marked the issue:
CUSTOMER CONFUSION.
No investigation.
The pattern mattered.
Ray was not stealing.
He had not deliberately targeted Louise.
In some ways, that made the lesson more uncomfortable.
He trusted the system because trusting it made his work faster.
When facts complicated the screen, he treated the customer as the complication.
During his final interview, Susan asked:
“What did you think when she showed you the bank statements?”
Ray answered:
“That they showed withdrawals.”
“Did it occur to you that we might have the money?”
“Maybe.”
“Why didn’t you check?”
“I had an auction schedule.”
Susan looked at him.
“That is the answer.”
Ray frowned.
“What?”
“You treated the schedule as more reliable than the person standing in front of you with evidence.”
Ray said:
“I didn’t create the billing error.”
“No.”
“You created the decision to keep moving after you had reason to doubt it.”
The company terminated his employment the following week.
Louise did not celebrate.
When Susan called to inform her, Louise became quiet.
“I don’t like thinking somebody lost his job because of me.”
Susan corrected her gently.
“He did not lose his job because of you.”