THE NEWS IN BRIEF
On July 8, 2026, Hakan Kardes, Alignment Healthcare’s former chief data and transformation officer, filed a lawsuit in California federal court alleging the Medicare Advantage insurer manipulated its accounting to manufacture profitability, according to Healthcare Dive. Kardes alleges that after his January 2025 promotion, he discovered engineers were being directed to classify routine work — software maintenance and bug fixes — as capital expenditures instead of operating expenses, improperly moving roughly $8–10 million off the income statement in 2024 and another $10 million in 2025. According to his complaint, reported on by Fierce Healthcare, that misclassification would have entirely erased Alignment’s first-ever profitable year: the company reported just $1.3 million in adjusted EBITDA for 2024, an amount smaller than the low end of the alleged capex misclassification for that year alone. Kardes says he raised the issue directly with CEO John Kao on March 18, 2025, and that within roughly two weeks Kao reversed promotions he had promised Kardes and began a process that led to his removal. The lawsuit names Kao, CIO Robert Scavo, COO Dawn Maroney, and CHRO Andreas Wagner as defendants, alleging they knowingly concealed the irregularities in violation of securities law. Alignment has called the allegations meritless, says Kardes is attempting to recoup forfeited equity, and points to an outside audit commissioned by its board that it says “upheld the integrity” of its accounting records. No regulator has brought charges; these are civil allegations that Alignment disputes, and Kardes’s claims have not been tested in court.
THE CONSULTANT’S VERDICT
Capex-versus-opex misclassification is one of the oldest tricks in the financial-statement-fraud playbook precisely because it doesn’t look like theft. Nobody wires money to a shell company. Nobody forges an invoice. A cost that should hit the income statement this quarter instead gets parked on the balance sheet and depreciated over years, and the only thing that moved was a dropdown menu in an expense-coding system. As alleged here, that is exactly the mechanism: engineers coding “bug fixes” and “maintenance” — textbook operating expenses under both US GAAP (ASC 350-40) and IFRS (IAS 38) — as capital additions instead. If true, the effect on adjusted EBITDA is not a rounding error. It is, on Kardes’s numbers, larger than the entire profit Alignment reported for the year in question.
Run the fraud triangle on what is alleged. The pressure is obvious and public: a company chasing its first profitable year, with adjusted EBITDA a headline metric watched by analysts, tied to stock price, and — per the complaint — tied to executive bonus targets. The opportunity sits in a control gap that shows up in fast-growing tech-enabled companies constantly: engineers, not accountants, making the first-pass judgment call on whether a piece of work is “new functionality” (capitalizable) or “keeping the lights on” (expense). Without a finance function independently testing that classification against a written capitalization policy, the people with the least incentive to get it wrong are being asked to police it, while the people with the most incentive to see it capitalized never touch the coding decision. And the rationalization writes itself: engineering leadership under pressure to hit growth-and-margin targets can talk itself into believing a bug fix is “really” a product enhancement, one judgment call at a time, until the aggregate number is enormous.
The retaliation allegation is the part that should worry an audit committee more than the accounting itself. Kardes says he reported the issue to the CEO — one of the very executives now named as a defendant — and that within two weeks his promised promotions were reversed and his exit began. If that sequence holds up, it is a case study in why the IIA Global Internal Audit Standards insist on organizational independence: internal audit and any whistleblower mechanism must have a reporting line to the board or audit committee that does not run through the executives whose compensation or reputation is on the line. A “speak up” channel that terminates at the CEO’s desk is not a control. It is a courtesy the CEO can revoke.
This is not a uniquely American, healthcare-sector, or public-company problem. I see the same structural gap constantly across the GCC, where fast-scaling technology, fintech, and healthcare platforms in Riyadh and Dubai capitalize development costs aggressively to flatter EBITDA for investors or lenders, often with no documented capitalization policy at all, let alone one enforced by finance independent of engineering. And whistleblower protection in the region is frequently a slide in an onboarding deck, not a functioning, board-anchored channel. The mechanics of this alleged scheme travel easily; the accountability structures that are supposed to catch it travel far less easily.
WHAT YOU SHOULD DO MONDAY MORNING
- Pull your software capitalization policy and read it against ASC 350-40 or IAS 38, whichever applies. Confirm it draws a clear, testable line between capitalizable new functionality and expensed maintenance — and confirm the line is written down, not tribal knowledge.
- Check who actually makes the capitalize-or-expense call. If the answer is “the engineers doing the work” with no independent finance review before the entry posts, you have this exact control gap regardless of what your policy document says.
- Sample this quarter’s capitalized development costs and trace each one to a specific, documented new-functionality justification. If the support is a Jira ticket labeled “enhancement” with no further detail, that is not evidence — that is exactly what this lawsuit alleges was happening.
- Map where your whistleblower channel actually terminates. If a report about senior executives’ financial reporting can only reach those same executives, or reaches them before it reaches the audit committee, fix the routing this week — not after your own version of this lawsuit.
- Cross-reference EBITDA-linked bonus and equity plans against restatement clawback triggers. If a metric drives executive pay, internal audit should be independently substantiating that metric on a cycle the compensation committee can rely on — not trusting the same function that benefits from it hitting target.
DON’T WAIT FOR THE HEADLINE TO BE ABOUT YOU
Right now, somewhere, an engineering team is coding routine maintenance as capital spend because nobody told them the difference matters, and a whistleblower channel exists on paper but dead-ends at the desk of the person it’s supposed to catch. Leadership assumes an outside audit or a policy document is the control doing the work. It isn’t, until someone independent actually tests it. This exact scheme is running inside companies whose leaders would tell you, with total confidence, it couldn’t happen to them. If you want an honest, confidential look at whether your capitalization policy, whistleblower routing, or EBITDA-linked incentives would actually catch this before a lawsuit does, message me directly on WhatsApp for an independent internal audit or fraud-risk health check — before a fraudster, or an aggressive accountant, finds the gap first.