Searching over 5,500,000 cases.


searching
Buy This Entire Record For $7.95

Download the entire decision to receive the complete text, official citation,
docket number, dissents and concurrences, and footnotes for this case.

Learn more about what you receive with purchase of this case.

SUTTER INSURANCE CO. v. APPLIED SYSTEMS

April 18, 2005.

SUTTER INSURANCE CO., Plaintiff,
v.
APPLIED SYSTEMS, INC., Defendant.



The opinion of the court was delivered by: MATTHEW KENNELLY, District Judge

MEMORANDUM OPINION AND ORDER

In this diversity suit, the plaintiff, Sutter Insurance Company, contracted with the defendant, Applied Systems, Inc., to purchase computer software. Sutter claimed that the software did not perform as represented and sued to recover the money it had paid, a total of $492,811 ($360,000 for the software, and $132,811 for service and maintenance). Applied counterclaimed to recover expenses it had incurred in developing further additions to the software that Sutter refused to take. After a bench trial, the Court ruled against Sutter on its claim and against Applied on its counterclaim — essentially leaving the parties where they were before suit was filed. Sutter Ins. Co. v. Applied Systems, Inc., No. 02 C 5849, 2004 WL 524434 (N.D. Ill. Mar. 11, 2004) ("Sutter I").

Sutter appealed from the Court's rejection of its claims, but Applied did not appeal from the rejection of its counterclaim. The Seventh Circuit vacated this Court's decision and remanded for further proceedings. Sutter Ins. Co. v. Applied Systems, Inc., 393 F.3d 722 (7th Cir. 2004) ("Sutter II"). On remand, the Court requested additional briefs from the parties. This Court's prior ruling

  Before revisiting the merits, a bit of background is necessary.*fn1 The trial involved (in addition to the counterclaim) Sutter's claims for breach of contract and under the Illinois Consumer Fraud Act and a parallel California statute. Sutter is a California insurance company that needed to purchase new software to produce and service its insurance policies. Applied is an Illinois producer of software.

  Sutter's insurance business included both "direct bill" policies, issued and billed for by Sutter itself, and "agency bill" policies, issued through agents, who collected premium payments from their various clients and remitted them to Sutter in bulk. For the agency bill policies, Sutter required a mechanism to bill the agents properly, account for partial payments, age accounts receivable, and report amounts paid and due on a policy-by-policy basis — functions that we will refer to generically as "agency billing."

  As discussed more fully in this Court's original ruling, the contract provided that Sutter would purchase, among other things, the software and services specified in Schedule A to the contract. Schedule A listed the features and functions of the "Diamond System," Applied's base software product. The purchase price, described in Schedule F, was $300,000 for the base system, plus $60,000 for the software for the first line of business that Sutter would convert to the new system — its California preferred homeowner's insurance line of business. Software for additional lines of business would likewise cost $60,000 per line. Of the $300,000 for the base system, $75,000 was paid upon signing of the contract, another $75,000 on acceptance of an implementation plan, and the final $150,000 on the date of first delivery of the system for testing. The $60,000 for the software for the California preferred homeowner's line was due on the date that software was accepted.

  A significant portion of Sutter's business involved agency bill policies, and as a result Applied's software was, relatively speaking, worthless to Sutter if it did not support agency billing. In our original ruling, the Court found that the features and functions of the Diamond System described in Schedule A to the contract included features that Sutter "reasonably understood . . . to encompass the agency billing, accounting, reconciliation, and reporting functions" that it required. Sutter I, 2004 WL 524434, *2. This proved not to be the case. As the Court found, "Sutter eventually learned that the software [for its other lines of business] did not include the agency billing and reconciliation functions that it had expected." Id., *5. Perhaps more importantly for present purposes, it "eventually became clear that the Diamond System did not support the type of agency billing reconciliation functions that Sutter had expected," Id., and that Schedule A represented were included and supported. Unfortunately, Sutter did not learn this until much later. The reason is that the California preferred homeowner's line, the first line of business for which software was installed, was a direct bill line of business. It was not until later, when the software for what Sutter calls its "Tier 1" lines was being developed, that Sutter came to learn that the base system did not include or support agency billing. By then, however, Sutter had already paid for the Diamond System and the preferred homeowner's software.

  Once it learned that the agency billing functions that it required were missing from Applied's software, Sutter terminated its relationship with Applied, told Applied to stop work on the Tier 1 software, and (later) demanded its money back. Id., *5-6. Sutter kept using the preferred homeowner's software, as it had no other alternative for that line of business, and Applied made no objection. Id., *6.

  The Court ruled that Sutter was not entitled to recover the money it had paid for the Diamond System and the California preferred homeowner's software. The Court determined that Sutter had failed to prove that Applied had breached the contract, specifically that it had failed to prove that this software was defective or failed to comply with Sutter's specifications. Id. On Allied's counterclaim to recover the expense it incurred in developing the Tier 1 software, the Court determined that this software did not conform to the specifications stated in Schedule A because it did not include or support agency billing and related functions. Id., *7. In short, the Court essentially concluded that the obligations to pay for the base system and for the Tier 1 lines were independent of each other, and that the failure of the Tier 1 lines did not entitle Sutter to recover what it had paid for the base system.

  The decision on appeal

  On appeal, the Seventh Circuit stated that our ruling appeared to be based on an inconsistency: "[i]t says on the one hand that Applied's inability to furnish Sutter with software capable of handling agency billing was not a breach of contract, but on the other hand that Applied's unsuccessful efforts to furnish such software [for the Tier 1 lines] did not conform to the specifications in Schedule A." Sutter II, 393 F.3d at 725. The court went on to say that in ruling for Applied on Sutter's claim, this Court "did not explain how Applied's interpretation could be squared with either the language of Schedule A or the extrinsic evidence that had been placed in evidence at the trial." Id. There was good reason, the Seventh Circuit stated, to doubt Applied's interpretation of the contract: "it would not make sense for Sutter to pay $360,000 for software good for only a minor line of business," i.e., the preferred homeowner's line. Id. at 725-26. The terms of contract, according to the Seventh Circuit, "support an inference that Applied was committing itself to adapt the Diamond System to all of Sutter's lines. . . ." Id. at 726. The court found rather implausible the possibility that Sutter had committed to pay $360,000 for "a pig in a poke" and suggested that this was good reason to reject Applied's proposed interpretation of the contract. Id. at 726. "The language [of the contract] as a whole favors Sutter, not Applied. Sutter's interpretation fits both the language of the contract and the contract's commercial setting better than Applied's does." Id. But because the Seventh Circuit was uncertain how this Court had reached its conclusion, it remanded the case for further proceedings. Id. at 726-27.

  Discussion*fn2

  We begin by clearing up an apparent misunderstanding of one aspect of the Court's ruling. The Seventh Circuit wondered why extrinsic evidence of the parties' dealings and intentions prior to signing the contract had been introduced without objection, and why this Court had, apparently, ignored that evidence in interpreting the contract. Sutter II, 393 F.3d at 725. The answers to both questions are simple. The extrinsic evidence was introduced, and no objection was made, because Sutter had made fraud-in-the-inducement claims under the consumer fraud statutes of Illinois and California. The parol evidence rule did not govern those claims — or at least no argument was made that it did. But the admission of that evidence on the fraud claims did not make its consideration proper in construing the contract for purposes of the breach of contract claim. The Court did not then and does not now rely on the extrinsic evidence in determining that claim.

  On remand, Sutter urges the Court to adopt the construction of the contract suggested by the Court of Appeals. Applied objects, contending that the issue was waived at the trial level. The Court disagrees. Sutter's contention throughout this litigation has been that the defects, including the lack of an agency billing function, infected Applied's software. In its complaint, Sutter alleged that "Applied breached the [contract] by failing to provide software that would conform to and perform ...


Buy This Entire Record For $7.95

Download the entire decision to receive the complete text, official citation,
docket number, dissents and concurrences, and footnotes for this case.

Learn more about what you receive with purchase of this case.