Icertis, the Bellevue, Washington-based contract lifecycle management vendor, has faced two publicly reported lawsuits of note: a November 2021 breach-of-contract suit brought by Change Healthcare Operations, LLC in King County Superior Court over a failed software implementation valued at $5,180,939, and a 2025 employment discrimination case filed by Richard Peterson that was dismissed with prejudice on October 20, 2025. The Change Healthcare case is by far the more substantive of the two and is what most people are searching for when they look up an Icertis lawsuit.1Artificial Lawyer. Icertis Sued Over Alleged Failings of CMS Implementation
What Change Healthcare Alleged
Change Healthcare Operations (CHC) hired Icertis in June 2020 to design and implement a contract management system under three agreements: a SaaS subscription and services agreement, an implementation statement of work, and an administrative services statement of work. The four-year contract was valued at $5,180,939.1Artificial Lawyer. Icertis Sued Over Alleged Failings of CMS Implementation
At the heart of the complaint was a single capability CHC said it needed: the ability to apply one contract amendment to multiple agreements at the same time. CHC alleged Icertis represented during the sales process that its platform could do this, then only disclosed after the contract was signed that it could not.2Contract Nerds. Three Ways to Improve Your Next CMS Implementation Agreement — Lessons From the Icertis Lawsuit
Beyond that misrepresentation claim, CHC alleged a broader pattern of implementation failures:
- Training and documentation gaps. The contract called for two full days of classroom training; CHC said it received about three hours. Key deliverables including a data dictionary, business requirements questionnaires, and dozens of reports were allegedly never provided.1Artificial Lawyer. Icertis Sued Over Alleged Failings of CMS Implementation
- Staffing problems. CHC alleged that Icertis failed to assign qualified subject matter experts, that its personnel did not work during CHC’s regular business hours, and that Icertis brought in subcontractors without the prior approval the contract required.2Contract Nerds. Three Ways to Improve Your Next CMS Implementation Agreement — Lessons From the Icertis Lawsuit
- Substandard work product. CHC claimed that about 75% of Icertis’s deliverables required rework by CHC’s own staff, costing nearly 1,000 hours of internal labor, and that the template harmonization work was substandard across the board.1Artificial Lawyer. Icertis Sued Over Alleged Failings of CMS Implementation
Termination and Damages Sought
CHC sent Icertis a formal notice of material breach in March 2021 and gave the company 30 days to cure. When CHC concluded the problems remained, it terminated all three agreements in April 2021 and filed suit that November, saying it was “left with nothing tangible to show for months of work” and would have to start over with a different vendor.2Contract Nerds. Three Ways to Improve Your Next CMS Implementation Agreement — Lessons From the Icertis Lawsuit
CHC said it had spent more than $3 million buying and preparing for the system. It asked the court for:
- Rescission of the contract, restoring CHC to its pre-signing financial position.
- Return of all amounts paid to Icertis, plus interest.
- Reimbursement of $1,672,032.04 in payments CHC said it had mistakenly made to Icertis after the contract was terminated.
- Punitive and exemplary damages on top of actual losses.1Artificial Lawyer. Icertis Sued Over Alleged Failings of CMS Implementation
How Icertis Responded
Icertis disputed the allegations publicly. Peter J. Kramer, executive in-house legal counsel, said the company was “committed to delivering unmatched technology and category-defining innovation through our contract intelligence platform” and was “deeply invested in our customers’ success.” Citing the pending litigation, Kramer said Icertis could not address the merits in detail but disputed “the allegations and characterizations set forth in the Complaint” and looked “forward to presenting the case in court.”3Artificial Lawyer. Icertis Sued Over Alleged Failings of CMS Implementation
Publicly available sources do not disclose how the case was ultimately resolved, whether by settlement, dismissal, or trial. The complaint did not attach the underlying contracts, so the specific contractual language governing deliverables and milestones is not part of the public record.
Peterson v. Icertis
The other publicly docketed matter is unrelated. Richard Peterson filed an employment discrimination suit against Icertis in the Circuit Court of Loudoun County, Virginia. Icertis removed the case to the U.S. District Court for the Eastern District of Virginia in March 2025, where it was assigned case number 1:25-cv-00542.4PACER Monitor. Peterson v. Icertis, Inc.
Icertis moved to dismiss for failure to state a claim in April 2025. District Judge Patricia Tolliver Giles denied the motion in June 2025, and the case was stayed in August 2025. Before the stay lifted, Peterson filed a stipulation of dismissal, and Judge Giles signed an order dismissing the case with prejudice on October 20, 2025. Dismissal with prejudice bars refiling. The docket does not disclose the terms or reasons behind the stipulated dismissal.4PACER Monitor. Peterson v. Icertis, Inc.
Why the Change Healthcare Case Drew Attention
The CHC lawsuit was widely discussed in the contract lifecycle management industry because it laid out, in concrete numbers, what a failed enterprise software implementation looks like from the customer’s side. Industry commentary on the case pointed out that termination alone is often an inadequate remedy when a months-long, multimillion-dollar implementation collapses, since the customer is left with no working system and has to begin the whole procurement and setup process again.2Contract Nerds. Three Ways to Improve Your Next CMS Implementation Agreement — Lessons From the Icertis Lawsuit
That is the practical value of the complaint even without a public outcome: it identifies the specific contractual points, from capability representations made during sales to training hours, deliverable lists, staffing standards, and subcontractor approval, where an implementation deal can go wrong and where a buyer may want harder language than a standard vendor template provides.