The accounting team began with forty randomly selected reservations.
They compared advertised rates, booking confirmations, final folios, and refund records.
I asked Nina for a summary rather than unrestricted access to guest information.
Names and card details were not necessary for me to understand what was happening.
By Thursday, the first report showed something troubling.
Some guests had paid the heritage preservation fee after it was removed from company policy.
Others had received quotes with the fee but canceled before paying.
Still others had been offered waivers after complaining.
There was no consistent rule.
“Could the billing software be wrong?” I asked.
“Partly,” Nina said. “But a system doesn't decide who gets a waiver based on their shoes.”
She explained that managers had authority to add packages to certain reservations and override charges manually.
The investigators were comparing those actions with reservation notes.
Several notes included phrases such as high-maintenance guest, uncertain payment, and price-sensitive arrival.
Some were ordinary service descriptions.
Others appeared to be judgments unrelated to a guest's booking.
“Don't assume intent from a phrase,” Nina warned.
“I won't.”
Nevertheless, I remembered Sterling looking at my old truck.
The receipt had not appeared by accident.
The accounting team also identified a second concern.
A portion of the charge had been recorded under an internal maintenance category.
That did not automatically mean someone took the money.
Revenue classifications can be mistaken without concealment.
But the property had used the fee long after receiving instructions to stop.
We owed guests an explanation.
I asked Nina whether we should begin refunds immediately.
“First establish the full affected population,” she said. “Then notify them with a clear correction.”
“What about those who canceled because of the quote?”
“We need a separate remedy. They didn't pay, but they may have lost deposits or alternative reservations.”
I agreed.
Before that meeting, the accounting firm sent a list of questions about the original fee policy.
Why had we created the heritage charge in the first place?
What work had it supposedly funded?
Who had authority to discontinue it?
The answers were less sinister than I had feared and more embarrassing than I liked.
Years earlier, we had established a clearly disclosed preservation contribution as part of certain optional historical-tour packages.
A portion supported building conservation.
It was never meant to appear automatically on every ordinary room reservation.
Over time, some properties had folded it into broad pricing categories.
When we reviewed the practice, we decided the confusion outweighed any benefit.
I had ordered the line eliminated across the group four months before my visit.
That instruction should have ended the matter.
Instead, one property kept using it.
The investigators asked whether preservation work had actually been performed.
Our maintenance records showed legitimate restoration spending.
But legitimate expenses did not justify charging guests a fee they had not authorized.
I wrote that distinction at the top of my notes.
It would be tempting to say the money had been stolen from a preservation fund.
There was no evidence of that.
The problem was the misleading billing itself.
The accountants then showed me how reservation systems recorded adjustments.
A clerk could select a package from a menu.
A manager could approve a different rate.
A guest's folio would retain timestamps for the additions.
But a shared workstation might make the identity of the person at the keyboard harder to establish.
That meant records had to be interpreted carefully and checked against other evidence.
I asked whether the extra charges on my proposed bill had all been authorized by Sterling.
“We don't know that yet,” the lead accountant said.
“His approval is attached to the pricing configuration, not necessarily every individual click.”
I accepted the correction.
The review was teaching me patience at a time when patience felt particularly difficult.
At lunch I walked to a bench outside the regional office.
I ate a sandwich wrapped in waxed paper.
A maintenance van pulled into the neighboring lot.
The driver got out, stretched his back, and drank water from a metal bottle.
I wondered how many times he had arrived at a hotel reception in dirty work clothes.
Would someone assume he could not afford the room?
Would they tell him he didn't belong?
I thought of the many people who never came to us for luxury.
Some came for weddings.
Some came because a loved one was in the nearby hospital.
Some were workers repairing the road.
Some were older couples spending savings on one special weekend.
None should have to prove status before receiving an honest bill.
By the time I returned to the meeting room, I knew our revised training needed practical examples like those.
Not just a statement about treating everyone equally.
Specific examples of assumptions staff must never make.
The following morning I sat with Carmen in a meeting room at the regional office.
She brought a binder rather than a slideshow.
Inside were staff schedules, duty rosters, training records, and notes from interviews.
She did not give me confidential statements.
Instead she described common themes.
Employees said service expectations had become inconsistent.
A guest with expensive luggage could get a courtesy upgrade.
A guest who asked for written prices could be labeled difficult.
Several workers had heard remarks about people who drove older vehicles.
Not everyone participated.
Some employees challenged the behavior quietly.
Others stayed silent because their schedules depended on management approval.
I asked whether Kendall had been interviewed.
“She has been invited,” Carmen said. “She hasn't decided yet.”
“Don't pressure her.”
“I won't.”
She turned a page.
“The housekeeping time records are a more immediate issue.”
Some staff reported arriving twenty minutes before their recorded shifts to prepare carts and collect supplies.
A supervisor's messages suggested those preparations were expected.
The payroll system did not always capture the time.
“If they're required to work, they must be paid,” I said.
“That's the concern. Counsel is reviewing the applicable wage rules and records.”
“Can we make sure current shifts are recorded correctly today?”
“Yes. We can correct the practice while calculating what is owed.”
We also audited the way promotional offers were displayed on the hotel's website.
One discount appeared prominently on the home page but required several conditions that were easy to miss.
The legal team reviewed the wording and asked marketing to make the conditions visible before guests began booking.
Another offer had expired but remained accessible through an old search result.
That page was corrected and redirected to current information.
I asked whether we could test the website with people who did not use booking platforms regularly.
The marketing director arranged a small usability review with volunteers who had no business relationship with the hotel.
Participants were asked to locate total prices, parking information, cancellation terms, and accessibility details.
Several struggled to find the cancellation policy on a mobile phone.
We moved it closer to the rate selection screen.
A participant asked why the total changed after choosing a room.
The designer demonstrated how taxes were added.
“Then show that earlier,” the participant said.
It was a sensible request.
The new layout showed a clear estimate before collecting payment information.
I had thought of the issue as a front-desk problem.
The review showed it began before guests arrived.
A fair booking experience needed consistent information from first click to final receipt.
We documented each improvement and assigned an owner to test it after the next software update.
I did not want the problem to return because somebody assumed a corrected page would remain correct forever.
That afternoon Carmen posted a multilingual notice explaining that every required work minute must be recorded.
Employees could report discrepancies privately.
A third-party payroll specialist would review past periods without asking workers to waive claims.
I wanted to send Marisol a message.
I didn't.
She had spoken to me as a stranger in a truck.
I would not make her carry my feelings about doing the right thing.
Instead, I asked Carmen to confirm that all housekeeping staff had received the notice.
“Everyone,” she said.
“Even the people who are off this week?”
“It's being mailed and translated where needed.”
A practical answer was more useful than a dramatic promise.
Later that day Sterling sent a written response to the audit team.
He said the heritage fee remained active because a software migration had delayed removal.
He also said the high proposed charge on my reservation reflected an optional premium package.
Nina compared that explanation with the check-in record.
I had not selected any package.
The reservation note listed only room 312 and one night's stay.
The software showed manual additions at the desk.
Sterling's initials appeared on the authorization for the local configuration.
“The initials might have been entered by someone else,” Nina said.
“Then confirm who had access.”
“Exactly.”
I opened a photograph of Eleanor at the piano.
In it she wore a blue cardigan and laughed at something outside the frame.
I wanted to tell her what we had found.
I also wanted her to tell me I had missed the warning signs without making me feel foolish.
I had trusted quarterly reports.
I had trusted the regional structure.
I had trusted that a plaque on the wall represented a culture still alive beneath it.
Those were not entirely unreasonable beliefs.
But trust needed checking.
That evening Claire arrived from the city.
She found me in the hotel parking lot with two coffees.
“Still here?”
“Not sleeping in the truck this time.”
“Good. I was about to take your keys.”
We walked along the public path beside the grounds.
She asked about the investigation and listened without trying to solve it.
When I described the wage issue, she stopped.
“Dad, people depend on those paychecks.”
“I know.”
“Do you?”
I looked at her.
She softened her voice.
“I don't mean that cruelly. I mean do you know what missing two hours a week does to someone who lives paycheck to paycheck?”
“No,” I admitted. “Not the way they do.”
“Then listen before deciding what makes it right.”
I promised I would.
We stood beneath the dripping trees.
The hotel windows shone warm against the dark hillside.
For years I had thought of those lights as proof that Eleanor's dream was still there.
Now I knew a building could look welcoming from the road while treating the people inside it very differently.
Click here to continue reading: PART 5: The Young Clerk Finally Explained Why She Had Followed Sterling’s Lead
The Night I Returned to Our Hotel and Was Told to Sleep in My Truck
Part 4 of 12
