Malam Team: After the Write-Down, Does the Pension-Platform Reset Really Open a New Path?
The main article treated the pension-platform write-down as the moment an old illusion finally broke. This follow-up shows that the reset did not just wipe out NIS 27.2 million of capitalized software development. It also cut the sale-route weighting to 10% and shifted the whole thesis toward Mango execution through the end of 2026.
What This Follow-Up Is Isolating
The main article focused on the gap between operating growth and accessible cash, and on the need for a cleaner corporate structure. This follow-up is narrower. It isolates the pension and provident-fund computing and operations activity, because that is where 2025 produced both the sharpest accounting hit and the clearest strategic reset going into 2026.
Why this matters is straightforward. The 2025 write-down was not just noise in earnings. It marked the failure of the old route, a partnership or software-sale path with a financial institution, and replaced it with a new route in which Malam has to prove that one Mango platform can consolidate three systems, migrate customers, and deliver real operating, computing, and regulatory savings.
The sharp takeaway is this: after 2025, this activity is no longer valued mainly through an external-option story. In the year-end valuation, the sale-of-the-business scenario carried only a 10% weighting, down from 20% a year earlier, while 90% of value relied on continued operations and system consolidation. The thesis has moved from finding a partner to executing internally.
| Anchor point | What was known at year-end 2025 | Why it matters |
|---|---|---|
| Original route | The company described a preferred path of cooperating with a financial institution through a software sale or partnership | That was supposed to turn a costly built platform into a commercialization route through an existing financial player |
| What failed | The negotiations with a bank in Israel did not mature into an agreement | The bank route stopped being a practical base case |
| P&L impact | Q4 included NIS 30.3 million of other expense tied to the activity | The issue did not stay buried in the notes, it hit reported earnings directly |
| What was actually impaired | NIS 27.2 million of software development in the activity | Most of the hit was a write-down of an asset built for a route that did not close |
| New valuation frame | Recoverable amount of roughly NIS 36 million, based on two scenarios | The remaining value now depends mainly on internal execution, not on an outside transaction |
| New timetable | Customer migrations began in March 2026 and are expected to finish toward the end of 2026 | 2026 is a proof year, not a harvest year |
The Bank Route Closed, and the Write-Down Followed Immediately
The important point here is not the write-down by itself. It is what came before it. In the descriptive section for the long-term savings activity, the company presents its preferred direction as cooperation with a financial institution, through either a software sale or a partnership, with the group’s pension and provident subsidiary providing the operational and computing layer as a subcontractor. That matters because this was supposed to be the route that commercialized the technology investment through an existing financial player rather than leaving it on a self-build basis.
That route did not close. The company explicitly links the prolonged negotiations with a bank in Israel, which did not mature into an agreement, to a roughly NIS 30 million loss recorded in the last quarter of 2025 within other expenses. Both the annual management report and the intangible-assets note make that link directly. This was not a technical performance stumble. It was an admission that the path meant to give the activity an external commercial anchor did not materialize.
Out of the NIS 30.3 million other-expense hit, NIS 27.2 million was an impairment of software development. That is not just a write-down. It is a formal reduction in value for an asset built around a strategy that did not close. Once the bank route fell away, the company had to re-underwrite what the unit was actually worth under a more realistic scenario set.
The New Valuation Framework Lowers the Dream Factor
This is the part a reader can miss if they stop at the NIS 27.2 million number. In the impairment note, the company does not merely write down an asset. It rewrites the value framework for the whole activity. The recoverable amount of the unit was set at roughly NIS 36 million, based on fair value less costs to sell, after weighting only two scenarios: sale of most of the activity, or continued activity with operational-system consolidation and efficiency measures.
That shift matters more than the small change in discount rate to 14.45% from 14.93%, and more than the long-term growth assumption staying at 1%. What matters is that management itself cut the sale-scenario weighting in half, from 20% to 10%, and pushed 90% of value into a scenario where it has to merge systems and generate efficiency on its own. Put differently, the external commercialization option did not disappear, but it was demoted to upside rather than base case.
That is also why the 2025 write-down does not yet open a new path in the strong sense of the phrase. It only closes the old one decisively. The new path opens only if the valuation assumptions turn into operating facts. Until then, most of the unit’s value still rests on what the company has to prove rather than on what it has already locked in.
Mango Starts In March 2026, but the Proof Is Not Yet in the Numbers
The alternative route the company now presents is fairly clear. The group’s pension and provident subsidiary is near the end of a consolidation of three computing systems into a single platform called Mango, based on its new pension system. According to the description, the platform was designed from the earliest planning stage so it could support both a new pension fund and provident and study funds, with the first live customer being a new pension fund and the provident/study-fund layer coming only afterward.
The timetable is not vague. Customer migrations began in March 2026 and are expected to be completed toward the end of 2026, so that by the end of the process one system will operate new pension, provident, study-fund, and IRA activity. If that works, the company expects savings in operating, computing, and regulatory expenses. In other words, the new route is not primarily a sudden growth story. It is first a simplification, absorption, and cost-savings story.
The problem is that Q4 still does not provide clean proof that the reset is already showing up in reported economics. In the segment table, the company says the 2.3% increase in revenue in the payroll, HR, and long-term savings segment was driven mainly by one-time income from prior years within long-term savings activity. At the same time, when the company shows that same segment excluding long-term savings, revenue was almost flat at NIS 65.6 million versus NIS 65.5 million, and segment profit rose only to NIS 16.7 million from NIS 16.0 million.
That chart does not say the activity failed to improve at all. It says something sharper: the write-down came before the proof. Part of the reported segment improvement relied on a one-time prior-years item, while the underlying payroll and HR core was basically flat. In simple accounting terms, even after the improvement, the segment line that includes long-term savings still sits below the profit level of that same segment excluding long-term savings. The pension and provident-fund activity has not yet turned from a repair story into a segment-lifting engine.
What Has To Happen By The End Of 2026
That is exactly why 2026 looks like a reset year here, not a growth year. For the 2025 charge to look in hindsight like a one-time cleanup rather than the first stop in a longer erosion story, four things need to happen:
| What needs to happen | Why it matters |
|---|---|
| Customer migrations onto Mango need to be completed by the end of 2026 | Without a full move onto one platform, the promised efficiency case has no real base |
| Operating, computing, and regulatory savings need to become visible | That is the actual test of the 90% scenario, not the existence of the platform itself |
| Improvement needs to show up without relying on prior-years one-off income | Otherwise it will be hard to argue the reset already changed the economics of the unit |
| There must be no additional write-down or new reset charge | That is the line between one-time cleanup and a process that keeps consuming value |
The core question is not whether Mango sounds good on paper. The question is whether by the end of 2026 the company can show that one platform really can run the full pension, provident, study-fund, and IRA stack at lower cost and with stable enough service quality. Only then can one say the new path is truly open. Right now it has mainly been defined.
Bottom Line
The careful answer to the title question is, not yet. After the write-down, Malam Team opened a new path in only one sense: it stopped grounding the value of this activity in hope for an outside deal, and started grounding it in internal execution of a single platform. That is an important change, but it is not the same thing as success.
As of year-end 2025, what is in hand is a NIS 27.2 million impairment, a roughly NIS 36 million recoverable amount, a lower weighting for the sale scenario, and a timetable running through the end of 2026. What is not in hand yet is clean numerical proof that the reset is already producing better economics. At this point, Mango is not the end of the story. It is the next test of it.