Holland Capital Partners v. MN Services was a Dutch contract dispute about the use of licensed pension administration software by MN Services N.V., a pension administrator, after it took over the administration of two further pension funds. The software supplier, Aquila Informatica B.V., sold its claim to Holland Capital Partners B.V. (HCP), which sued for licence fees and for contractual penalties for MN’s failure to notify Aquila in writing. The case reached the Supreme Court of the Netherlands twice. In the end MN had to pay EUR 700,000 in licence fees, and penalties claimed at EUR 20 million were mitigated to EUR 500,000.[1][2][3]
Background
MN Services grew out of the pension fund for the metal and technology sector (PMT) and was made an independent company from 1 January 2001, with PMT as its client. Its business plan for 2001 to 2003 aimed at strong growth by winning new clients. Aquila, an information architecture firm that also supplied software, worked with MN on a redesign of its pension administration.[1]
On 12 December 2001 MN and Aquila signed a framework agreement and a sub-agreement for the supply of “Oracle business components” and “Oracle base components” for a licence price of EUR 2,000,000. Article 9 of the framework agreement provided that the fee agreed in the sub-agreement was payable if MN was taken over (9.2), took over an organisation (9.3) or “in any way” combined with another organisation (9.4), and the information system developed with Aquila’s products was also deployed at that other organisation. The sub-agreement set that fee at 17.5% of the licence price. Article 9.6 required MN to notify Aquila in writing within two weeks of deciding to deploy the system in those cases, on pain of a penalty of EUR 25,000 for each week of delay, capped at five times the original product value.[1]
MN later took on the asset management (from 2007) and pension administration (from 1 January 2010) of the metalworking and electrical engineering industry pension fund PME, and also took over the pension administration of the merchant navy pension fund Koopvaardij. Both administrations had previously been run by another provider, Syntrus Achmea. Aquila was involved in some of MN’s preparatory work, including a 2004 presentation on insourcing PME. In 2011 or the first half of 2012 Aquila asked MN to pay the fee, and on 28 September 2012 MN refused.[1]
The dispute
On 30 September 2013 HCP, a company that buys and collects claims, bought and took assignment of Aquila’s claim. It sought EUR 700,000 in licence fees and penalties for MN’s failure to notify the combinations with PME and Koopvaardij. The District Court of The Hague dismissed the claims. The Hague Court of Appeal held that article 9.4 applied: MN had combined with the departments of Syntrus Achmea that administered PME and Koopvaardij, as shown by a social protocol treating the move of 158 staff as a transfer of undertaking, and MN had not disputed that the system was used for them. It awarded the EUR 700,000 but rejected the penalties, eventually holding that it would be unacceptable under reasonableness and fairness to impose them on top of the fee, given that the scope of articles 9.3 and 9.4 had been unclear to MN and Aquila had known of MN’s growth plans.[1]
Decision or outcome
Supreme Court, 2018
The Supreme Court upheld the finding that article 9.4 applied, because the Court of Appeal’s unchallenged finding that the system was also deployed at the departments MN took over could support it on its own. It overturned the award of statutory commercial interest, because the higher commercial rate does not apply to contracts concluded before 8 August 2002.[1]
It also upheld HCP’s complaint about the penalties. The fact that Aquila knew of MN’s strategy to grow through mergers and cooperation did not mean that Aquila knew when a combination actually happened, or that its interest in a written notice had gone; the Court of Appeal had not addressed Aquila’s point that the timing of the notice mattered because that was when the fee became due. And by relying on the lack of clarity of articles 9.3 and 9.4, which MN had not argued, the Court of Appeal had impermissibly supplemented MN’s defence. The case was referred to the Amsterdam Court of Appeal.[1]
Amsterdam Court of Appeal, 2020
After referral, the Amsterdam court held that the penalty clause was not set aside by reasonableness and fairness, but that the penalties should be mitigated under Article 6:94 of the Dutch Civil Code. The weekly penalty of EUR 25,000 amounted to EUR 1.3 million a year, and HCP’s claim totalled EUR 20 million, up to EUR 10 million for each of the two missed notifications.[2]
The court found that Aquila had suffered no loss from the missing notifications: it had learned from information MN gave during a quotation exercise that it was entitled to the fees, which the court assumed Aquila knew or should have understood by early 2011, and it had been able to enforce them. The need for litigation resulted from MN disputing the fees, not from the missed notices. The clause’s purpose was limited to ensuring Aquila learned in time that a fee had become due, and there was insufficient evidence that MN had withheld notice deliberately. The court called the gap between actual loss (nil) and the penalty claimed (EUR 20 million) a strong indication for mitigation.[2]
It mitigated the penalties to ten times EUR 25,000 for each missed notification and ordered MN to pay EUR 700,000 in licence fees with statutory interest from 1 January 2010, plus EUR 250,000 for PME and EUR 250,000 for Koopvaardij with interest from 3 December 2013, and costs.[2]
Supreme Court, 2022
HCP appealed again. The Advocate General advised dismissal, and on 18 March 2022 the Supreme Court dismissed the appeal without giving reasons, as the complaints did not raise questions important for legal unity or development.[4][3]
Later claim
In a separate case decided on 25 September 2024, Stichting Loyaliteit Aqln claimed a licence fee from MN under the same framework agreement for other cooperation arrangements. The District Court of The Hague held that no fee was due, because MN had not combined with another organisation and, on the arguments made, it could not be established that the information system was deployed at any of the cooperation arrangements; no penalty was therefore owed either.[5]
Significance for software licensing and SAM practice
The case concerns a bespoke supply agreement, not a standard vendor licence, but its clauses resemble common terms that tie the licence to the licensee’s own organisation and charge for use by acquired or combined entities.
- Corporate change as a licensing event. Taking over the administration of a client’s pension fund, with its staff and processes, counted as combining with another organisation, so using the existing system for that business triggered a fee.[1]
- Notification clauses. The supplier’s interest in a timely written notice survived even though it knew of the licensee’s growth strategy in general terms. The penalty clause was enforced, though heavily reduced.[1][2]
- Penalties and actual loss. Mitigation turned on the purpose of the clause, the absence of actual loss and the absence of deliberate concealment.[2]
- Assigned claims. The claim was pursued by a buyer of receivables rather than by the supplier itself.[1]
Lessons learned
- Clauses that charge a fee when the licensee combines with another organisation can be triggered by taking over a client’s operations. The courts applied article 9.4 to MN’s takeover of the PME and Koopvaardij administrations from Syntrus Achmea.[1]
- A written notification duty backed by a weekly penalty is enforceable even if the supplier learned of the change in other ways. The Supreme Court held that general knowledge of growth plans did not remove the supplier’s interest in timely notice.[1]
- Courts may mitigate a contractual penalty that is grossly out of proportion to the loss, but will not set it aside. The Amsterdam court reduced EUR 20 million to EUR 500,000.[2]
- Each new combination is assessed on its own facts. A later claim under the same agreement failed because no combination or deployment was established.[5]