Paul R. Wallace, Judge.

Submitted: May 5, 2022

Upon Defendant Trimble Inc.'s Motion to Dismiss Count II of the Complaint, GRANTED.

Patricia L. Enerio, Esquire, Jamie Brown, Esquire, HEYMAN ENERIO GATTUSO &HIRZEL, Wilmington, Delaware; Gerry Silver, Esquire (argued), SULLIVAN &WORCESTER LLP, New York, New York, Attorneys for Plaintiff Outbox Systems, Inc. d/b/a Simplus.

Steven T. Margolin, Esquire, Samuel L. Moultrie, Esquire, GREENBERG TRAURIG, LLP, Wilmington, Delaware, Attorneys for Defendant Trimble Inc.

MEMORANDUM OPINION AND ORDER

Paul R. Wallace, Judge.

The Court here resolves Defendant Trimble Inc.'s Motion to Dismiss Count II of the Complaint alleging that Outbox Systems, Inc. d/b/a Simplus failed to state a claim for account stated and that Count II is impermissibly duplicative of Count I. For the reasons set forth below, that motion is GRANTED.

I. FACTUAL AND PROCEDURAL BACKGROUND

This dispute arises from Defendant Trimble Inc.'s alleged breach of certain technology consulting agreements between itself and Plaintiff Outbox Systems, Inc. d/b/a/ Simplus ("Simplus").

Simplus is a corporation organized under the laws of Delaware, with its principal place of business in Salt Lake City, Utah. Trimble is also a corporation organized under the laws of Delaware, but its principal place of business is Sunnyvale, California. Trimble provides software and hardware services to customers in industries such as agriculture, construction, geospatial and transportation, and logistics.

On April 1, 2020, the parties executed a Master Consulting Services Agreement ("MSA") under which Simplus was to provide technology consulting services to Trimble. The MSA provided that services would be performed pursuant to statements of work ("SOWs") entered into by the parties. The MSA stated that "[u]nless otherwise expressly specified in a [SOW], (i) all payments are due in U.S. Dollars within 45 days of Trimble's receipt of an undisputed invoice."

The parties entered into three separate SOWs between November 9 and December 14, 2020. Each SOW provided for billing by Simplus on a "time and materials" basis using the hourly rates set forth therein.

Simplus says it performed its obligations in accordance with the MSA and SOWs and invoiced Trimble as it completed work. But Trimble allegedly failed to perform its duties under the same. For instance, Trimble was obligated to provide Simplus with certain "Product Bundles" at the outset of a project. These Product Bundles relate to particular offerings and pricing Trimble would be making available to its customers for its building, construction, and architectural product lines. Without these Product Bundles, Simplus would be unable to complete a design and build as requested; that meant Simplus's builds couldn't then be fully integrated.

Nevertheless, Simplus delivered its builds to Trimble using what information Trimble did provide, and these builds were at least "functional from a business perspective." Thereafter, Trimble decided to halt the project and, in August 2021, instructed Simplus to stop its efforts because the work was incomplete. Simplus alleges in its Complaint that the work wasn't complete because Trimble failed to perform its contractual obligations.

Simplus brought this action alleging Trimble's failure to pay invoices that Simplus sent for the work it had performed. According to Simplus, Trimble never expressly disputed any of Simplus's invoices. Simplus sent a total of seventeen invoices from June 16, 2021, to August 19, 2021. They added up to $2,132,348.98. To date, Trimble hasn't paid even one of these invoices. Simplus drew claims in in its complaint for: (i) breach of contract; (ii) account stated; and, in the alternative, (iii) unjust enrichment.

The first claim alleges Trimble breached the MSA and SOWs by failing to pay Simplus for its services invoiced thereunder. The second claim reads (i) that "[a]n account existed as between Simplus and Trimble"; (ii) that Trimble "failed to pay Simplus the total amount due of $2,132,348.98 on outstanding invoices"; and (iii) that "Trimble never made timely objection to the particular invoices as billed and/or account stated, never disputed the amount of any invoice, and did not timely dispute its requirement to pay any particular invoice." Finally, the unjust enrichment claim alleges that Trimble's failure to pay for Simplus's services has conferred an unearned and undeserved benefit upon Trimble, which it would be against equity and good conscience for Trimble to retain.

Trimble moved to strike Simplus's demand for an affidavit of defense under 10 Del. C. § 3901 and to dismiss Count II of the Complaint. Simplus agreed to withdraw its demand for an affidavit of defense-mooting that issue and leaving the viability of Count II as the only point of dispute. At bottom, Trimble's Motion poses two questions: (i) whether Simplus pleaded facts sufficient to support an account stated claim; and (ii) whether the account stated claim is impermissibly duplicative of Simplus's breach-of-contract claim.

II. STANDARD OF REVIEW

A party may move to dismiss under this Court's Civil Rule 12(b)(6) for failure to state a claim upon which relief can be granted. In resolving a 12(b)(6) motion, the Court (1) accepts as true all well-pleaded factual allegations in the complaint; (2) credits vague allegations if they give the opposing party notice of the claim; (3) draws all reasonable factual inferences in favor of the non-movant; and (4) denies dismissal if recovery on the claim is reasonably conceivable. So dismissal is inappropriate unless "under no reasonable interpretation of the facts alleged could the complaint state a claim for which relief might be granted."

"Generally, matters outside the pleadings should not be considered in ruling on a motion to dismiss." But the Court might consider documents or exhibits outside the pleadings when they are "integral to a . . . claim and incorporated into the complaint."

III. PARTIES' CONTENTIONS

According to Trimble, Simplus has failed to adequately plead even one necessary element of an account stated claim. Trimble says that the Complaint contains no allegations of an agreement constituting an "account" being created after any debt was incurred. Instead, says Trimble, the Complaint merely alleges that the parties entered into a written agreement and that invoices were subsequently sent to Trimble for services allegedly rendered. It further argues that there are no factual allegations that Trimble stated or admitted to owing any specific sum to Simplus on the reputed account, much less that Trimble made this admission "after the original account or debt was created." Finally, Trimble insists the account stated claim is "entirely duplicative of [Simplus's] breach of contract claim."

In Simplus's view, Count II should not be dismissed because it has pleaded factual allegations sufficient for an account stated claim. Specifically, it contends that the invoices sent to Trimble constituted a then-existing debt, and that Trimble failed to object to the invoices within a reasonable time. These facts are sufficient to plead that Trimble assented to owing a specific sum or that it agreed to a past debt, says Simplus, because "allegations of a 'failure to object to an invoice within a reasonable time can constitute the assent necessary for estoppel by account stated.'" In other words, Simplus urges it does not need to plead that Trimble expressly assented or admitted to owing a certain amount.

During argument, the Court questioned the practical effect of the account stated claim in light of the breach-of-contract claim. Simplus explained the claims are not redundant because "you don't have to prove all the elements of a breach of contract on an account-stated claim." In other words, under its account stated theory, Simplus contends it does not have to show performance, breach, or "get into every nitty-gritty" of the complicated MSA details at issue in this case.

IV. DISCUSSION

For any number of reasons, Simplus can't-from these parties' written agreements and the facts alleged-formulate an account stated claim that can stand under Delaware law. First, Simplus fails to state a claim for account stated because there seems to have been no recognizable "account" formed and there is nothing in Simplus's pleading that could reasonably support a read that Trimble stated or admitted to owing any specific sum on an "account"-if one had existed. Second, the account stated claim, in these circumstances, impermissibly duplicates Simplus's breach-of-contract claim both as to the substance of the alleged wrong complained-of and the wholly identical damages sought. Third-and perhaps the Court should have led with this-the account stated claim attempts to circumvent the parties' contractual arrangements in a way antithetical to bedrock Delaware contract law. Plainly, the account stated claim can't survive.

A. History of Account Stated Claims.

"Account" is a common law form of action, defined as an "unsettled claim or demand by one person against another based upon a transaction creating a debt and creditor relation between the parties which is usually but not necessarily represented by an ex parte record kept by one or both of them." An account stated claim is understood as a type of contract claim. As one court explains, "an action for 'account stated' still sounds in contract just like an action for quasi-contract or unjust enrichment, and is no more 'independent' from contract actions generally than a negligence action is independent of tort actions generally." In other words, an account stated is "just a variety of contract."

To make a prima facie account stated claim, Delaware law requires a plaintiff to allege the following: "(1) an account existed between the parties; (2) the defendant stated or admitted to owing a specific sum on the account to the plaintiff; and (3) the defendant made this admission after the original account or debt was created."Beyond that, however, Delaware jurisprudence is limited in this space. As such, a general overview of account stated claims is helpful.

1. How Relevant Treatises Explain Account Stated Claims.

Williston on Contracts explains that "[a]n 'account stated' is a promise by the debtor to pay a stated sum of money which the parties have agreed upon as the amount due.... [An account stated] may be implied from the retention of an account rendered for an unreasonable period of time without objection and from the surrounding circumstances." But, a promise "to pay a sum of money based on an antecedent transaction will not by itself create an account stated, even though the promise is supported by consideration and is binding; rather there must be an antecedent debt to which the promise relates and which the promise 'states' or 'restates.'"

According to Williston, the "essential elements of an account stated are (1) previous transactions between the parties establishing the relationship of debtor and creditor; (2) an agreement between the parties, express or implied, on the amount due from the debtor to the creditor; and (3) a promise by the debtor, express or implied, to pay the amount due." "The basic requirement of an account stated is that an exact and definite balance must be struck as to which both the creditor and debtor assent."

So, as a general principle, unequivocal assent between the parties is paramount in establishing an account stated claim. Per the Restatement (Second) of Contracts, "assent may be inferred from [] conduct . . . [and] retention of the statement for an unreasonably long time is a manifestation of [] assent. How long a time is unreasonable is a question of fact to be answered in light of all the circumstances."

And, Woolley on Delaware Practice tells us:

An account is an agreement by both parties that all items are true. It changes the character of the original debt and is a new contract or undertaking, . . . No recovery can be had under an account stated, unless there is evidence that there was an account stated between the parties, in which the person said to be charged, stated, or admitted a certain sum to be due and owing from him to the other. In the absence of such proof no recovery can be had under the count for account stated.

2. Delaware Courts' Treatment of Account Stated Claims.

There are few Delaware cases that discuss account stated claims, much less recent Delaware cases.

In 1926, this Court spoke of an account stated claim in Baliezewski v. Putzcus. In that case, the plaintiff brought an action before a Justice of the Peace, where the claim was for the sale and delivery of goods. The defendant appealed the entry of judgment to this Court, and the plaintiff framed his claim here as one of "account stated." The defendant sought to strike the claim because it set out a different cause of action than that tried before the Justice of the Peace. Citing earlier Delaware cases, the Beliezewski court noted "[a]n account stated is an agreement, by both parties, that all the items are true. It changes the character of the original debt, and is a new contract or undertaking." Moreover, "[a]n account stated alters the character of the original indebtedness, and is itself in the nature of a new promise or undertaking, and raises a new cause of action between the parties."Relying on these principles, the Court held that the action before the Justice of the Peace was a "different cause of action" than the account stated claim raised by the plaintiff on appeal. In other words, this Court's actual holding was that the account stated claim argued on appeal was an entirely different claim than the breach-of-contract count championed below. And so, the Court had little reason to-and did not-definitively resolve what might be needed to satisfy the elements of an account stated claim under Delaware law.

Much more recently, in 2019, this Court was presented with a motion to dismiss an account stated claim in Sparebank 1 SR-Bank ASA v. Wilhelm Maass GMBH. The defendant ordered, received, and failed to pay for ten shipments of custom steel components from a manufacturer that later filed for bankruptcy. The Sparebank plaintiff purchased that manufacturer's claims against the defendant from the company's bankruptcy estate. The arrangement between the defendant customer and manufacturer was relatively straightforward. The defendant would place orders for steel products and the manufacturer would produce and ship the ordered products. The manufacturer then would send the defendant invoices. The defendant allegedly never paid the invoices and claimed it had never placed the orders at issue.

The defendant argued the plaintiff failed to plead facts to support an account stated claim because the complaint was devoid of facts that the defendant stated or admitted to owing a specific sum on the account to the plaintiff. The plaintiff answered that discovery would reveal the defendant acknowledged at some point an obligation to pay a past debt. The Court held that the complaint contained no allegations that the defendant stated or admitted to owing a specific sum on the account, and dismissed the claim.

In Citibank (South Dakota) N.A. v. Santiago, the Court of Common Pleas was also resolving a motion to dismiss an account stated claim. There, the plaintiff brought a number of claims against the defendant that centered around non-payment of credit card statements. The complaint sufficiently alleged a breach-of-contract claim; namely, (1) a contract existed between the parties for a specific amount, (2) defendant breached by failing to pay the amounts due, and (3) as a result, plaintiff suffered damages. The court, on deciding the account stated claim, noted the plaintiff merely alleged the defendant under "the account" was required to make prompt and regular payments. The court granted the motion to dismiss because the complaint failed to plead facts that the defendant stated or admitted to owing a specific sum on the account to the plaintiff.

Finally, the United States District Court for the District of Delaware discussed an account stated claim in CP Printing Ltd. v. Glitterati Inc. There, the plaintiff moved for summary judgment on breach-of-contract and related claims-none of which were an account stated claim. The plaintiff claimed to have sold defendant approximately $228,202.24 in printed books. But the defendant paid the balance only in part, leaving a substantial amount outstanding. The plaintiff argued the "invoices delivered to [defendant] . . . operate[d] as account stated [sic]." In a brief discussion citing just a general principle from Williston-not Delaware law-the federal court noted that "[w]hile the failure to object to an invoice within a reasonable time can constitute the assent necessary for estoppel by account stated, what constitutes a 'reasonable time for the purposes of this rule is generally a question for the jury.'" "As a result, a debtor's 'silence with respect to . . . invoices received is not so conclusive as to require a directed verdict against it.'"Accordingly, the district court denied the plaintiff's motion for summary judgment.

In sum, Delaware state courts have rarely dealt with account stated claims, and when they have, the factual recitations were often not very detailed. But what the Court can draw from these cases is that a plaintiff must plead facts that the defendant stated or admitted to owing a specific sum on an account to plaintiff. Further, the common law doctrine and various treatises make clear that the defendant must make such admission after the original account or debt was created. But no court, applying Delaware law, has expressed with clarity: (1) whether the "account" can be culled from a contractual relationship like the one here?; and (2) if so, to satisfy the elements of a Delaware account stated claim, whether such admission must be express or might be implied? As to the first question, it cannot. As to the second, silence is not enough.

B. Dismissal of Simplus'S Account Stated Claim is Warranted.

1. Simplus Failed to Plead Facts Sufficient to Support a Delaware Account Stated Claim.

The basic elements of an account stated claim are the same across jurisdictions, but courts differ on certain specifics, including the nature of the assent necessary to plead an account stated claim. To reiterate, Delaware state courts have defined the requirements of an account stated as follows: "(1) an account existed between the parties; (2) the defendant stated or admitted to owing a specific sum on the account to the plaintiff; and (3) the defendant made this admission after the original account or debt was created." Some other courts suggest that express assent is not always necessary-namely, "the failure to object to an invoice within a reasonable time can constitute the assent necessary for estoppel by account stated."

Simplus insists Trimble's failure to object to its invoices within a reasonable time is "sufficient to plead assent or agreement to a past debt, and therefore Trimble's motion to dismiss the account stated claim should be denied."

Trimble counters that Delaware authority is devoid of this implied assent principle for account stated claims, and that Simplus's reliance on CP Printing, a federal district court case, is misplaced because that case did not involve an actual account stated claim-or, it appears, application of Delaware law.

Just so. Delaware case law does not support allowance of Simplus's implied assent postulate at all, much less in these circumstances.

The only Delaware case that suggests silent assent might be sufficient for an account stated claim is Baliezewski v. Putzcus. In that case, the Court noted that "[a]n account stated . . . exists where the accounts between two parties have been examined and a balance is found in favor of one of the parties, and the party against whom the balance is found either expressly or impliedly agreed to pay such balance found to be due." But Baliezewski's thumbnail sketch of an account stated claim seems a bit too hastily and ill-drawn. Of particular note, Baliezewski cites to no authority to support its implied-agreement proposition. Nor did Baliezewski actually adjudicate the merits of an account stated claim. So, it is unsurprising that not one subsequent Delaware state court case addressing account stated claims cites Baliezewski. So the Court looks to those more recent Delaware cases that have adjudicated account stated claims.

In Sparebank 1 SR-Bank ASA v. Wilhelm Maass GBMH, where unpaid invoices were at issue, the plaintiff insisted "that an account existed between the parties based on an express or implied agreement that [defendant] would pay for [specified orders of steel]." This Court explained dismissal was appropriate for the account stated claim because the complaint "makes no allegations that [defendant] stated or admitted to owing a specific sum," and dismissed the account stated claim. The same occurred in Citibank (South Dakota) N.A. v. Santiago, where the Court of Common Pleas dismissed an account stated claim because the complaint contained no factual allegations that the defendant stated or admitted to owing a specific sum.

In Chrysler Corp. v. Airtemp Corp., this Court, when discussing an account stated claim, turned to Woolley: "No recovery can be had under an account stated, unless there was an account agreed upon between the parties, by which the person said to be charged, stated, or admitted a certain sum to be due and owing." Woolley, an authority oft-cited when explaining such arcana of Delaware law, says nothing to suggest that silent or implied assent is sufficient for an account stated claim.

Simplus turns to one federal district court case, CP Printing, that does suggest that in certain commercial contexts the failure to object to invoices within a reasonable time might constitute the assent necessary for estoppel by account stated. But, that case actually contained three different counts: breach-of-contract, quantum meruit, and unjust enrichment-not an account stated claim. The account stated was addressed only because the plaintiff raised it in its briefing. And the federal trial court's succinct fact-bereft order denying summary judgment says nothing of Delaware law.

Those courts that do recognize implied assent as sufficient tend to clearly say so when limning the elements of an account stated. Yet, other than Baliezewski's allusion to such, Delaware law is devoid of such language.

Why? Because Delaware law requires an express agreement to the incurred debt between the parties for an account stated claim to survive and prevail. In turn, to have any chance of withstanding a motion to dismiss in this Court, one bringing an account stated claim would have to establish, at the very least, that the purported account debtor expressly agreed to pay the certain sum at issue. Failure to object to contract-borne invoices "within a reasonable time" isn't enough.

Here, Simplus relies wholly on the implied assent principle and-on that failure alone-falls short in its pleading of facts sufficient for any viable account stated claim here. The Complaint contains no facts alleging Trimble expressly stated or admitted to owing a specific sum on an account, or that Trimble made such an admission after the original debt (i.e., the invoices) was created. Accordingly, Simplus has failed to plead facts sufficient to support an account stated claim here, and Trimble's motion to dismiss for failure to state a claim must be granted for that reason. But even if the pleaded facts somehow aligned to a reasonably conceivable account stated claim, the Court still would be wary of allowing such to stand next to a well-pleaded breach-of-contract count.

2. The Account Stated Claim is Impermissibly Duplicative.

No doubt, Delaware's trial courts have shown growing antipathy toward both bootstrapped and needlessly duplicative claims in what are otherwise straightforward breach-of-contract cases. Sure, there is some utility and real need for pleading in the alternative under the right circumstances-for instance, where the complaining party expresses some palpable doubt as to a written contract's validity or enforceability. Where so, that need should be easily discernable in the complaint. Where not, the Court might rightly dismiss as completely duplicative or otherwise needless a pendant claim in favor of the well-pleaded breach-of-contract count. Doing so-as explained further below-keeps fidelity to Delaware's pro-contractarian ethos.

Trimble contends the account stated claim is "entirely duplicative" of Simplus's breach-of-contract claim. It is.

Simplus grounds both its breach-of-contract claim and its account stated claim on Trimble's alleged breach of the MSA and SOWs for failure to pay invoices.Put simply, both counts are based on precisely the same facts and focus precisely on the same alleged failure to pay invoices-which failure is expressly governed by the of-contract claim in Schuss, which were not duplicative because, though the claims shared a common nucleus of operative facts, the claims each "depend[ed] on additional facts as well"). MSA and SOWs. And there is nothing in Trimble's pleadings that suggests any doubt as to the validity or enforceability of the express contract that controls its relationship with Simplus. So, the account stated claim is subject to dismissal as impermissibly duplicative of the breach-of-contract claim because the claims are based completely on the same facts.

Simplus also pleads the same damages for both counts. The breach-of-contract claim takes aim at the unpaid invoices. And citing just those, Simplus complains it "has suffered damages in an amount to be determined at trial, but believed to be not less than $2,132,348.98, plus interest and costs of collection."The account stated claim also takes aim at the unpaid invoices-"Trimble failed to pay Simplus the total amount due of $2,132,348.98 on outstanding invoices."And, as a result, says Simplus, it "has suffered damages in an amount to be determined at trial, but believed to be not less than $2,132,348.98, plus interest and costs of collection." When as here such a pendant count does no more than reiterate the facts alleged or damages sought via the well-pleaded primary breach-of-contract count, that claim will be dismissed as impermissibly duplicative or worse-as with an account stated claim like that brought here-antagonistic to the parties' written agreement.

3. An Account Stated Claim Can't Be Used to Purloin New Contract Rights.

The foregoing reveals a more fundamental concern with Simplus's account stated claim. During argument, Simplus posited that its account stated claim would allow it to recover damages without "hav[ing] to prove all the elements of a breach of contract"-in other words, Simplus believes it could recover with no regard or reference to performance, breach, or the "nitty-gritty" of the parties' contractual arrangement. Given this explanation, it is no wonder the account stated claim duplicates both the substance and damages of the breach-of-contract claim. In essence, the account stated claim was intended as a short-cut for obtaining contract damages.

Delaware law will not tolerate use of an account stated claim in this manner. "[W]ith very limited exceptions, our courts will enforce the contractual scheme that the parties have arrived at through their own self-ordering, both in recognition of a right to self-order and to promote certainty of obligations and benefits.""Upholding freedom of contract is a fundamental policy of this State."Delaware's contractarian principles have guided its courts in developing a nuanced jurisprudence for the analysis and enforcement of contracts.

A well-settled and basic tenet of Delaware contract law is that "a party may not come to the court to enforce a contractual right it did not obtain for itself at the negotiating table." Neither will courts "rewrite contracts to read in terms that [parties] could have, but did not, obtain at the bargaining table." Indeed, our courts are "most chary about implying a contractual protection when the contract could easily have been drafted to expressly provide for it." "This is because a court's role in interpreting contracts is to effectuate the parties' intent. For a court to read into an agreement a contract term that was [not included] . . . would be to create new contract rights, liabilities and duties to which the parties had not assented in contravention of that settled role."

These principles are dutifully adhered to and hold especially true for sophisticated parties engaged in arms-length negotiations. Our law "presumes parties are bound by the language of the agreement they negotiated" and "respect[s] the ability of sophisticated businesses . . . to make their own judgments about the risk they should bear" and the protections they should incorporate.

This Court regularly sees language in the service agreement contracts forged by sophisticated parties that details the specifics of their invoicing, payment, "deemed approved," and invoice resolution process. Simplus's and Trimble's MSA has no such language. And the Court cannot allow it to be effectively added thereto via some conjured account stated claim.

Speaking of just such a circumstance recently, one court noted "not every debt . . . can form the basis of an account stated, particularly when it is being used as a substitute for an action of debt upon a contract involving a contractually specified sum, because a creditor under these circumstances is not required to resort to a new contract to collect such a debt." Yet, through the attempted account stated claim, either a "new contract" or, at very least, newly engrafted contract rights are precisely what Simplus attempts to impose in the parties' already self-ordered relationship. As another court has explained, that cannot happen: "a claim for an account stated may not be utilized simply as another means to attempt to collect under a disputed contract."

If Simplus seeks to recover damages for unpaid invoices under its contract with Trimble, then it's just going to have get into the "nitty-gritty" of its performance thereunder, Trimble's alleged breach, and the possible claims and defenses afforded its adversary under Delaware contract law. There is no shortcut to judgment via an account stated route here.

V. CONCLUSION

Among other failures, Simplus has wholly relied on an implied assent principle to devise its account stated claim. In turn, it has failed to plead a reasonably conceivable account stated claim under Delaware law. What's more, Simplus's account stated claim is entirely duplicative of its breach-of-contract claim-both in the facts pleaded to establish each and in the damages sought thereunder. Finally, an account stated claim may not be used as a vehicle to recover contract damages without proving a breach-of-contract claim. This is a situation where redundancy should not only be avoided, but is intolerable.

Accordingly, Trimble's Motion to Dismiss Count II is GRANTED.

IT IS SO ORDERED.