The thirteenth pension is a software release: M&S and the code behind Swiss social insurance

Summary

• M&S Software Engineering AG provides the technical implementation, maintenance and support behind AKIS for first-pillar compensation offices, while the cooperative IGAKIS—not M&S—owns AKIS; M&S markets MSPension for second-pillar administration under a different product and governance boundary.
• The company's defensible advantage is the accumulation of statutory and operational knowledge embedded in configurable workflows, calculations, accounting, documents, interfaces and audit trails, not merely a browser interface or a Swiss Azure hosting location.
• Named migrations show both benefits and constraints: Previs transferred the records of 1,250 employers and more than 45,000 insured persons and pensioners, while the Solothurn compensation office described significant unplanned follow-up work and organisational strain after a rare central system change.
• Public procurement records expose the switching cost mechanism. A federal AKIS contract was awarded on technical and intellectual property grounds, and a Basel-Landschaft notice indicated that replacing a legally required module would also have meant replacing AKIS.
• Buyers should consider legal compliance performance, portability of reconciled data, control evidence, cloud topology, incident obligations, support depth and a funded exit plan as essential purchasing tests; M&S publishes too little evidence on pricing, service levels and exit terms for these questions to be answered from marketing materials.

December has a release date

In December 2026, the first payment of a thirteenth old-age pension in Switzerland will usefully illustrate a point about government software. The policy can be stated in a sentence, but the operational rule cannot. According to theimplementation guide of the Federal Social Insurance Office, the additional amount is equal to one-twelfth of the old-age pension payments made during the year. It only goes to people entitled to an old-age pension in December. Survivor and disability pensions remain on twelve payments. The thirteenth payment must not reduce supplementary benefits. For a widow or widower reaching the reference age, a compensation office may have to compare annual totals because the higher monthly survivor pension may still produce a lower annual amount than an old-age pension paid thirteen times. An exact calculation cannot be made before December.

This is not a website content change. It is a release affecting eligibility, temporal logic, benefit categories, annual aggregation, entitlement interactions, decision letters, accounting, payment files, exception handling and reconciliation with central registers. It requires test cases for deaths, entitlement commencements, pension conversions, retroactive corrections and people whose status changes during the year. It requires controls proving that the new payment is neither omitted nor duplicated. It must go live on the date chosen by law, not when a software backlog becomes manageable.

M&S Software Engineering AG does not decide any of these rules. Parliament, the electorate, the Federal Council and the competent authorities set the policy and issue the legal and administrative instructions. But the software used by the compensation offices determines whether these instructions become reproducible administrative work. TheOFAS description of the first pillarlists the main tasks of the offices: set, reduce or exempt contributions; determine pensions and helplessness allowances; collect contributions and pay benefits; settle with members, insured persons and the Central Compensation Office; conduct recovery procedures; and keep individual accounts. A defect in the execution layer can therefore become an incorrect invoice, a delayed pension, an incorrect account or an audit exception.

It is in this layer that M&S matters. The company's history and current product documentation place it behind AKIS in the first pillar and MSPension in the second. Its business promise is that legal changes can be converted into a managed evolution of a long-lived platform. The harder question for its clients is what happens after decades of this evolution: who owns the application, who understands the rules in the code, who can support the system under time pressure, and how an institution could leave without losing the evidence on which past decisions rest.

The thirteenth payment is therefore a better introduction to M&S than another inventory of offices and staff. It exposes the company's real product: a controlled continuity between a changing regulatory body and the money that must always arrive correctly.

The company behind the calculation

The exact company in question is M&S Software Engineering AG, an active Swiss corporation headquartered at Hilfikerstrasse 4 in Bern and with IDE number CHE-106.548.389. Public reproductions of the commercial register record its original registration in January 1990 and the current legal name. Thecompany portraitindicates that Jürg Mathys and Hans-Jörg Scheitlin founded Mathys & Scheitlin AG on 1 January 1990, that it acquired the occupational pension software manufacturer Güntert AG in 2013 and merged it in 2014, and that the name changed to M&S Software Engineering AG in October 2020. These events matter because they explain how a single supplier accumulated both first-pillar engineering experience and a second-pillar product base; they do not make Microsoft, IGAKIS, an individual pension fund or an Indian delivery unit the subject of this article.

M&S describes itself as owned by its partners and employees. A 2020 story published in Computerworld and preserved by the company states that a management buyout transferred the company to five long-serving employees in 2016, followed by a broader partner group. The public share register of a private Swiss corporation is not available here, so 'employee-owned' must be treated as a current representation of the company rather than an independently reconstructed cap table. The structure may nevertheless have practical significance. A supplier whose senior engineers are also owners may retain domain knowledge and encourage long product horizons.

It may also concentrate product, customer and succession knowledge within a relatively small group. Employee ownership is not a substitute for documented key person cover.

The best defensible description of current operational size is 'around 180 to 200 people', not a single mistaken estimate. Thecompany homepagementions around 180 employees in Bern and Schlieren. A July 2026 Great Place to Work profile reports 192 employees in Switzerland and Liechtenstein, while a 2026 pension industry event guide indicates around 200. An older page still mentions 140. These figures may reflect timing, headcount definitions or inclusion of other sites, but the pages do not reconcile them. The M&S homepage highlights Bern Wankdorf and Schlieren; an employer profile from the University of Bern and the M&S company portrait also name Chennai, and the latter identifies a CEO of 'M&S India'. The public materials do not establish the precise legal, employment or subcontracting relationship between that operation and the Swiss corporation. A buyer should ask, especially if production support or personal data access crosses legal entities or borders.

The current public management boundary is clearer. Markus Burkhart, an early architect of AKIS, has been CEO since 2019. Swiss commercial register notices reproduced in March 2026 show Jacqueline Lindinger becoming chair of the board and list a management and advisory group rooted in the company. M&S's current recruitment also gives a useful view of its operational capability: a2026 job posting for a.NET/C# developerdescribes complex web applications built with.NET/C# and Microsoft SQL Server, Scrum teams, code reviews, unit testing and developer support from concept through to acceptance and customer issue resolution. That is company evidence, not a code audit, but it is more concrete than a generic 'digital solutions' label.

M&S is private. No public audited revenue, margin, recurring revenue share, customer concentration or product-level profit was located in the frozen evidence set. Its size is therefore visible mainly through employment, product usage, public procurement notices and named implementations. This limitation should shape any assessment: it is a documented operating company with a substantial institutional footprint, but not a company whose financial resilience can be inferred from public accounts.

One supplier, two different boundaries

The most important identity correction lies within the product portfolio. M&S commonly says it is the manufacturer of AKIS for the first pillar and MSPension for the second. This shorthand masks a material legal difference.

TheAKIS website itselfstates that the software is owned by IGAKIS Genossenschaft and technically implemented in collaboration with M&S. The AKIS datasheet is more specific: M&S develops, maintains and supports the application on behalf of IGAKIS, with M&S mainly providing second-level support. IGAKIS is a cooperative of compensation offices. Its history describes a user organisation, project and maintenance teams, cooperative decision-making and M&S as its sole software supplier. In other words, the first-pillar arrangement combines collective ownership of the application by the customers with concentrated technical delivery by a single company.

This division is not semantic. It determines who holds the intellectual property rights, who prioritises shared changes, who contracts for software work, who represents the member offices and who can provide help desk knowledge. It also complicates the usual dependency story. A compensation office is not simply captive to a proprietary application owned by M&S. It participates, directly or through the cooperative structure, in a collectively owned system. Yet the public record shows that technical capability and support knowledge may still be exclusive to M&S.

Collective ownership can improve bargaining and pool the costs of legal changes while leaving execution concentrated.

MSPension sits on the other side of the boundary. M&S presents the browser-based standard solution as its occupational pension product, built on common M&S core components. Earlier documents call it M&S¦Pension; current pages and datasheets use MSPension. The product serves company pension funds, public-law pension funds, collective and joint arrangements, administration service providers and vested benefits foundations. M&S also names partners such as HRS Informatik and Five Informatik around implementation and archiving.

The public evidence supports M&S's role as software publisher and service provider, but it does not disclose the full MSPension licence terms or an intellectual property schedule.

Keeping the two boundaries separate improves analysis. In the first pillar, the governance question is how a cooperative translates the common and divergent needs of many offices into a roadmap delivered by a single engineering company. In the second, it is how individual funds or administrators buy, configure and potentially leave an integrated supplier platform. The technical components may share a lineage, but the customer control surface is not the same.

AKIS turns the law into a case queue

AKIS is best understood as a case processing and accounting environment, not simply a benefit calculator. Itsfour-page product datasheetdescribes a browser-based system covering communication, specialised applications, accounting and a common framework. Inputs can arrive via the connect portal, central registers, the Central Compensation Office, Swissdec, the federal sedex exchange, scanning or manual entry. They initiate processes within integrated workflow, document and people management. Specialised modules then perform contribution, benefit or cantonal task work, and management information shows queues, results and controls.

The scope follows the legal workload. Member and insured person registers establish who owes contributions and under what relationship. Contribution modules calculate, post and control first-pillar contributions and assigned levies. Individual accounts record the earnings history used for entitlements. Benefit modules manage old-age, survivor and disability pensions, loss-of-earnings allowances and family allowances. Cantonal modules may cover supplementary benefits, medical expenses and health insurance premium reductions. Accounting handles the resulting receivables, payments and transfers.

The product document indicates that pension calculations still depend on the ACOR solution of the Central Compensation Office, a reminder that AKIS is a node in a federal system rather than an independent policy engine.

M&S and IGAKIS claim that the standard package contains around 500 configurable process types and around 1,500 activity types. These are supplier-side counts, not independently audited measures of functional scope. They are nevertheless revealing. The unit of value is not just a screen. It is a defined path with inputs, responsibilities, deadlines, documents, postings, checkpoints and completion conditions. A salary declaration, for example, may produce a difference calculation and a posting to the individual account; a benefit case may require checks in central registers, a decision, a payment and a subsequent correction.

The architecture explains both automation and dependency. An event bus can start work from incoming or outgoing electronic messages. Web services connect archives and third-party financial systems. The product says it connects to around 20 registers and exchange channels. A configurable workflow can route a case to a team, execute eligible steps without intervention, pause for evidence, impose a second check and record what happened. This can reduce manual handoffs.

But each external interface creates a versioned contract, each local configuration is part of an office's operating model, and each automated exception still requires someone who understands the law and the software state.

The technology is conventional by design: a multi-tier Microsoft web stack using.NET and C#, with Microsoft SQL Server named in current recruitment. Conventional technology is an advantage for recruitment and support, but it does not make the application replaceable. The scarcity lies in the domain models, regression suites, conversion utilities, configuration knowledge and interpretation of federal instructions. A generic C# team can read the code; it cannot instantly reproduce three decades of contribution, pension and cantonal exception management.

AKIS can be run on-premises or through M&S's SaaS offering in Microsoft Azure Switzerland. This choice changes infrastructure responsibility, not the legal outcome. Whether servers are managed by the office, M&S or Microsoft, a January payment must still be correct and a historical decision still explainable.

MSPension must remember the past

Second-pillar administration has a different financial logic. Thecurrent OFAS explanationsets the legal floor: occupational coverage starts at defined age and salary conditions, retirement savings accumulate from age 25, a minimum interest applies to mandatory assets, and benefits cover old age, death and disability. Individual pension institutions may offer arrangements above the mandatory minimum. This creates a mix of federal parameters, fund regulations, employer affiliations, plan variants and personal histories.

MSPension's published module map follows this mix. Its active member core manages entries, exits, salary and plan changes, savings accounts, interest, contributions, credits and chargebacks. A benefits module establishes and administers applications and pays out pensions or capital for old age, death and disability. Plan administration contains plan definitions, contribution and benefit calculations and tax parameters. Contract management covers employer affiliations and pricing offers. Optional areas handle vested benefits, pillar 3a and individual investments.

Integrated accounts receivable/payable and general ledger functions link case results to money, while documents and management reports preserve the administrative trail.

One small feature says a lot about the product's purpose: M&S states that retroactive changes can be processed even in periods already closed in accounting. Social insurance history is not append-only. A corrected salary, late notification, changed disability degree, divorce, reactivation or revised entitlement may require the current system to modify the consequences of a past event without destroying the record of the closed period. The software must calculate a difference, post it correctly, regenerate or supplement evidence, and show an auditor how the current result emerged.

The product's process layer can start work from payroll interfaces, connect portals, scanning or manual lists. It defines who acts, what outputs—documents, reports or cash movements—must exist and what control procedure applies before completion. M&S claims that all steps are logged. Its accounting description says that a general ledger balance can be traced back to an affiliation or insured person. These are product claims rather than independent control reports, but they describe the right problem: a pension platform is a ledger of decisions as much as money.

MSPension is browser-based, uses.NET/C#, and is described as multi-tier and scalable. It can be run in-house or consumed as SaaS. Its connect surfaces serve employers, insured persons, brokers and fund bodies; interfaces extend to payroll systems, the Central Compensation Office, brokerage platforms and industry exchanges. The scope is commercially attractive because a single data model can support administration, portal service, documents and accounting. It also increases the blast radius of a faulty release and the cost of untangling.

Public adoption figures require caution. The M&S homepage indicates around 250 pension institutions and 600,000 insured persons. A pension services directory updated in April 2026 indicates 750 institutions and 700,000 insured persons. A 2026 event publication mentions around 750 institutions and 850,000 insured persons. The likely explanation may be different counts of legal pension institutions, pension plans or sub-funds within collective arrangements, but none of the pages defines its denominator. It would be imprudent to pick the largest number and call it current market share.

A serious due diligence request should demand a dated reconciliation: legal clients, production tenants, administered schemes, active members, pensioners, and whether partner-managed installations are included.

Connect is the gateway and the fault line

The connect platform is where the internal administrative system becomes an external service. In AKIS, employers, trustees and insured persons can initiate or participate in first-pillar processes. In MSPension, employers can declare entries, exits, salary and plan changes; insured persons can view their situation and run simulations; brokers and other parties can submit structured information. Online entry, file upload and web services can replace paper or rekeying.

This gateway changes the economics. A clean digital message can start a workflow and, if all conditions are met, pass through automated activities. The institution can process more volume without equivalent headcount growth. It can give a customer a status or result earlier. Cost is shifted upstream to identity, validation, interface certification, exception design and support. 'No break in support' is only useful when the incoming message is complete, authentic, semantically stable and matched to the right person or employer.

Swissdec illustrates the moving-interface problem. Its payroll standard coordinates electronic reporting across domains, and itscurrent transition guideended support for ELM 4.0 for most non-tax payroll domains on 30 June 2026; 2026 payroll requires ELM 5.0 or higher. Swissdec also published ELM 6.0 documentation in March 2026. A software vendor must support overlapping versions, certification cycles, employer payroll products and deadlines without corrupting contribution data. The visible portal may barely change while the message contract underneath changes.

The same goes for central registers and future federal services. A2025 review by the Swiss Federal Audit Officefound that the decentralised structures of the first pillar had produced fragmented IT, inefficient interfaces, redundant systems and weak interoperability. It identified IGAKIS as one of several IT pools and said that around half of compensation offices use AKIS. The audit praised pragmatic federal digital work but criticised fragmented governance, incomplete economic analysis and cross-project risk management. The BISS framework planned by OFAS and the first-pillar e-platform aim to standardise secure exchange and offer insured persons more direct digital services, with public-facing services expected no earlier than 2028.

This does not make AKIS obsolete. It changes what it must connect to and which responsibilities remain local. A federal platform may standardise an account request or a message route while compensation offices still administer contributions, cases and assigned cantonal tasks. For M&S, interoperability may open a cleaner boundary—or turn years of local integration into a new version programme. The watchpoint is whether federal standards reduce proprietary coupling or simply add another layer.

The regulatory corpus never closes

M&S markets 'evolution rather than revolution'. In this market, it is a testable operational proposition, not a slogan. The regulatory corpus changes at multiple speeds.

AVS 21 came into force in 2024, changed the terminology from retirement age to reference age, made retirement more flexible and began increasing the reference age for women in annual steps. The2026 ruleis 64 years and six months for women born in 1962, with transitional compensation for certain cohorts. The thirteenth old-age payment arrives in December 2026. Swissdec message versions succeed each other. The minimum parameters and disclosure duties of occupational pension provision change. At the time of writing, AVS 2030 is in consultation, while BISS promises new digital communications and data exchange. Some changes are enacted, some are administrative, and some remain proposals. Production software must distinguish them.

The delivery challenge has at least four stages. First, a legal instruction must be converted into cases and parameter changes without ambiguity. Second, shared behaviour must be separated from institution-specific policy and configuration. Third, calculations, documents, interfaces and accounting consequences must be tested together. Fourth, the release must be deployed, explained and supported before the effective date. A defect found in a user acceptance environment is software work; a defect discovered after a pension run is operational and political work.

The IGAKIS cooperative model helps by pooling the specialised inputs of compensation offices. Its anniversary publication describes around 50 project and maintenance teams and around 140 entity employees from member offices at the time. Members contribute domain knowledge; IGAKIS manages projects; M&S provides engineering. This arrangement can create better requirements than a supplier guessing at administrative practice. It can also make prioritisation slow or diffuse when many offices have different organisation, culture and assigned cantonal tasks—the same institutional friction identified by federal auditors.

M&S publishes no longitudinal release performance data: no percentage of legal changes delivered on time, escaped defect rate, rollback frequency, mean emergency fix time or customer-specific upgrade lag. There is also no public evidence showing how many variants of each product are in support. 'Continuously adapted' is plausible given the age and current use of the systems, but procurement should convert the claim into service obligations and historical evidence.

Migration is the product test

A pension fund or compensation office migration is not finished when records have been copied. It is finished when the new system can reproduce balances, histories, open cases, documents, entitlements, interfaces, controls and future results—and when staff can operate it under real deadlines.

Previs Vorsorge provides an unusually concrete second-pillar example. Its ownApril 2025 reportsays it introduced MSPension and a new PrevisConnect portal in early 2025. The transfer covered data and documents of 1,250 affiliated employers and more than 45,000 insured persons and pensioners. The cutover had a firm reference date of 31 December 2024: information had to leave the previous administration software and enter the new one correctly. Previs called the undertaking relatively complex and said the change was largely smooth, while noting a missing tax calculator compared to the old application's features. It is both a success reference and a reminder that parity must be defined feature by feature.

First-pillar changes show a broader operational coalition. The social insurance bodies of Appenzell Ausserrhoden, Uri and Appenzell Innerrhoden went live with AKIS as part of a coordinated 'Avanti' programme. The public account from SOVAR described more than a year of preparation, data migration, a new environment and six inspection releases before go-live, with support from M&S, IGAKIS, an IT partner and experienced peer offices. AnAppenzell Innerrhoden public procurement noticecalled its broader migration project complex and required a new archiving and operations solution to interface with M&S's AKIS.

The Neuchâtel case in 2026 adds language and prior-system risk. TheProAct implementation reportsays that the Neuchâtel cantonal compensation office was the first truly French-speaking compensation office to migrate to AKIS and the first migration from NIL/NIL+ after four IGS migrations. The programme used HERMES, workshops, training, bilingual coordination and post-launch support. As a consultant case study, it is promotional and recent; it nevertheless identifies the work that a licence does not automatically buy.

These examples show why installed-base counts alone are a poor quality measure. A migration consumes customer staff, external project leadership, supplier specialists, peer knowledge, data remediation capacity, test environments and a cutover window. It may expose undocumented exceptions in the old system. It must prove not only that totals reconcile but also that individual histories and work in progress still make sense. The buyer effectively acquires an institutional implementation, not just software.

The same evidence explains the exit cost. After an office has converted its documents, configured plans, trained staff, integrated payroll and archives, rebuilt portals and accumulated new workflow history, reversal requires more than a. A successor must understand how raw fields, documents, process state and accounting evidence reconstruct a legal decision. The supplier's migration competence is both a customer benefit and a source of dependency.

The Solothurn warning

The most useful public counterweight to smooth implementation stories comes from the Ausgleichskasse des Kantons Solothurn. Its2023 annual reportsays that the multi-year MOVE project put AKIS into service in June 2023. The office called the software change a success, thanked M&S, IGAKIS and other offices, and expected that a process-oriented browser system would eventually lighten routine work. It also said that a compensation office very rarely changes its central application, lacked experience with a programme of this size, and faced follow-up work that had not been planned. Additional adaptations and training remained necessary. The organisation was heavily loaded, and backlog reached extreme levels amid a broader crisis of leadership and operation.

The report does not prove that AKIS or M&S caused this crisis. It describes deeper organisational, personnel, leadership and communication problems, and it explicitly judges the implementation successful despite them. It also records a punishing coincidence: as staff were absorbing the new central system, the office had to implement AVS 21. The pension teams worked through the year-end close to ensure that January 2024 payments were correct.

This distinction is essential. A technology article can easily attribute every post-launch problem to the product or excuse every problem as 'change management'. The record supports neither. It supports a more demanding conclusion: a central platform programme changes roles, queues, controls, vocabulary, interfaces and how staff know whether work is done. If organisational capacity is already thin, even a functioning system can increase short-term backlog because the institution is learning, correcting converted data and redesigning processes while continuing legal service.

For a buyer, the Solothurn warning changes the business case. The project cost must include temporary productivity loss, dual running, data correction, training, additional support, post-launch tuning and simultaneous legal releases. Success criteria should measure backlog, payment timeliness, error and rework rates, not just a technical go-live. The supplier should be asked to show staffing assumptions and failure conditions under which a cutover is delayed. A client should reserve the right to stop, reconcile and roll back.

This also changes how M&S should be assessed. The relevant question is not whether its software can be installed. It is whether the supplier can help a public or quasi-public institution reach stable throughput after installation, while distinguishing product defects, configuration errors, conversion gaps and customer operational problems. Public case studies do not provide this comparative data.

Azure moves the boundary, not the duty

M&S offers both products on-premises and as SaaS in Microsoft Azure Switzerland. Swiss hosting is a rational response to latency, procurement preference and data location concerns. It is not, in itself, proof of sovereignty, security or continuity.

TheFederal Data Protection and Transparency Commissionertreats cloud use as outsourced processing. The institution that determines the purpose of processing remains responsible for lawful processing, data minimisation, security, subcontractors, data subject rights and any cross-border disclosure. A pension fund or compensation office cannot transfer this responsibility to M&S, and M&S cannot transfer its contractual obligations to Microsoft. The subcontractor chain must be understood contractually and operationally.

'Azure Switzerland' also leaves architectural questions unanswered. Microsoft'sreliability documentationexplains that availability zones have independent power, cooling and networking, but applications must use supported zonal or zone-redundant designs; for many resources, the workload team must configure and test resilience. Microsoft'sshared responsibility modelstates that the customer retains responsibility for data and identities, with allocation varying by service model. A Swiss region establishes a location boundary for selected services. It does not reveal whether MSPension or AKIS is deployed across zones, how databases fail over, where backups and support logs go, or whether recovery depends on another geography.

M&S's public product material says that its system management, combined with Microsoft safeguards, provides high security and reliability. That is a company claim. The public evidence examined for this article did not include a service description with uptime percentage, recovery time objective, recovery point objective, maintenance windows, tenant isolation design, backup immutability, tested disaster recovery results or compensation for missed service levels. Nor did it show which Azure services are used or which responsibilities M&S retains.

Buyers need these documents under confidentiality if necessary; locality should never be allowed to replace topology.

On-premises deployment is a genuine alternative, but not a dependency-free option. It shifts infrastructure, patching, monitoring and some recovery to the institution or its IT provider while leaving application releases, specialist support and product knowledge with M&S and IGAKIS. It may complicate version consistency across clients. SaaS can standardise operations and improve supplier visibility, but it can also bundle application and infrastructure release into a single event.

The right comparison is therefore a responsibilities matrix. For each deployment model, the buyer should identify who manages identity administration, encryption keys, vulnerability remediation, database recovery, operating system patching, application deployment, interface monitoring, incident triage, user support, evidence retention and communications with authorities and insured persons. 'Hosted in Switzerland' answers only one cell.

Auditability is a control system

Social insurance software processes identity, health-related circumstances, family situation, salaries, contribution histories, bank details, tax information and benefit decisions. Confidentiality matters, but accuracy and availability are equally important. A perfectly secret but incorrect or unavailable pension calculation is still a failure.

Swiss oversight is saying so increasingly explicitly. Themodernised first-pillar supervision framework of OFASrequires implementing bodies to ensure the stability of their information systems, information security and data protection. The explanatory material describes these systems as critical infrastructure and requires that serious incidents affecting stability or operation be reported. OFAS also published a 2025 guide for internal control systems in compensation offices. Occupational pension institutions face legal duties of management, information, accounting, actuarial and audit; theOFAS overviewnotes annual insured person information and access to annual accounts and reports.

M&S's product design addresses part of this control surface. AKIS and MSPension describe logged workflow steps, configurable control procedures, integrated documents, management information and drill-down into accounting. These features can support segregation of duties, four-eyes review, completeness checks and reconstruction of a posting. Whether this is the case in practice depends on configuration, access control, log protection, retention, change governance and exception queue quality.

An audit trail feature is only an effective control if an institution can show who reviews it, how exceptions are resolved and whether privileged users can alter evidence.

The company portrait lists ISO 9001:2015 and 'ISO 27001/17' certifications since 2021. A business directory separately lists ISO/IEC 27001:2022. No current certificate, accredited issuer, legal entity scope, covered sites, cloud service scope or statement of applicability was found in the public evidence examined. This does not show that the certifications are invalid. It means that procurement should inspect the certificates and the latest surveillance findings rather than repeating an abbreviated acronym. The same applies to marketing references to annual assessments or 'bank-grade' security.

No credible public report of an M&S product security breach or material SaaS outage was found in the frozen evidence set. This is not evidence that none occurred. Private business-to-business incidents may not be public, and a search cannot establish an incident history. M&S also does not expose a public status history that would allow independent availability analysis. A buyer should request a defined period of incident records, severity, recovery and notification, including near-misses and material subcontractor events, under appropriate confidentiality.

Security due diligence should follow the data and the decision. Can a support engineer see production personal data? Are identities federated and privileged sessions logged? Are test environments fed with production copies or masked data? Are exported reports signed or tamper-evident? Can the logs reconstruct a retroactive calculation before and after a rule release? What happens if an archive connector is unavailable while a workflow completes? These questions link cybersecurity to the administrative duty the system exists to fulfil.

Revenue without a public price list

M&S publishes no prices for AKIS, MSPension or M&S¦SaaS. Its service catalogue—development, maintenance, support, implementation, consulting, training and operations—suggests multiple revenue streams, but the public material does not disclose their proportions. It would be speculation to invent a per-member subscription, a licence metric or a gross margin.

Public procurement reveals the economic shape more clearly. The2021 report of the Confederation Procurement Conferencerecords an award of CHF 9.89 million for AVIT2 covering October 2021 to September 2026 to IGAKIS Genossenschaft and M&S Software Engineering AG. The justification given was technical particularity and intellectual property protection. A procurement index reproducing the full notice indicates that IGAKIS held all rights to AKIS and that the required help-desk services could be supplied exclusively by M&S. The public documents do not split the contract value between the cooperative and the company, so it is not M&S revenue.

The arrangement demonstrates a recurring business logic. Clients pool product ownership and shared changes through IGAKIS, while M&S earns engineering, maintenance and support work around the platform. For MSPension, M&S can combine product rights, implementation and ongoing services more directly, with partners providing selected functions. SaaS adds an operations responsibility and likely recurring charges, but the billing unit is not public.

The customer's economic calculation should therefore be lifecycle-based. The initial licence or subscription cost is only one line. Implementation absorbs project staff, conversion, interfaces, testing and training. Steady-state cost includes maintenance, legal releases, support, cloud consumption, archives, identity services and local product administration. Change requests may be shared, configurable or bespoke. Exit requires extraction, reconciliation, successor implementation, parallel running and evidence retention.

There may be substantial benefits. A shared standard platform can spread the cost of legal changes, allow smaller institutions to reuse controls and reduce duplicate engineering. Automation can reduce manual handling and rework. Federal auditors noted potentially significant process savings from digital services, while criticising the absence of comparable cost-benefit analysis across the first pillar. M&S does not publish client-level total cost studies with baseline, implementation cost, achieved staff savings and service quality.

Buyers should not accept 'automation' as a benefit category without measuring cases handled, exception rates, time and cost.

The price of exit

Dependency here is neither a moral accusation nor a simple licence clause. It is the accumulated cost of preserving legal continuity while changing the machinery underneath.

The most direct public evidence comes from procurement. A2020 Basel-Landschaft noticeconcerned modifications to the AKIS supplementary benefits module required by a new law from January 2021: new calculations, geographically variable rents, changed cost coverage and an asset threshold. The associated award justification stated that IGAKIS held the rights and code knowledge, that the module could only run with AKIS base modules, and that replacing it would have meant replacing AKIS. That is a legal change meeting architectural coupling in a single document.

There are at least seven layers of switching cost.

First, data semantics. Names and balances can be exported; the meaning of statuses, historical corrections, plan versions, document links and open workflows is harder. Second, calculation parity. A successor must reproduce entitlements and accounting at a chosen reference date, including edge cases. Third, reconstruction of interfaces with central registers, payroll, archives, finance, banks, brokers and portals. Fourth, control evidence: an institution must preserve why past decisions were made, not just their current totals. Fifth, staff knowledge and training. Sixth, cutover risk under fixed contribution and payment schedules.

Seventh, contractual and intellectual property dependency, especially when only one party can modify or support the code.

Integration amplifies cost. The appeal of MSPension is that active members, pensioners, plans, benefits, contracts, documents and accounting share a system. The appeal of AKIS is that cases, people, contributions, benefits and assigned tasks are integrated. The same integration means that a buyer cannot lightly replace one module if data, processes and accounting assumptions cross it. A collection of loosely connected products might be easier to swap one by one but harder to operate and reconcile each day.

Exit readiness is the discipline that keeps this trade-off legitimate. Contracts should define regular exports in documented, non-proprietary formats; extraction of process state and audit history; packaging of documents and metadata; configuration and rule inventories; assistance rates; deletion certification; legacy read-only access; and transition support after termination. Customers should test exports before renewal, not discover their limits during a tender. For AKIS, the cooperative's ownership may be an asset if the rights, build capability and transition knowledge are operationally usable rather than merely legal.

For MSPension, the burden rests more directly on bilateral terms.

The goal is not zero switching cost. A system that faithfully models decades of social insurance history will always be expensive to replace. The goal is to make the cost estimable, the evidence portable and the decision reversible without endangering payments.

Competition is real but segmented

M&S does not operate in a market without alternatives. It operates in several narrow markets where alternatives have their own communities, histories and migration costs.

In the first pillar, the Federal Audit Office lists several IT pools and providers alongside IGAKIS: IGS, Insite, iPension, Ensemble AVS, OSIV and GILAI for different implementing bodies and functions. TheeAHV/IV associationalso lists IGAKIS, IGS, EnsembleAVS, Insite, iPension and NIL among the IT organisations.IGSsays it serves 16 Swiss social insurance organisations in three language regions plus Liechtenstein with an integrated portfolio. These are not interchangeable products in a catalogue; they are institutional and technical ecosystems. Neuchâtel's move from NIL/NIL+ to AKIS shows that competition can result in a migration, but only through a significant programme.

In the second pillar, visible alternatives includeSwissPension, which presents a pension administration product with a four-decade history;xPlan by aXentafor occupational pension administration; andPAKT by Prevo-Systemfor collective life insurance business. The scope differs. Some focus on autonomous pension funds, some on collective foundations or insurers, and some combine software with administration services. Generic enterprise resource planning, workflow or accounting tools can replace components but not immediately Swiss pension calculations and regulatory history.

Competition therefore occurs during infrequent decision windows: a legacy product hits a strategic limit, an institution changes its operating model, a collective arrangement grows, or a board accepts migration risk. In steady state, the incumbent has an information advantage on configurations, data and unresolved edge cases. A tender may attract alternatives while finding that only the incumbent can deliver an urgent legal change on the current platform. The public procurement record makes this tension visible.

M&S's sustainable advantages are a large reference community, deep domain tenure, integrated products, a Swiss delivery identity, a cooperative relationship in the first pillar and an end-to-end service catalogue. Its disadvantages or risks are the same features seen from the buyer side: concentration of specialist knowledge, Microsoft stack dependency, opaque pricing and service metrics, and costly exit. Competitors should be tested on comparable outcomes rather than feature counts. Can they migrate history? Can they prove legal releases? Can they manage cutover? Can they support workflows in French, German and Italian?

Can they preserve audit evidence? A lower licence price without these answers is not a substitute.

What a buyer should demand

An institution acquiring or renewing M&S software should turn the company's strengths into evidence-based obligations.

Start with the rights map.For each module, connector, report template and tool, identify the rights holder, source code maintainer, build operator and the party authorised to provide support. The AKIS answer must distinguish IGAKIS ownership from M&S delivery. MSPension contracts should identify third-party components and the consequences if a partner relationship ends.

Conduct a legal change trial.Give bidders a real but historical rule change—AVS 21, the supplementary benefits reform or a pension plan amendment—and demand a trail from legal interpretation to requirements, test cases, calculation, documents, accounting, approval and deployment. Ask M&S for on-time release and post-release defect history. The trial is a controlled translation, not a slide on agility.

Prove an end-to-end case.Select representative normal, retroactive and exception cases. Trace an entry from connect or payroll through identity matching, workflow, calculation, control, posting, payment and archived evidence. Reconcile management totals with individual cases. Demonstrate what happens when a central register, archive or bank interface is unavailable.

Rehearse migration and exit.Require multiple dress rehearsals, record-level and aggregate reconciliation, document counts, open case conversion, production-volume performance and a rollback decision point. At the same time, export the same environment to the proposed exit package and have samples rebuilt by an independent team. Previs's year-end cutover and SOVAR's six inspection releases provide realistic reference points.

Inspect controls rather than badges.Examine certification scope, privileged access, segregation of duties, deployment approval, log immutability, vulnerability management, penetration test remediation and incident exercises. Map each material control to the client, M&S, IGAKIS, a local IT partner or Microsoft. Verify that the institution can produce regulatory and audit evidence without supplier improvisation.

Make continuity measurable.Contractual uptime is not enough. Define payment and deposit deadlines, maximum data loss, recovery time per service, degraded mode operation, batch rerun, contact escalation, crisis communications and staffing. Require evidence of restored backups and zone or region failure exercises. Disclose which recovery choices keep data in Switzerland and what they cost.

Price the full lifecycle.Separate licence or subscription, hosting, environments, storage, interfaces, standard legal maintenance, customer modifications, implementation, training, premium support and exit assistance. Use volumes that can be audited and cap reclassifications. Compare cost per case processed and per member administered alongside error, backlog and service measures.

Test organisational capacity.Request named roles, language coverage, concurrent programme load, key person succession and the split between Swiss corporation employees, partners and any overseas operation. References should include a recent migration, a difficult legal release and a customer who has challenged the supplier—not just showcase accounts.

These requirements do not presuppose that M&S will fail them. They recognise that a supplier embedded in legal administration should be judged on the same qualities it sells: traceability, control and continuity.

Evidence gaps and watchpoints

M&S is unusually visible for a private specialist supplier, but consequential gaps remain.

There is no public reconciled customer count for MSPension. Figures of 250 and 750 institutions and 600,000, 700,000 and 850,000 insured persons coexist in recent material. There is no published list linking these figures to legal clients, schemes or partner-managed installations. AKIS's claim of 'more than half' is broadly supported by the Federal Audit Office, but the current office-by-office production deployment status is not public.

There is no public price list, revenue, balance sheet, customer concentration, retention rate or research and development spend. The CHF 9.89 million federal award is joint with IGAKIS and cannot be treated as M&S revenue. Financial resilience and dependence on a few large programmes remain unquantified.

There is no public SaaS service schedule, architecture diagram, recovery proof, subcontractor inventory, tenant model or status history page. Certification claims are not publicly accompanied by current certificates and scope. No credible public report of a breach or material outage was found, but this absence does not settle the operational history. Product documents describe controls and logs; no independent assurance report was available to test their design and operation.

There is no public standard exit pack, data dictionary, migration assistance rate, source code escrow for MSPension or reference showing a complete departure from either platform. The named cases are migrations into AKIS or MSPension, not out. Procurement records prove coupling more clearly than portability.

Several short-term watchpoints may reduce these uncertainties:

• The first payment of the thirteenth AVS pension in December 2026 will test benefit logic, annual comparisons, communication and payment controls in compensation offices.
• The AVIT2 federal award period recorded in procurement runs until September 2026. Its successor arrangement may reveal current costs, scope, rights and support concentration.
• The Neuchâtel implementation in 2026 may show over time whether AKIS and its delivery model scale in French-speaking Switzerland without excessive local variation.
• Mandatory use of ELM 5.0 and the emergence of ELM 6.0 will test interface version discipline between payroll providers and social insurance systems.
• BISS and the federal first-pillar e-platform, whose first insured-person services are not expected before 2028 at the earliest, may standardise interfaces and shift the balance between central services and local IT pools.
• M&S's changing public scale figures and references to Chennai or Liechtenstein should be reconciled with headcount by legal entity, access locations and support responsibilities.

The most useful disclosure M&S could make would not be another market share superlative. It would be a dated operational data sheet defining customer units, release performance, service availability, security scope, hosting design and tested portability. These metrics would allow institutions to distinguish mature continuity from dependency that has simply remained unmeasured.

Continuity is the product

M&S Software Engineering AG occupies a modest corporate footprint and a disproportionate administrative position. It is not the author of Swiss social policy, the owner of every product associated with its name, or a hyperscale cloud. It is the engineering company that helps turn legal choices and pension regulations into thousands of repeatable decisions in compensation offices and pension arrangements.

The company's moat is cumulative. It consists of rule interpretations turned into tests, configurable processes, calculation histories, interfaces, accounting links, migration tools, support routines and people who remember why an exception exists. Microsoft Azure Switzerland can host this machinery, but does not create the knowledge. A cooperative may own AKIS, but ownership alone does not reproduce M&S's delivery capability. A competitor may offer a modern interface, but must still migrate the legal and operational past.

This cumulative value creates a legitimate trade. Institutions gain shared development, legal continuity and integrated control. In return, they accept concentration and a high switching cost. The trade remains healthy only if the dependency is governed: rights are explicit, releases are measurable, controls are inspectable, recovery is tested, prices are decomposed, data is portable and exit is rehearsed.

December 2026 will pass, and the thirteenth pension will become another ordinary annual process. That ordinariness is the achievement that social insurance software is supposed to produce. It is also what makes the supplier easy to overlook. M&S's importance appears at the moment a new legal phrase must become a correct payment—and at the much rarer moment an institution asks whether someone else could do it without losing everything the system already knows.