Netanel Group: Is The Internal-Control Weakness A Closed Incident Or A Deeper Signal
The cash came back and the balances were closed, but that does not make the story fully closed. At Netanel Group, the failure around the controlling-shareholder events turned into a material control weakness, received a negative conclusion from the auditor as well, and stays open until the company proves that its related-party identification and approval process actually works.
Where The Main Article Stopped, And What This Follow-Up Is Isolating
The main article argued that Netanel entered 2026 with projects finally moving, but with balance-sheet room still tight. This follow-up isolates a different question: is the internal-control weakness around the controlling-shareholder events already cleaned up, or does it point to a governance layer that is still reacting after the fact.
Economically, part of the story is indeed closed. The controlling shareholder ultimately bore the full cost of Event 24 and Event 25, the company reported that no debit balances remained as of the reporting date, and in Event 25 the reimbursement also included annual interest at 5.02%.
But that does not close the analytical story. The same episode is also the basis for the conclusion that internal control over financial reporting and disclosure was not effective as of December 31, 2025. That is not only a management conclusion. The auditor also wrote that, because of the identified material weakness, the company did not maintain the audited control components effectively as of December 31, 2025.
What works in the company's favor should be said clearly. The audit committee did not rubber-stamp the issue. It re-examined the Event 25 calculation, cut the company's attributed share from NIS 800 thousand to NIS 620 thousand, and ultimately led to the retroactive approval of Event 25 being removed from the agenda. That shows that once the matter reached the proper forum, there was real scrutiny.
The problem is that the scrutiny started late. So this follow-up is not asking whether the money came back. It is asking whether the identification, reporting, and approval mechanism for related-party transactions actually works in real time, especially in a company where the controlling-shareholder and related-party layer is far from marginal.
What Was Actually Closed
The economic event itself went through a fairly aggressive cleanup. Event 24 ended with the company initially attributing about NIS 477 thousand to itself, approving that amount retroactively, and then receiving the full amount back from the controlling shareholder during the first quarter of 2026. Event 25 started with an attributed company share of about NIS 800 thousand, fell to NIS 620 thousand after the audit committee's review, and was then taken off the retroactive-approval path altogether after the controlling shareholder waived company participation and reimbursed the full amount plus interest.
| Item | Event 24 | Event 25 |
|---|---|---|
| Company share under the calculation discussed | NIS 477 thousand | NIS 800 thousand |
| After the audit committee review | Retroactively approved as a non-extraordinary transaction | Company's share revised to NIS 620 thousand, and retroactive approval removed |
| Final cash outcome | The controlling shareholder paid the company back in full during Q1 2026 | The controlling shareholder reimbursed the full amount plus 5.02% annual interest |
The debit and credit balances were ultimately closed as well, but they also show how long it took to get there.
The positive columns are debit balances owed by the controlling shareholder to the company. The negative columns are credit balances. The chart shows why it is important to distinguish between a clean closing balance at the endpoint and what happened along the way. On June 30, 2025 there was still a debit balance of about NIS 640 thousand. By December 31, 2025, after Event 25, the debit balance had already reached about NIS 1.662 million. Only by the reporting date did the picture move back to a credit balance of about NIS 95 thousand.
That is the key distinction. The cash came back, but it came back only after a retrospective audit-committee and board process, not through a control that stopped the transaction before execution.
Why It Is Hard To Call This A Technical Incident
The central point is that the weakness was not framed around the closing balance alone. It was framed around process. The company's wording is direct: during 2024 and 2025 it failed to identify, in a timely manner, the existence of a transaction with the controlling shareholder, and therefore the transaction was not brought to the audit committee before execution. In both the immediate report and the annual internal-control disclosure, the company ties the failure to deficiencies in the design and operation of the identification, reporting, and approval mechanisms for related-party transactions.
That matters because even Event 24, which ultimately left no debit balance, still needed retroactive approval. In other words, the problem is not only that money went out and later came back. The problem sits earlier, at the point where the company should have recognized in time that it was dealing with a controlling-shareholder transaction.
The filing also does not allow the issue to be treated as fully sealed from an accounting-perimeter perspective. The company states explicitly that it is still examining the full impact on the interim financial statements as of June 30, 2025 and September 30, 2025, and that it will update on any material development. In plain terms, the cash side may be closed, but the reporting envelope is not yet fully described as behind the company.
Even what the company has done so far still sits at the plan stage rather than the proof stage. The board adopted the audit committee's recommendations to strengthen controls, and the committee is expected to formulate a plan and recommendations through external advisers. That is the right direction, but it is still a description of intended remediation, not of a control process that has already been tested successfully across another reporting cycle.
Why This Looks Deeper At Netanel
The reason this is hard to dismiss as administrative noise is that at Netanel the related-party layer is dense even without these events. Note 27 in the annual report shows not only executive compensation, but a broad set of agreements, services, and employment arrangements that all require ongoing mapping and accurate approval discipline.
| Relationship layer | Example from the report | Why it matters |
|---|---|---|
| Urban-renewal services | Agreement with Netanel Boutique, annual cap of up to NIS 5.0 million, and evacuation bonuses of NIS 3.731 million in 2025 | This is a continuing and material related-party arrangement |
| Travel services | The arrangement with Lior Tours is re-approved every year | The company already knows this is a sensitive approval track |
| Asset sale to a relative of controllers | Penthouse sale to Avner Netanel for about NIS 5.8 million | Even one-off transactions require timely classification and approval |
| Employment of relatives | Employment of Micha Netanel and Dekel Yamin was approved in 2024 and 2025 | The relationship layer is not one-off, but part of the operating structure |
That table is not meant to imply that every approved arrangement is problematic. Quite the opposite. It shows that the company operates inside a framework where related-party transactions are not a footnote. There is a formal structure, there is an audit committee, there are board approvals, and there are shareholder approvals where needed. Precisely for that reason, the failure around Events 24 and 25 looks less like the absence of a framework and more like a gap between framework and execution.
That matters in a residential-development company. When the company asks the market, lenders, and partners to look forward to permits, sales, and future surplus, the trust layer around reporting cannot be loose. Once the company itself says that the control over transactions with controllers did not work in real time, and the auditor adopts that conclusion, a trust tax is created. Not a tax that freezes activity, but one that makes every operating improvement harder to read at face value.
What Has To Happen For The Issue To Be Truly Closed
Three things need to happen before this story can move from a deeper governance issue to a closed incident.
First, the company needs to finish examining the impact on the June 30, 2025 and September 30, 2025 interim statements, and clarify whether this is only a disclosure-and-control issue or whether it also requires retrospective statement-level adjustments. As long as that line stays open, it is hard to say the reporting perimeter is fully sealed.
Second, the remediation plan has to become a process that works in practice. Not only external advisers and recommendations, but a clear path that identifies in advance transactions, balances, and benefits involving controllers and related parties, especially in an operating environment where projects, services, travel, and family employment are already woven into the business.
Third, the next reporting cycle has to pass without similar noise. That is the real test. Not whether the money was reimbursed, but whether the next report presents the issue as a weakness that was fixed rather than as a headline that still shadows the company's interpretation layer.
Conclusion
The bottom line is straightforward. Economically, the incident is more closed than open. Governance-wise, it is still more open than closed. The controlling shareholder ultimately bore the full cost, the debit balances were closed, and the company has started a remediation path. But that does not erase the fact that the failure stretched across 2024 and 2025, that the transaction was not identified in time, that the auditor concluded the audited control components were not effective at the end of 2025, and that as of the reporting date the company was still examining the impact on interim statements.
In a company where related-party transactions are a recurring part of the operating map, that cannot be treated as a footnote. It is not necessarily a sign of a deep governance crisis, but it is clearly a sign that the market still needs proof of repair, not only a closed balance.
Disclosure: Deep TASE analyses are general informational, research, and commentary content only. They do not constitute investment advice, investment marketing, a recommendation, or an offer to buy, sell, or hold any security, and are not tailored to any reader's personal circumstances.
The author, site owner, or related parties may hold, buy, sell, or otherwise trade securities or financial instruments related to the companies discussed, before or after publication, without prior notice and without any obligation to update the analysis. Publication of an analysis should not be read as a statement that any position does or does not exist.
The analysis may contain errors, omissions, or information that changes after publication. Readers should review official filings and primary sources before making decisions.