Financial Expertise Helped Conceal and Distribute Millions Stolen from Children’s Healthcare of Atlanta

A business owner and former Certified Public Accountant was sentenced in July 2026 to four years in federal prison and ordered to pay $682,860 in restitution for his role in laundering $5.3 million stolen from a nonprofit children’s hospital. Ronald Deabler, 66, of Atlanta, was convicted by a federal jury in February 2026 on charges of conspiring to launder the proceeds of a vendor email compromise scheme.
Reaction to the sentence was swift, and much of it was some version of: “That’s too light.” Part of what fuels that reaction is who the money belonged to. The victim was Children’s Healthcare of Atlanta, Inc. (CHOA), a nonprofit pediatric health system. CHOA patients include children being treated for cancer and other life-threatening illnesses. The news came just as CHOA was amid an active fundraising campaign.
Nonprofit governance expert Doug White noted that embezzlement in a nonprofit setting does more than drain financial resources. It erodes donor trust and makes the organization’s mission harder to fulfill. That’s a real cost, separate from the dollar figure, and it’s worth naming before moving on.
Beware VEC
Of course, whether the victim is a nonprofit, a for-profit company, or a government agency, theft is theft. The bereft character of the CPA and rationalizations offenders use to justify fraud — pressure, opportunity and the ability to talk themselves into it — are a subject for other forums. What CHOA experienced is worth examining closely here not because of who did it or why, but because the mechanism is one that targets accounts payable departments at organizations of every kind, every day. Understanding exactly how it worked and what stopped further losses once it was discovered are the focus here.
The mechanism itself has a name: vendor email compromise, or VEC. VEC is a variant of business email compromise in which the attacker doesn’t spoof the target’s own executives, but instead quietly takes over a real vendor’s inbox and commences communication as the vendor. That is what makes VEC schemes so effective, and it’s exactly what happened to CHOA.
How It Happened
A furniture vendor’s email account, hacked
In early June 2023, according to the U.S. Attorney’s Office for the Northern District of Georgia, a hacker gained access to the email system of a commercial furniture vendor that did business with CHOA. Posing as an employee of that vendor, the hacker contacted CHOA and requested a change to the bank account on file for the vendor’s ACH payments. CHOA updated its records. The new account belonged not to the vendor, but to Ronald Deabler.
A single payment, misdirected
On or about June 13, 2023, the hacker directed CHOA to wire $5.3 million into Deabler’s account — a legitimate payment obligation, redirected in full to an account the real vendor did not control. Deabler, a business owner and former CPA, had agreed to move the stolen money in exchange for a commission, using his financial background to make the funds harder to trace.
Laundering the proceeds
Shortly after the deposit landed, Deabler opened a second bank account and attempted to shift the entire $5.3 million into it. His bank blocked the transfer before it could go through in full, though he still managed to move more than $1 million to the new account. He then converted roughly $3.5 million into four cashier’s checks and mailed them to individuals and entities as instructed by the hacker — a classic layering step, designed to break the money into pieces and put distance between the theft and its final destination.
Detection and recovery
CHOA and its vendor caught the fraud within days of the wire going out. CHOA notified its bank, which traced the money to Deabler’s account, and investigators traced it further from there. In the end, roughly $4 million of the $5.3 million was recovered from Deabler’s accounts and from the accounts that had received his cashier’s checks. That recovery rate is unusually good for a business email compromise loss of this size. It happened because CHOA and its bank moved fast, not because the fraud was caught before the money left the building. And CHOA still lost $1.3 million.
How to Prevent It from Happening to You
Every element of this scheme is common. A hacker compromises a vendor’s email, poses as a real employee, and requests a change to banking details already on file. The request looks routine because, on its face, it is routine. Vendors update their banking information for legitimate reasons all the time. That’s exactly why bank account change requests deserve more scrutiny than almost any other transaction in accounts payable.
Treat every bank account change request as a control point
No change to a vendor’s banking details should take effect on the strength of an email alone, regardless of how convincing it looks or how much correct detail it contains. A hacker with access to a real vendor’s inbox can reference real invoice numbers, real contacts, and real formatting.
Verify through a channel the requester doesn’t control
Confirm any change by calling a phone number pulled from your own vendor master file or a prior signed contract — never a number supplied in the email making the request. If the hacker controls the vendor’s email, a phone number in that same email may lead back to the hacker, not the vendor.
Treat callbacks as a floor, not a ceiling. Fraudsters increasingly anticipate them, spoofing caller ID or standing up fake customer service lines to match. Automated bank account ownership validation closes that gap by confirming account ownership, account number accuracy, and routing details independently of anything the requester provided — catching what a rushed or well-spoofed callback might not.
Separate who requests a change from who approves it
Bank account changes should require sign-off from someone outside accounts payable, ideally a manager or a second finance employee with authority to reject the change and no involvement in day-to-day vendor communication. A lone AP clerk acting on an urgent-sounding email is exactly the failure point this scheme relies on.
Add a waiting period for large or first-use payments
Consider a mandatory hold, even a short one, between when a vendor’s banking details change and when the first payment goes out to the new account. This is particularly important for high-dollar vendors. That window gives a second reviewer time to catch what a rushed approval would miss.
Use independent verification tools, not just process
Add a layer that doesn’t depend on a single employee’s judgment in the moment:
- Bank account validation services that confirm ownership of an account before funds move,
- positive pay arrangements with your bank, and
- ACH monitoring for unusual first-time payments to new accounts.
This isn’t just good practice — it’s increasingly a compliance requirement. Nacha’s WEB Debit Account Validation Rule obligates ACH originators to validate an account before its first use and before any change to the account number. That is precisely the step that was missing here. We’ve written before about how that requirement plays out in real-world bank account compromise cases and what it takes to stay on the right side of it.
Move fast if something looks wrong
CHOA recovered roughly three-quarters of what was stolen because it and its vendor caught the fraud within days and notified the bank immediately. Speed after detection doesn’t prevent a loss, but it can significantly reduce one. An incident response plan for suspected payment fraud, with your bank’s fraud department contact already on hand, is worth having before you need it.
Conclusion
Theft is theft, whether the victim is a nonprofit, a for-profit company, or a government agency. It is a betrayal of trust and taking advantage of honest and legitimate organizations. The failure of character of the perpetrators belongs in a different conversation than this one. But there’s no getting around the fact that this particular theft hits hard, because the money taken was meant to help treat children with cancer and other serious illnesses. That’s worth pausing on. It’s not, however, where the practical lesson lives.
The practical lesson is that this scheme succeeded through a single, ordinary-looking request to change a vendor’s bank account information. And it very nearly succeeded completely. The organizations that avoid this outcome aren’t the ones lucky enough never to be targeted — vendor email compromise attempts are common enough that most AP departments will see one eventually. They’re the ones with disbursement controls strong enough that a convincing email, on its own, is never enough to move money.
To learn how VendorInfo’s vendor bank account verification can help prevent this from happening to you, contact us.


