Madison came into my office the following Monday with her shoulders squared.
She had a paper cup of coffee and a neat black notebook.
Dana sat beside me.
A neutral human-resources consultant named Theresa joined by video.
We explained that Madison could bring a representative if she wanted and that the meeting was for fact-finding.
No one asked her to waive legal rights.
No one threatened to call the police unless she admitted wrongdoing.
I had learned that a rushed confrontation could damage both an investigation and a person's reputation.
Madison said the black device was a portable payment reader.
“Kyle brought it in when the other terminal was slow.”
“Which payment provider issued it?” Dana asked.
“I don't know.”
“Did you process transactions through it?”
“Sometimes.”
“Where did the receipts go?”
“To Kyle.”
She looked at me.
“I was told it belonged to a restaurant group he worked with.”
I asked whether she had questioned why our own approved terminals weren't enough.
She said Kyle had described it as a trial system.
“Did customers consent to having their cards used on two devices?”
“I thought it just checked rewards.”
Her answer was not impossible.
It was also not enough to clear up the situation.
Dana asked how often Kyle was present.
Madison said he usually supervised the afternoon shift and brought the device himself.
She admitted telling lower-spending guests there were no tables.
“Kyle wanted us to protect the average check.”
“Did you believe that was an appropriate way to treat people?” I asked.
She stared at her coffee.
“Everybody needs this job.”
It was the first time her voice sounded young.
I remembered how easily I had judged her from one ugly encounter.
Her actions were wrong.
But it mattered whether she had been following an abusive manager's instructions, participating in fraud, or both.
After the interview, Theresa placed Madison on paid leave while the device and customer records were examined.
We gave her an anti-retaliation contact number and asked her to preserve relevant messages.
Later that afternoon, Evelyn called.
She had found something unusual in the monthly reconciliation files.
Kyle maintained a separate spreadsheet labeled service recovery adjustments.
It was not listed in our accounting procedures.
Inside were payments described as refunds, hospitality charges, and promotional credits.
Some entries were matched to the correct transaction numbers.
Others had no traceable merchant reference.
Several were marked with initials that appeared to refer to Madison.
None of this proved a card-data crime.
But it raised a second question about money moving through a system Kyle controlled.
Evelyn compared the spreadsheet to verified bank deposits.
The cash totals had discrepancies too.
They were small enough to be dismissed as mistakes in a busy restaurant.
Together, they deserved a closer look.
I wanted to call Kyle.
Dana advised against doing that before preserving the records.
We copied the spreadsheet from the company account using a documented process.
The original stayed untouched.
A forensic accountant named Omar Singh was brought in to review transaction records and access logs.
He asked us not to jump from “unexplained” to “stolen.”
“Money in restaurants doesn't always follow a tidy line,” he told me.
“Tips, voids, refunds, vendor credits, and chargebacks create noise.”
“I know.”
“Then let's separate noise from losses.”
He began with a list of every person authorized to approve refunds.
Kyle appeared on the list.
I did too.
A former supervisor appeared, though she had left six months earlier.
Her credentials should have been deactivated.
I felt a wave of embarrassment.
Omar also wanted to know how voided meals were handled.
In a restaurant, an incorrect order might be removed for an innocent reason.
A guest could change their mind.
A kitchen could prepare the wrong dish.
A server could enter the same item twice.
Those adjustments had to be possible without turning every error into an accusation.
Our old procedure allowed a manager to void a small order without attaching a reason.
Kyle had preferred it because it was fast.
During a busy shift, speed sounded appealing.
But the lack of documentation made later review almost impossible.
Omar showed me several examples.
One voided sandwich corresponded to a kitchen ticket marked wrong bread.
That looked ordinary.
Another canceled meal had no explanation and occurred after closing.
That needed investigation.
He taught me to ask what the record actually supported.
Not what my anger wanted it to mean.
We tested the new process during a lunch rush.
A server named Nicole entered soup instead of salad.
She approached Denise for a correction.
Denise approved it and selected the documented reason.
It took perhaps twenty seconds.
Nicole seemed nervous.
“Am I going to get written up?”
“No,” Denise answered.
“People make mistakes. The record just needs to show what happened.”
I watched Nicole relax.
That was a kind of training I had never considered.
Good controls shouldn't frighten honest employees away from reporting errors.
If every correction brought punishment, people would hide problems instead.
After service, Omar reviewed the updated report and found the void traceable.
He smiled.
“This is what a usable record looks like.”
It seemed a small victory compared with the uncertain reader investigation.
But it was progress we could measure.
In the evening, Denise asked whether I wanted to approve every void personally.
“No,” I said.
“I want a process that works when I'm not standing next to you.”
She nodded.
That sentence was becoming the real test of my ownership.
Our procedures had been more careless than I wanted to admit.
When I hired Kyle, he'd promised to improve those controls.
He had never completed the access review.
And I had never checked.
While Omar worked, Amber came to my office carrying a small envelope.
“I don't want to make a big deal of this,” she said.
Inside were two written warnings from Kyle.
One accused her of giving discounts without permission.
The other said she had damaged Rosie's image by seating visibly distressed guests near the window.
Both were signed by Kyle.
Neither had been copied to the employee personnel system.
“Why didn't you come to me?” I asked.
Amber hesitated.
“Do you remember the meeting last winter?”
I did.
A snowstorm had cut business in half.
Kyle had proposed reduced staffing.
Amber had asked whether servers would still receive promised minimum shifts.
I had told Kyle to handle it.
“Afterward, he told me you didn't want employees bringing you complaints,” she said.
“I never said that.”
“I believe you now.”
Her words landed harder than anger.
The way I had delegated problems made Kyle's claim believable.
I thanked her for keeping the documents.
Then I asked what she wanted from the restaurant.
Not what punishment she wanted Kyle to receive.
What she needed to feel safe working there.
She considered the question.
“A way to report something without the person I'm reporting getting the complaint first.”
I wrote that down.
“And I want the rules to be the same when you're here and when you're not.”
I wrote that down too.
The next day, Omar found the first transaction he could conclusively describe as improperly approved.
A refund had been issued to a card that did not match the card used for the original sale.
The original customer's meal was legitimate.
The refund was not documented as a customer request.
A manager credential had authorized it.
It was one entry.
Not the full explanation.
But it was no longer merely an uncomfortable suspicion about behavior at the register.
Someone had used our financial systems in a way the records could not justify.
Omar looked up at me from his laptop.
“Frank, now we need to find out who controlled that credential at that time.”
I nodded.
I had wanted simple answers when I walked into Rosie's in torn clothes.
Instead, I was learning how many kinds of trust a business can lose before its owner notices.
Click here to continue reading: PART 5: The Card Processor Traced the Extra Reader While Kyle Tried to Control the Story
The Day I Entered My Mother’s Restaurant With Four Dollars and No One Recognized Me
Part 4 of 16
