Archive

Tag Archives: erp

A Home Depot gift card sales associate stole 8,325 physical gift cards with a combined value of $4,085,043. Felecia Ingram, 53, of Covington, Georgia, had worked for the company since 2008. She pleaded guilty to access device fraud on May 1, 2025, and the U.S. Attorney's Office for the Northern District of Georgia announced her sentence on February 26, 2026: three years and one month in prison.

What happened

From March 2020 through July 2021, according to the release, Ingram used her network access credentials to activate the stolen cards by creating false orders for them. News coverage says the orders made the cards look like they were meant for corporate events. After the cards were live, she deleted the false orders.

That is seventeen months. Divide the card value by the card count and each one averaged about $491.

The release says Home Depot found the fraud when its gift card team spotted a discrepancy in the gift card ledger balances. It does not say when the discrepancy first appeared, or how long it sat there.

Restitution came to $3,946,776, which is $138,267 below the face value of the cards. The release doesn't explain the gap.

Why the gap existed

Activating a gift card creates spendable value. That makes it a payment, whatever the system calls it. In this case the thing that triggered the activation was an order, and an order is a document an associate with the right access can create.

The deletion is what made it work. A false order sitting in the system next to an activated card is a question somebody can ask. A false order that has been removed leaves a card with value on it and nothing behind it. Nobody knows what to look up.

The sources describe the access in one phrase, network access credentials, and say nothing about what else those credentials allowed. They also don't say whether anyone approved the orders or whether activation waited on payment. If it did neither, the ledger was the only check left, and the ledger caught it.

Controls that would have caught it

Activation tied to a settled payment. A card shouldn't go live until payment has cleared against the order, or until a second person has approved a corporate order on the record. An order that creates value without settled payment should sit in a queue, not turn on a card.

No deleting orders that activated stored value. Cancel or void them, keep the original, and require a reason and a second approver. Whoever can create the order should not be the person who can remove it.

Physical stock counted against activations. Inactive cards are inventory, serial numbers included. A regular count of the cards on the shelf, compared to the cards sold and the cards activated on approved orders, turns a missing box into a number.

An AI prompt example for ERP fraud detection

This case calls for queries about activation, not about transactions after the fact. Against an ERP's order management and stored-value ledger, a controller could run something like:

"List all orders from the last three years that activated stored-value cards where no payment settled against the order, or where the order was later cancelled or deleted, grouped by the user who created it."

A second query goes after the stock:

"For each day, compare the count and face value of gift cards activated against cards sold at registers and cards on approved bulk orders, and flag any day where activations exceed both."

Neither query depends on knowing who to suspect. Both depend on the system keeping a record of deleted orders. In some systems that is a setting somebody has to turn on.

The pattern for this series

Part 12 was a CFO deleting credit card charges. This was an associate deleting orders. The release doesn't say how long the discrepancy had been in the ledger before the gift card team saw it.

Source disclaimer

The case details in this article are drawn from a press release published by the U.S. Attorney's Office for the Northern District of Georgia, a public government source, along with contemporaneous news reporting on the same case. All facts, figures, and quotations describing the case are sourced from those releases and reports. The analysis of the control gap, the proposed detection controls, and the AI prompt examples are original commentary and are not part of the source material.

References

United States Attorney's Office, Northern District of Georgia. Press release on the sentencing of Felecia Ingram for stealing gift cards from The Home Depot, February 26, 2026. https://www.justice.gov/usao-ndga/pr/former-home-depot-associate-sentenced-federal-prison-stealing-more-4-million-company

The Covington News. "Covington woman sentenced to prison after stealing $4 million in gift cards from Home Depot." https://www.covnews.com/news/crime/covington-woman-sentenced-to-prison-after-stealing-4-million-in-gift-cards-from-home-depot/


More of my writing lives at A Tinkerers Notebook.

My book Gamifying the Enterprise: Game Mechanics for Continuous Proficiency is on Amazon. All my books are on my Amazon author page.

The AD&D365 configuration guides are at adnd365.com/start.

Connect with me on LinkedIn.

Mandy Urban made more than 245 transfers out of her employer's bank accounts and into accounts she controlled, $1,115,344.73 in all. She was a senior staff accountant at a Charlotte company from January 2019 to June 2022. She pleaded guilty to wire fraud in March 2024 and was sentenced in February 2026 to 41 months in prison followed by two years of supervised release.

What happened

Her job covered a lot of ground. According to the U.S. Attorney's Office, she maintained the company's general ledger and prepared its financial statements. She also reconciled the accounts, bank statements included.

Divide $1,115,344.73 by 245 and you get about $4,552. The release says "more than" 245 transfers, so the real average sits lower. Then, in the release's words, she "falsified the company's books and records to conceal the scheme."

The release also lists two Florida convictions. In 2015 she was sentenced to five years of supervised probation for grand theft of about $135,000. In June 2022 she was sentenced to two years in prison for a different scheme to defraud. June 2022 is also the month her employment at the Charlotte company ends in the release's timeline. It does not say how that employment ended, or whether the two are connected.

Why the gap existed

In a company where the controls work, the ledger, the financial statements built from it, and the bank reconciliation check one another. Here one person held all of them. The release doesn't mention anyone else reviewing her work.

A bank transfer to an account that belongs to no vendor and no employee is a detectable event, provided something compares outgoing destinations to the master files. More than 245 of them is a pattern, however small each one was.

The 2015 conviction predates her start date by four years. It was public record on her first day. The release doesn't say whether anyone looked.

Controls that would have caught it

Keep bank reconciliation away from whoever posts to the ledger. The person who reconciles the cash accounts should not be able to post to them, and should work from statements that come straight from the bank. Preparing the financial statements is a different job again, which belongs to a different person where headcount allows and to an outside reviewer where it doesn't.

Match every outgoing transfer destination to the master files. A transfer needs a payee that exists in the vendor or employee records, with the account approved by someone other than the person releasing the payment. A new destination account should trigger a notification, not pass as a quiet setup step.

Screen finance hires, and rescreen them, with the results held outside finance. Anyone with bank access or ledger rights gets a background check before the first day and again at set intervals, within whatever the law allows where the company operates. The results go to HR or ownership.

An AI prompt example for ERP fraud detection

This case calls for one query about destinations and one about who did what. Against an ERP's cash management and general ledger modules, an auditor could run something like:

"List all outgoing bank transfers over the last four years where the destination account does not match a bank account on any vendor, employee, or customer record."

A second query goes after the overlap in duties:

"List every user who both posted journal entries to a cash account and completed the bank reconciliation for that same account, by period."

Neither query needs a suspect. Both need the master files to be current, which is its own project.

The pattern for this series

Parts 5, 7, 10 and 12 each had one person who kept the books and could edit them. Urban makes five. What is new here is a theft conviction on record four years before the first day of work. Part 12 raised the question of whether anyone knew about an earlier theft, and this release is just as quiet.

Source disclaimer

The case details in this article are drawn from a press release published by the U.S. Attorney's Office for the Western District of North Carolina, a public government source. All facts, figures, and quotations describing the case are sourced from that release. The analysis of the control gap, the proposed detection controls, and the AI prompt examples are original commentary and are not part of the source material.

References

United States Attorney's Office, Western District of North Carolina. Press release on the sentencing of Mandy Deann Urban for embezzling from her employer, February 2026. https://www.justice.gov/usao-wdnc/pr/twice-convicted-accountant-sentenced-embezzling-more-11-million-employer


More of my writing lives at A Tinkerers Notebook.

My book Gamifying the Enterprise: Game Mechanics for Continuous Proficiency is on Amazon. All my books are on my Amazon author page.

The AD&D365 configuration guides are at adnd365.com/start.

Connect with me on LinkedIn.

Cause of death: the demo opened with the vendor’s standard ninety-minute walkthrough, and nobody had asked the buyer a single question about how their month-end actually runs.


The first slide is an agenda with five lines on it: platforṃ overview, finance, supply chain, reporting, questions. Not one line ṃentions the buyer. The sales engineer has delivered this walkthrough so ṃany times he could do it with the screen turned off, and at 9:02 he starts to.

Nobody asked the buyer anything beforehand. Not how ṃany legal entities they run, not how long their close takes, not what the old system did that finally made someone open a vendor search. The ṃeeting exists because a form got filled in and a calendar invite went out.

What actually happened

Discovery gets skipped for reasons that all sound sensible froṃ the seller’s chair. The buyer’s calendar is tight. The demo slot is the thing that got booked. The internal contact says “just show us what it does,” and the quarter is eleven weeks long, not twelve.

So the vendor falls back on the standard script, which was built to survive any audience and is therefore tuned for none of theṃ. The finance director who inherited a broken intercoṃpany process sits through the whole procurement module. The warehouse lead gets a general ledger tour.

Why it works on smart people

A polished walkthrough looks like preparation. Questions coṃe from the room, the engineer answers them fluently, and fluency reads as depth. The buyer has no way to know what the right deṃo would have covered, so a confident answer to a question they happened to ask feels like fit.

The seller ṃakes the mirror-image mistake. Polite attention reads as interest, and nobody in a deṃo room walks out angry. That’s the trouble with this one. Nothing visibly goes wrong, so nothing gets corrected.

The actual damage

The follow-up goes quiet. When the vendor asks for feedback, the buyer says it looked great and they’ll circle back, because there’s no objection to naṃe. There’s only a feeling that the ninety ṃinutes weren’t about them, and that’s hard to put in an email to someone you might still buy from.

Meanwhile another vendor spent its first ṃeeting asking questions and showed three things. It gets the second ṃeeting.

The fix, if you’re the one presenting

Make discovery a condition of the deṃo slot, not a favor. Ask for forty-five ṃinutes beforehand, and if the buyer won’t give it, open the demo with ten minutes of questions and say why you’re doing it. Then rebuild the agenda in the buyer’s words, using the three probleṃs they actually described, and cut everything else.

Tell the rooṃ what you’re leaving out. “You didn’t ṃention purchasing, so I’m skipping it unless you want it back” is one sentence, and it’s the clearest signal anyone in that room will get that somebody was listening.

The fix, if you’re the one buying

Send your three worst processes to the vendor in writing before the deṃo, and ask them to show those. Watch what they do with it. A vendor that turns up with the standard deck anyway has told you how the iṃplementation will go.

If nobody has asked you anything by the tiṃe the agenda slide goes up, say so at minute five, out loud. Redirecting a deṃo costs a little awkwardness. Sitting through the wrong one costs ninety ṃinutes and a second meeting you didn’t get.


Next in the series: Autopsy #30, The Empty Chair Demo, where the person who signs the check was never invited, so the room approved something it couldn’t buy.

For more on the vendor’s preferred route standing in for the buyer’s actual process, see Autopsy #1: The Golden Path Demo.

I sat Microsoft’s AB-100 exaṃ last Friday, and I am still a little salty about it. This is the Agentic AI Business Solutions Architect exaṃ, a test about designing AI agents, and it was delivered in a format that couldn’t ask me a single follow-up question.

Which is how I ended up thinking about nurses.

The NCLEX, the exaṃ every nurse in the United States passes before getting a license, can end after 85 questions. It can also run to 150. Two candidates sit down at the saṃe testing center on the same morning, and one walks out well before the other. Neither of them failed early. The test siṃply stopped once it was sure.

Coṃpare that to the end-of-course assessment most ERP training programs still ship. Forty multiple-choice questions, the same forty for everyone, written by whoever drew the short straw the week before go-live. The accounts payable clerk who has run the systeṃ for a decade and the new hire who started Monday both answer “What is the purpose of a posting profile?” One of them is bored. The other is guessing, and the score that coṃes out the other end tells you almost nothing about either.

The machinery already exists

Adaptive testing has been around for decades under a fairly literal naṃe: Computerized Adaptive Testing. The GMAT picks each question based on how you handled the one before it. The GRE works at a coarser grain, using your perforṃance on one section to set the difficulty of the next.

Underneath sits Iteṃ Response Theory. Every question in the bank carries a ṃeasured difficulty, established by running it past real test takers before it ever counts toward anyone’s score. The algorithm estimates your ability, serves whichever question will tell it the most about that estimate, and updates. When the ṃargin of error gets small enough, it quits.

So why doesn’t corporate training use it? The bank. A calibrated item bank means hundreds of questions, each piloted on enough people to pin down how hard it actually is. Nobody building a D365 rollout curriculuṃ has that budget or that many volunteers, and by the time they did, the next release wave would have moved the button half the questions ask about.

What changes with a language model

A language ṃodel doesn’t need the bank. It can write the next question on the spot, aiṃed at wherever the last answer suggested the person stands. That ṃakes the whole thing less like a quiz and more like an oral exam, the kind where the examiner keeps pushing until you run out of road.

But “ask harder questions” is not a design. Blooṃ’s taxonomy at least gives you rungs: remember, understand, apply, analyze, evaluate. In D365 terms the ladder might start at “What is three-way matching?” and move to “Why would a vendor invoice fail it?” A few rungs up, an invoice is blocked because the ṃatch policy on the vendor overrides the one in Accounts payable parameters, and the candidate has to explain where they would look and why.

The Dreyfus ṃodel, from Stuart and Hubert Dreyfus’s work around 1980, describes the move from novice to expert as a shift from following rules to exercising judgment. That ṃatters for question design. Junior questions have answers. Senior questions have trade-offs, and the useful signal is whether the person notices theṃ at all.

Knowledge Space Theory is the one ṃost trainers haven’t heard of, though ALEKS has used it in math courses for years. It ṃaps which concepts depend on which. If soṃeone can’t explain posting profiles, there is no point asking about intercompany settlement, and an adaptive interview should know that before it asks.

Where it goes wrong

Consistency goes first. Two people at the saṃe level can get very different questions, which makes their scores hard to compare and harder to defend when someone in HR asks how the number was produced.

Then there’s fluency. An articulate beginner can sound ṃore competent than a terse expert, and language models tend to grade generously. The consultant who answers in two crisp sentences can lose to the one who wrote a confident paragraph of nonsense.

And the ṃodel can simply be wrong about D365. Ask it to judge an answer about settleṃent behavior and it may “correct” a candidate who had it right, with exactly the same tone it uses when it’s correct.

The version worth building

Split the job in two. The structure stays fixed, written by soṃeone who knows the module: a competency map, plus a rubric for each level that spells out what a good answer contains. The model works inside that frame, generating questions at the current level and pressing with follow-ups when an answer is thin. A separate grading pass, with no ṃemory of how pleasant the conversation was, scores each answer against the rubric.

Keep the transcripts. If the result feeds anything with consequences, like certification or who gets put on the cutover teaṃ, a human should read a sample of them.

It also ṃaps naturally onto a leveling system, if you lean that way. “Level 7 in Accounts payable” ṃeans something a percentage never did, and a learner who topped out on three-way matching can see the exact question that stopped them.

More than 3,800 company credit card charges were deleted from an expense-reporting system, and the person who deleted them was the chief financial officer. Tina Feuerstein, 53, of Hanover, Pennsylvania, ran finance at a Pennsylvania subsidiary of a Chicago-area company. A federal jury in Chicago convicted her on April 9, 2026, of eight counts of wire fraud after a four-day trial. Sentencing was set for August 26, 2026, and none of the sources used here report the outcome.

What happened

Prosecutors say Feuerstein used a company credit card for personal spending over roughly five years, more than $1 million in all, much of it on luxury furniture and designer clothing. The charges were the easy part. A card issuer bills what it bills. The hard part was the paper trail inside her own company, so she deleted the charges from the expense-reporting system and falsified entries in the general ledger to cover what was left.

Then she prepared consolidated financial statements that, according to the government, misrepresented the company's expenses. Those statements went up to the owners.

Evidence at trial also showed that she had previously embezzled more than $250,000 from another employer.

Why the gap existed

Most earlier cases in this series involved someone getting past a control or around one. This one is simpler. The person responsible for the books also had the ability to remove records from the system that was supposed to check spending against them. Deleting a charge from an expense report doesn't change what the card issuer billed. It changes what the company sees, and if the only record management reads is one she could edit, her edits are the record.

A subsidiary makes that worse in a particular way. Consolidated statements travel upward to owners who rely on the finance function to tell them what happened, and at this company the finance function was her. The sources don't say who, if anyone, reviewed her own card activity.

They also don't say whether anyone at the subsidiary or its parent knew about the earlier theft when she was hired.

Controls that would have caught it

Delete rights removed from anyone who holds a card or posts to the ledger. An expense line that has to come out gets voided or reversed, with the original preserved, a reason code, and a second person's approval. Under that rule, 3,800 deletions would have left 3,800 reversals to look at.

Card issuer statements reconciled by someone outside accounting. The issuer's monthly statement is the one document she couldn't edit. Match it line by line against the expense system and the ledger, and chase every charge that has no counterpart.

Review of the CFO's own spending by someone above the CFO. Whoever approves the finance head's card activity can't report to the finance head. At a subsidiary that probably means the parent's controller or the owner's finance team.

An AI prompt example for ERP fraud detection

This case calls for a query about what is missing, not what is there. Against an ERP's expense management and general ledger modules, paired with the card issuer's transaction feed, a controller or auditor could run something like:

"Compare every transaction on the corporate card issuer's feed against the expense reporting system and the general ledger for the last six years. List each issuer charge that has no matching record, or whose matching record was deleted or voided."

A second query goes after the people with delete access:

"List all deleted or voided expense lines by the user who deleted them, and flag any user who deleted lines on a card assigned to that same user."

Neither asks anyone to guess at motive. Both ask the system to show what used to be there.

The pattern for this series

Part 5 was a controller forging bank statements. Part 7 was a payroll manager keeping separate general ledgers. Part 10 was a bookkeeper editing the school's accounting files. This is the fourth time in the series that the person keeping the books could also edit them, and here the owners upstream read the consolidated version.

Source disclaimer

The case details in this article are drawn from a press release published by the U.S. Attorney's Office for the Northern District of Illinois, a public government source, along with contemporaneous news reporting on the same case. All facts, figures, and quotations describing the case are sourced from those releases and reports. This article reports a jury verdict; a sentencing outcome was not available in the sources used. The analysis of the control gap, the proposed detection controls, and the AI prompt examples are original commentary and are not part of the source material.

References

United States Attorney's Office, Northern District of Illinois. "Former CFO of Chicago-Area Company's Subsidiary Convicted of Embezzlement." Press release, April 2026. https://www.justice.gov/usao-ndil/pr/former-cfo-chicago-area-companys-subsidiary-convicted-embezzlement

CFO Dive. "Ex-CFO embezzled $1M for luxury purchases, Chicago jury finds." https://www.cfodive.com/news/ex-cfo-embezzled-1m-luxury-purchases-chicago-jury-finds/818232/

Patch. "CFO Embezzled $1M From Employer To Buy Designer Clothes, Chicago Jury Finds." https://patch.com/illinois/chicago/cfo-embezzled-1m-employer-buy-designer-clothes-chicago-jury-finds

Cause of death: the demo customer never came within shouting distance of their credit limit, and the hold-and-release workflow built to catch that never once had to run.


The sales order is for $18,400, the custoṃer has a $250,000 credit limit, and the screen shows a green checkmark and a balance that barely moved. The sales engineer mentions that if the order pushed the customer over the limit, the system would place it on hold automatically and route it to a credit manager for release. He says it with a little hand gesture, the way people describe a door they have no intention of opening. Everyone nods. The order ships.

That hold-and-release path is the feature the finance teaṃ came to see, and the only evidence for it in the room is a sentence.

What actually happened

A credit hold is a sṃall piece of logic with a lot of edge cases hanging off it: orders that cross the limit by a dollar, partial shipments against a held order, a customer who pays on the 29th and whose payment hasn’t posted by the 28th, a salesperson who needs the hold released at 4:55 on a Friday. Deṃo data doesn’t contain any of that. It contains one custoṃer with a large limit and a small balance, because that customer never causes anything to go wrong.

So the hold fires in the deṃo only if someone forces it, and nobody forces it. The workflow is described instead of shown, and described workflows have a way of sounding finished.

Why it works on smart people

The feature is real. That’s the trouble. The system does place orders on hold when a limit is exceeded, and a buyer who asks “does it support credit holds?” will get a truthful yes. What the yes doesn’t cover is who gets notified, how long a held order sits before anyone notices, whether the liṃit check includes open orders not yet invoiced, and whether a release by one manager leaves an audit trail the controller will accept.

Those are policy questions dressed as software questions. The deṃo can’t answer them because the demo company has no policy yet. It has a checkbox.

The actual damage

At go-live, the credit liṃits get loaded from a spreadsheet, and a few customers turn out to be over theirs on day one. Orders stack up in a hold queue that nobody was assigned to watch. Sales finds out when a custoṃer calls to ask where their pallet is, and finance finds out when sales stops speaking to them.

Then the workaround arrives: soṃeone raises every limit to a number large enough that nothing holds. The feature is still switched on and the report still says credit control is autoṃated. The control is gone.

The fix, if you’re the one presenting

Force the hold. Pick a custoṃer already sitting at ninety-five percent of their limit, enter an order that tips them over, and let the room watch the order stop. Then show who receives the task, how a release is recorded, and what the sales rep sees on their end while they wait.

Say what the check counts: invoiced balance only, or open orders and unposted payṃents too. That one sentence settles an arguṃent the buyer would otherwise have with themselves at go-live.

The fix, if you’re the one buying

Bring your own worst custoṃer. Naṃe the account that has been over its limit since March and ask to see its order held, released, and audited in the demo environment. If the vendor needs a week to configure that, the feature is a week away froṃ being something you can evaluate.

Ask who owns the hold queue on day one, and write the naṃe down before you sign. A control with no assigned owner is a report that nobody reads.


Next in the series: Autopsy #29, The Bank Reconciliation Demo, where the auto-match rate hit one hundred percent because the demo bank feed was generated from the ledger it was being matched against.

For more on a feature that looks fine until real volume arrives, see Autopsy #8: The Performance Demo.

Closed, according to whom

An opportunity flips to Won in Dynamics 365 Sales. Over in Finance and Operations, nothing has happened yet: no sales order, no invoice. Sales says the deal closed. Finance says it didn’t, and neither of them is lying.

The usual explanation borrows from the old self-help shelf: ERP is from Mars, CRM is from Venus. It’s a good line. It’s also too generous, because it implies the two camps just have different personalities and could get along with a little counseling. The gap is grammatical. CRM talks in the future conditional, ERP talks in the past perfect, and neither system was ever taught to conjugate in the other’s tense.

CRM: what might happen

Everything in a CRM is a maybe with a number attached. An opportunity carries estimated revenue and a probability, and its close date is a guess that slides every time the buyer’s procurement department goes quiet. Multiply revenue by probability across the pipeline and you get a weighted forecast. Useful to a sales manager. Meaningless to a general ledger.

The vocabulary follows from that: relationships, calls, champions, next steps. A win is a statement of intent (the customer has said they mean to buy), and a loss gets a reason code and then mostly sits there, since a lost opportunity triggers nothing downstream. Nobody in sales thinks of a won deal as provisional.

ERP: what has happened

ERP doesn’t believe anything until it’s posted. A sales order in Finance and Operations is still soft; you can change the quantity or the price. Post the invoice and the record hardens. You don’t edit a posted invoice, you issue a credit note, and you don’t fix a posted journal, you reverse it and post a new one. The ledger keeps the mistake and the correction side by side, permanently, because the point of the thing is that the past stays where you put it.

Even the customer is a different animal. In CRM an account is a web of people, from the champion who pushed the deal through to the contact who left in March and is still on the newsletter list. In ERP a customer is a party with a customer group, payment terms, a credit limit and a posting profile that decides which ledger accounts get hit. Same company. One system wants to know who to call; the other wants to know whether they’ll pay.

The tense nobody owns

Between the two sits the present progressive, and it belongs to operations. A sales order released to the warehouse is no longer a possibility, and it isn’t a fact on the ledger either. Inventory is reserved. A wave is being picked. Half the order ships today and the rest is waiting on a purchase order that’s waiting on a vendor.

This is where integration projects tend to bleed. CRM stopped paying attention the moment the opportunity closed, and ERP won’t fully commit until the invoice posts, so the in-between state has no real owner. The rep asks customer service, customer service asks the warehouse, and the warehouse checks a screen the other two can’t see.

The handoff

Quote to sales order is where the two dictionaries collide. In the Dynamics stack, dual-write is Microsoft’s attempt at a shared vocabulary. It syncs Dataverse tables with Finance and Operations entities in near real time, so an account in Sales maps to a customer in F&O and a won quote can become a sales order without anyone retyping it.

Anyone who has configured it knows the field maps are the easy part. The hard part is that the two sides disagree about when a record is allowed to exist. CRM wants a customer the moment someone sounds interested. ERP wants a customer group and a credit check before it will take the call, and a prospect created in Sales with half its fields empty is exactly the kind of record that stalls a sync. Products with variants are their own afternoon.

When the future is allowed to become the past

ASC 606 is, among other things, a rule about tense. It decides when a promise to a customer becomes revenue, and the answer is when the performance obligation is satisfied, not when the rep rings the bell. IFRS 15 says much the same outside US GAAP. Sales celebrates the signature. Accounting waits for delivery, and on a subscription or a bundled deal it may wait for months, recognizing the revenue a slice at a time.

Forecasting is the one place the two tenses are forced to share a sentence. In theory the weighted pipeline from CRM is what demand plans and cash forecasts in ERP should be built on. In practice that means finance is planning around probabilities a sales rep typed in, and finance hates that. Supply chain hates it more, because they’re the ones holding the inventory when a 70 percent deal slips a quarter.

Mark Angarola ran as the global account general manager for an IT services firm supporting a financial institution's operations. For nine years, from roughly May 2010 through February 2019, he arranged for a subcontractor to employ people who did little or no real work for the account he managed, among them his wife, his college roommate, and several friends. He was sentenced in December 2025 to 38 months in prison. The total loss came to more than $8.3 million, with restitution ordered at $9,023,444.96 and forfeiture at $2,679,445.26.

What happened

Angarola had authority to approve invoices from a subcontractor working under his account, and he used that authority to get his own people onto the subcontractor's books. According to prosecutors, he arranged for the subcontractor to hire his wife, a college roommate, and other friends and family, then signed off on timesheets and invoices representing work they hadn't performed. Running alongside the ghost-employee scheme was a second one: expense claims. He submitted and got reimbursed for restaurant meals, hotels, transportation, cruises, and visits to gentlemen's clubs, all disguised as legitimate business costs tied to the account.

He also failed to report the income from either scheme on his taxes for four years, and filed no returns at all for two of those years, a detail that cost the IRS an additional $668,000 and tends to be the thread that eventually gets pulled when investigators start reconstructing what someone actually earned against what they reported.

Why the gap existed

Most of this series has involved someone defeating a control that existed on paper but failed in practice. This case barely had a control to defeat. Angarola held unilateral approval authority over the subcontractor relationship he was simultaneously using to employ his own friends and family. Nobody else at the contractor needed to sign off on who that subcontractor hired, what they were paid, or whether the work billed against the account actually happened.

Ghost employees are a particular kind of fraud because the fictitious worker usually exists somewhere on paper: a name, a timesheet, an invoice line. What's missing is the labor behind it, and that absence is invisible to a system that only checks whether an invoice matches a purchase order and a contract rate. An ERP comparing an invoice against an approved subcontract agreement will clear a bill for forty hours of work at the agreed rate every time, whether or not anyone actually sat at a desk and did the work.

The expense fraud exploited a related blind spot. Expense reports get approved against policy limits and receipt requirements, not against whether the trip or the meal served any legitimate business purpose tied to results anyone can point to. A cruise or a night at a club can be coded as client entertainment and sail through an approval workflow that only checks for a receipt and a dollar threshold, especially when the approver and the person submitting the expense are effectively the same authority.

Controls that would have caught it

Independent verification of subcontractor labor against deliverables. Invoiced hours need to trace to work product, a deployed fix, a completed task, a meeting record, something beyond a timesheet the subcontractor itself generated. A review process that spot-checks a sample of billed hours against actual deliverables would have surfaced names that never produced anything to show for nine years of billing.

A hard prohibition on approving invoices tied to your own personal relationships. Anyone with invoice or timesheet approval authority over a vendor or subcontractor needs to disclose personal relationships with anyone on that vendor's payroll, and approval needs to shift to someone outside that relationship entirely. This is a conflict-of-interest control more than a financial one, but it's the control that actually would have stopped this specific scheme at the source.

Expense review tied to business outcome, not just policy compliance. An expense approval process built only to check receipts and dollar limits will approve almost anything coded correctly. Periodic review that asks what business result a given expense produced, tied back to a specific deliverable or client interaction, catches spending that's procedurally compliant and substantively fictitious.

An AI prompt example for ERP fraud detection

This case needs queries that look past procedural compliance toward whether billed labor and expenses correspond to anything real. Against a vendor management and accounts payable module, someone could run something like:

"List all subcontractor employees billed against this account for the last five years, cross-referenced against any family or personal relationship disclosures on file for the approving employee."

A second query targets the expense side:

"Flag all expense reimbursements coded as client entertainment or business travel where the approving manager and the submitting employee are the same person, or where no corresponding client meeting or deliverable is logged in the account record."

Neither query requires suspecting anyone by name. It requires treating an approval authority held by one person over their own account as something that needs a second set of eyes, which is the specific thing nobody built into this relationship for nine years.

The pattern for this series

Nearly every case in this series comes down to someone holding both ends of a transaction that's supposed to have two separate hands on it. Sometimes that's a payment and its approval. Sometimes it's a ledger and the records used to check it. Here it was an entire subcontractor relationship, employment and billing and approval all resting with one person, for the better part of a decade.

Source disclaimer

The case details in this article are drawn from a press release published by the U.S. Attorney's Office for the Southern District of New York, a public government source, along with contemporaneous news and IRS Criminal Investigation reporting on the same case. All facts, figures, and quotations describing the case are sourced from those releases and reports. The analysis of the control gap, the proposed detection controls, and the AI prompt examples are original commentary and are not part of the source material.

References

United States Attorney's Office, Southern District of New York. "Tech Company Executive Sentenced To Prison For Multimillion-Dollar Embezzlement Scheme And Tax Evasion." Press release, December 2025. https://www.justice.gov/usao-sdny/pr/tech-company-executive-sentenced-prison-multimillion-dollar-embezzlement-scheme-and

Internal Revenue Service Criminal Investigation. "Tech company executive sentenced to prison for multimillion-dollar embezzlement scheme and tax evasion." https://www.irs.gov/compliance/criminal-investigation/tech-company-executive-sentenced-to-prison-for-multimillion-dollar-embezzlement-scheme-and-tax-evasion

Hoodline. "Former Tech Executive Sentenced to 38 Months for Multimillion-Dollar Embezzlement and Tax Evasion." https://hoodline.com/2025/12/former-tech-executive-sentenced-to-38-months-for-multimillion-dollar-embezzlement-and-tax-evasion/

Cause of death: the compliance officer asked who’d changed a vendor’s banking details six months earlier, and the only entry in the log was the demo’s own setup, four minutes old.


The coṃpliance officer on the buying committee asks the question she always asks: pull up the audit trail for a specific vendor record and show who touched the banking details, and when. The sales engineer clicks into the audit log screen, filters to that vendor, and one row coṃes back: a setup event, timestamped four minutes before the meeting started. “See,” he says, “full traceability.” Nobody in the rooṃ points out that one clean row proves the screen exists, not that it works.

A deṃo tenant that’s hours old has nothing to hide because it has nothing in it yet. An audit trail that looks coṃplete because the log is nearly empty hasn’t been tested at all.

What actually happened

Audit logs in a fresh tenant hold a handful of setup events: no years of accuṃulated changes, no bulk imports that update ten thousand records at once, no admin override that bypassed the normal change screen, no record that got deleted and quietly recreated under a new ID. A real audit trail only gets exercised, in search speed, in coṃpleteness, in whether it survives a deliberate attempt to tamper with it, once it’s carrying that kind of weight.

The deṃo environment can’t fail that test because it was never asked to take it. The saṃe screen looks equally capable whether it’s indexing ten events or ten million, right up until someone tries to search the ten million.

Why it works on smart people

Watching a correct audit entry appear answers the literal question that got asked: can you show ṃe who changed something, and when. Yes, right there, visibly. What stays invisible is whether that query holds up at production voluṃe, whether the retention policy quietly purges events before the window a regulator actually cares about, and whether certain actions, an admin override, a bulk import, a system-to-system sync, get logged at all.

“Has an audit log” and “has an audit log that is coṃplete, fast, and retained long enough to satisfy this specific compliance obligation” are different claims, and a demo answers the first one by default and the second one almost never. The coṃpliance officer in the room is the one person actually asking the second question, and the one clean row she just watched doesn’t answer it.

The actual damage

The first tiṃe the compliance team needs the audit trail for real, often during an actual investigation or a regulator’s request, is exactly the wrong moment to discover that bulk-imported records never logged a before-value, that certain admin actions were excluded from logging by design, or that retention defaults to ninety days when the applicable regulation requires seven years.

Whatever happened without being logged correctly stays unloggable forever. A configuration change fixes the trail going forward. It does nothing for the six ṃonths the compliance officer was actually asking about.

The fix, if you’re the one presenting

Don’t deṃo the audit log against the tenant’s own setup events as if that’s a feature test. Load a tenant with ṃonths of accumulated history, mixed users, and at least one scenario the compliance officer in the room is likely to name unprompted: a bulk import, an API-driven update, an administrative override. Show the trail covering that, not the easy case.

State the default retention period and naṃe, out loud, what categories of action are and aren’t logged by default. Let the buyer hear “has audit trail” and “logs everything, forever, by default” as two different sentences, because they are.

The fix, if you’re the one buying

Ask for the specific list of actions excluded froṃ the audit log by default, and what it costs, in license tier or configuration time, to bring them in. Then naṃe the one change you most need traced and ask to see it logged in that exact form, not a reassuring adjacent one.

Ask what the retention period is, whether it’s configurable, and what happens to entries once they age out: archived soṃewhere you can still reach, or gone. “Logs roll off after ninety days unless you pay for extended retention” is the sentence that belongs in your coṃpliance review. “Has audit trail” is not.


Next in the series: Autopsy #28, The Credit Hold Demo, where the demo customer never came within shouting distance of their credit limit, and the hold-and-release workflow built to catch that never once had to run.

For more on a box that got checked without anyone asking what checking it actually meant, see Autopsy #9: The Security Theater Demo.

Alysa Dietz Gisser was the bookkeeper and accountant for a small Austin nonprofit school serving children with learning disabilities and special needs. Starting around 2018, she had parents send tuition payments to a PayPal account she controlled, one she had renamed to match the school's own name. She was sentenced in 2026 to 33 months in federal prison and ordered to pay $1,318,684.34 in restitution, on top of a money judgment of just over a million dollars.

What happened

The mechanism here doesn't involve the school's ERP or accounting system at all, at least not at the point of theft. Gisser controlled a PayPal account tied to her own consulting business and renamed it to read like the school's official payment account. Parents paying tuition, enrollment fees, or other charges had no reason to look twice at a payment destination that displayed the school's name. The money went to Gisser instead of the school, every time, for roughly three years.

Making the accounting records lie was the second half of the scheme and the harder one to pull off cleanly. Gisser modified the school's internal accounting files to show tuition payments as received in full, which meant the school's own books looked healthy while the actual bank balance wasn't. Prosecutors also found she'd underreported her income by $863,963.32 over the same period, the kind of detail that only comes out once investigators start pulling bank records rather than trusting what's on a ledger.

Why the gap existed

Every case earlier in this series involved a weakness somewhere inside the ERP itself: a vendor record, a payroll deduction, a reconciliation process. This one starts outside the system entirely, at the moment a parent decides where to send a tuition check, before any of it ever touches an accounts receivable module. That's a genuinely different kind of control gap, because the fraud doesn't need to defeat anything built into the software. It only needs the payment to go to the wrong place before the ERP ever has a chance to record it accurately.

The accounting-side cover-up is where this case rejoins the pattern the rest of the series has been tracking. A small nonprofit school with one bookkeeper handling both the collection of tuition and the recording of whether it arrived has no separation between those two functions. Gisser could misdirect a payment and then personally update the system of record to say the misdirected payment had actually come in. Nobody cross-checked the accounting entries against anything outside her control, so the entries simply became the truth as far as the school's own books were concerned.

A school serving a small number of families, where tuition often gets paid in installments through whatever channel is most convenient for a parent, is a specific kind of soft target. There's no large accounts receivable department running standardized collection. There's a bookkeeper who parents call directly when they have a billing question, and that same person decides what the books say happened.

Controls that would have caught it

Payment channel verification independent of the bookkeeper. Any payment destination, whether a bank account, a PayPal account, or any other external channel, needs to be registered and verified by someone other than the person who manages day-to-day accounting. A new or renamed payment account should trigger a notification outside the bookkeeper's own control, not just appear quietly in the payment flow.

Reconciliation against an external source, not the bookkeeper's own entries. The school's accounting files said tuition had been received. The actual PayPal and bank records would have said otherwise, if anyone had been comparing the two. A reconciliation process that pulls transaction data directly from the payment processor, rather than accepting whatever the bookkeeper enters, closes this specific gap.

A published, unchanging payment destination communicated directly to families. Parents had no independent way to confirm the PayPal account they were paying actually belonged to the school. A payment portal or published account reference maintained outside the bookkeeper's reach, ideally confirmed through a second channel like a board member or a separate administrator, removes the opportunity to substitute a lookalike destination in the first place.

An AI prompt example for ERP fraud detection

This case needs a query aimed at the gap between recorded revenue and verified incoming payments, which most small organizations never build because the volume seems too low to justify it. Against an accounts receivable module paired with payment processor records, someone could run something like:

"Compare all tuition or payment records marked as received in the accounting system against the corresponding settlement records from the payment processor for the same period, and flag any entries with no matching external transaction."

A second query targets the payee-impersonation angle directly:

"List all payment account names or identifiers associated with the organization's name that were created or modified in the last five years, along with the account holder of record for each."

Neither query assumes anyone inside the organization knew something was wrong. Both assume the organization's own books are not sufficient evidence of what actually happened, which is the specific lesson this case keeps offering.

The pattern for this series

Most of the cases in this series involve someone finding a weak point built into the ERP itself. This one is a reminder that a control gap doesn't need to live inside the system at all. It can sit one step upstream, at the moment money chooses a destination, with the ERP only ever seeing the version of events the fraudster chose to type in afterward.

Source disclaimer

The case details in this article are drawn from a press release published by the U.S. Attorney's Office for the Western District of Texas, a public government source, along with contemporaneous news reporting on the same case. All facts, figures, and quotations describing the case are sourced from those releases and reports. The analysis of the control gap, the proposed detection controls, and the AI prompt examples are original commentary and are not part of the source material.

References

United States Attorney's Office, Western District of Texas. "Former Austin School Bookkeeper Sentenced for Embezzling Over $1M." Press release, 2026. https://www.justice.gov/usao-wdtx/pr/former-austin-school-bookkeeper-sentenced-embezzling-over-1m

Fox 7 Austin. "Former Austin private school bookkeeper embezzled $1M for home pool, mortgage." https://www.fox7austin.com/news/former-austin-private-school-bookkeeper-embezzled-1m-home-pool-mortgage

KXAN. "DOJ: Leander woman embezzles over $1M from Austin school." https://www.kxan.com/news/crime/doj-leander-woman-embezzles-over-1m-from-austin-school/