Chapter 7 - The dependent code
The executive program had been redesigned twice since Oliver died.
That helped Lenora.
Old records were messy.
The OM-117 code originally belonged to Oliver.
After death, human resources marked:
Deceased, inactive.
Six weeks later, someone reactivated it.
User credentials:
Lenora’s executive administration account.
Reason entered:
Continuing dependent care during family transition.
No such category existed in policy.
Then claims.
Invoice from Lucas’s school originally read:
Lucas Hale.
The copy attached to internal reimbursement packet showed:
O. Mercer.
Same amount.
Same date.
The name field altered.
Another:
Orthopedic therapy invoice.
Original:
Lucas Hale.
Internal PDF:
Oliver Mercer.
Then travel reimbursement:
Audrey and Lucas flying to a summer program.
Internal dependent name:
Oliver Mercer.
Oliver had been dead eight months.
No one noticed?
The program was self-funded.
Claims did not go through a health insurer with a live eligibility check.
Internal finance processed them.
Lenora, as board chair, had authority to approve exceptions above normal limits.
Her assistant entered coding.
Auditors saw:
Executive benefit.
Chair approval.
Receipts.
They sampled totals, not the underlying child’s identity.
Control failure.
Then tax treatment.
Benefits for an executive’s qualified dependent could receive different payroll treatment from benefits for another shareholder’s child or a personal gift.
By coding Lucas as my dependent under Oliver’s old profile, Lenora avoided:
Gift reporting issues.
Compensation disclosure to Audrey.
Program caps applicable to Audrey’s own benefits.
Board visibility.
It also made the payments appear tied to my household rather than hers.
I asked Nina:
“How much did the company report as benefits connected to me?”
“Some flowed through non-payroll reimbursement categories.”
“Meaning?”
“We have tax work to correct.”
May you like
Of course.
A dead child had remained alive in our accounting system because my mother found the code useful.
