The person signing the checks may be the person you trust most. That is exactly why you verify the checks.
In my Certified Fraud Examiner studies, I keep returning to one hard truth: fraud does not always arrive as a stranger breaking through the perimeter. Sometimes it is already inside, with legitimate access, familiar routines, and no independent review. Two cases (one in Florida, one in Minnesota) show different ways that breach can happen. They are not connected. The lesson is.
Access is not authorization. Familiarity is not proof. And trust, by itself, is not a control.
Case One: The bookkeeper nobody suspected
The video investigation of Jessica McKinnon, a longtime bookkeeper in Santa Rosa County, Florida, describes an estimated $1.2 million embezzled from her employer between 2019 and 2023. The case involved check fraud with a forged maker, payroll manipulation, and electronic transfers. According to the video, the money went toward designer clothing, travel, and plastic surgery.
The video says McKinnon told her employer false stories about bonuses and raises to explain missing funds, maintaining what investigators characterized as a false life for years. Investigators subpoenaed bank records to trace deposits into her account. The video recounts her arrest outside her home after the investigation surfaced.
The case eventually reached a guilty plea to grand theft over $100,000. The initial charges described in the video (including fraud, money laundering, and unlawful use of a two-way communication device) did not remain in the case. In July 2026, a judge sentenced McKinnon to 12 years in Florida state prison and ordered approximately $1.2 million in restitution.
Watch the investigation here: The Call Is Coming From Inside the House
McKinnon, the video notes, was a previously convicted felon at the time of this scheme. At one point in the footage, an investigator tells her husband that she had thirty-one prior felony convictions from a case going back twenty years. The footage also shows investigators speaking with her husband, whom the video identifies as an engineer for a fire-suppression company. What stands out in that interview is what the husband does not do: he does not hold her record against her. The footage shows a man standing by his wife through her arrest. His loyalty is his own business, and the footage captures it plainly. But for anyone designing financial controls, the prior record is exactly the kind of background fact a diligent employer checks, because a trusted position built on familiarity instead of verification is how this scheme ran for years. Those details are not evidence of the financial scheme, and they do not change the accounting lesson: controls should be designed around records and verification, not assumptions about someone’s household or character.
Source: Fraud investigation video documenting the Jessica McKinnon case
The Fraud Triangle: Read the evidence, not the story we invent
The Fraud Triangle gives us a useful framework: opportunity, pressure, and rationalization. It is a way to examine conditions, not a license to claim we know what someone was thinking.
Opportunity was the open door. McKinnon’s role gave her access to bookkeeping and payroll processes. When one person can initiate, record, and influence financial transactions without truly independent review, the opportunity for occupational fraud grows. Access to a system is not permission to use it for personal gain.
Rationalization appears, in the video’s account, in the repeated stories about bonuses and raises. Those explanations helped make missing money seem legitimate to the employer. They are part of the reported scheme; I cannot claim to know McKinnon’s private reasoning.
Pressure requires the same discipline. The reported spending shows where some of the money went. It does not, by itself, establish what pressure she felt or why she acted. A careful CFE lens separates documented conduct from speculation. That distinction matters. We protect the perimeter with evidence, not guesses.
Case Two: The meal count that became a federal verdict
In Minnesota, the breach was not a single bookkeeper’s access to an employer’s accounts. It was paperwork submitted to a public program, and claims that, prosecutors proved, did not match reality.
FOX 9 Minneapolis–St. Paul reporter Paul Blume reported that a federal jury found Muna Wais Fidhin, of Savage, Minnesota, guilty on all nine counts: wire fraud, federal programs bribery, and money laundering. The jury deliberated for less than three hours after a nearly three-week trial.
Prosecutors proved that Fidhin enrolled M5 Café and M5 Care in the Federal Child Nutrition Program and claimed more than 300,000 meals had been served. She billed the government approximately $1 million and paid about $27,000 in kickbacks to a Feeding Our Future insider. FOX 9 reported that about $550,000 reached her and was spent in part on personal expenses, including a home mortgage and a luxury SUV loan. The evidence included fake child rosters, fabricated invoices, and inflated reimbursement submissions.
Federal prosecutor Austin Bowyer put the issue plainly: “You do not act in good faith with grossly inaccurate meal claims. That is not an accident, that is a lie.”
In closing, defense attorney Steve Schleicher called Fidhin “a person, not a fraud,” and argued that she trusted the wrong people. That was the defense’s position. The jury returned its verdict. Fidhin became the 75th defendant convicted in the sprawling Feeding Our Future scheme. After the verdict, U.S. District Judge Nancy Brasel rejected the prosecution’s request to detain her and ordered electronic home monitoring pending sentencing. FOX 9 reported that no sentencing date had been set.
Source: Paul Blume, FOX 9 Minneapolis–St. Paul, “Guilty verdict: Jury convicts fraudster in $1 million Feeding our Future fraud scheme,” October 21, 2026.
Two doors into the same house
The Florida case is occupational fraud: a trusted insider with access to financial processes. The Minnesota case is fraud against a public program: claims and documents presented as proof of meals served. Different doors. Same underlying vulnerability: people and systems accepted what they were given without enough independent verification.
One case used payroll and financial transactions. The other used meal counts, rosters, invoices, and reimbursement requests. In both, access and paperwork created an appearance of legitimacy. Neither appearance should have been mistaken for proof.
That is the scale lesson. Fraud can exploit one employer’s internal controls or a large program’s verification process. When a system funds claims instead of confirmed outcomes, the paperwork can become the product.
Protect the perimeter
Separate the duties. Never let one person control writing checks, recording transactions, and reconciling the accounts. If staffing is limited, build an independent review into the process. Small organizations need controls too; being small is not a reason to leave the door open.
Reconcile bank statements yourself, or assign that work to someone independent of the person handling payments and bookkeeping. Compare the statement with the accounting records, investigate unfamiliar transactions, and follow every discrepancy to resolution. A reconciliation done by the same person who created the records is not independent oversight.
Verify claims against reality. Check meal rosters against reliable attendance records and invoices against meals actually served. Confirm that the service, goods, or work being billed can be independently substantiated. Fund outcomes, not paperwork.
Treat kickbacks as a red flag, not a side issue. In the Minnesota case, FOX 9 reported approximately $27,000 in kickbacks alongside approximately $1 million in billing. A payment intended to keep a pipeline flowing can signal that the pipeline itself needs examination.
And never confuse familiarity with assurance. A trusted employee still needs oversight. A detailed invoice still needs verification. A confident explanation still needs evidence.
The AfroDruids ethos emphasizes financial literacy and using tools to protect what matters. My security standard is simple: trust is not verification. Access is not authorization. Familiarity is not proof. We don't confuse confidence with credibility, and we don't fund anyone's fantasy.
When the numbers require belief instead of proof, stop. Ask for the records. Verify independently. Walk away from the claim until it stands on evidence.
Felicia Baxter
TN Private Investigator
blkladypinkertonsdetectiveagency.com
